OAI-PMH DSpace 7.2

[Jan Broulím]

Hi,

we installed DSpace 7.2 and migrated the database from our previous version.

Everything seems to be working fine, seen here - https://sulis29.zcu.cz/home,

however there is something missing/bad within OAI-MPH interface , can be checked on https://sulis29.zcu.cz/server/oai/.

Do you have any suggestion what might help?

Thanks

Jan

[darryl....@usask.ca]

Jan, did you remember to run the OAI import task -- https://wiki.lyrasis.org/display/DSDOC7x/OAI#OAI-OAI-PMHServerMaintenance

I had some similarly weird issues with OAI and it was because I forgot to run that, and thus had no actual OAI data to serve up.

- Darryl

[Jan Broulím]

Yes, I also tried 'dspace oai import -c' for full import
Any suggestions? Do you have some instance where can be seen how dspace oai should look like? https://sulis29.zcu.cz/server/oai seems not working properly.

Thanks

[Jan Broulím]

The same I can see on the testing website https://api7.dspace.org/server/oai

Is this OK?

Jan

[DSpace Technical Support]

Hi Jan,

Put a trailing slash on that OAI URL and it should work.  For instance: https://api7.dspace.org/server/oai/ works... but https://api7.dspace.org/server/oai fails to load the visual styles.  Right now there's a known bug that CSS/styling doesn't load right if you miss that trailing slash...but that doesn't impact OAI-PMH behavior, as the CSS/styles are just for human readability. https://github.com/DSpace/DSpace/issues/3059

Tim

[Jan Broulím]

Hi Tim,

thank you. With trailing slash CSS works, but what about the content? E.g. https://api7.dspace.org/server/oai/ - there is a red message "Invalid context" and the page is empty. UI points to https://demo7.dspace.org, where I can see that it is not empty.

Is this correct?

The same behaviour is with our Dspace7.2 and already performed oai imports.

Jan

[Tim Donohue]

Hi Jan,

The "invalid context" page is showing you that you haven't specified which context you want OAI-PMH to use & then lists all the available contexts you can chose from.  So, that error is just telling you the options that are available in DSpace so that you can choose which you want.

If you click "Identify" on any of those Contexts (e.g. the "Default Context") you'll see the OAI-PMH results for that OAI context, e.g. clicking on "Identify" under "Default Context" brings you here: https://api7.dspace.org/server/oai/request?verb=Identify   From that "Identify" page you'll see the repository info, and then (in the upper right) links to all the sets, records, etc in your OAI-PMH index.

This human-readable HTML screens here are all just for ease of finding the OAI-PMH endpoints. They have no impact on harvesting by another site, as OAI-PMH itself is a protocol that has no human-readable interface.

Tim

[Jan Broulím]

Hi Tim, thank you for the explanation!

However, then I have a question - what might be the source of our error; when trying the same on our DSpace: https://sulis29.zcu.cz/server/oai/request?verb=Identify

we obtain "HTTP Status 500 – Internal Server Error".

Baskend can be checked here: https://sulis29.zcu.cz/server

Frontend here: https://sulis29.zcu.cz/

"dspace oai import -c" was finished successfully

Jan

--
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 a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/pMOWq7iaHWw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/20ed9529-abdb-45f7-b2d2-ab214b3d6451n%40googlegroups.com.

[Tim Donohue]

Hi Jan,

A 500 error is a general error that just means "something went wrong on the backend".  You should check your dspace.log files for the details behind the error.  It can be caused by a variety of reasons, so the only way to solve it is to check the specifics in the logs (after reproducing the error).  Here's more information on troubleshooting errors: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim