Hi Simon, The qualifier bit that DSpace allows is really just descriptive documentation and not part of the DC spec. Have a look at the Index of Terms in here http://dublincore.org/documents/dcmi-terms . Once upon a time DC was restricted to the 15 terms listed in the 'legacy' namespace, they were later augmented with some more terms added in the 'terms' namespace. DSpace's metadata registry has become a bit outdated over the years and is a sort of mixture of the two with some extras and with our own qualifiers added. What you find is that where the metadata is exposed to the outside world eg for OAI harvesting purposes, the qualifiers are stripped away and some naming corrections are made.
Hope that helps, Cheers, Robin. On Mon, 2011-05-09 at 16:16 +0100, Brown, Simon Contractor, Digital Consulting Services wrote: > Hi Robin, > > Thank you for your insight into this. Does qualified DC terms not count > strictly as DC? For example, does 'contributor.corporate' for a corporate > author not strictly count as DC for 'contributor'? This is something that's > not clear to me from dublincore.org. > > Thanks again, > -Simon > > -----Original Message----- > From: Robin Taylor [mailto:robin.tay...@ed.ac.uk] > Sent: Monday, May 09, 2011 1:32 AM > To: Brown, Simon Contractor, Digital Consulting Services > Cc: dspace-tech@lists.sourceforge.net > Subject: Re: [Dspace-tech] Conflict with mixing metadata schemas and batch > ingest > > Hi Simon, > > > > 1) That DSpace uses the unique name of the metadata schema as the > > prefix for metadata elements but we would rather have the ‘dc’ prefix > > for any Dublin Core metadata whether from the default or custom > > metadata schemas. > > > > The short answer is, don't do it :) The prefix 'dc' represents the > Dublin Core namespace in DSpace. Its impossible to have 'dc' represent 2 > different namespaces. In addition, Dublin Core is a published standard > with a fixed set of terms. Over the years DSpace's metadata registry has > become a little polluted with terms that are not strictly DC but if > anything the intention would be to tidy that up and encourage people to > use other schema for non DC terms. I would strongly urge you to use > something other than DC for non-DC terms. Its always nice if you can > find another published standard that fits your needs but you can always > define a local one if none are available. Probably not what you wanted > to hear, sorry. > > > 2) While you can mix metadata elements for an item from multiple > > schemas in manual submission, for the batch ingest you can only > > specify a single schema for the batch. > > I haven't used this in recent times but I thought you could mix schema. > I know there are lots of references to the 'Dublin Core metadata' in the > code but I thought that was just a hangover from the days when only > Dublin Core was used, and in fact you could mix metadata schema. have > you tried this out ? > > Cheers, Robin. > > > ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
