Saved Search & Filter Presets for Articles

Description Add the ability for users to save their commonly used filters (e.g., source, date range, topic tags) as presets. This would make it easier for government staff to quickly return to frequently used queries without manually reapplying filters each time.

Why Currently, users can filter and search articles, but they must reapply filters on every visit. Saved search presets would streamline workflows, improve efficiency, and make the system feel more personalized.

Acceptance Criteria

• Users can apply filters (e.g., source = “state.gov”, topic = “policy”) and save them as a named preset.
• Presets should be visible under a “Saved Filters” dropdown on the article listing page.
• Users can rename or delete existing presets.
• Presets are stored per user account and synced via backend (not local storage).
• Frontend must update dynamically when a saved preset is applied.

Technical Notes

• Extend backend API with a /api/filters endpoint to handle CRUD operations for saved presets.
• Store presets in MongoDB with references to the authenticated user.
• Frontend (Next.js) should implement a simple UI dropdown + management modal for presets.
• Consider caching recently used presets with Redis for faster retrieval.