Descriptive metadata contents should be encoded using Dublin Core or Dublin Core Terms, following both the appropriate guidelines recommended by the extension schemas' maintenance agencies and the Ex Libris Guidelines for descriptive metadata. The metadata should be embedded in the METS file as XML, using the mdWrap tag.
mets:mdWrap MDTYPE="DC"
This profile specifies MDTYPE attribute value on the dmdSec:mdWrap element. The MDTYPE can be only "DC".
mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx"
This profile specifies OTHERMDTYPE attribute value on the techMD:mdWrap, digiprovMD:mdWrap and rightsMD:mdWrap elements. The MDTYPE="OTHER", and the OTHERMDTYPE="dnx".
sourceMD/mdWrap/@OTHERMDTYPE
This profile specifies OTHERMDTYPE attribute value on the sourceMD:mdWrap elements. If the MDTYPE="OTHER", then a value must be declared for OTHERMDTYPE from the listed attribute values
mets/fileSec/fileGrp/@USE
This is the supported value for mets/fileSec/fileGrp USE attribute.
The root <mets> element must include only the METS name space URL.
A conforming METS document should not contain a <metsHdr> element.
Conforming METS documents must contain one, and only one, IE-level <dmdSec> element
Conforming METS documents may contain up to one file-level <dmdSec> element per file
Any metadata provided must be embedded in the METS file as XML using the mdWrap tag.
mdRef is not supported.
If a <dmdSec> of a conforming document contains a <mdWrap> with <xmlData>, the <xmlData> must conform to those listed in the extension schemas section above.
For IE-level, the dmdSec ID should be referenced by the DMDID value "ie-dmd".
For File-level, the dmdSec ID should be referenced by the DMDID value "FL{ID}-dmd".
techMD (technical metadata) - DNX sections that holds the technical metadata
rightsMD (intellectual property rights metadata) - Access Rights Policy, Copyrights Metadata.
sourceMD (analog/digital source metadata) - Any kind of metadata that is relevant for preservation.
digiprovMD (digital provenance metadata) - Provenance events.
A conforming METS document will contain one <amdSec> element for each object in each level - IE, Representation and file.
Each <techMD> element must contain an <mdWrap> element and corresponding MDTYPE/OTHERMDTYPE attribute. The MDTYPE/OTHERMDTYPE attributes must conform to the controlled vocabulary contained within this profile. MDTYPE/OTHERMDTYPE attributes must describe the type of file as (DNX).
Any amdSec or child element techMD, rightsMD, sourceMD or digiprovMD ID need to be referenced by the ADMID value denoted in either the fileSec section or structMap div section sections.
When referenced using ADMID from the fileSec level - the metadata will be associated specifically with that particular file.
A <rightsMD> element can be populated only in the "ie-amd-rights" or "rep-amd-rights" section.
The <fileSec> must contain a <fileGrp> for each Representation (set of files).
For example, the <fileSec> of a typical METS document implementing this profile might contain one <fileGrp> representing TIFF master images, one <fileGrp> representing high resolution JPEG reference images , one <fileGrp> representing medium resolution JPEG reference images and one <fileGrp> representing OCR full text files.
Each <fileGrp> represented in the <fileSec> must have an ID and ADMID attribute.
The ADMID attribute will associate each Representation with its <amdSec> sections.
Each <file> represented in the <fileGrp> must have an ID and ADMID attribute.
The ADMID attribute will associate each file with its <amdSec> and structMap sections.
Each <file> element must contain an <FLocat> element which specifies the location of the content file in an xlink:href attribute in Rosetta's permanent repository.The <FLocat> element must contain an xlink:href attribute, as well as a LOCTYPE attribute, which in all cases should be "URL".
A conforming METS document must contain at least one <structMap>; it may, however, contain more than one <structMap>.
A conforming <structMap> must contain a TYPE attribute. "logical" and "physical" are reserved (see description below). Other types are not validated by Rosetta METS xsd (only by the LOC METS xsd) and can be used for delivery only using external viewers.
Each <structMap> must include a LABEL attribute value.
Each <div> must include a LABEL attribute value.
The physical <structMap> represents a flattened structure and must only contain two levels of <div> elements with no further nesting. The top level <div> element required by the METS schema contains one level of child <div> elements to represent the linear sequence of the components of the Representation.
The logical structMap represents the full hierarchical structure of the Representation, and can contain as many levels of nested <div> elements as required to express the object's full structure.
A <div> element may or may not directly contain <fptr> elements. (In other words, a <div> of the <structMap> may or may not have content files directly associated with it).
An <fptr> element must directly point to a <file> element via its FILEID attribute;
A conforming METS document should not contain a <structLink> element.
A conforming METS document should not contain a <behaviorSec> element.
This profile supports all kinds of content files.
No specific tools are required by this profile.