OAI error OJS 2.4.8.1

Software Support
1

We received information from WorldCat that they could not sync schedule due to error on OAI page that is generated by our
OJS 2.4.8.1

https://eap-iea.org/index.php/eap/oai

Please advise how to fix that.
Thanks

2

What specific error did they report? You have some weird looking setSpecs, but OAI seems to be responding normally.

3

Hello,
This is error message they sent:
The sync schedule for your collection, Scientific Critique : eap:SC, in the repository http://eap-iea.org/index.php/eap/oai
has been disabled by the WorldCat Digital Collection Gateway after multiple automated retries. The repository reports that it is
unavailable at the URL you have set up. If the issues preventing the sync from succeeding have been corrected you can re-enable the
collection by logging in to the Gateway and re-setting the sync schedule.
Most Recent Errors:
2017-04-04T11:10:56
OAI harvest check failed for repository.
Error prior to running batch. Repository/Collection error.(OaiHarvesterCheckError)
Report timed out.(Reporting)
2017-04-03T10:10:13
OAI harvest check failed for repository.
Error prior to running batch. Repository/Collection error.(OaiHarvesterCheckError)
2017-04-03T05:09:01
OAI harvest check failed for repository.
Error prior to running batch. Repository/Collection error.(OaiHarvesterCheckError)
2017-01-03T05:00:40
Harvester error.(HarvestError)

4

Do you actually have a section name “Scientific Critique” (abbreviation SC)? I see “Scientific Critique and Controversies” (abbreviation SCC) on your list of OAI Sets, but not eap:SC.

Another potential concern is the message “Report timed out.(Reporting)”, which might suggest an OAI run longer than the servers PHP or Apache timeouts, but that might be a red herring.

5

It is possible that one editor in journal changed title of that section in journal. Is that so big problem that prevents successful OAI harvesting?

6

It may be as simple as letting WorldCat know that the collection “eap:SC” no longer exists, but a new collection “eap:SCC” should be added.

7

I contacted their support so we will see what they will say. I will let you know if there is something that may be technically important for OJS.

Thanks on support

8

Hi @vvucic,
just in case it may help, there also seems to be a matter of using the http versus the https protocol, as explained here http://forum.pkp.sfu.ca/t/failed-testing-oai-support-in-worldcat-digital-collection-gateway/5027/3?u=afisher