Hi, You’ll need to edit the relevant xsl file(s) in /dspace/config/crosswalks/oai/metadataFormats
You’ll then need to update the OAI index: · cd dspace/bin · ./dspace oai import -c -v · ./dspace oai import clean-cache And then your setup may vary but for us we have to wait overnight for results to show in the OAI feed. (I think this is something about SOLR re-indexing??) We haven’t used QDC but I *think* that’s probably most appropriate for this purpose. My (admittedly only semi-informed) understanding is the DC per se only uses the dc.contributor and not any further qualification. Probably best to do a bit of research about what the different standards allow to make sure that anyone harvesting your feeds can read it as intended. Deborah From: [email protected] <[email protected]> On Behalf Of Cameron, Jacob Sent: Wednesday, 30 June 2021 4:59 AM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] OAI Question Hello Everyone! Just a quick OAI question maybe someone can help me with. We added a field to our Dublin Core called dc.contributor.indigenous to recognize the indigenous names of authors of items in our collections. However when we are harvested using oai_dc or qdc it’s pulling it as dc.contributor. Is there a way for it to fix this so it shows the subfields? https://opus.uleth.ca/oai/request?verb=GetRecord&identifier=oai:opus.uleth.ca:10133/5758&metadataPrefix=qdc<https://opus.uleth.ca/oai/request?verb=GetRecord&identifier=oai:opus.uleth.ca:10133/5758&metadataPrefix=qdc> https://opus.uleth.ca/oai/request?verb=GetRecord&identifier=oai:opus.uleth.ca:10133/5758&metadataPrefix=oai_dc<https://opus.uleth.ca/oai/request?verb=GetRecord&identifier=oai:opus.uleth.ca:10133/5758&metadataPrefix=oai_dc> Thanks! Jake -- Jake Cameron, BCS(UNB) Systems Support Specialist III Information Systems and Technical Services University of Lethbridge Library Phone:(403)329-2756 This e-mail, including any and all attachments, is only for the use of the intended recipient(s) and may contain information that is confidential or privileged. If you are not the intended recipient, you are advised that any dissemination, copying or other use of this e-mail is prohibited. Please notify the sender of the error in communication by return e-mail and destroy all copies of this e-mail. Thank you. -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx<https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx> --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YTBPR01MB3919057D4F4635ADD5CDA8E184029%40YTBPR01MB3919.CANPRD01.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/dspace-tech/YTBPR01MB3919057D4F4635ADD5CDA8E184029%40YTBPR01MB3919.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>. ________________________________ "The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system." -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/SYCPR01MB5037CFF0937CD580C08097B2C5019%40SYCPR01MB5037.ausprd01.prod.outlook.com.
