-
Notifications
You must be signed in to change notification settings - Fork 0
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
Medium field autosuggest from Getty AAT #1494
Comments
Hmm, while Getty AAT was built into the library we use for vocabulary autocomplete... on testing, it's working strangely. It may not actually be ready for prime-time. I will investigate more, and reach out to the maintainers of the library. |
Just for our records in attempts to debug, some technical info on other issues with Getty in the qa gem is in this open ticket on qa here: samvera/questioning_authority#84 |
Filed a ticket on the qa gem at samvera/questioning_authority#346 |
Yeah, this isn't going to "just work" for our needs from the existing code library we were working. We could invest time in "fixing" it for our needs -- ideally contributing our improvements back, but if we can't get agreement with the community on that, alternatively as a custom "adapter" for the It would probably take a few days or a week of work. We may be able to do it as part of our "samvera maintenance pledge". For now, I'll move this back to "backlog"! |
We decided the default QA behavior was good enough, and implemented that. |
Medium field to auto-suggest from the Getty AAT standard vocab.
The text was updated successfully, but these errors were encountered: