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 On Tuesday, April 16, 2019 at 11:41:54 AM UTC-4, Tim Donohue wrote: > > 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 > > On Mon, Apr 15, 2019 at 8:00 PM <[email protected] <javascript:>> wrote: > >> 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 <[email protected]> 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, [email protected] >>>> 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 >>>>> <https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/QDC.properties> >>>>> ? >>>>> >>>>> How must oai.cfg be adjusted to allow for the export of QDC? Would >>>>> this be done soley through this oai.cfg >>>>> <https://github.com/DSpace/DSpace/blob/master/dspace/config/modules/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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> 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 >>> >>> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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 > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
