...
This is an INTERMEDIATE format, it is NOT for exporting or harvesting metadata!
XSLT translation
Extensible Stylesheet Language (XSL) and XSLT is a powerful mechanism for transforming one XML expression into another. Since many metadata formats are expressed in XML, you can use XSL stylesheets quite effectively to implement crosswalks.
...
- Invoke an XSLT engine and your XSL stylesheet to translate the incoming metadata format to DSpace Intermediate Format.
- Hand the intermediate XML to a method that stuffs its field values into the Item (like many calls to
).Code Block Item.addDC
The Format
It cannot be overemphasized that this is strictly an internal metadata format. It must never be recorded, transmitted, or exposed outside of DSpace, because it is NOT any sort of standard metadata. We must not allow it to "escape" to prevent its being mistaken for an actual supported and sanctioned metadata format. It exists to support internal transformations only.
This format is designed to be a straightforward and precise representation of the DSpace data model's Item metadata. It represents the new metadata model described in MetadataSupport, which includes a "metadata schema" field.
Namespace
See XmlNamespaces for details. All elements are in the "dim" namespace, identified by the URI
...
element and allow validation.
Elements
Here is an example of a metadata record:
...
An XML Schema document (XSD) description will be forthcoming once this design is approved.
Extensions
For ItemBatchUpdate (importing existing bibliographic data and uploading of corresponding files), DIM is "extended" the following ways:
...
Modifications are in XSLTIngestionCrosswalk and are therefore common to ItemImport and XSLTingest (described in ItemBatchUpdate).
Opinions? Comments?
Should DIM support the types of BITSTREAM and/or BUNDLE? If so what fields would be used? – ScottPhillips