Page History

...

1. A conforming METS document must represent only one DSpace Item.
2. A conforming METS document is a complete manifest of the DSpace Item. Do not include content or metadata files in the SIP that are not referenced in the METS document.
3. The DSpace Content Object Model organizes DSpace Items into Bundles. Bundles are exclusive classifications of files within a DSpace Item.
4. Content files--files intended for the Content bundle--must be included in or referenced from the fileSec and the structMap. Metadata files--files intended for the Thumbnail, Text (Extracted), License, CC_License and Metadata bundles--are included in or referenced either from the fileSec, dmdSecs or amdSecs.
5. DSpace has defined a set of technical metadata elements for preservation and administration. This metadata includes a unique identifier, checksum, checksum type, mimetype, file size, creation date and file path originally assigned to the file. If this data exists within a system that is authoring a conforming METS document it should be included within the METS document.
6. Inclusion of technical metadata should occur in the techMD element and should conform to the DSpace Required Technical Metadata Element Set defined in this document. This metadata should be encoded using the PREMIS Data Dictionary.
7. A conforming document may contain user supplied Creative Commons licenses in the rightsMD element.
8. A conforming METS document must reference all files accompanying the METS document and comprising the DSpace Item via an xlink:href attribute on either an mdRef or FLocat element. There must be only one FLocat element per parent File element.
9. A conforming METS document must contain the ID attribute of the METS root element.
10. A conforming METS document should contain the PROFILE attribute of the METS root element.
11. DSpace implementations will ignore the metsHdr element, its attributes, child elements and their attributes.
12. The dmdSec is reserved exclusively for bibliographic description and subject analysis of the item and its constituent files, at a ratio of one dmdSec for each metadata record. Multiple expressions of the same metadata in multiple schemas must be recorded in separate dmdSecs and must be grouped through the GROUPID attribute.
13. A conforming METS document must contain at least one dmdSec containing the metadata record for the entire DSpace item the document represents.
14. Each unique configuration of techMD and rightsMD elements must be contained within a separate amdSec element.
15. A conforming METS document must contain the ID attribute for all amdSec elements.
16. DSpace implementations will ignore the sourceMD element, its attributes, child elements and their attributes.
17. DSpace implementations will ignore the digiprovMD element, its attributes, child elements and their attributes.
18. File elements must not contain the FContent child element. A conforming METS document may not contain content encoded as binary or xml data. These encoding mechanisms may be used to include metadata in the METS document.
19. It is strongly recommended that the USE attribute be present for every fileGrp element included in conforming METS documents. The USE attribute identifies Bundles within the METS SIP. Eligible values for this attribute are restricted to the DSpace Bundle Type vocabulary.
20. Multiple expressions of the same content object (e.g. thumbnails and archival masters of the same image) though organized in separate DSpace bundles should be related via the GROUPID attribute of the File element.
21. In the case of multiple expressions of the same content object in different file formats (e.g. .pdf, .ps, .latex), it is strongly recommended that the USE attribute be present on the one file element representing the format that is preferred for public consumption. The value of this attribute must be "preferred".
22. If available, supply the CHECKSUM, CHECKSUMTYPE, CREATED and MIMETYPE attributes of the File element.
23. The first div element under the first structMap element shall be used to identify the DSpace Item and, for websites, the primary bitstream. It must not contain an fptr element unless the DSpace Item is a website with a primary bitstream. It must contain AMDID and DMDID (IDREF) attributes that identify the appropriate metadata for the Item to be processed into the DSpace metadata database tables upon ingest.
24. All files in the content bundle must be represented by child div elements of the first div (DSpace Item div) element of the first structMap element.
25. Multiple structMap elements recording alternate organizations of the DSpace Item are encouraged when applicable.
26. A conforming METS document represents a single DSpace Item and must not contain any mptr elements referencing other METS documents.
27. DSpace implementations will ignore the structLink element, its attributes, child elements and their attributes.
28. DSpace implementations will ignore the behaviorSec element, its attributes, child elements and their attributes.

Technical Requirements of Content, Behavior and Metadata Files

...

1. The list of allowable content files that may be referenced in conforming documents via the FLocat element is restricted to those files each DSpace instance has agreed to support.

...

1. Metadata Files should be encoded in xml and should validate to the schema corresponding to the mdType attribute value of the mdRef element.

Tools and Applications

...

1. This profile is intended for use with the DSpace Packager Plugin, sometimes called the Lightweight Network Interface and discussed at http://wiki.dspace.org/index.php/PackagerPlugins.

Examples

CSAIL Example

DSpace to DSpace Example