...
- 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.
...
See XmlNamespaces for details. All elements are in the "dim" namespace, identified by the URI http://www.dspace.org/xmlns/dspace/dim
There will eventually be a schema for this namespace, as soon as dspace.org establishes a place to put schemas. The purpose of the schema is to document the {dim}} element and allow validation.
...
<dim:list>...</dim:list>now can enclose multiple items:<dim:dim>...</dim:dim><dim:field ... type="field-type">...</dim:field>is used to specify either type="unique" (to remove prior field content before inserting new one) either type="key" (to specify that the current record replaces the record which may (or not) exist with the same value: useful for external identifiers)<dim:remove mdschema="schema-name" element="element-name" qualifier="qualifier-name" lang="language_country"/>remove field occurrence(s) corresponding to the specified element-name, qualifier-name and (optional) language_country.<dim:original>file-path</dim:original>specifies the path of the document file to upload (not a "symbolic link")<dim:licence>file-path</dim:licence>specifies the path to the licence file to upload<dim:collection> collection complete handle or internal number </dim:collection>: Additional collection to link with the document
Modifications are in XSLTIngestionCrosswalk and are therefore common to ItemImport and XSLTingest (described in ItemBatchUpdate).
...