...
We haven't yet actually proposed keeping the contents of a filed and just changing the name. Do we want to follow the name/date procedure and replace current language fields with new fields from a reexport from contributing repositories? Certainly, this field's data cleanup is not the highest priority. Carl says if we are already reexporting/reimporting name and date fields, especially since we'll probably have to do this for every record, it will not add much effort or complexity to add this field in with the rexport/reimport.
Relation Elements
- dc.relation.ispartofseries will be mapped to dcterms:isPartOf (dc.relation.ispartof)
- The following relation elements will be added to the dcterms (or dc.) namespace dcterms:conformsTo (dc.relation.conformsTo), dcterms:hasFormat (dc.relation.hasFormat), dcterms:isRequiredBy (dc.relation.isRequiredBy), and dcterms:references (dc.relation.references) will be added to the dublin core schema. These elements exist in the dublin core standard, but are missing from the Dome metadata registry.
- dc.relation.isbasedon will be mapped to dcterms:source (dc.source.none). There is no dcterms:isbasedon element.
- dc.relation.uri will be mapped to dcterms:relation (dc.relation.none)
- dc.relation.type will be mapped to vra(?):worktype in a new VRA Core schema that will be established in the Dome metadata registry.
We need to understand how DSpace uses the dc.source.none and dc.source.uri fields to avoid any conflict in mapping dc.relation.isbasedon to dc.source.none.
Rights Elements
- dc.rights.uri will no longer be used in Dome (there are currently no populated dc.right.uri fields).
...
The only complication with this is shared with language. We would like to change the name of a field without changing the contents and we don't have as nice a way to reexport subjects from IRIS/AT and then reimport to Dome, replacing the current subject fields. Carl says if we are already doing this for names and dates, especially since we'll probably have to do this for every record it will not add much effort or complexity to throw this field and the language field in with the rexport/reimport.
Type Elements
- We will identify the one vocabulary that we will use for the DOME Core type field. This vocabulary will be mapped to dcterms:type (dc.type.none).
- When a type vocabulary is defined within a specificaiton (for example, VRA Core type), we will use the identified field within that schema. We will add the schema and field to the Dome metadata registry.
- For type vocabularies that are not defined within a metadata specification (for example, local type vocabularies) we will use a 'localType' (need to find a better name) element in our homegrown DOME metadata schema (current prefix: custommd).
Currently type values from all vocabularies are entered in a dc.type.none element. Separating the values by vocabulary from existing Dome records will be tricky.
Metadata Manipulation Notes
...