Hi Michael, thank you for reporting/sharing this.
Not a solution, but I wanted to share two observations to narrow the problem down. *DSpace 6.3 XMLUI - Fresh install* Item link: https://repository.openpolytechnic.ac.nz/handle/11072/128 Bitstream link: https://repository.openpolytechnic.ac.nz/bitstream/handle/11072/128/Curry_2002%20-%20Working%20Papers%20-%20res_wp602curryl.pdf?sequence=1&isAllowed=y Conclusion: Can't reproduce *DSpace 6.3 XMLUI - Upgraded instance & item that already exists pre-upgrade* Item link: https://ramscholar.dspace-express.com/handle/10675.1/96 Bitstream link: https://ramscholar.dspace-express.com/bitstream/handle/10675.1/96/sept%2011%2c%202006.pdf?sequence=1&isAllowed=y Conclusion: Can't reproduce Both of these installations have OAI enabled but I didn't have the time to look at the record there https://repository.openpolytechnic.ac.nz/oai/request?verb=ListRecords&metadataPrefix=oai_dc https://ramscholar.dspace-express.com/oai/request?verb=ListRecords&metadataPrefix=oai_dc Hope this helps!! Would be interested in learning whether this is specific to your institution/customization, JSPUI specific, ... as it may affect others as well !! with kindest regards, Bram [image: logo] Bram Luyten 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Gaston Geenslaan 14, 3001 Leuven, Belgium atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> On Thu, 27 Feb 2020 at 12:52, Michael White <michael.wh...@stir.ac.uk> wrote: > Hi, > > > > We’re using DSpace v6.2, JSPUI. > > > > Whilst troubleshooting an issue with a large number of broken full text > links harvested from our repository via OAI-PMH by the CORE service, CORE > reported to us that "the provided full text link in the OAI-PMH > dc:identifier field is broken." > > > > For example, for this item in our repository: > > > > https://dspace.stir.ac.uk/handle/1893/30142 > > > > - the link to the associated bitstream from this repository record is: > > > > > https://dspace.stir.ac.uk/retrieve/17570e9c-aa29-4c15-99b2-af5892853652/Revisions_Final_Chronic_wounds.pdf > > > > - however, if harvested via OAI-PMH: > > > > > https://dspace.stir.ac.uk/oai/request?verb=GetRecord&identifier=oai:dspace.stir.ac.uk:1893/30142&metadataPrefix=oai_dc > > > > - then the bitstream link in dc.identifier is wrong: > > > > <dc:identifier> > http://dspace.stir.ac.uk/bitstream/1893/30142/-1/Revisions_Final_Chronic_wounds.pdf > </dc:identifier> > > > > - i.e. it contains "-1" where I'd expect to see the bitstream UUID. > > > > And looking at the "raw" XOAI output, it appears to be wrong there too (so > not an issue with the oai_dc crosswalk?): > > > > > https://dspace.stir.ac.uk/oai/request?verb=GetRecord&identifier=oai:dspace.stir.ac.uk:1893/30142&metadataPrefix=xoai > > > > <field name="url"> > http://dspace.stir.ac.uk/bitstream/1893/30142/-1/Revisions_Final_Chronic_wounds.pdf > </field> > > > > However, a large number of the OAI-PMH bitstream links do work - e.g.: > > > > > https://dspace.stir.ac.uk/oai/request?verb=GetRecord&identifier=oai:dspace.stir.ac.uk:1893/58&metadataPrefix=oai_dc > > > > - includes the correct bitstream URL: > > > > <dc:identifier>http://dspace.stir.ac.uk/bitstream/1893/58/1/Thesis.pdf > </dc:identifier> > > > > I've tried clearing the cache, and rebuilding the OAI-PMH index, but this > issue remains. I also searched the Mailing list archives and JIRA, but > couldn't find anything that seemed to relate to this problem. > > > > I'm not sure, but my current working theory is that links to "older" > bitstreams do work because they relate to records added to the repository > before the upgrade that moved DSpace from using numeric IDs to UUIDs - but > records added since then, that make use of UUIDs, don't work . . . . (but I > haven't managed to prove this theory yet!). > > > > Has anyone else come across this? Does anyone know of a solution (I'm > happy to hack code/apply patches if required)? > > > > If you're on this version of DSpace, are all the bitstream URLs harvested > via OAI-PMH from your repository correct? > > > > If anyone has any fixes, thoughts, observations etc, they would be most > welcome as I'm currently at a loss as to how to resolve this and, given the > importance of CORE for supporting the upcoming REF here in the UK, my > library colleagues are getting a bit jumpy ;-). > > > > Cheers, > > > > Mike > > > > > *Michael White Senior Developer* > > > *Business Applications and Integrations Information Services* > > > 4B19, Cottrell > > University of Stirling > Stirling > FK9 4LA > > Tel: +44 (0)1786 466877 > Email: michael.wh...@stir.ac.uk > Web: stir.ac.uk/informationservices > <http://www.stir.ac.uk/informationservices> > > <https://www.facebook.com/stirlinglibrary/> > <https://twitter.com/isstirling> <https://www.instagram.com/isstirling/> > <https://www.youtube.com/user/infoservicesatstir> > > [image: Banner] <https://www.stir.ac.uk/> > > > > > ------------------------------ > The University achieved an overall 5 stars in the QS World University > Rankings 2018 > The University of Stirling is a charity registered in Scotland, number SC > 011159. > > -- > 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 Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/AM6PR03MB5560135CD01E0191E3F1C1C0D4EB0%40AM6PR03MB5560.eurprd03.prod.outlook.com > <https://groups.google.com/d/msgid/dspace-tech/AM6PR03MB5560135CD01E0191E3F1C1C0D4EB0%40AM6PR03MB5560.eurprd03.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- 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 Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CACwo3X2AAXtaKF9Eyq7EfhGzB2WciFNWwJ4Vi%2BS2JQ7g21BCcg%40mail.gmail.com.
