http://www.loc.gov/standards/mets/profiles/00000036.xml
http://formex.publications.europa.eu/schema/cellar-mets-profile.xml
Publications Office METS Document Profile for General Information Packages
This profile describes the rules and requirements for using METS as general information exchange package.
Developed by infeurope S.A. on behalf of the Publications Office of the European Union, this profile is intended for the ingest and retrieval of publication data maintained by the Publications Office.
2010-12-08T15:40:00Z
Publications Office of the European Union
2 rue Mercier, L-2985 Luxembourg
OP-METS@publications.europa.eu
Operation Type
read.req
read.rsp
create.req
create.rsp
update.req
update.rsp
/mets/@TYPE
These are the values permitted for the TYPE attribute of <mets>.
Notice Type
notice
prenotice
/mets/@LABEL
These are the values permitted for the LABEL attribute of <mets>.
Entity Type
work
expression
manifestation
dossier
event
agent
//div/@TYPE
These are the values permitted for the TYPE attribute of <div>. The <structMap> is used to describe the top level hierarchy of "cohesive objects" (e.g. work -> expression -> manifestation) defined in the Common Data Model.
Ingestionstatus
success
failure
/mets/metsHdr/@RECORDSTATUS
These are the values permitted for the RECORDSTATUS attribute of <metsHdr>.
Metadata Type
op_dmd
op_tmd
//mdRef/@OTHERMDTYPE
//mdWrap//@OTHERMDTYPE
These are the values permitted for the OTHERMDTYPE attribute of <mdRef> and <mdWrap>.
CELLAR METS - MIME Types
Publications Office of the European Union
http://formex.publications.europa.eu/authority/media-types.html
//mdRef/@MIMETYPE
//file/@MIMETYPE
The Publications Office of the EU uses media types as defined in the IANA MIME Media Type registry: http://www.iana.org/assignments/media-types/. In case a media type is not registered (yet) in the IANA registry, the media type defined by the vendor or developer of the media type is used instead. In case of multiple media types with the same file extension, the media type is completed with a type specifying the exact media type. For example: application/pdf;type="pdfx".
The list of media types permitted in the CELLAR (IANA registered and unregistered) can be found at the following address: http://formex.publications.europa.eu/schema/mediatypes.html
Granularity and Information Type
node.content
node.metadata
node.all
tree.content
tree.metadata
tree.all
//structMap/@TYPE
These are the values permitted for the TYPE attribute of <structMap>.
The TYPE attribute provides two levels of granularity for read and update. Valid values consist of a dot-separated pre- and postfix.
Prefixes:
tree - means the elements specified within the <structMap> and all its child elements
node - means only the elements specified within the <structMap>
Postfixes:
metadata - only descriptive metadata is concerned
content - only content related data streams and technical metadata are concerned
all - metadata and content are concerned
Data Stream Handling
ref_only
//FLocat/@USE
This is the only value permitted for the USE attribute of <FLocat>.
The USE attribute indicates that for the specified file only its reference will be maintained by the ingesting system.
The attribute TYPE has to be present.
A <metsHdr> has to be present.
The number of <dmdSec> is bound to the number of <structMap> elements. I.e. for each <structMap> there must be exactly one related <dmdSec>.
The number of <amdSec> depends on the number of <structMap> elements. I.e. for each <structMap> there must be exactly one related <amdSec>. Further <amdSec> elements related to an ingestion report referenced by the <metsHdr> of a response message are permitted.
In any case the LABEL attribute has to be present. The value indicates whether the METS message represents a "prenotice" or a "notice".
The attribute CREATEDATE has to be present.
The attribute RECORDSTATUS has to be present in case of a response.
The attribute LASTMODDATE has to be present in case of a response.
In case of a response with RECORDSTATUS set to "failure" the attribute ADMID has to be present and refer to a report within corresponding <techMD> element(s) that are nested within a superior <amdSec> element.
In any case the <metsHdr> element has to contain a <metsDocumentID> element that uniquely identifies the message.
In any case the value "OTHER" has to be chosen for the attribute MDTYPE.
In any case the attribute OTHERMDTYPE has to be present and its value must be set to "op_dmd" for descriptive metadata.
For the specification of metadata either the element <mdRef> or <mdWrap> has to be used.
The concurrent utilization of <mdRef> and <mdWrap> within the same parent element is prohibited.
The occurrence of the <techMD> element is limited to the number of manifestations that occur in the related <structMap> element.
For the attribute MDTYPE of the element <techMD> the value "OTHER" has to be chosen.
For each <techMD> the attribute OTHERMDTYPE has to present and its value must be set to "op_tmd" for technical metadata.
For the specification of metadata either the element <mdRef> or <mdWrap> has to be used. The concurrent utilization of both elements is prohibited.
The concurrent utilization of <mdRef> and <mdWrap> within the same parent element is prohibited.
METS documents implementing this profile must not use the <stream>, <transformFile> or nested <file> elements.
Content files can either be referenced via <FLocat> or embedded via <FContent>.
The concurrent utilization of <FLocat> and <FContent> within the same <file> elements is prohibited.
Each <file> element must not use more than one <FLocat> element.
For each specified data stream for which the ingesting system should only maintain a reference, the USE attribute of <FLocat> must be present.
For each reference to an external resource given by the <FLocat> element, the xlink:href has to contain a corresponding absolute URL. In case that the content will be provided together with the METS document via the same physical ZIP archive, the xlink:href must specify a corresponding relative URL.
Each <file> element must provide a SHA-1 hash value for the referenced or embedded data stream via its attributes CHECKSUM and CHECKSUMTYPE.
For each <structMap> the ID attribute has to be present.
Depending on the specified operation the TYPE attribute of the <structMap> element has to be present.
For each <div> element the attributes TYPE and CONTENTIDS are mandatory. While TYPE has to be used to specify the entity type of the object represented by the given <div> element, the attribute CONTENTIDS has to be used to list all known production identifiers for the specified object. These Production identifiers are URIs that must be given in CURIE syntax.
For the root <div> element the attribute TYPE has to be set to "work", "dossier" or "agent".
For a <div> element with the TYPE attribute set to "work" the TYPE attribute for each of its child <div>'s has to be set to "expression".
For a <div> element with the TYPE attribute set to "expression" the TYPE attribute for each of its child <div>'s has to be set to "manifestation".
For a <div> element with the TYPE attribute set to "manifestation" further child <div> are prohibited.
For a <div> element with the TYPE attribute set to "dossier" the TYPE attribute for each of its child <div>'s has to be set to "event".
For a <div> element with the TYPE attribute set to "event" further child elements are prohibited.
For a <div> element with the TYPE attribute set to "agent" further child elements are prohibited.
The <mptr> element is not supported and its usage prohibited.
The <fptr> element in only permitted for <div> elements with the attribute TYPE set to "manifestation".
METS documents implementing this profile must not use the <area>, <par> or <seq> elements.
METS documents implementing this profile must not use the <structLink> element.
METS documents implementing this profile must not use the <behaviorSec> element.
oj-JOL_2006_088_R_0063_0120100930125926