EPrints Technical Mailing List Archive

Message: #08566

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] OAI2 Harvesting Problem

CAUTION: This e-mail originated outside the University of Southampton.
Hi All,

Update on this after some mooching around. Our "ListSets" option in OAI2 no longer works and sends me to an error page:


When I redid the Divisions/Uni Structure recently in EPrints the Subjects were removed as we haven't used them in years. This caused a couple of issues with the advanced search and some abstract pages. Looking at the ListSets page for another repository, the Subjects are part of this.

I'm going to attempt to correct it by either altering the ListSets (probably not) or by resurrecting the Subjects. I'll update with any success/failure.

Hopefully I can prevent other would-be unintentional wreckers following in my footsteps.

Thanks,
James

On Thu, Apr 8, 2021 at 3:58 PM James Kerwin <jkerwin2101@gmail.com> wrote:
Hi All,

Hope everyone is happy and healthy.

Our repository is harvested by a company named EBSCO. Recently they have started receiving the following warning and failing to harvest:

"Harvest has been aborted by an error "Could not harvest from https://livrepository.liverpool.ac.uk/cgi/oai2: The remote server returned an error: (500) Internal Server Error"

They use this base URL:

https://livrepository.liverpool.ac.uk/cgi/oai2

This whole area is slightly off my radar so I was hoping if there are any common things I could check? Obviously the repository is up and running. I've asked for the dates of the most recent successful harvest and the first failure as well as if it is still happening. I also need to speak with our Computing Services Department to check if the IPs can get through the firewall.

Is there anything else I can/should check based on all of your collective experience?

We did recently get a new security certificate, but I can't imagine that is a problem as we do this each year without any issues.

Thanks,
James