Create direct linked data lookups for homosaurus and getty

[chrisrlc]

• Add Direct Lookup for Homosaurus qa_server#374 - Add homosaurus direct lookup
  • Usage:
    • Term retrieval by id: http://localhost:3000/authorities/show/linked_data/homosaurus_direct/homoit0001709
      • QA search url: https://homosaurus.org/v3/homoit0001709.jsonld
    • Search: http://localhost:3000/authorities/search/linked_data/homosaurus_direct?q=Pronouns
      • QA term url: https://homosaurus.org/search/v3.jsonld?q=Pronouns
  • Could not find any documentation on how to adjust search url template to include language or maxRecords parameters
• Add Direct Lookup for Getty Vocabs qa_server#384 - Add getty direct lookup
  • Usage:
    • Term retrieval by id (aat subauthority): http://localhost:3000/authorities/show/linked_data/getty_direct/aat/300264973
      • QA term url: https://vocab.getty.edu/aat/300264973
    • Search (aat subauthority): http://localhost:3000/authorities/search/linked_data/getty_direct/aat?q=amphora
      • QA search url: https://vocab.getty.edu/queries?toc=Finding_Subjects&query=CONSTRUCT+%7B%3Fs+dc%3Aidentifier+%3Fid%3B+skos%3AprefLabel+%3FprefLabel.%7D%0AWHERE+%7B%3Fs+a+skos%3AConcept%3B+luc%3Aterm+%22amphora%22%3B+skos%3AinScheme+aat%3A%3B+skos%3AprefLabel+%3FprefLabel.%0A++%3Fs+dc%3Aidentifier+%3Fid.%0A++BIND%28REPLACE%28%22amphora%22%2C+%22%5B%2C*%28%29%5D%22%2C+%22%22%2C+%22i%22%29+AS+%3Fstripped_query%29.%0A++BIND%28REPLACE%28%3Fstripped_query%2C+%22%28%5C%5CS%2B%29%5C%5Cs*%22%2C+%22%28%3F%3D.*%241%29%22%29+AS+%3Ffilter_query%29.%0A++FILTER+regex%28str%28%3FprefLabel%29%2C+%3Ffilter_query%2C+%22i%22%29.%0A%7D+ORDER+BY+asc%28lcase%28str%28%3FprefLabel%29%29%29&implicit=true&equivalent=false#Finding_Subjects
  • Uses subauthorities to differentiate between aat, tgn, and ulan
    • Theoretically, we could break this down further and create separate getty_directs for each aat, tgn, and ulan, and separate subauthorities to match current list from cached ld lookup configs (e.g. https://github.com/cul-it/qa_server_aws_deploy/blob/dev/config/authorities/linked_data/getty_aat_ld4l_cache.json#L154) - will bring this up during testing on int to see if there's a need.
  • Adding a limit to the sparql query only limits # of rows in results, not number of distinct authorities, so couldn't include a maxRecords parameter in the search url template for users
  • This was a pain. I'm basically just trying to massage the user-supplied query directly in the sparql query, and that has limits. Especially when there's logic in the getty docs that wants different handling depending on language and etc.
    • Since the MESH direct lookup may also include a sparql query, we may be able to extrapolate some common sparql-handling logic (e.g. remove stop words and special characters?) and preprocess the user query and search url template in the ruby code. But for now, didn't want to override ld config handling code for a single direct lookup config if we didn't need to.