...
In order the make easier the preparation of conformant SIPs, the DSpace Content Object Model is here mapped to the METS object model.1.
- DSpace Item = METS Document (Structural Requirements #19)
- This profile identifies a single METS document with a single Item in the DSpace Content Object Model. This profile does not anticipate or allow for the aggregation of multiple DSpace Items into one METS document for ingest.
...
- DSpace Bundle = METS <fileGrp> (Structural Requirements #12)
- DSpace groups files into "bundles," the purpose of which is to make it easier for DSpace to process them. These Bundles are loosely controlled by a vocabulary of bundles types. Creators of SIP documents who are familiar with DSpace bundle types are encouraged to organize <fileGrp> elements by bundle and to label them using the USE attribute. The USE attribute of the <fileGrp> element is reserved for use with the DSpace Bundle Type Vocabulary, but it is not required. DSpace will deposit the files in any unlabeled <fileGrp> element into the "Content" bundle.
...
- Content Bundle = METS <structMap> (Structural Requirements #17)
- The first <structMap> is reserved to organize the files intended for the DSpace "Content" Bundle. These files will be displayed to the public.
...
- Bitstream = METS <file> element, <mdRef> element (Structural Requirements #1)
- All files intended for inclusion in the DSpace Item as bitstreams should be found at either a xlink:href attribute of the <file> element, or a xlink:href attribute of the <mdRef> element. Metadata files referenced from <mdRef> elements in the <dmdSec> and <amdSec> elements will be deposited in the DSpace item as bitstreams. Only the metadata record for the whole item will be processed into the DSpace metadata database tables.
...
- DSpace Item MD = METS <div> (Structural Requirements #16)
- The <div> element is a child of the <structMap> element and is recursive. In the first <structMap> there must be only one first level <div> element. It may contain any number of child <div> elements. This first level <div> element represents the DSpace Item within the structMap and must contain references to metadata for the Item.
...
- Primary Bistream = METS <fptr>
- When DSpace ingests websites as items it identifies a "primary bitstream," or index file that it presents to the public. All other website files are suppressed to the DSpace user. The first <div> element under the first <structMap> element, also called the DSpace Item <div>, may only contain a child <fptr> element when the METS document represents a website with a primary bitstream. This <fptr> element should then reference the <file> element that represents the primary bitstream.
...
- Preferred Bitstream = METS <file> element @USE (Structural Requirements #)
- There are some potential DSpace Items that are not websites (they do not have a primary bitstream) that need to show preference for one bitstream or file above all others. One example of this is a potential item that contains three versions of the same document (e.g. pdf, ps and latex). It is advantageous to the user to know that the pdf is the version intended for public consumption. In this case this profile recommends that USE attribute of the <file> element representing the preferred bitstream contain the value "preferred".
Descriptive Metadata
As outlined in Rules of Description #1 and #2, the DSpace has adopted the Metadata Object Description Schema (MODS) as a transfer schema for descriptive metadata in SIPs.
...