...

• Is it possible to ultimately implement DCTERMS with full functionality? What changes to the data model will be necessary?
• If both QDC and DCTERMS are included, which will be considered the default? Is this projected to change?
• How will this proposal integrate with other suggested changes to DSpace metadata, including Proposal for Metadata Enhancement? How might it affect integration with Fedora? How might it affect other desired changes to metadata in DSpace, including implementing functional structured metadata such as MODS, METS, and PREMIS?
• What challenges will this proposal present—or solve—for harvesting?
• To enable repositories to migrate existing metadata to QDC and DCTERMS registries, we will need to develop robust tools for repositories to deploy. One outstanding issue is the design and development of these tools.  

Relevant JIRA tickets:

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

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

DS-202: Metadata Generator Plugin

• Not sure whether this is related. But I assume if DCMI requires some properties to be unique (for example identifiers), I guess you would need a generator to ensure unique identifiers get generated.  

DS-433: Update DublinCore Registry to Implement latest DC Standards

DS-716: Add an administrative metadata schema to DSpace

DS-800: Manage visibility of metadata fields as field attribute rather than in dspace.cfg 

DS-805: QDC schema registry needs to be brought into conformity with the current DCMI standards

DS-815: DCDate throws NullPointerException with mangled dates

DS-1134: Multilingual metadata for communities/collections

DS-1420: Exception handling for deleting a metadata field

Areas/processes that will be affected by registry update:

...