-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADD LC RWO Lookups #395
Comments
There's an API for RWOs: https://id.loc.gov/rwo/agents/suggest2/?q=. This API doesn't currently allow filtering by type (Persons, Orgs, etc.) This is different than what the non-RWO lookups use in the Samvera Gem, see: #364. Perhaps we could create a new lookup that builds off the gem, swapping out URIs starting with http://id.loc.gov/authorities/names/ with http://id.loc.gov/rwo/agents/ If we go with the latter we'll need:
|
I'm just remembering now that for the non-RWO lookups we already had to override the Samvera results because they started with "info:...", see: https://github.com/samvera/questioning_authority/wiki/Connecting-to-Library-of-Congress-%28LOC%29. This new lookup just add http://id.loc.gov/rwo/agents/ prefix instead of http://id.loc.gov/authorities/names/. |
For my own reference: Persons -> rdftype:PersonalName |
@sfolsom I just realized that this seems to be already implemented -- see http://localhost:3000/authorities/search/loc/names_Geographic?q=Cambridge This isn't using the rwo/agents prefix, though. |
Right. Sorry I should have mentioned that. We just need the results returned with the rwo URL. |
@sfolsom Sorry for the delay! Please approve LD4P/qa_server_container#96, and we'll be able to merge and test. |
This is available now on int, e.g. http://lookup-int.ld4l.org/authorities/search/loc/agents_Geographic?q=Cambridge |
For vocabs that model RWOs in id.loc.gov (and we're using those URIs in application profiles) add lookups.
Waiting on LOC to provide a list, but we know LCNAF (minus Name/Titles and Titles) will need this.
The text was updated successfully, but these errors were encountered: