Files
SkinbaseNova/docs/collections-v4-implementation-summary.md
2026-03-28 19:15:39 +01:00

119 lines
7.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Collections v4 Implementation Summary
## Scope completed
- Added collection lifecycle, premium presentation, series, campaign, analytics, saved-library, and staff surface foundations on the existing collections stack.
- Reused the current Laravel + Inertia collections architecture rather than introducing a parallel system.
- Kept public safety constraints intact by continuing to route recommendations and surfaces through public-only collection queries.
## Backend
- v4 schema is backed by the collections platform migration that adds lifecycle, scoring, presentation, series, and campaign fields plus supporting tables for:
- collection history
- collection daily stats
- collection surface definitions
- collection surface placements
- collection saved lists and list items
- Fixed the attachment history regression in `CollectionService` so artwork attach actions correctly record the acting owner.
- Aligned collection surface placement storage with the actual database schema by persisting:
- `placement_type`
- `campaign_key`
- `notes`
- `created_by_user_id`
- Added `automatic` surface mode support so rule-driven surfaces can resolve purely from eligible public collections without depending on manual placements.
- Broadened automatic surface rules so staff can filter by owner, presentation style, theme token, collaboration mode, score thresholds, analytics/commercial flags, and explicit include/exclude collection IDs.
- Added definition-level surface scheduling and fallback behavior so staff surfaces can activate on schedule and hand off cleanly to fallback keys when inactive or empty.
- Added staff surface cleanup support so placements can be deleted directly, definitions can be deleted once their placements are cleared, and overlapping active placement windows can be flagged for staff review.
- Preserved `saved_at` timestamps in saved collection queries so v4 saved-library sorting works consistently.
- Added dedicated owner workflow endpoints for presentation, campaign, and lifecycle updates so the v4 API surface matches the studios scoped editing responsibilities instead of relying only on the generic collection update route.
- Added manual linked-collection support with persisted ordering, owner studio controls, and public-page rendering that prioritizes curated links while still filtering out non-public targets.
- Added first-class series title and description metadata so series landing pages and in-page sequence callouts no longer have to infer copy from keys or campaign labels.
## Owner and staff UI
- Added missing Inertia pages:
- `CollectionDashboard`
- `CollectionAnalytics`
- `CollectionHistory`
- `CollectionStaffSurfaces`
- Expanded the staff surfaces studio so definitions and placements can both be hydrated back into the form and updated through explicit staff routes.
- Added staff surface deletion controls plus conflict callouts for overlapping scheduled placements on the same surface.
- Expanded staff surface rule guidance so broader automatic filters and `quality_score` ranking are discoverable from the studio.
- Expanded the staff surfaces studio to manage definition-level activation windows and fallback surface keys.
- Added batch editorial tooling to the staff surfaces studio so staff can preview and apply campaign metadata updates across multiple collections while optionally planning surface placements in one pass.
- Upgraded the collection manage studio to expose v4 metadata and insight links:
- lifecycle state
- analytics toggle
- presentation style and emphasis
- theme token
- series key and order
- campaign key and label
- series title and description
- sponsorship and partner labels
- monetization and brand-safety notes
- archive and expiry scheduling
- AI quality review output
- Added linked-collection controls in the manage studio so owners can curate manual related strips alongside series and campaign metadata.
- Added dashboard, analytics, history, and staff-surface shortcuts directly in the collection studio.
## Public and saved-library UI
- Upgraded the public collection page with:
- owner-only analytics/history shortcuts
- campaign and series badges
- premium presentation and score callouts
- intro-block and featured-artworks presentation toggles driven by persisted layout modules
- series navigation and sibling collection links
- series titles and descriptions where owners provide them
- manual linked collections merged ahead of recommendation-driven related collections
- Added a dedicated public series landing route so related collection sequences can be browsed as ordered standalone pages.
- Rebuilt the saved collections page into a v4 library surface with:
- saved-list creation
- add-to-list actions
- dedicated saved-list detail routes
- saved-list order preservation on dedicated list pages
- saved-list reorder actions for active lists
- remove-from-list actions
- unsave cleanup that also removes related saved-list items
- filter and sort controls
- recommended next collections
## Testing added
- Added focused feature coverage for:
- premium presentation layout modules hiding intro copy while enabling a featured-artworks strip on public collection pages
- staff surface placement creation with v4 placement fields
- staff surface definition and placement updates
- automatic surface resolution respecting public eligibility rules
- broader automatic surface filtering using owner, presentation, score, and include/exclude rules
- surface definition fallback behavior when scheduled windows are inactive or a surface resolves no items
- placement assignment history entries being recorded for affected collections
- deleting staff surface placements while recording placement removal history
- preventing surface definition deletion until attached placements are cleared
- flagging overlapping active placement windows as staff-visible conflicts
- previewing batch editorial campaign and placement changes without persisting them
- applying batch editorial campaign metadata while skipping ineligible public-surface placements safely
- public series landing pages honoring series order while excluding private and restricted entries
- series title and description metadata flowing through series landing pages and collection page sequence callouts
- dashboard summaries counting lifecycle buckets, pending submissions, attention queues, and expiring campaigns from the owning curator's collections only
- collection analytics payloads returning totals, range deltas, timeline points, and ranked top artworks for owners
- allowing active collection editors to access analytics and history while blocking unrelated viewers
- dedicated presentation, campaign, and lifecycle workflow routes persisting the expected scoped collection metadata while preserving owner-only authorization
- syncing manual linked collections, hydrating them back into the manage studio, and preventing public pages from leaking private linked targets
- saved-list creation and adding saved collections to lists
- browsing a saved-list route and removing a collection from that list
- preserving saved-list item order on dedicated list routes
- reordering saved-list items
- unsaving a collection clearing that user's saved-list memberships
## Verification status
- The focused Collections v4 feature coverage is passing in `tests/Feature/Collections/CollectionsFeatureTest.php`.
- Current verification includes analytics, history, lifecycle, presentation, campaign, series, linked collections, saved-library, recommendation safety, public discovery, surface automation, placements, and staff batch editorial tooling.
## Follow-up candidates
- Add pagination controls for long history timelines beyond previous/next.
- Expand saved-library UX with drag-and-drop reorder flows.
- Add richer staff planning ergonomics on top of the current batch editorial tools if editorial operations need more campaign-specific scheduling views later.