Outputting Qualified Dublin Core through DSpace's OAI- proper system configuration?

tuf0...@temple.edu

unread,

Apr 8, 2019, 10:05:07 AM4/8/19

to DSpace Community

Group-

We're configuring our DSpace and want to be able to output qualified Dublin Core through OAI. Would someone be able to give us an overview of how the system must be configured to do this?

Should be putting field values exclusively in the 'dcterms' schema fields? Or, should we be entering our field values into the 'dc' fields, but then defining a crosswalk to QDC via the 'QDC.properties' crosswalk?

How must oai.cfg be adjusted to allow for the export of QDC? Would this be done soley through this oai.cfg document, or must other changes be made also?

Forgive our inexperience, and thank you for your help!

-Gabe

tuf0...@temple.edu

unread,

Apr 10, 2019, 1:53:50 PM4/10/19

to DSpace Community

Does anyone have any insight into this? Thank you in advance for your help!

Tim Donohue

unread,

Apr 12, 2019, 5:24:46 PM4/12/19

to tuf0...@temple.edu, DSpace Community

Hello,

DSpace already supports Qualified Dublin Core through OAI. You need to specify the "metadataPrefix=qdc" parameter to your OAI queries. Here's an example of QDC through the Demo site's OAI interface: http://demo.dspace.org/oai/request?verb=ListRecords&metadataPrefix=qdc

If you need to change the Qualified Dublin Core being outputted, you should modify the "qdc.xsl" crosswalk file (which translates DSpace metadata fields to QDC). This file is located at [dspace]/config/crosswalks/oai/metadataFormats/qdc.xsl. Here's what it looks like: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl

After you update that crosswalk, I believe you will need to restart Tomcat for any changes to take effect. You also may need to clear the OAI-PMH cache ([dspace]/bin/dspace oai clean-cache).

Good luck,

Tim

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To post to this group, send email to dspace-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

--

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

tuf0...@temple.edu

unread,

Apr 15, 2019, 9:00:55 PM4/15/19

to DSpace Community

Tim-

This clears up a lot. Thank you so much!

We have one follow up question can the qdc.xsl [https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl] file be used to output fields from the "dc" schema as QDC, or just from the dcterms schema? In other words, if we want the contents of two fields, dc.contributor.committeemember & dc.contributor.author, to be distinguishable in our OAI output, can they remain 'dc' fields, or must they be in the 'dcterms' schema?

Thank you again for your help!

-Gabe

On Friday, April 12, 2019 at 4:24:46 PM UTC-5, Tim Donohue wrote:

Hello,

DSpace already supports Qualified Dublin Core through OAI. You need to specify the "metadataPrefix=qdc" parameter to your OAI queries. Here's an example of QDC through the Demo site's OAI interface: http://demo.dspace.org/oai/request?verb=ListRecords&metadataPrefix=qdc

If you need to change the Qualified Dublin Core being outputted, you should modify the "qdc.xsl" crosswalk file (which translates DSpace metadata fields to QDC). This file is located at [dspace]/config/crosswalks/oai/metadataFormats/qdc.xsl. Here's what it looks like: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl

After you update that crosswalk, I believe you will need to restart Tomcat for any changes to take effect. You also may need to clear the OAI-PMH cache ([dspace]/bin/dspace oai clean-cache).

Good luck,

Tim

On Wed, Apr 10, 2019 at 12:53 PM <tuf0...@temple.edu> wrote:

Does anyone have any insight into this? Thank you in advance for your help!

On Monday, April 8, 2019 at 10:05:07 AM UTC-4, tuf0...@temple.edu wrote:
Group-

We're configuring our DSpace and want to be able to output qualified Dublin Core through OAI. Would someone be able to give us an overview of how the system must be configured to do this?

Should be putting field values exclusively in the 'dcterms' schema fields? Or, should we be entering our field values into the 'dc' fields, but then defining a crosswalk to QDC via the 'QDC.properties' crosswalk?

How must oai.cfg be adjusted to allow for the export of QDC? Would this be done soley through this oai.cfg document, or must other changes be made also?

Forgive our inexperience, and thank you for your help!

-Gabe

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-c...@googlegroups.com.

To post to this group, send email to dspace-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Mark H. Wood

unread,

Apr 16, 2019, 10:55:54 AM4/16/19

to DSpace Community

On Mon, Apr 15, 2019 at 06:00:55PM -0700, tuf0...@temple.edu wrote:
> We have one follow up question can the qdc.xsl [
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl]
> file be used to output fields from the "dc" schema as QDC, or just from the
> dcterms schema? In other words, if we want the contents of two
> fields, dc.contributor.committeemember & dc.contributor.author, to be
> distinguishable in our OAI output, can they remain 'dc' fields, or must
> they be in the 'dcterms' schema?

Since DCMI doesn't seem to have defined a distinct element for
commmittee-member*, you may want to see if there is another metadata
namespace with some or all of the additional elements that you need,
and add it.

IOW if you are choosing only between the QDC and DCTERMS namespaces,
you'll have to invent your own nonstandard field either way, and then
how will any harvester be able to interpret it properly?

You might wish to take a look at the ETD-MS schema:
http://www.ndltd.org/standards/metadata/etd-ms-v1.1.html
but you'd have to write your own crosswalk and create a local
namespace for it in DSpace. (Unless someone has already done that,
and would be willing to share.)

-------------------
* A quick string-search of the DCTERMS specification found zero
occurrences of the word "committee".

--
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

Tim Donohue

unread,

Apr 16, 2019, 11:41:54 AM4/16/19

to tuf0...@temple.edu, DSpace Community

Hello Gabe,

That "qdc.xsl" file (and all the OAI Crosswalks) can be used to translate any internal schema into the given OAI output format. In fact, there are already examples in that qdc.xsl file of outputting "dc" schema fields into QDC. For example, this section outputs "dc.contributor.author" internal field into the "dc.contributor.author" QDC field (in this situation they are the same name, but you could just as easily translate one field to another: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl#L34-L38

All of the OAI Crosswalk files can literally translate from any schema into any other schema. So, it's up to you to define the proper "mapping" / "crosswalk" for any new or updated fields (there's no "validation" built into OAI to correct your mappings, but you can always test them via the OAI-PMH interface to see if they look right). If you get stuck, you may also wish to look at some of the other OAI Crosswalk files. For example, the "oai_dc.xsl" has good examples of mapping a field of one name to a different field. You could use a similar strategy in your qdc.xsl as needed. https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl

- Tim

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.

To post to this group, send email to dspace-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

alaw

unread,

Apr 17, 2019, 11:44:53 AM4/17/19

to DSpace Community

The etdms.xsl crosswalk, https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/metadataFormats/etdms.xsl, includes fields from etd-ms. You can also create your own custom crosswalk or modify the existing ones. For instance we are developing a custom crosswalk to export metadata for our regional Digital Public Library of America hub.

- Anne

Reply all

Reply to author

Forward