This page is outdated and kept for archival purposes only. It contains the proposal and discussion of the "Metadata for all DSpace objects" concept. The actual implementation of this concept in DSpace 5 is outlined in Metadata for all DSpace objects. |
This is based on Claudia's comments in the commiter list and the topic discussed elsewhere. Goals should be to expand on this and relate it to other projects/efforts. For instance, the async release proposal will now include establishing a true "API" for DSpace legacy objects and placing this in the "modules" directory where other projects can depend on it. |
- enable metadata for all dspace objects (communities, collections,
items, bundles, bitstreams, metadatavalues, epersons, groups).
- revise the default metadata registry see
https://jira.duraspace.org/browse/DS-433
- not only manage the metadata schema, but also related vocabularies
(like DCMI Type) and encoding schemata.
- enable multiple metadata schemas per default (dcterms, an
administrative one and a couple of standard namespaces like those used
for prism)
- think about whether standard namespaces (supposed the namespace is
complete in the default registry) should be editable at all. An instance
can always use it's own namespace.
- manage metadata field related configurations like hide option,
display, browse, search etc. in the db rather than in dspace.cfg. At the
moment one can delete/move a field which via the UI which is used as
configuration parameter
- get rid of the deprecated DCValue