Title: Message Title
|
|
|
|
Valid comment! The reason why I didn't consider it yet was because I didn't know what the effects would be of such an "update" if people already had a dcterms namespace with elements in it.
Looking at https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/administer/MetadataImporter.java it seems like loadType is already geared to deal with this, skipping the ones that already exist.
In my view, this leaves two options:
- including the update of existing schema's in the standard upgrade. For people already using a dcterms schema, this would have the consequence that it may get filled with additional fields
- Make it optional & document it well.
I lean towards the first option, thinking that only a very small number of people may be already using a dcterms schema. And if not, getting these extra (Standard!) fields in there is not such a bad side affect.
|
|
|
|
|
|
|
|
DSpace's current implementation of Dublin Core was a subset or simplified version of the Dublin Core standard created by OCLC. Since the first release of DSpace, Dublin Core has undergone major revisions. DC version 1.1 was implemented in 2007 with 15 base elements a subset of the larger DCMI. Some users are currently misusing the DC standards, or lac...
|
|
|
|
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
