Tag & category merge #123

Closed
opened 2026-07-15 19:53:44 +00:00 by claude-bot · 0 comments
Contributor

Feature idea (audit Phase 5, rank #6) · Effort: low

Why
Long-running research accretes near-duplicate tags/categories; the management UIs (TagManagement, CategoryManagement) support rename/delete but not merge-with-reassign.

Proposal
Add "merge into." that re-points the junction rows (entry_tags / entry_categories / motif_categories) from the source to the target and deletes the source, in a transaction.

Why it was likely missed
Tags started small and only became unwieldy at scale.

Acceptance criteria

  • Merging tag/category A into B re-assigns all A's items to B and removes A.
  • The reassignment is transactional (no partial merge on failure).

Filed from the 2026-07-15 codebase audit. Full report: docs/.internal/report-2026-07-15.md (gitignored).

**Feature idea** (audit Phase 5, rank #6) · Effort: low **Why** Long-running research accretes near-duplicate tags/categories; the management UIs (`TagManagement`, `CategoryManagement`) support rename/delete but not merge-with-reassign. **Proposal** Add "merge into." that re-points the junction rows (`entry_tags` / `entry_categories` / `motif_categories`) from the source to the target and deletes the source, in a transaction. **Why it was likely missed** Tags started small and only became unwieldy at scale. **Acceptance criteria** - [ ] Merging tag/category A into B re-assigns all A's items to B and removes A. - [ ] The reassignment is transactional (no partial merge on failure). --- _Filed from the 2026-07-15 codebase audit. Full report: `docs/.internal/report-2026-07-15.md` (gitignored)._
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/TeaLeaves#123
No description provided.