Epic 5: Collections Improvements #24
Description
Epic Overview
Improve collections functionality with archiving capabilities and performance optimizations for large datasets.
User Value
Users need better management of collections over time, including cleanup options and performance with large amounts of content.
Stories in This Epic
- Collection Archive System
- Collection Restore Functionality
- Pagination for Collections Lists
- Pagination for Document Lists
- Collection Management UI Improvements
Design Considerations
Should collections be deletable at all? Consider:
- ✅ Cultural preservation value of curated collections
- ✅ Accidental deletion risk
- ❌ User expectations for content management
- ❌ Cleanup of test/duplicate collections
Proposed Approach: Archive instead of delete to preserve cultural content while allowing cleanup.
Technical Requirements
- Add archived field to Collection schema
- Archive/restore GraphQL mutations
- Pagination for large lists
- UI for archive management
Acceptance Criteria
- Collections can be archived and restored
- Archived collections hidden from normal views
- Lists perform well with 100+ items
- No data loss from archive operations
Related Epics
- Epic Link to GitHub #4: Search Improvements (archived collections in search)