Ftr/dev 15167 implement recipient lookup tool#4683
Open
james-at-kc wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Search the recipients index in OpenSearch to find the most relevant results that can then be passed to the Advanced Search query. Cris may have insights from the filter semantic sessions for how to implement this filter.
Technical Details:
The lookup_recipient tool should look for matches on the following fields: recipient_name, uei, duns
The lookup_recipient tool returns a list of recipient names.
The tool should query the recipient OpenSearch index a single time to find a relevant match
Test cases are created to capture different scenarios for the filter, including the usage of fuzzy matching
Requirements for PR Merge:
Explain N/A in above checklist: