Closed apinkney0696 closed 1 year ago
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: https://github.com/samvera/questioning_authority/issues/84
Filed a ticket on the qa gem at https://github.com/samvera/questioning_authority/issues/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 qa
gem.
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.