The priorities below are based on the October 2011 community survey on improving metadata support. DCAT has interpreted the community priorities based on the survey results and have fleshed out those priorities with detailed descriptions, specifics and examples. Anyone should feel free to add their feedback as we will eventually evolve this page into a project plans. mproved
Improved (or more transparent) flexibility:
- simplify/make local customizations more accessible through UI:
- simplify where/how things are done - bring more functionality to the UI or the metadata registry
- create more educational/tutorials on how/where to do things (i.e. how to plug in metadata schemas)
- import/export to metadata other than DC (like in Eprints where you pick a format for export)
- expose RDF triples
Update the Qualified Dublin Core registry in DSpace to the latest standards of the DCMI
- as discussed in the survey, link to the relevant schema on DC website and lock down (allow adds, but not changes), isolate where customizations are done
- prohibit changes and deletions that would break compliance with the standardized default Dublin Core metadata schema, create separate place for local customizations
Hierarchal metadata:
- add functionality / move towards relational aspect functionality - like MODS
- allow relationships between community/collection/bitstream metadata
- possible iterative solution - create functionality that emulates hierarchal behavior
- example: adding in author affiliation
- example: metadata on bitstream - related back to items
...
Enhanced metadata for Communities, Collections and/or individual Files (bitstreams)
Update the Qualified Dublin Core registry in DSpace to the latest standards of the DCMI
- as discussed in the survey, link to the relevant schema on DC website and lock down (allow adds, but not changes), isolate where customizations are done
...