I migrated our DSpace v5.4 installation to a new virtual machine running v6.3. I did so last summer. I believed I had everything working until last week when I was informed that OAI was not accessible.
We have our DSpace server accessed through another server running Apache web server which redirects requests to the internal server running DSpace. The requests come in as https://libraries.mercer.edu/ursa which is rewritten to access the DSpaceserver. The various links on the regular DSpace interface are set to include this as part of the link. So for regular usage everything has been running as expected. If you go to the page https://libraries.mercer.edu/ursa/oai you will retrieve the page successfully but the various links on the page have the form of https://libraries.mercer.edu/oai and therefore will not get directed to the right place. The very first link on the page titled “DSpace OAI-PMH Data Provider” points to https://libraries.mercer.edu/ursa/oai# and has the text “Invalid context” under it. I have manipulated the various variables in the ./modules/oai.cfg file without success. I also tried modifying the tomcat configuration by both adding a link to the directory call “ursa#oai” and adding a context line to the server.xml Can someone please tell me where those links get these destination defined? I apologize in advance if this has already been answered. I spent much of yesterday reviewing the threads on this forum and haven’t found a solution. -- 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/2aa97c5d-2bad-42d8-9083-91d70d646d13%40googlegroups.com.
