Design proximity search feature for the front-end

[JonellaCulmer]

What we're after

Leverage the back-end research on proximity search to design a user-friendly front-end interface. The initial iteration should address user needs, prioritize usability, and effectively implement the following new filters: q_proximity, max_gaps, proximity_filter, and proximity_filter_term.

Notes on proximity search capabilities 🔒

Related issues

• Research implementing proximity in legal search  openFEC#5945
• Implement Proximity Search openFEC#6076
• Feature/6076 add proximity search openFEC#6087

Applicable search systems:

• AOs
• MURs
• ADRs
• AFs
• Statutes
• Rulemakings
• Global legal resources search

Considerations:

• May need to explain that this doesn't apply to regulations as that relies on eCFR
• What functionality is the most valuable to implement on the front-end
• What guidance do we need to provide on how to use it?

Completion Criteria

• Designs Finalized:

  • Proximity search interface designs are completed and shared with stakeholders.
  • Present designs at the 1/22 sync meeting for review and feedback.

• Documentation:

  • Provide clear usage guidance for the proximity filters within the UI.

• Follow-Up Ticket:

  • Create a new ticket to track the addition of proximity-by-distance functionality to the website UI, based on approved design specifications.

[JonellaCulmer]

@patphongs @tmpayton Here are the updated mocks as promised. Let me know if you see anything else that needs changes.

One question - I have "anywhere" as an option for the any state for before or after, can we do that? Or should it be blank?

[tmpayton]

Hi @JonellaCulmer, anywhere isn't an option at this time but these look great! Thank you!