...
Potential need to adopt RIOXX for SHARE: http://rioxx.net/v1-0/ Will need to be more attentive to funders and grant numbers even in absence of SHARE. Compliance-driven need.
Bram Luyten (Atmire) worked to ensure DSpace/RIOXX compliance.
Will definitely need to maintain DC alongside DCTERMS. Question of whether to keep legacy qualified DC or to migrate to local. Ability to crosswalk dc.title to dcterms.title, not absolutely a requirement to migrate to that element in DSpace metadata.
Mission for DSpace 5: Death to the Qualifiers.
RIOXX using DCTERMS for what DSpace currently relies on QDC for; uses DC where DSpace uses DC.
Potential of additional schema to ship with DSpace: RIOXX, ETD schema.
Next Steps
1) Highest priority is to examine qualified fields-- we will start migration with this set.
Example: dc.contributor.advisor–> uketd:advisor ? Going beyond DC, DCTERMS, local, DSpace. Keeping an eye on developments around ETD and research data schema.
QDC list pulled from Full Draft mapping of QDC, DCTERMS, and local schema
For ongoing re-evaluation of QDC mappings, see Re-evaluation of QDC mappings
QDC currently in DSpace, with suggestions for mappings from DCAT Metadata Team members.
QDC in DSpace |
---|
dc.contributor.advisor |
dc.contributor.author |
dc.contributor.editor |
dc.contributor.illustrator |
dc.contributor.other |
dc.coverage.spatial |
dc.coverage.temporal |
dc.date.accessioned |
dc.date.available |
dc.date.copyright |
dc.date.created |
dc.date.issued |
dc.date.submitted |
dc.date.updated (SWORD element) |
dc.description.abstract |
dc.description.provenance |
dc.description.sponsorship |
dc.description.statementofresponsibility |
dc.description.tableofcontents |
dc.description.uri |
dc.description.version (SWORD element) |
dc.format.extent |
dc.format.medium |
dc.format.mimetype |
dc.identifier.citation |
dc.identifier.govdoc |
dc.identifier.isbn |
dc.identifier.ismn |
dc.identifier.issn |
dc.identifier.other |
dc.identifier.sici |
dc.identifier.slug (SWORD element) |
dc.identifier.uri |
dc.language.iso |
dc.language.rfc3066 (SWORD element) |
dc.relation.haspart |
dc.relation.hasversion |
dc.relation.isformatof |
dc.relation.ispartof |
dc.relation.ispartofseries |
dc.relation.isreferencedby |
dc.relation.isreplacedby |
dc.relation.isversionof |
dc.relation.replaces |
dc.relation.requires |
dc.relation.uri |
dc.rights.holder (SWORD element) |
dc.rights.uri |
dc.source.uri |
dc.subject.classification |
dc.subject.ddc |
dc.subject.lcc |
dc.subject.lcsh |
dc.subject.mesh |
dc.subject.other |
dc.title.alternative |
2) Have DSpace metadata proposal formalized for Open Repositories, deadline of February 1. Also Dublin Core 2014.
3) Non-intrusive approach to modifying hard-coded metadata values via JIRA tickets
...