Looking for input on Improving Metadata Support in DSpace 1.8
During the DSpace Developers meeting at Open Repositories there was a general consensus that there lies a big challenge and opportunity in improving the metadata support in upcoming DSpace releases. Because there are many different tasks, both from an organizational/policy point of view, as well as developer coding work, we ask your input to make it clear where the priorities lie and what the focus should be.
There is also a strong need for involvement of people who actually want to take on this work, so please indicate whether you are interested to commit some time, either as a repository manager (who are subject matter expert in this case) or as a developer.
Which challenges could and should be tackled ?
Please indicate for each of these whether you recognize this as a priority or not. Realize that we won't be getting anywhere if you declare everything as a priority or nothing at all. So even if all of these topics are very important to you, please try to identify the ones that would make your life or the lives of your users and management a lot easier.
1. Updating the Qualified Dublin Core registry in DSpace to the latest standards of the Dublin Core Metadata Initiative
Problem: The registry in DSpace hasn't been changed for the last 8 years. Standardization on this matter would really help compatibility with other systems and benefit from the learnings that took place in the DCMI community.
Related links: https://jira.duraspace.org/browse/DS-805 https://jira.duraspace.org/browse/DS-433
Is this a priority to you: .............. (your feedback)
Do you wish to contribute your time (either as a developer or repo admin): ................... (your feedback)
2. Enable Metadata on all DSpace Objects
Problem: Each DSpace object (Item, collection, community, ...) is being treated differently with regards to metadata. Since the system to attribute metadata to items is robust and benefits from great flexibility, there would be a benefit to apply this approach to all DSpace objects.
Related links: https://wiki.duraspace.org/display/DSPACE/Metadata+For+All|display/DSPACE/Metadata+For+All||\ (-----------> Sarah, Val, Elin, Is there a better link for this ?)
Is this a priority to you: .............. (your feedback)
Do you wish to contribute your time (either as a developer or repo admin): ................... (your feedback)
3. Add metadata authority controls / vocabularies to the data model
Problem: Although you can manage the metadata scheme in the data model, there is little out of the box support for vocabularies (like DCMI Type) and encoding schemata
Related links: ( Sarah, Val, Elin, Is there a better link for this ?)
Is this a priority to you: .............. (your feedback)
Do you wish to contribute your time (either as a developer or repo admin): ................... (your feedback)
4. Standardize the default namespaces
Problem: Instead of creating an own, customized metadata schema, many people edit the default registry effectively breaking compliance with the standard. Supposed the namespace is complete in the default registry, should it be editable at all? Addressing this would enable easier migrations/updates of the standard namespace in the future and would enforce/enable institutions to keep better track of their own customizations to the metadata schema.
Is this a priority to you: .............. (your feedback)
Do you wish to contribute your time (either as a developer or repo admin): ................... (your feedback)
5. Move metadata related configurations from dspace.cfg to the database
Problem: There are no verifications or safeties when editing/removing metadatafields in your schemas that are used in dspace.cfg for configuring browse parameters, search indexes, visibility (on simple & full item view). Not only will moving this to the DB and creating webUI config & hints for this solve this problem, it will be a huge increase in usability for the repository managers.
Is this a priority to you: .............. (your feedback)
Do you wish to contribute your time (either as a developer or repo admin): ................... (your feedback)
