Submissions of Limited METS

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Submissions of Limited METS

Producers can deposit materials using a limited METS format, which means uploading material that can conform to a DC section of METS without requiring the time and potential errors of creating and validating a full METS file. (Only DC is supported.)

The directory structure of a SIP includes limited METS.

Metadata Types

The metadata types supported by this workflow are at the IE level only and include the following:

Descriptive metadata (dmdsec METS section)
Source metadata (sourceMD METS section)
Any DNX section at the IE level (for example, CMS or generalIECharacteristics)

Material Flow

A material flow that uses the limited METS functionality should be created as follows:

Material flow should be Automated
Content Structure should be DC or Set Of Files (Simple or Complex)
Submission format can be any of the types associated with an automated material flow (for example, NFS, FTP, SFTP)

Directory Structure

If the submission job is used to upload limited METS content, the following is the directory structure required by the submission job:

//PredefineFolderForSF/ - (Directory)
Rosetta accesses this folder (configured in the submission format to be used) and uploads the content located in one (or more) of the sub-folders beneath it.
//PredefineFolderForSF/<SubFolder> - (Directory)
This directory contains the data of a single intellectual entity that is uploaded to Rosetta.
//PredefineFolderForSF/<SubFolder>/content/???.xml - (File)
The METS file contains the metadata information to be added to the IE(s) created by Rosetta. Only one xml file is expected to be read by Rosetta.
//PredefineFolderForSF/<SubFolder>/content/streams – (Directory)
This directory contains all the IE associated streams. All the files are uploaded to Rosetta into a single REP.

Limited METS Structure

The METS may contain one or more of the following sections:

Descriptive metadata (dmdsec METS section) – If there is more than one dmdsec, Rosetta will use the first one
Source metadata (sourceMD METS section)
Any DNX section at the IE level (for example, CMS or generalIECharacteristics)

The METS file has no naming convention.

An example for such a METS file can be found below.

Limited METS Sample

The following sample includes a descriptive metadata section (dmdSec), a source metadata section (sourceMD) and a DNX section (CMS).

<mets:mets xmlns:mets="http://www.loc.gov/METS/">

<mets:dmdSec ID="ie-dmd">

<mets:mdWrap MDTYPE="DC">

<mets:xmlData>

<dc:record xmlns:dc="http://purl.org/dc/elements/1.1/">

<dc:creator>Exlibris</dc:creator>

<dc:identifier>ISBN 1-56389-016-X</dc:identifier>

<dc:title>Limited Mets Test</dc:title>

</dc:record>

</mets:xmlData>

</mets:mdWrap>

</mets:dmdSec>

<mets:amdSec ID="ie-amd">

<mets:sourceMD ID="ie-amd-source-dc">

<mets:mdWrap MDTYPE="DC">

<mets:xmlData>

<dc:record xmlns:dc="http://purl.org/dc/elements/1.1/">

<dc:creator>Source MD Creator</dc:creator>

<dc:title>Source MD (DC) Title</dc:title>

<dc:date>01-01-2012</dc:date>

</dc:record>

</mets:xmlData>

</mets:mdWrap>

</mets:sourceMD>

<mets:techMD ID="ie-amd-tech">

<mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">

<mets:xmlData>

</record>

</section>

</dnx>

</mets:xmlData>

</mets:mdWrap>

</mets:techMD>

</mets:amdSec>

</mets:mets>

Mets for Structural IEs

Structural and content IEs belonging to the same structure can be submitted into Rosetta using a single METS submission.

Structural IEs are identifiable by the METS not having any representation and file information. If the METS has representation and file information, it is a content IE.

Like with a CSV submission, a METS submission for structural IEs can contain the relationship data, but the relationships are created by a job after the import of the file.

Only structural IEs can hold the relationships to their children in the tree – either other structural IEs or content IEs. Relationships are optional in a structural IE and can point to an IE either in the SIP or in Rosetta. The relationship indication must be from the parent IE to the child IE, unless the parent IE is already in Rosetta, in which case the submitted child IE can point to the parent IE.

The following relationships are possible for structural IEs:

Parent to Child Relationship – Recorded in the relationships IE DNX section defined above. The following values should be present in the relatedObjectIdentifierType and relatedObjectIdentifierValue DNX keys:
Child to Parent Relationship – Prohibited if both parent and child are in the SIP. In this case, the parent should point to the child.

IE submitted as a child of a parent IE already in Rosetta – the child IE should contain the IE relationships DNX section. The sub-type should be IS_PART_OF and the relationship object identifier type and value should be PID with the parent IE PID. This relationship is added to the parent structural IE in Rosetta pointing to the child IE with the HAS_PART relationship sub-type.<

Mets for Structural IEs
Relationship Direction	IE Classification Type	Related Object Location	Relationship Type	Relationship Sub-type	Relationship Object Identifier Type	Relationship Object Identifier Value
Parent to Child	Structural	SIP	Structural	HAS_PART	METS_FILE	The file name of the child IE in the SIP
Parent to Child	Structural	Rosetta	Structural	HAS_PART	PID	Child IE PID
Parent to Child	Content	All	All	All	All	All
Child to Parent	All	Rosetta	Structural	IS_PART_ OF	PID	Parent IE PID
Child to Parent	All	SIP	All	All	METS_FILE	All