Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
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
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
On Mon, May 09, 2011 at 10:44:32AM +0100, Graham Triggs wrote: IIRC, this isn't particularly well documented. But it is possible to create import packages using multiple metadata schemas. http://www.dspace.org/1_7_0Documentation/System%20Administration.html#SystemAdministration-Configuringmetadata\prefix\.xmlforDifferentSchema DS-534 addressed the documentation of this feature. How could we improve it further? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgp99Vj0O8Ii9.pgp Description: PGP signature -- 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
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
On 10 May 2011 16:44, Mark H. Wood mw...@iupui.edu wrote: http://www.dspace.org/1_7_0Documentation/System%20Administration.html#SystemAdministration-Configuringmetadata\prefix\.xmlforDifferentSchemahttp://www.dspace.org/1_7_0Documentation/System%20Administration.html#SystemAdministration-Configuringmetadata%5Cprefix%5C.xmlforDifferentSchema DS-534 addressed the documentation of this feature. How could we improve it further? I said IIRC!! I didn't actually look at the current docs :) -- 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
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. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
On 9 May 2011 09:31, Robin Taylor robin.tay...@ed.ac.uk wrote: 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 ? IIRC, this isn't particularly well documented. But it is possible to create import packages using multiple metadata schemas. The trick is to have separate metadata files for each schema. 'dc' goes into the standard dublin_core.xml, But for any other schema, you need to create a file called: metadata_prefix.xml The contents of which is structured just like dublin_core.xml, except on the dublin_core element, you need to include a schema=prefix attribute. G -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
Thank you Graham - I have not tried creating two metadata.xml files for a single item from two different schemas but I will and will report the results. -Simon From: Graham Triggs [mailto:grahamtri...@gmail.com] Sent: Monday, May 09, 2011 2:45 AM To: Robin Taylor Cc: Brown, Simon Contractor, Digital Consulting Services; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest On 9 May 2011 09:31, Robin Taylor robin.tay...@ed.ac.ukmailto:robin.tay...@ed.ac.uk wrote: 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 ? IIRC, this isn't particularly well documented. But it is possible to create import packages using multiple metadata schemas. The trick is to have separate metadata files for each schema. 'dc' goes into the standard dublin_core.xml, But for any other schema, you need to create a file called: metadata_prefix.xml The contents of which is structured just like dublin_core.xml, except on the dublin_core element, you need to include a schema=prefix attribute. G -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
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. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Conflict with mixing metadata schemas and batch ingest
I am using version 1.7. I hope I can convey the specifics of this complication correctly, please bare with me. I am helping to set up a DSpace repository to initially contain a Thesis collection, but then in the future to contain many collections of different types with their own metadata needs. We would really like to use custom metadata schemas to separate out the metadata specific to certain collections but also use qualified Dublin Core for all metadata. For, example for theses we would like to have a 'dc.thesis.degree', but you can only have the 'dc' prefix if you use the default metadata schema!!! Here are the specifics of the project: We are planning to use the batch ingest tool to load the retrospective thesis content (~20,000 items) into DSpace. We have decided upon using a specific standard set of Dublin Core metadata elements as defined by the NDLTD for ETDs (http://www.ndltd.org/standards/metadata/etd-ms-v1.00-rev2.html) Although these are Dublin Core elements, some are specific only to theses and we would therefore prefer to use a custom metadata schema to keep them separate from the default schema. The complication is 2 fold: 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. 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. Ideally, I want to have a few custom DC metadata elements for theses in a custom metadata schema and mix these with the main DC elements for things like author and title, but have all metadata prefixed with 'dc'. Is there any way you can make DSpace to allow the 'name' of two different schemas to be 'dc' Thank you for any input you have into this. Simon Brown Digital Consulting Services Supporting the Dudley Knox Library, Naval postgraduate School scbr...@nps.edu 831.656.3574 Phone 831.656.3238 Fax -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Conflict with mixing metadata schemas and batch ingest
I'm sorry about my confusion. I meant to say: 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 an item in the metadata XML. -- View this message in context: http://dspace.2283337.n4.nabble.com/Conflict-with-mixing-metadata-schemas-and-batch-ingest-tp3504507p3504556.html Sent from the DSpace - Tech mailing list archive at Nabble.com. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
