Open sfolsom opened 11 months ago
@sfolsom This is ready for you to test on lookup-int! Direct lookup results use the id.loc.gov api (same results as what you'd find here: https://id.loc.gov/search/?q=cs:http://id.loc.gov/vocabulary/classSchemes). Each result has an id, label, and uri parsed from: https://id.loc.gov/search/?q=cs:http://id.loc.gov/vocabulary/classSchemes&format=json
Please let me know if you'd like any changes!
Example endpoint: https://lookup-int.ld4l.org/authorities/search/loc/classSchemes?q=superintendent
Note: This is one of those lc authorities I mentioned that returns what appears to be duplicate results, e.g. https://id.loc.gov/search/?q=superintendent&q=cs%3Ahttp%3A%2F%2Fid.loc.gov%2Fvocabulary%2FclassSchemes. Our QA endpoint filters out these duplicate ids.
Looks good. I don't understand why https://id.loc.gov/search has duplicate results, but it's nice to see that the API results do not.
Create direct lookups for the following LC Classification Schemes.
The Samvera QA Code seems to offer search for some LC vocabs: https://github.com/samvera/questioning_authority/wiki/Connecting-to-Library-of-Congress-%28LOC%29.
Related links: See https://id.loc.gov/techcenter/searching.html for API documentation.
Example of a direct search config to base new config off: https://github.com/cul-it/qa_server/blob/f3083a8f1392e72890f8d6e6a763c9e0ace1ea0c/config/authorities/linked_data/oclcfast_direct.json#L32