File tags, Versioning and activity tracker. #530
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#530
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
4 screenshots with 3 new UI elements.
our current preview section could grow and become the actual details pane as well, instead of opening a small window with the details of the file. look at the attached screenshots of the examples of opencloud.
divide this issue into sub-issues if necesarry.
Read the four OpenCloud screenshots. What they show, mapped to what Cairn has and hasn't:
The container: a persistent details sidebar. All four are the same right-hand pane in different sub-views: an overview (icon/preview, Last modified, Owner, Size, Version count, a Tags input) with drill-in rows for Actions / Shares / Versions / Activities; a per-version list with Restore and Download per entry; an activity timeline ("X updated file in Space, date"); and a shares panel (people search + role, space members with roles, public links). Your instinct that our preview pane could grow into this is sound — the pane already owns the right-hand slot, and the drill-in mechanic matches the admin drill-in we built for #389. On phones this would follow the #389 pattern (takeover or sheet, not a squeezed sidebar).
What exists today vs what's new backend work:
/data/.cairn/audit), the notification feed derives from Inbox + transfers, and recents track access. A per-file feed needs a queryable store +GET /api/v1/activity?path=— decision needed on whether the audit log becomes that store or a separate lighter event log (audit has retention/compliance semantics we may not want to couple to UI).Proposed sub-issue split (in build order): 1) details-pane shell — grow the preview pane into the sidebar with overview + drill-ins, wiring only what exists (metadata, shares); 2) file activities (event store + API + timeline panel); 3) tags (store + API + UI + filter); 4) file versioning (design/ADR first, then storage, then UI). Each gets its own mockup per house rules; 1 can ship without 2–4 (rows appear as backends land).
Happy to open the sub-issues in that shape — say the word. One question: should the details pane replace the current small details window entirely (one surface, per OpenCloud), or keep the dialog for phone and grow the pane on desktop only?
Split approved by Nikola — sub-issues opened, this becomes the tracking issue:
Build order 538 → 539/540 → 541; the shell ships without the others and grows rows as backends land.
Closing: all four sub-issues shipped — #538 (details pane shell), #539 (per-file activity feed), #540 (file tags), #541 (versioning, ADR + storage + restore/download UI). The pane has since been refined further through the pane-v2 fidelity work (v0.6.230–241), and tag search landed in v0.6.241.