Support for suggest2 API and modernization #107
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is mainly an information PR for some work in progress to see if there's any interest. I added support for the
suggest2
API which does keyword searching of all variants in addition to left anchored searches, but it wasn't as big an improvement as I hoped. Things could also be extended to support the many new information types that the LoC now includes (e.g. BIBFRAME works).In addition to the new API, I added a bunch of additional stuff including:
limit
parameter to control number of choices returnedI couldn't find any documentation on the
didyoumean
API and it doesn't seem to return many results, so I'm not sure how useful it is. More generally it's unclear to me what the best API or APIs to use is and the Library of Congress doesn't really provide much guidance. It would probably take more time than I have available currently to do enough experimentation to figure it out, but I'd be happy to accept feedback from an expert.