hoangsonww/AI-Gov-Content-Curator

Saved Search & Filter Presets for Articles

Open

#43 opened on Sep 23, 2025

View on GitHub
 (1 comment) (1 reaction) (2 assignees)TypeScript (18 forks)auto 404
backendbugci/cdcrawlerdeploymentduplicateenhancementfrontendgood first issuehelp wantednewsletter

Repository metrics

Stars
 (29 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Examine the existing filter implementation in the frontend and backend. Identify the current filter state management in Next.js (e.g., URL params or local state). Review the backend API structure to understand how to add a /api/filters endpoint with CRUD operations. Study the MongoDB models and authentication middleware to reference the user. For Redis caching, look into how to expire and invalidate presets. The task involves creating a new route handler, a MongoDB schema for presets, a React component for the dropdown and management modal, and integrating with the existing filter component.
Tech stack
typescriptreactnextjsnodejsexpressmongodbredis
Domain
full stackbackendfrontenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptReactNext.jsMongoDB
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70