Add saved filter presets for authenticated users [AICC-68]

[Copilot]

Government staff need to save commonly used filter combinations (source, topic, date range) instead of manually reapplying them on each visit.

AICC-68

Backend

• Model: FilterPreset schema with userId, name, filters (source/topic/dateRange), unique index on (userId, name)
• Routes: /api/filters CRUD endpoints, all authenticated
• Controller: Validates duplicates, enforces user isolation
• Tests: 17 specs covering auth, validation, CRUD operations

Frontend

• Component: SavedFilters dropdown with preset list, save/rename/delete modals
• Integration: Added to home page search bar, applies filters on preset selection
• Visibility: Renders only for authenticated users

API Usage

// Create preset
POST /api/filters
Authorization: <jwt-token>
{ "name": "State Dept Policy", "filters": { "source": "state.gov", "topic": "policy" } }

// Apply preset (client-side)
GET /api/filters → select preset → update query params

Presets persist per-user in MongoDB, not localStorage.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• ai-content-curator-backend.vercel.app
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/AI-Gov-Content-Curator/AI-Gov-Content-Curator/node_modules/next/dist/compiled/jest-worker/processChild.js (dns block)
• fastdl.mongodb.org
  • Triggering command: node ./postinstall.js (dns block)
• scarf.sh
  • Triggering command: node ./report.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Saved Search & Filter Presets for Articles</issue_title>
<issue_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.</issue_description>

Comments on the Issue (you are @copilot in this section)

@hoangsonww todo for now

• Fixes Saved Search & Filter Presets for Articles #43

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
ai-gov-content-curator	Ready	Preview	Comment	Nov 2, 2025 9:40pm

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[hoangsonww]

AICC-68