Thank you Kimberly--I meant to send my response out to all. ;-) I look forward to hearing more.
Deborah, Thank you, this is excellent information. We do not host our own DSpace, but I'm glad to know of a backend solution. Maybe our vendor can implement these changes. All best, Yvonne On Thu, Oct 12, 2023 at 10:16 PM Kimberly Chapman < librariankimbe...@gmail.com> wrote: > Hi Yvonne, > > We have been successfully harvesting the dc.date.issued field into Primo > for a few years now. > > I can find out which of my colleagues can discuss what they did on the > Alma/Primo side and connect you via separate email. > > Note that we’re currently on a hosted DSpace 5 instance. > > Al best, > > Kimberly Chapman > University of Arizona Libraries > > > Sent from my iPhone > > On Oct 12, 2023, at 5:34 PM, Fitchett, Deborah < > deborah.fitch...@lincoln.ac.nz> wrote: > > > > Kia ora, > > > > It sounds like you’ve tried a lot of things on the Primo side. What about > modifying the OAI feed on the DSpace side? > > > > There are two options for doing this: > > > > 1. If you don’t think any other harvesters would want all the > different dates, you could simply edit the crosswalk so that instead of > crosswalking all the dc.date.* options, it only uses dc.date.issued > > 2. Alternatively you could create a separate “context” so that most > harvesters use your default context but Primo uses a dedicated one with > only the data you want there. Then you can leave the crosswalk alone for > other harvesters, but edit the crosswalk for Primo. > > > > Eg we have: > > “request” > https://researcharchive.lincoln.ac.nz/dspace-oai/request?verb=ListSets as > our default context > > “catalog” > https://researcharchive.lincoln.ac.nz/dspace-oai/catalog?verb=ListSets as > the context for harvesting into Primo > > > > (At the moment our crosswalks are practically the same, For Reasons, but > the option is there. 😊 ) > > > > See > https://wiki.lyrasis.org/display/DSDOC7x/OAI+2.0+Server#OAI2.0Server-AdvancedConfiguration > for documentation. > > > > Deborah > > > > *From:* dspace-community@googlegroups.com < > dspace-community@googlegroups.com> *On Behalf Of *Yvonne > *Sent:* Friday, October 13, 2023 5:06 AM > *To:* DSpace Community <dspace-community@googlegroups.com> > *Subject:* [dspace-community] Pulling dc.date.issued into Alma > > > > *Caution:* This email originated from outside our organisation. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > Hello DSpace Community, > > > > The State University of New York--64 campuses--use ExLibris's Alma/Primo > VE. Alma has a method to import digital collections from the major players > in repositories, including, of course, DSpace. > > > > We have been working to import collections from DSpace so they are > discoverable in Primo VE, but we have not found a way to get the > dc.date.issued to display in the item records. No matter what we have > tried, dc.date.accessioned is the displayed field. As with other Dublin > Core fields, precedence is given to alphabetical order, and unfortunately > the field we want is at the bottom of the list. > > > > Has anyone out there successfully imported DSpace collections into Alma > with dc.date.issued being displayed in the item record? > > > > We have tried normalization rules, regex, and the sorting function in the > import profiles, and none have made any difference in the result. > > > > Many thanks for your kind attention. > > Yvonne Kester > > SUNY Library Services > > -- > 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 Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-community+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/CAKZKP2At4WPDVAobWvf7OiPQ5PNuATDAtAtOts-5tmY%3DnHcneg%40mail.gmail.com > <https://groups.google.com/d/msgid/dspace-community/CAKZKP2At4WPDVAobWvf7OiPQ5PNuATDAtAtOts-5tmY%3DnHcneg%40mail.gmail.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 Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-community+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524EA5D9A87C5E535F5D2C4C5D2A%40ME3PR01MB7524.ausprd01.prod.outlook.com > <https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524EA5D9A87C5E535F5D2C4C5D2A%40ME3PR01MB7524.ausprd01.prod.outlook.com?utm_medium=email&utm_source=footer> > . > > -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-community+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/CAKZKP2Bq5ywRVnkk%3DNBrZ87kzGz6mupJkJ_kBpnrtrRkb98EWQ%40mail.gmail.com.
