LCNAF plugin can't search when OCLC option is selected

Description

From https://github.com/cvonkleist,
The LCNAF plugin can't search when the OCLC option is selected. This is happening because OCLC has dropped support for the web service powering the search. We see this error in ArchivesSpace:

SRUSearcher::SRUSearchException in LcnafController#search
I emailed OCLC about it, and this is what they had to say:

Thanks for pointing this out. It turns out that we have not supported this service for some time. We have been directing users to the version hosted by the Library of Congress instead:

http://id.loc.gov/authorities/names.html

I will work on updating our documentation accordingly.
You can see that the service is broken by doing the following request with curl:

curl 'http://alcme.oclc.org/srw/search/lcnaf?query=test'
I expect to get search results; however, this is what comes back:

HTTP/1.0 302 Found
Location: http://ServiceUnavailable.oclc.org
Connection: close
If I follow this 302 redirect, I see this:

Directory Listing Denied: This Virtual Directory does not allow contents to be listed.
Here is the line in the ArchivesSpace LCNAF plugin source code where the service URL is set:

https://github.com/archivesspace/archivesspace/blob/6026a8ab461b55271d6b9418808e3ea1284c72fb/plugins/lcnaf/frontend/controllers/lcnaf_controller.rb#L62

Environment

None

Activity

Show:
Laney McGlohon
June 6, 2018, 1:09 PM
Edited

As of June 2018, the OCLC search is not working again. OCLC does have this API for VIAF - https://platform.worldcat.org/api-explorer/apis/VIAF - which could be an alternative when the plugin is worked on again.

Jordon Steele
June 8, 2018, 1:46 PM

Has there been any discussion about creating a plugin for VIAF identifiers instead of LCNAF? I think the flaw to this idea is that VIAF may require human intervention to select the country vocabulary you want to use, but there are advantages to using international identifiers. Maybe y'all have already discussed it. We're a VIAF shop.

Lora Woodford
August 30, 2018, 6:57 PM

Per Dev prioritization meeting, we will "fix" this by implementing improved error reporting indicating when the OCLC endpoint is no longer reachable, but there is little more we can do at this juncture. Will add a quick ping to the endpoint before attempting to do anything else, and if that does not succeed will inform the user that the OCLC service appears to be down.

As to the VIAF suggestion, this should go in as a separate feature request and that work can be scoped there.

Joshua Shaw
April 14, 2020, 1:18 PM

OCLC was up when I just tested, so I’ll try again later and see if I can find a time when it is down to test the new error messaging.

Brittany Newberry
April 23, 2020, 1:11 PM

Tested on test site and OCLC search is working. I will test again to see if error messaging works when search is down

Done

Assignee

Lora Woodford

Reporter

Laney McGlohon

Labels

Sprint

midMar-earlyApri

Fix versions

Priority

Minor