...
7. 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".
...
- Do you as a content provider have this information?
Panel - If you do have this information, its inclusion is still optional but strongly recommended.panel
- If you can, write both.
- If you can't write both, write the <techMD> using PREMIS elements.
- If you can't write that, write the attributes in the <file> element.
DSpace Bitstream Metadata
...
3. Technical metadata for DSpace Items and Bitstreams occurring in the techMD element should conform to the DSpace Required Technical Metadata Element Set defined at http://wiki.dspace.org/index.php/DSpaceMETSSIPProfile. This metadata should be encoded using the PREMIS Data Dictionary.
Controlled Vocabularies
<strong>namename:</strong> DSpace Bundle Types
<strong>maintenance maintenance agency:</strong> DSpace Federation
<strong>URIURI:</strong> http://www.dspace.org/standards/vocab/bundles/bundleTypev1p0/DSpacebundletypev1p0.pdf<strong>values
values:</strong>
...
- ORIGINAL
- TEXT(EXTRACTED)
...
- THUMBNAIL
- LICENSE
...
- CC_LICENSE
- METADATA
Structural Requirements
1. A conforming METS document must represent only one DSpace Item.
...