...
* 84% of respondents use DSpace or plan to use DSpace
* According to respondents, the top 5 metadata schemas to include in DSpaceAside from a vast majority (*include figure) who indicated that Dublin Core was the most relevant standard to them, there were needs to support ingest and export for following standards, in order of priority: Dublin Core, MODS, PREMIS, Open URL ContextObject, ETD-MS (* removed "include" here because that's too vague**)
* 72% of respondents indicated it is a priority to add metadata authority controls/vocabularies to the data model
...
* 56% of respondents indicated it is a priority to update to update the Qualified Dublin Core registry to the lastest latest standards of the DCMI.
* 54% of respondents indicated would not have objections to prohibiting changes/deletions that would break compliance with the standardized default Dublin Core metadata schema
...
From the survey it is clear that there are improvements to metadata support in DSpace that could help solve some common challenges for many organizations. Many will agree that there is no one size fits all repository software. DSpace is the most popular repository software, used by over 1,000 organizations for a reason – it is relatively easy to get a repository up and running. If we are to add more complexity/flexibility to DSpace we We need to be careful that adding functionality it is not at the cost of making it more difficult for the vast majority of DSpace use cases. In addition, there are existing software solutions that provide for the ultimate in flexibility, namely Fedora. With that in mind, DCAT has proposed exploring the following priorities with the DSpace Committers/Developers and the user community:
1) Adding metadata authority controls/vocabularies to the data model: Since there is an existing add-on for controlled vocabularies (INSERT LINK), DCAT interprets this to mean that the rights to use a controlled vocabulary and possibly link from an external source. Some examples would be the National Agricultural Library (linked open data) and the National Library of Medicine (subject based).
2) Updating the Qualified Dublin Core registry to the current DCMI standards and locking it down (allow adds, but not changes or deletions that would break compliance) as well as isolating where customizations are done to ensure better standardization INSERT LINK TO DC TERMS, adopting the newer DC Terms namespace (as an evolutionary step over the 15 original elements in the dc namespace). DCAT also recommends that the default configuration should separate out standardized DC metadata, administrative metadata and local customizations into distinct metadata schemas. Repository administrators should be at least informed and furthermore actively discouraged to apply modifications to the standardized DC metadata that will effectively break compliance. Therefor, putting those modifications in a separate metadata schema will lower the risk of breaking compliance.
3) Enhancing the metadata available for Community, Collections and Files (bitstreams)
...