Skip to content
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

Use Synonyms when ARASAAC returns 404 #46

Open
2 tasks
hectoritr opened this issue Oct 18, 2024 · 0 comments · May be fixed by #47
Open
2 tasks

Use Synonyms when ARASAAC returns 404 #46

hectoritr opened this issue Oct 18, 2024 · 0 comments · May be fixed by #47
Assignees

Comments

@hectoritr
Copy link

hectoritr commented Oct 18, 2024

Main Problem:
Currently, we are still encountering 404 Not Found errors when using ARASAAC's "beast search" or "search" endpoints, even after implementing fallback mechanisms such as searching for infinitive forms of verbs, handling plurals. The 404 errors occur when the API fails to return a relevant pictogram for certain search terms.

Edge Cases:
Non-Infinitive Verbs: While the system attempts to handle verb forms, some cases still result in a 404, particularly for more complex or uncommon variations.
Synonyms or Alternative Phrases: The current approach does not account for synonyms that could be equally valid for the user’s intended action or object.

Proposed Solution:
Implement a strategy where, if a 404 error is encountered, we leverage an LLM (Large Language Model) to generate synonyms or alternative phrases for the original search term.
The system will:

  • Generate synonyms for the original term using the LLM.
  • Reattempt the search using the generated synonym(s).

Example:
Search for "brushing teeth" → 404 error.
Generate synonyms: "cleaning teeth," "brush teeth."
Search for "cleaning teeth" → Result found.
If still 404, reattempt with "brush teeth."

@hectoritr hectoritr changed the title Use Synonims when ARASAAC returns null Use Synonyms when ARASAAC returns 404 Oct 18, 2024
@AliLee0923 AliLee0923 linked a pull request Oct 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants