Recommendations towards “Updating the Qualified Dublin Core registry in DSpace to the latest standards of the DCMI,” a priority identified in the October 2011 community survey on improving metadata support. It also seeks to comply with the proposal to Standardize the Default Namespace. Discussion of this issue thus far is stored as a DCAT Discussion Forum topic, "Updating the Qualified Dublin Core registry in DSpace."

Recommendation (tentative, pending further community input):

• Update current “DCMI Terms” metadata registry to QDC
  
  • provide brief definition and reference (link?) for "DCMI Terms" and "QDC"
  • provide reasoning - why is compliance with QDC (ultimately DCTERMS) important/desirable
  • provide a few specific examples of what fields would change from/to, perhaps identify some of what the basic differences would be from current DCMI
• Add DCTERMS as new, parallel metadata registry
  
  • provide brief definition and reference (link?) for "DCTERMS"
  • provide reasoning - why is compliance DCTERMS important/desirable
  • provide a few specific examples of what fields would change from/to, perhaps identify some of what the basic differences would be from current DCMI
• Lockdown registries, offering migratory tools to pull out local customizations and push into new local schema. Make it possible but not easy to delete or edit elements in QDC and DCTERMS registries. Continue to enable the addition of qualifiers in the QDC registry
• Clarify end result - how many metadata registries DSpace will ship with – 3?: 
  
  • 1) QDC - which will be an up date of the current DCMI, and will set as the default metadata schema 
  • 2) DCTERMS - which will be an optional metadata schema, ultimate goal of replacing QDC at some point in the future
  • 3) Local schema - which would ship empty, for the purpose of local customizations
    
    

Main goal of these recommendations:

...

(please add any JIRA tickets that could be affected by this proposal!)

It would be useful if we could make a guess at which JIRA issues would be RESOLVED (issue will be specifically addressed by the project) vs. which ones will be AFFECTED (a decision will have to be made that may impact, but not necessarily resolve the issue) vs. which ones are RELATED (issues that relate in some way to metadata schema options in DSpace, but we either aren't sure it will be resolved or it will likely not be resolved) to the DC update project.

DS-125: Date type can't be repeatable in the submission

...