Digital Archive Batch Ingest Guide
Batch ingest overview
What is batch ingest?
Batch ingest is a method by which users can submit multiple content objects and their metadata to the OCLC Digital Archive at one time. Users mail content objects and their metadata to OCLC on electronic media, such as CD or tape. The metadata is in the form of one or more XML files that are compliant with the Metadata Encoding & Transmission Standard (METS). The metadata and other files constitute the Submission Information Package (SIP).
The Batch Ingest service requires use of the OCLC Submission Builder to create SIPs. The Submission Builder takes the following information and converts it into a SIP:
- A tab-delimited file of metadata, called the DA record file
- A manifest (list) of content object file names
- Some user-keyed data
When OCLC receives the batch of content objects and SIP(s), it is automatically submitted to the Digital Archive via the batch ingest process.
Definitions
Batch. A set of content objects and associated metadata from one institution received by OCLC at one time.
Content owner/custodian. The institution that owns or has custody of the content. Content objects in the Digital Archive are associated with the OCLC symbol of the content owner/custodian.
DA record file. A file containing the metadata elements used to create Digital Archive records for the content objects you batch ingest.
Log. A text file containing a list of the Submission Builder's transactions.
Manifest. A list of the names of the files that constitute the content objects of the SIP.
METS (Metadata Encoding & Transmission Standard). A standard for encoding descriptive, administrative, and structural metadata about content objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium. For more information, see
http://www.loc.gov/standards/mets.
SIP (Submission Information Package). The metadata and other files that describe the content objects in the batch. Used to ingest objects into the Digital Archive.
Submitter. The institution responsible for creating the SIP and submitting the batch to OCLC.
Tracking Identifier. User-assigned number identifying each piece of media in the batch.
Manage objects in the Digital Archive
Batch ingest users have access to the Digital Archive Administration Module and Digital Archive records in Connexion through a permission added to their OCLC cataloging authorization. The Administration Module allows you to:
- Configure access to objects and their level of preservation
- Manage other administrative properties of the objects
- View a brief display of their Digital Archive records
- View the objects themselves and reports associated with them
The Digital Archive in Connexion allows you to:
- Update and delete the metadata that was created for the object during the batch process
- Delete objects that were batch loaded from the archive
- Disseminate batch loaded objects
- View the objects themselves and reports associated with them
The Administration Module is located at
http://digitalarchive.oclc.org/admin/.
The documentation for the Administration Module (along with the other Digital Archive documentation) is located at
http://www.oclc.org/support/documentation/digitalarchive/.
Important: content objects and files
A content object is composed of one or more files. You can batch ingest any type of file.
Batch ingest process
| |
Action |
| 1 |
Determine the content objects you want to submit to the Digital Archive. |
| 2 |
Identify or create media tracking identifiers. |
| 3 |
Determine if the manifest will be a separate file or included in the Digital Archive record metadata file(s).
If the DA record file does not include filenames, create a manifest (a text file of filenames of content objects). One manifest must exist for each DA record file. |
| 4 |
Create the DA record file: a tab-delimited text file of metadata (include filenames of content objects if there is no manifest). |
| 5 |
Use the OCLC Submission Builder software to create the Submission Information Package (SIP) for the content objects to be batch ingested. |
| 6 |
Copy the SIP and its content objects onto media (CD, LTO tape, etc.). |
| 7 |
Fill out tracking form (records number of SIPs and content objects in the batch being submitted). |
| 8 |
Label media. |
| 9 |
Mail media and tracking form to OCLC. |
| 10 |
OCLC receives media and:
- Ingests the batch into the Digital Archive
- Creates Digital Archive records for the objects based on the submitted DA record file
- Generates reports documenting the ingest process
|
| 11 |
OCLC sends an e-mail confirming successful submission or explaining why submission failed. |
| 12 |
Log on to the Digital Archive Administration Module to organize content objects (set permissions, change copyright statement, view reports, etc.). |
| 13 |
Optional. Log on to the Digital Archive (Connexion) and update the metadata in the records created from the batchloading process. |
back to top
Before you begin
Software required for batch ingesting
To batch ingest your content objects, you need two programs:
- A small plug-in program, Sun Microsystem's Java 2 Runtime Environment (JRE) is required in order to run the OCLC Submission Builder.
- The OCLC Submission Builder is the software used to create Submission Information Packages (SIPs).
System requirements
The system requirements for the Submission Builder are below.
| Requirement |
Specification |
| Processor |
Intel Pentium III, 864 MHz or greater |
| Operating system |
Windows 2000, NT 4.0, or XP |
| Memory |
256 MB RAM or more |
| Hard drive disk space |
8.5 MB or more |
| Display |
1024 X 768 or higher |
| Internet access |
Required |
Download Java 2 platform
| |
Action |
| 1 |
Type this address in your browser's address bar:
http://java.sun.com/j2se/1.3/download.html
The Java 2 Platform, Standard Edition (J2SE) page appears. |
| 2 |
Click Download for the JRE Windows version you need (U.S. English only or all languages).
The Binary Code License Agreement page appears. |
| 3 |
Read the agreement.
Click Accept to accept its terms. |
| 4 |
On the Download page click Download j2re-1_3_1_06-windows-i586.exe. |
| 5 |
On the File Download window click Save. |
| 6 |
On the Save As window click Save.
Save the download in your Program Files directory. |
| 7 |
On the Download Complete window click Open. |
| 8 |
The setup program appears.
Click Yes to agree to the license terms. |
| 9 |
The Choose Destination Location window appears.
If you have not already done so, choose your Program Files directory.
Click Next>. |
| 10 |
On the Select Browsers window choose your browser(s).
Click Next>.
The Java Platform installs. The setup program closes automatically. |
Install OCLC Submission Builder
| |
Action |
| 1 |
Open Windows Explorer and navigate to the directory in which you saved the setup.zip file.
Double-click setup.zip. |
| 2 |
On the WinZip window double-click setup.exe. |
| 3 |
On the Install window click OK. |
| 4 |
On the Setup window click Yes. |
| 5 |
On the Submission Builder Setup Wizard, click Next>. |
| 6 |
On the Select Destination Directory window, click Next>.
Choose your Program Files directory. |
| 7 |
On the Select Start Menu Folder window, make your selection.
Click Next>. |
| 8 |
On the Select Additional Tasks window, select the additional icons you want, if any.
Click Next>. |
| 9 |
On the Ready to Install window, click Install. |
| 10 |
The Submission Builder installs. On the final window click Finish. |
Create authorization group
After receiving the e-mail notification that Digital Archive privileges have been added to your OCLC cataloging authorization, follow the steps below to use the Digital Archive Administration Module to create an authorization group.
The authorizations you put in this group can access your content after you have ingested it into the Digital Archive.
Important: If you do not create an authorization group, your batch cannot be ingested.
| |
Action |
| 1 |
Log on to the Digital Archive Administration Module.
In your browser's address bar type:
http://digitalarchive.oclc.org/admin/
The Administration Module screen appears. |
| 2 |
Type your authorization and password.
Click Logon. |
| 3 |
The Authorization Groups tab appears.
At the top left of the tab, click Create New.
At the top right, the Authorization Group box now reads: New Authorization Group Name. |
| 4 |
The name you type must exactly follow this format (including capitalization and spaces):
[[OCLC symbol]] Batch Authorization Group
Example
KUK Batch Authorization Group |
| 5 |
Add authorizations.
In the Authorizations Not Included window, click an authorization you want to add to your Batch Authorization Group. Click the left arrow to move the authorization to the Authorizations Included window.
Remove authorizations.
In the Authorizations Included window, click an authorization you want to remove. Click the right arrow to move the authorization to the Authorizations Not Included window.
Click Cancel to undo all your edits. |
| 6 |
Click Save. |
More information on the administration module
See the Digital Archive Administration Module help system or the HTML and PDF user guides at:
http://www2.oclc.org/digitalpreservation/documentation/.
back to top
Metadata
Two kinds of metadata
Two kinds of metadata are required when creating a Submission Information Package (SIP):
- The manifest: a list of the names of the files that constitute the content objects.
- The Digital Archive record file: the metadata elements (from table below) that constitute the Digital Archive records that describe the content objects.
Two ways to organize metadata
There are two ways to organize metadata:
- Two files: One DA record file and one manifest file.
- One file: Instead of putting the filenames in the manifest, you can add them to the DA record file. See DA record file guidelines below.
General guidelines
- DA record and manifest files must be ASCII text files (TXT).
Important: Special characters (digraphs, diacritics, accents, etc.) are not accepted.
DA record file guidelines
- The DA record file is composed of rows of metadata elements, one row for each content object. Each row must be separated by a carriage return or a line feed.
- The DA record file is a tab-delimited file. Within each row, each metadata element must be separated from the others by a tab. Make sure tabs do not exist within metadata elements.
- Within each row, the metadata elements must be in the order listed in the metadata elements table below.
- Optional. In place of a separate manifest file, the DA record file can include the names of the files that constitute the objects in the SIP. In this case, the last value in each row is the filename. If the object is composed of more than one file, the last value in the row is a comma-delimited list of all the files that make up the content object.
- Each row of metadata contains 66 tabs (67 if filenames are included) and one carriage return. Important: All tabs must be present. Only required metadata elements must be present (see metadata elements table below).
Example row without filenames
Key: |=tab.
lat | | | Personal | "Huygens, Christiaan, 1629-1695" | Corporate | Smithsonian Institution. Libraries | | | | | | | | | | Created | 1999-03-23 | eng | | | | | | | | | | | | | | SMI | | Image Only | | | SIL4-1- | 41600261 | 2792527 | | | SMI | SIRIS | 563028 | Smithsonian Institution Libraries | | | | | | | | | | | | | | | | | | Systema Saturnium | Christiani Hvgenii ... Systema Satvrnivm | | [return or line feed]
Manifest guidelines
- Manifest files contain only object filenames (the filename may be preceded by the file's path).
- One filename per row. Separate each row by a carriage return or a line feed.
- No spacing or punctuation in manifest file
Example
SIL4-1.tif
SIL4-2.tif
Example with path
D:\data\images\tifs\SIL4-1.tif
D:\data\images\tifs\SIL4-2.tif
DA record elements
Important: The elements below are not currently accepted. If they are present in your DA record file, the system ignores them.
Note: Numbers in parenthesis are those of elements in the following metadata elements table.
- Fixity check date and status (30-31)
- Virus check date and status (66-67)
Required elements
Note: Numbers in parenthesis are those of elements in the following metadata elements table.
- Digital Archive record language (19)
- Object path (38)
- Title, Unqualified (64)
Metadata elements
| No. |
Element name |
Definition/Qualifiers |
Note |
| 1 |
Content Object Language |
Describes the language of the content object. |
This element must use the ISO639-2 encoding scheme. |
| 2 |
Content Description Qualifier |
Qualifiers:
Summary
Version
TimePeriod |
Use Version to differentiate between two objects with the same name where one version is the Access copy and the other is the Preservation copy. |
| 3 |
Content Description |
Describes the content of the object. |
|
| 4 |
Creator Qualifier |
Qualifiers:
Unqualified
Personal
Corporate
Conference |
If Qualifier left blank, system sets it to Unqualified in the Digital Archive. |
| 5 |
Creator |
An entity primarily responsible for making the content of the resource, such as an author, editor, or compiler. |
|
| 6 |
Creator Qualifier |
Qualifiers:
Unqualified
Personal
Corporate
Conference |
If Qualifier left blank, system sets it to Unqualified in the Digital Archive. |
| 7 |
Creator |
An entity primarily responsible for making the content of the resource, such as an author, editor, or compiler. |
|
| 8 |
Creator Qualifier |
Qualifiers:
Unqualified
Personal
Corporate
Conference |
If Qualifier left blank, system sets it to Unqualified in the Digital Archive. |
| 9 |
Creator |
An entity primarily responsible for making the content of the resource, such as an author, editor, or compiler. |
|
| 10 |
Current Operating System Name |
Name of the operating system needed to access the content object. |
Elements 10-16 describe a single environment. If the value of Current Operating System Name is present, then the value of Current Operating System Version must also be present. |
| 11 |
Current Operating System Version |
Version of the operating system needed to access the content object. |
Elements 10-16 describe a single environment. |
| 12 |
Current Operating System Location |
Location of the operating system needed to access the content object. |
Elements 10-16 describe a single environment. |
| 13 |
Current Rendering Application Name |
Name of the software required to access the object. |
Elements 10-16 describe a single environment. If the value of Current Rendering Application Name is present, then the value of Current Rendering Application Version must also be present. |
| 14 |
Current Rendering Application Version |
Version of the software required to access the object. |
Elements 10-16 describe a single environment. |
| 15 |
Current Resources |
Speed of the microprocessor needed to access the content object. |
Elements 10-16 describe a single environment. |
| 16 |
Current Resources Memory |
Amount of memory needed to access the content object. |
Elements 10-16 describe a single environment. |
| 17 |
Date Qualifier |
Qualifiers:
Created
Valid
Issued
Modified
Available
Unqualified |
If Qualifier left blank, system sets it to Unqualified in the Digital Archive. |
| 18 |
Date |
A date associated with an event in the life cycle of the resource. Typically, Date is associated with the creation or availability of the resource. |
The date must follow W3C-DTF formats:
yyyy-mm-dd
yyyy-mm
yyyy |
| 19 |
Digital Archive Record Language |
Language of the digital archive record. |
Required element. This element must use the ISO639-2 encoding scheme. |
| 20 |
Encoding Standard |
A high-level description of how the content object is encoded. Valid values:
HTML
XHTML
Blank |
Important: Values must be capitalized as shown or ingest fails. |
| 21 |
Event Name |
Name of the event, for example Preingest or Object Origin. |
Event Name is mandatory if any other Event element is present. The Event elements together describe an event in the object's lifecycle. |
| 22 |
Event Agency |
The agency responsible for the event. |
|
| 23 |
Event Procedure |
How the process was carried out. |
|
| 24 |
Event Specifications |
Citation to guidelines, rules, etc., governing the process. |
|
| 25 |
Event DateTime |
Date and time of the process. |
The date must follow W3C-DTF formats:
yyyy-mm-dd
yyyy-mm
yyyy |
| 26 |
Event Outcome |
Whether the process was successful. Information might overlap with Original Functionality and Functionality in Archive elements. |
|
| 27 |
Event Rationale |
Reason process was carried out. |
|
| 28 |
Event Note |
Any other information about the process. |
|
| 29 |
Event Reporter |
Who reported that the event took place. Might be the same as or different from the Event Agency. |
|
| 30 |
Fixity Check Date |
|
Element not currently accepted. If present, the system ignores it. |
| 31 |
Fixity Check Status |
|
Element not currently accepted. If present, the system ignores it. |
| 32 |
Functionality in Archive |
Records loss of original functionality when the content object is ingested into the Digital Archive. |
|
| 33 |
Institution Symbol |
OCLC symbol of the content owner. |
|
| 34 |
Local Note |
A note about the content object that does not fit other note elements. |
|
| 35 |
Object Type |
Classifies the content object. Valid values:
Multi-type Object
Image Only
Text Only |
Important: Values must be capitalized as shown or ingest fails. |
| 36 |
Object Locator Original |
Original location of the content object. For example, a URL. |
The encoding scheme for Object Locator is URI. |
| 37 |
Object Locator Local Archive |
The location of the content object in a local archive. |
The encoding scheme for Object Locator is URI. |
| 38 |
Object Path |
The portion of the content object's filename that identifies it as a unique object. |
Required element.
Examples
Sealaska\SHF\Curry\04\01 is the path for an object that consists of 72 TIFF files.
Note: The system treats each object's path as the filename.
First object's filename: Sealaska\SHF\Curry\04\01\001.tif
Second object's filename: Sealaska\SHF\Curry\04\01\002.tif |
| 39 |
OCLC Identifier |
The OCLC control number of the bibliographic record that describes the content object. |
Qualifier is set to OCLC number in the Digital Archive. |
| 40 |
OCLC Identifier |
The OCLC control number of the bibliographic record that describes the content object. |
|
| 41 |
OCLC Identifier |
The OCLC control number of the bibliographic record that describes the content object. |
|
| 42 |
OCLC Identifier |
The OCLC control number of the bibliographic record that describes the content object. |
|
| 43 |
Other Metadata Identifier, Institution Identifier |
Institution ID of an identifier that points to additional content object metadata that exists outside the Digital Archive. The metadata could either be purely descriptive or preservation-related metadata. |
|
| 44 |
Other Metadata Identifier, System Name |
System name of an identifier that points to additional content object metadata that exists outside the Digital Archive. The metadata could either be purely descriptive or preservation-related metadata. |
|
| 45 |
Other Metadata Identifier, Metadata Identifier |
Identifier that points to additional content object metadata that exists outside the Digital Archive. The metadata could either be purely descriptive or preservation-related metadata. |
|
| 46 |
Publisher |
An entity responsible for making the resource available. |
Qualifier is set to Unqualified in the Digital Archive. |
| 47 |
Publisher |
An entity responsible for making the resource available. |
Qualifier is set to Unqualified in the Digital Archive. |
| 48 |
Publisher |
An entity responsible for making the resource available. |
Qualifier is set to Unqualified in the Digital Archive. |
| 49 |
Peripherals |
Records peripherals needed to access the content object. |
|
| 50 |
Relation Qualifier |
Qualifiers:
IsVersionOf
HasVersion
IsReplacedBy
Replaces
IsRequiredBy
Requires
IsPartOf
HasPart
IsReferencedBy
References
IsFormatOf
HasFormat
Unqualified |
For definitions of the qualifiers, see <
http://dublincore.org/usage/terms/dc/current-elements/ >.
|
| 51 |
Relation Encoding Scheme |
Valid encoding schemes:
URI
LocalId
OCLCArchiveId |
|
| 52 |
Relation Value |
Refers to a related resource. |
|
| 53 |
Relation Qualifier |
Qualifiers:
IsVersionOf
HasVersion
IsReplacedBy
Replaces
IsRequiredBy
Requires
IsPartOf
HasPart
IsReferencedBy
References
IsFormatOf
HasFormat
Unqualified |
For definitions of the qualifiers, see <
http://dublincore.org/usage/terms/dc/current-elements/ >.
|
| 54 |
Relation Encoding Scheme |
Valid encoding schemes:
URI
LocalId
OCLCArchiveId |
|
| 55 |
Relation Value |
Refers to a related resource. |
|
| 56 |
Relation Qualifier |
Qualifiers:
IsVersionOf
HasVersion
IsReplacedBy
Replaces
IsRequiredBy
Requires
IsPartOf
HasPart
IsReferencedBy
References
IsFormatOf
HasFormat
Unqualified |
For definitions of the qualifiers, see <
http://dublincore.org/usage/terms/dc/current-elements/ >. |
| 57 |
Relation Encoding Scheme |
Valid encoding schemes:
URI
LocalId
OCLCArchiveId |
|
| 58 |
Relation Value |
Refers to a related resouce. |
Element not currently accepted. If present, the system ignores it. |
| 59 |
Standard Identifier SICI |
A SICI that identifies and locates the object outside the Digital Archive. |
The qualifier is Unqualified. |
| 60 |
Standard Identifier EAN |
An EAN that identifies and locates the object outside the Digital Archive. |
The qualifier is Unqualified. |
| 61 |
Standard Identifier ISBN |
An ISBN that identifies and locates the object outside the Digital Archive. |
The qualifier is Unqualified. |
| 62 |
Standard Identifier ISSN |
An ISSN that identifies and locates the object outside the Digital Archive. |
The qualifier is Unqualified. |
| 63 |
Standard Identifier LCCN |
An LCCN that identifies and locates the object outside the Digital Archive. |
The qualifier is Unqualified. |
| 64 |
Title, Unqualified |
Records the formal name of the content object. |
Required element. |
| 65 |
Title, Alternative |
A variation or commonly used substitute for the formal title. |
|
| 66 |
Virus Check Date |
|
Element not currently accepted. If present, the system ignores it. |
| 67 |
Virus Check Status |
|
Element not currently accepted. If present, the system ignores it. |
| 68 |
Content file names |
Filename or comma-delimited list of all filenames that make up the content object. |
Optional. Not required if you send a separate manifest. |
System-generated elements
| No. |
Element name |
Definition |
| 1 |
Object Composition |
The file types that make up the content object and the number of files, according to type. |
| 2 |
Logical Object Size |
The approximate uncompressed size of the content object. |
| 3 |
DA Identifier |
The Digital Archive record identifier. The system assigns a unique number to each record after ingest. |
| 4 |
Archived Object Identifier |
The system assigns a unique number to each logical object. |
| 7 |
Ingest Date |
Date the object described by this record was ingested into the Digital Archive. |
| 8 |
Created |
Contains the OCLC symbol of the institution which created the Digital Archive record, followed by the date of creation. The OCLC symbol is a unique identifier assigned by OCLC to member institutions. |
| 9 |
Modified Date |
The last date the Digital Archive record was modified. |
back to top
Submission Builder
About
Use the OCLC Submission Builder to create Submission Information Packages (SIPs) from your DA record files and manifest files for your content objects.
Note: Only one instance of the Submission Builder can run at a time.
SIP directory and naming convention
Each SIP is a directory (folder) containing various files and content folders.
SIPs have a system-generated name in this format:
SIP[OCLC symbol]-[date: yyyy-mm-dd]-[nn-nn-nn-nnn]
Example
SIPKUK-2003-01-20-16-41-19-189
Internet access
Important: You must be connected to the Internet while using the Submission Builder. When creating a SIP, the Submission Builder compares the METS encoding of the SIP to the online current METS schema.
User information
The first time you run the Submission Builder, you see the User Information screen so you can enter your user information.
| |
Action |
| 1 |
Start the OCLC Submission Builder.
The User Information screen appears. |
| 2 |
Submitter. Type the OCLC symbol of the submitter of the content. |
| 3 |
Submitter e-mail. Type the e-mail of the submitter of the content. |
| 4 |
Content owner/custodian. Type the OCLC symbol of the owner of the content. |
| 5 |
Optional.
Change the submission output directory. Type the path of a new directory where you want the Submission Builder to put your completed SIPs. |
| 6 |
Click Submit. |
All subsequent times you run the Submission Builder, the main screen appears. To go to the user information screen, click View/Change User Information File.
Create a SIP
| |
Action |
| 1 |
Start the OCLC Submission Builder.
The Profile screen appears. |
| 2 |
Content owner/custodian.
The OCLC symbol is the one you most recently entered. The system stores all the symbols you enter.
Select content owner. Click the list to select the OCLC symbol of the content owner/custodian.
Add a new content owner. Click Add/Delete. A new window opens. Type the OCLC symbol of the content owner in the OCLC institution symbol field. Click Add.
Optional. Type a note in the note field. Click Close.
Delete content owner. Click Add/Delete. A new window opens. Select the OCLC institution symbol from the list. Click Delete. Click Close. |
| 3 |
Optional.
View a note on a content owner/custodian. Click Add/Delete. Select the OCLC symbol from the list. The note appears. |
| 4 |
DA record filename. Type the path of the DA record file or click Browse to navigate to the folder containing your DA record file. |
| 5 |
Object structure. Choose Simple. Complex is not yet implemented and is ignored if chosen. |
| 6 |
Manifest filename (if filenames not part of DA record file). Type the path of the manifest filename or click Browse to navigate to the folder containing your manifest file. |
| 7 |
Tracking Identifier.
Click Add/Delete. A new window opens. Type the tracking identifier in the box.
Optional. If there are multiple numbers, type them on separate rows by pressing <Enter> after each number.
Click Submit. |
| 8 |
Optional.
Clear. Click Clear to erase everything you have typed.
Close. Click Close to exit the program.
View/Change User Information. Click View/Change User Information File to check or edit the OCLC symbols of the submitter or content owner, the submitter e-mail and output directory. |
| 9 |
Click Create.
The Output Directory window appears. |
| 10 |
Click OK.
Optional.
Change output directory. Click Browse to designate a different output directory.
The Submission Result window appears. |
| 11 |
Click OK. |
Memory error
If you get a memory error when trying to create a SIP, follow the steps below.
| |
Action |
| 1 |
Error window appears saying there is not enough memory to create the SIP.
Click Close to close the Submission Builder. |
| 2 |
Split the metadata and manifest files into smaller files. |
| 3 |
Create multiple SIPs from the smaller files. |
Submission errors
If you get a submission error when trying to create a SIP, follow the steps below.
| Error message |
Action |
| Cannot create submission. Object path in DA record file does not match content filenames. |
Click OK.
Compare the object path in the DA record file with the filename in the:
- DA record file
- Manifest (if applicable)
Correct the object filename path in the DA record file (and/or manifest, if applicable). |
| Cannot create submission. Please supply a tracking identifier. |
Click OK.
Click Add/Change to add a tracking identifier. |
| Invalid DA record filename path. Please provide a valid path. |
Click OK.
Type the corrected DA record filename path or click Browse to navigate to the folder containing your metadata file. |
| Invalid manifest filename path. Please provide a valid path. |
Click OK.
Type the manifest filename path or click Browse to navigate to the folder containing your manifest file. |
Uninstall Submission Builder
| |
Action |
| 1 |
Click Start>Settings>Control Panel.
The Control Panel screen appears. |
| 2 |
Click Add/remove programs. |
| 3 |
Select Submission Builder. |
| 4 |
Click Change/Remove.
The system responds Are you sure you want to remove? |
| 5 |
Click Yes. |
System recovery
If the SIP creation process is interrupted (your computer crashes, etc., while generating a SIP), the SIP Builder creates files and folders that you must delete before creating a new SIP:
| |
Action |
| 1 |
Open Windows Explorer and navigate to the OCLC Submission Builder folder. |
| 2 |
Open the log folder. |
| 3 |
Delete the lock file. |
| 4 |
Navigate to the SIP folder. |
| 5 |
Delete any tmp folders (and files they contain). |
back to top
Submit content
Submitter and content owner guideline
Important
The submitter and content owner/custodian can be different institutions, but the same pair must be used for each SIP in a batch.
Example
| |
SIP 1 |
SIP 2 |
SIP 3 |
| |
Submitter |
Content owner |
Submitter |
Content owner |
Submitter |
Content owner |
| Batch 1 |
KUK |
KNT |
KUK |
KNT |
KUK |
KNT |
| Batch 2 |
TOL |
UTL |
TOL |
UTL |
TOL |
UTL |
| Batch 3 |
AKR |
AKR |
AKR |
AKR |
AKR |
AKR |
Accepted media
OCLC accepts the following media:
- CDs R/RW
- DVD R/RW
- External hard drives (USB or Firewire)
Copy SIP and content objects to media
| |
Action |
| 1 |
Navigate to the directory containing your SIPs. |
| 2 |
Copy the SIP folder to the media.
Note: SIP names follow this format:
SIP[OCLC symbol]-[date: yyyy-mm-dd]-[nn-nn-nn-nnn]
Example
SIPKUK-2003-01-20-16-41-19-189 |
| 3 |
Copy your content objects to media using multiple discs or tapes, as needed. |
Label media
Each CD jewel box/case or tape case must bear a label with the following information:
- Digital Archive
- Name of submitting institution
- OCLC symbol of submitting institution
- Tracking identifier
- Instruction to return or discard media after ingest
- The word "SIP" to indicate media containing the SIP
If there is more than one CD or tape, each must be labeled with the institution's OCLC symbol and numbered.
Example
KUK 1 of 67
KUK 2 of 67
OCLC mailing address
Mail packages to this address:
OCLC
Digital Archive, MC 431
6565 Frantz Rd.
Dublin, OH 43017
If mailing more than one package per batch, label packages N of N.
Example
1 of 3, 2 of 3, 3 of 3, etc.
Batch submission status e-mail
When the batch is processed, OCLC sends an e-mail is sent to the submitter. The e-mail contains the information in the table below.
| Item |
Description |
| Link to batch ingest report |
Example
http://digitalarchive.oclc.org:33333/report?idnum=000110557 |
| Batchload date/time |
Example
Fri. Jan 17 10:49:15 EST 2003 |
| Batch number |
Example
DA0062 |
| Batch result |
Success or failure |
| Content owner |
OCLC symbol of content owner
Example
KUK |
back to top
View batch ingest reports
About
Use the Digital Archive Administration Module to manage your content objects (organize them in content groups, set access, view reports, etc.).
Log on
| |
Action |
| 1 |
Type the Administration Module URL in your browser's address bar:
http://digitalarchive.oclc.org/admin/
The Administration Module Logon screen appears. |
| 2 |
Type your authorization and password. Click Logon.
Click the Reports tab. |
Using the administration module
For information on using the Administration Module, see the Administration Module guide on the Digital Preservation documentation page:
http://www.oclc.org/support/documentation/digitalarchive/.
Reports
The batch ingest process generates three reports.
| Report |
Describes |
| Batch |
The overall status of the batch. |
| SIP |
The overall status of each SIP in the batch. |
| Object |
The status of each object in the SIP. |
View batch ingest reports
| |
Action |
| 1 |
Log on to the Digital Archive Administration Module. |
| 2 |
Click the Reports tab. |
| 3 |
Click Batch Report. The Ingest Batch Reports screen appears. |
| 4 |
Click the batch number you want to view. The Batch Report screen appears. |
| 5 |
Click the batchload XML file.
The report appears. |
View SIP reports
| |
Action |
| 1 |
Log on to the Digital Archive Administration Module. |
| 2 |
Click the Reports tab. |
| 3 |
Click Batch Report. The Ingest Batch Reports screen appears. |
| 4 |
Click the batch number you want to view. The Batch Report screen appears. |
| 5 |
Click the SIP XML file.
The report appears. |
View object reports
| |
Action |
| 1 |
Log on to the Digital Archive Administration Module. |
| 2 |
Click Object Report. The Object Report screen appears. |
| 3 |
Click the ingest date of the object. The Report Date screen appears. |
| 4 |
Click the Ingest XML file.
The report appears. |
back to top
Batch ingest report
Summary
| Report element |
Description |
| Batchload date/time |
Date and time batch was created. |
| Batchload status |
Success or failure. |
| Batch submitter |
OCLC symbol of institution submitting the content for batch ingest. |
| Content owner/custodian |
OCLC symbol of institution owning or administering the ingested content. |
| Number of objects processed |
Number of objects in SIP that were processed. |
| Number of SIPs submitted |
Number of SIPs in batch. |
| Number of valid objects |
Number of valid objects in batch. (If batch is successful, will match the number of processed objects.) |
| Number of valid SIPs |
Number of valid SIPs in batch. |
| Report date/time |
Date and time report was created. |
SIP details
To view the report elements below, click the filename (or the + in front of it).
| Report element |
Description |
| Number of objects |
Number of content objects in SIP. |
| SIP name |
Name of SIP. |
| Status |
Success.
If the batch fails, each SIP in it has a status of either valid or invalid. An invalid SIP causes the batch to fail. |
| Tracking identifier |
User-assigned number identifying each piece of media in the SIP. |
Error details
Error report elements only appear if there is an error in the batch. To view the report elements below, click the filename (or the + in front of it).
| Report element |
Description |
| Batch contains unexpected data |
Data other than SIP(s) and content objects submitted. |
| Contains no files |
Either SIP files or content objects were not submitted. |
| Contains too many files |
Either too many SIP files or content objects submitted. |
| File type not supported |
Content object is not a supported file type. |
| Invalid format for batch |
Incorrect data format on media (CD, tape). |
| SIP content manifest mismatch |
At least one mismatch between manifest and content objects. |
| SIP manifest missing |
SIP did not include manifest and filenames were not included in DA record file. |
back to top
SIP report
Summary
| Report element |
Description |
| Batchload number |
System-assigned number identifying the batch. |
| Content owner/custodian |
OCLC symbol of institution owning or administering the ingested content. |
| Number of objects |
Number of objects listed in SIP. |
| Report date/time |
Date and time report was created. |
| Status |
Success (if batch is successful).
If the batch fails, each SIP in it has a status of either valid or invalid. An invalid SIP causes the batch to fail. |
Tracking identifier
To view the report elements below, click the filename (or the + in front of it).
| Report element |
Description |
| Tracking identifier |
User-assigned number identifying media in the SIP. |
Object details
To view the report elements below, click the filename (or the + in front of it).
| Report element |
Description |
| Link to ingest report |
Click link to view ingest report. |
| Name |
Name of SIP. |
| Number of files |
Number of files making up the object. |
| Object path |
The path of the object (on the computer it was stored on). |
| Status |
Ingested successfully. |
back to top
Object report
Summary
| Report element |
Description |
| Archived object ID |
The number that identifies the object in the digital archive. |
| Authorization group |
The group containing the authorizations allowed to access the object. |
| Content group |
The group(s) containing the object. |
| Copyright statement |
The name and text of the copyright statement assigned to the object. |
| DA record number |
The number that identifies the digital archive record. |
| Ingest date/time |
Date and time ingest occurred. |
| Ingest method |
One of two OCLC services used to ingest content objects into the digital archive:
|
| Institution symbol |
The OCLC symbol of the institution. |
| Process status |
The current status of the record. |
| Report date/time |
Date and time report was generated. |
| Service level |
Bit Preservation. Object is stored in the OCLC Digital Archive.
Local. Object is to be disseminated from the OCLC Digital Archive for storage in a local archive. |
Detail
To view the report elements below, click the filename (or the + in front of it).
| Report element |
Description |
| File name |
Name of file. |
| File size |
Size of the file. |
| Fixity check date and time |
Date and time of most recent fixity check. |
| Fixity check status |
Result of fixity check. "Success" means the file is stable and has not changed. |
| Mime type |
Format of the file. |
| Virus check date and time |
Date and time of most recent virus check. |
| Virus check status |
Result of virus check. "Success" means no virus was found. |
back to top
Librarians' Toolbox:
