...
- dcterms:identifier (dc.identifier.none) will be used for an Item's primary identifier, assigned prior to deposit in Dome.
- Custom identifier fields (dc.identifier.govdoc, dc.identifier.isbn, dc.identifier.ismn, dc.identifier.issn, dc.identifier.sici, dc.identifier.vendorcode) will no longer be used in Dome.
- Existing custom identifier fields will be consolidated to a new element that will be added to the Dome metadata registry (dome:otherIdentifier(?)). The new element will be established in a new "Dome" namespace that we will create for our custom elements.
- dc.identifier.uri will only be used by the DSpace system to record the Handle it assigns to the Item. Can it be mapped to a new element (dome:URI(?)) in the newly established "Dome" namespace that we will create for our custom elements? Will moving this field to a new namespace cause problems for external harvesters of Dome metadata?
?What steps need to be taken to bring the existing use of identifier fields in Dome into compliance with the above rules, especially multiple instances of dcterms:identifier (dc.identifier.none)?
...