Mark/nodedesk
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

EPIC C: Search + Account Lifecycle (Week 2-3) — Phase 1: Metadata #32

New issue
Closed
opened 2026-05-28 00:57:50 +00:00 by Mark · 2 comments
Mark commented 2026-05-28 00:57:50 +00:00
Owner
Copy link

Phase 1: Metadata

  • Type: epic
  • Priority: high
  • Area: search-account

Decomposed from nodedesk#3

## Phase 1: Metadata - Type: epic - Priority: high - Area: search-account --- _Decomposed from [nodedesk#3](https://forgejo.tail018ac4.ts.net/Mark/nodedesk/issues/3)_
Mark commented 2026-05-28 03:39:44 +00:00
Author
Owner
Copy link

⏸ Needs Decision

Blocking factors:

  • Didn't meet auto-approve criteria — scope=medium, risk=low, spec=aligned

Scope: medium Risk: low Spec: aligned Type: feature
Summary: This epic covers enriching the existing search system with richer metadata (tags, status, timestamps, snippets) and potentially adding metadata-based filtering/faceted search to the global search results.
Suggestion: Extend search.ts SearchResult types to include tags, timestamps, and status; add searchVector support to Contact and Location models for broader metadata coverage; enrich the search page UI with metadata badges, snippets, and optional filter controls; keep backward compatibility with existing TopSearch and URL-based query interface.
Rationale: SCOPE=medium: builds on existing search infrastructure (src/lib/search.ts + /app/search/page.tsx) with new types, query fields, and UI enrichment — roughly 5-10 files (search.ts, search page, possibly new search components, schema migration for searchVector on Contact/Location). RISK=low: purely additive on top of existing search — no auth/billing/core data paths modified, existing FTS and CONTAINS modes untouched. SPEC=aligned: the project already has a working search foundation with TopSearch component, search results page, and FTS mode; metadata enrichment is the natural next step and matches the stated search-account area. The epic label and sparse body suggest this is the umbrella for Phase 1 sub-tasks but given existing search maturity, metadata enrichment is the correct interpretation.

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=low, spec=aligned --- **Scope:** medium **Risk:** low **Spec:** aligned **Type:** feature **Summary:** This epic covers enriching the existing search system with richer metadata (tags, status, timestamps, snippets) and potentially adding metadata-based filtering/faceted search to the global search results. **Suggestion:** Extend search.ts SearchResult types to include tags, timestamps, and status; add searchVector support to Contact and Location models for broader metadata coverage; enrich the search page UI with metadata badges, snippets, and optional filter controls; keep backward compatibility with existing TopSearch and URL-based query interface. **Rationale:** SCOPE=medium: builds on existing search infrastructure (src/lib/search.ts + /app/search/page.tsx) with new types, query fields, and UI enrichment — roughly 5-10 files (search.ts, search page, possibly new search components, schema migration for searchVector on Contact/Location). RISK=low: purely additive on top of existing search — no auth/billing/core data paths modified, existing FTS and CONTAINS modes untouched. SPEC=aligned: the project already has a working search foundation with TopSearch component, search results page, and FTS mode; metadata enrichment is the natural next step and matches the stated search-account area. The epic label and sparse body suggest this is the umbrella for Phase 1 sub-tasks but given existing search maturity, metadata enrichment is the correct interpretation. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.
Mark commented 2026-05-29 20:46:54 +00:00
Author
Owner
Copy link

GSD pipeline blocked at IMPLEMENT: API call failed after 3 retries.
]11;?\[?7h ┊ review diff

[?7ha//home/b/Projects/nodedesk/tests/settings.spec.ts → b//home/b/Projects/nodedesk/tests/settings.spec.ts

[?7h@@ -7,5 +7,6 @@

[?7h 

[?7h await page.goto("/

GSD pipeline blocked at IMPLEMENT: API call failed after 3 retries. ]11;?\[?7h ┊ review diff [?7ha//home/b/Projects/nodedesk/tests/settings.spec.ts → b//home/b/Projects/nodedesk/tests/settings.spec.ts [?7h@@ -7,5 +7,6 @@ [?7h  [?7h await page.goto("/
Mark 2026-06-15 05:40:41 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
blocked:gate-fetch

   
blocked:gate-implement

   
blocked:needs-attention

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:needs-local-checkout

   
blocked:no-changes

   
bug

Bug report

  
feature-request

   
in-progress

   
needs-decompose

Ready to be decomposed into sub-issues

  
needs-triage

   
ops-task

   
quickfix

   
security/high

High severity security issue

  
security/low

Low severity security issue

  
security/medium

Medium severity security issue

  
triage-approved
No labels
blocked:gate-fetch
blocked:gate-implement
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:needs-local-checkout
blocked:no-changes
bug
feature-request
in-progress
needs-decompose
needs-triage
ops-task
quickfix
security/high
security/low
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
Mark/nodedesk#32
No description provided.