Hi, I am facing an error when trying to use VIAF in Valuesuggest. I always get an error message and there is no reponse. The browser console shows error 500. I have tried with different versions and Omeka S installations.
Could anybody confirm it?
OCLC seems to have taken down their VIAF autosuggest endpoint:
http://www.viaf.org/viaf/AutoSuggest
This may be a temporary, or they could have removed the service altogether. I don’t see an announcement about it.
1 Like
I’m having the same issue and I also did not find any announcements or release notes mentioning this.
However, I think the Autosuggest endpoint still exists, but is now behind paywall authentication 
See the closed lock icon at VIAF API Swagger AutoSuggest endpoint
Hi @xvalenti and @jimsafley ,
I have contacted OCLC, who are providing and maintaining the VIAF API. They told me that they have switched to HTTPS only and have changed some other things as well. Unfortunately, their developer documentation is behind a login (which I do not have), so I had to troubleshoot and figure it out myself.
I’m glad to announce that I have succeeded and I have made a fix in this Pull Request on GitHub. Let’s hope that the Omeka S maintainers will accept it soon so it will be available in the next version of the ValueSuggest module.
Best regards,
Maarten Coonen
2 Likes
Hi @ mcoonen!
It works like a charm. Thanks a lot for your research and fix!
Best regards
1 Like
We have a (probably) related issue with the URI Dereferencer for VIAF URIs. Omeka currently does not show any metadata for the URI’s, and this stopped working around the same time as the ValueSuggestmodule. The endpoint for this module may also be behind the API authentication?
Yes, thanks for bringing this to our attention. We’re working on a fix in the add-service-options branch.
The fix is in version 1.4.3
Wonderful, thank you!
We’ve installed the fix and VIAF URI’s are now correctly deferenced. However, we’ve now lost the Geonames metadata. Could this be a consequence of this fix?