Title: Message Title
|
|
|
|
I think that only Community and Collection currently look like they have metadata in the same sense as Item. But they do, so I need to discuss namespace design.
These object types have several fields in common: COPYRIGHT_TEXT, INTRODUCTORY_TEXT, SHORT_DESCRIPTION and SIDEBAR_TEXT. Should Community's COPYRIGHT_TEXT, for example, be the same metadata type as Collection's, or should we have e.g. dspace.community.copyright and dspace.collection.copyright?
It's possible, too, that some of these "naturally" should be single-valued. I'm uneasy about having multiple COPYRIGHT_TEXTs for example. Please discuss.
|
|
|
|
|
|
|
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 m...
|
|
|
|
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
