...
LEVEL OF COMMUNITY EFFORT: likely low to medium
LEVEL OF DEVELOPER EFFORT: likely low to medium
- *?Citation metadata?: * perhaps use a subset of PRISM for citation metadata include it as a new namespace
...
- depends on what schema (XML based schemas are more complex - dspace doesn't support XML - MODS,
- MODS implemenation better done after fedora intergration since it is XML
- need metadata expert
- 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
- *?Citation metadata?: * perhaps use a subset of PRISM for citation metadata include it as a new namespace
6) Improved (or more transparent) flexibility:
LEVEL OF COMMUNITY EFFORT: likely high
LEVEL OF DEVELOPER EFFORT: likely high
- 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
7) Enhancing the metadata available for Communities, Collections and Files (bitstreams)
LEVEL OF COMMUNITY EFFORT: likely high
LEVEL OF DEVELOPER EFFORT: likely high
- get discussioin started and find some dev interested in archtecting it
- very large changes, every single object in DSpace, will present and upgrading challenging to convert to an entirely different object model could be preparation for integration with Fedora - re-factoring how best we can re-work dspace to support in the next few versions - not a quick jump