I was working on the crosswalk that generates DataCite metadata for DOI submissions through EZID, and saw a potential problem. So long as an Item has one value each for dc.rights and dc.rights.uri, it's easy enough to compose a <rights rightsURI='foo'>bar</rights> element. But I don't think there is any rule requiring only single values here. Multiple rights statements are actually rather common on software these days, and I don't see why they wouldn't be useful with some works of any type.
Notice that it's not unreasonable to have both paired and unpaired
values of dc.rights. I don't see any support for sparse ordered lists
of metadata values, so how to ensure that the pairs line up?
So, please discuss:
1. If and when we build real schema support for metadata namespaces,
we may want to include cardinality rules. Some fields may not
have a sensible meaning for multiple values. We may need to
*require* at least one value for other fields.
2. dc.rights/dc.rights.uri would seem to be a nice entering wedge for
support of hierarchial metadata structures, since clearly some
uses of these fields (CC for example) are naturally paired.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
