Getting results in type ahead without requiring a space after a search term

[sfolsom]

For tracking purposes, please create a separate issue for each indexing improvement request.

• [X] Please describe the expected performance and accuracy of a particular vocabulary. Many type ahead searches currently require adding a space after the term in order to get results that make sense.
• [X] If applicable, please update and provide links related to existing tests, https://github.com/LD4P/qa_server/pull/130

We see this not just in AAT, but the test above should account for AAT, where we noticed it first.

[elrayle]

@sfolsom When I perform a search using the test in #130, I see the expected result as the first result.

-
    query: precious
    position: 5
    subject_uri: "http://vocab.getty.edu/aat/300011054"
    replacements:
      maxRecords: '10'

This translates to API request...

https://lookup.ld4l.org/authorities/search/linked_data/getty_aat_ld4l_cache?q=precious&maxRecords=4

with results...

[
  {"uri":"http://vocab.getty.edu/aat/300011054","id":"300011054","label":"precious metal"},
  {"uri":"http://vocab.getty.edu/aat/300133732","id":"300133732","label":"precious stone (material)"},
  {"uri":"http://vocab.getty.edu/aat/300266077","id":"300266077","label":"mitrae pretiosae"},
  {"uri":"http://vocab.getty.edu/aat/300011175","id":"300011175","label":"[semi-precious stone, semiprecious stone]"}
]

Did you run the accuracy test and it reported different results?

[sfolsom]

weird, control-F for 'precious' in the following doc to see the Sinopia screenshot: https://docs.google.com/document/d/1UxSeZ9xWpIZ__UxzMAtJGlXUrRzY-yZ3OukZNw2FDrg/edit?usp=sharing

[sfolsom]

for the needed extra space issue check out the screenshots for the Geonames searches in https://docs.google.com/document/d/1UxSeZ9xWpIZ__UxzMAtJGlXUrRzY-yZ3OukZNw2FDrg/edit?usp=sharing

[elrayle]

@sfolsom Can you review this issue and determine if it is still a problem? I believe this was an issue in Sinopia and not at QA or the cache.