-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.0
-
Component/s: DSpace API
-
Labels:
-
Attachments:
-
Comments:19
-
Documentation Status:Not Required
Many have wished for the flexibility of DSpace's operable metadata infrastructure, which is specific to Item, to be available in other types such as Community and Collection. Support for operable metadata should be pushed down from Item to DSpaceObject so that all DSOs can use it.
I recognize that there are a number of other ways in which DSpace's metadata support could be generalized, but I think that it's useful to separate out this aspect, as it is in some ways foundational to much of the other work that has been proposed, and could be done quickly and with minimal disruption of other code.
Some discussions and related work:
- is related to
-
DS-2395 ItemDAO* still uses bundle.name (now moved to metadatavalue)
-
- Closed
-
-
DS-2396 Checksum checker and bitstream.user_format_description on version 5.0rc2
-
- Closed
-
-
DS-2166 DSpace 5.0 Upgrade process is broken (related to Metadata 4 All)
-
- Closed
-
-
DS-2164 Metadata4All Bug with EPerson
-
- Closed
-
-
DS-2788 Performance degradation of SOLR Discovery indexing in DSpace 5
-
- More Details Needed
-
-
DS-1134 multilingual metadata for communities/collections
-
- Closed
-
- required by
-
DS-1782 DSpace needs local object identifiers
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...