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

[SPIKE] [Resources & Support] Research alternative search methods to replace 'bespoke' search features in VA.gov products #20145

Open
1 task
FranECross opened this issue Dec 19, 2024 · 1 comment
Labels
Drupal engineering CMS team practice area Needs refining Issue status Public Websites Scrum team in the Sitewide crew R&S: Tagging/Searching sitewide

Comments

@FranECross
Copy link

FranECross commented Dec 19, 2024

Description

Currently, Resources & Support search feature is custom and very limited in what is returned (only searches titles, not content).

This spike is to take a holistic look at the various products in VA.gov that have a search feature and create a white paper listing and outlining:

  • Products which have a search feature
  • What search engine/code/? is used for that feature
  • Do any features share code or use the same search feature; what API if any is being used
  • Each search features limitations
  • Options for updating to a different search engine/feature/API e.g. Elasticsearch, Solr, MeiliSearch, etc., keeping in mind that we want not only titles but body of content searched and results returned.
  • High level estimates for each option
  • Is there additional cost associated with any of the options

Information to Consider

  • More content will be added to Resources & Support, which is one of the drivers to improving its search feature by returning more content (title/body of content included in searches), as well as speed and accuracy.

User story

AS A Veteran, their caregiver, family member or survivor using the various search features across VA.gov
I WANT to have accurate, fast search results when I search for information or forms
SO THAT I can achieve my research and needs faster and with a minimum of frustration and angst.

Engineering notes / background

Acceptance criteria

  • create a white paper listing and outlining:
  • Products which have a search feature
  • What search engine/code/? is used for that feature
  • Do any features share code or use the same search feature; what API if any is being used
  • Each search features limitations
  • Options for updating to a different search engine/feature/API e.g. Elasticsearch, Solr, MeiliSearch, etc. keeping in mind that we want not only titles but body of content searched and results returned.
  • High level estimates for each option
  • High level estimates for each option
  • Is there additional cost associated with any of the options
@FranECross FranECross added Needs refining Issue status sitewide Drupal engineering CMS team practice area Public Websites Scrum team in the Sitewide crew R&S: Tagging/Searching labels Dec 19, 2024
@mnorthuis
Copy link

Both Search.gov and AI should be considered as potential services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Needs refining Issue status Public Websites Scrum team in the Sitewide crew R&S: Tagging/Searching sitewide
Projects
None yet
Development

No branches or pull requests

2 participants