You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[v1] Collection membership on media detail pages #230
On a movie/series detail page, show the collections that item belongs to, with links to browse each collection's full item list. Currently there's no way to navigate from an item to its collections or see what else is in them.
User value / why v1
Collections are a core discovery mechanism (franchises, studios, genres, curated lists). When viewing Dune (1984), the user should see it's in "Dune Saga" / "Sci-Fi" collections and jump to those to find related titles. Without this, collections are only reachable from the library browse view — disconnected from the items they contain.
API surface
GET /api/v2/items/{id}/collections — list collections containing this item (id, title, poster_url, item_count). Or extend the existing item detail response with a collections array.
Existing collection detail endpoint already lists items; this just needs the reverse lookup.
Client impact
Web: new "Collections" section/row on the detail page with poster chips linking to each collection view
Android/Apple: same section; "None" if clients defer the UI, but API should still ship
Rough size
S (server-side): reverse lookup on the existing item↔collection mapping + include in detail response.
Closing — shipped in PR #239 (merged): item detail carries an additive collections array via a real reverse lookup, plus a GET /api/v2/capabilities/item-collections endpoint and the web Collections row — all present on current main. Native client UI was explicitly deferrable per the issue. It stayed open only because #239 used Related issue: instead of Closes.
Activity
chore(api): regenerate media route manifest for item-collections
randrini commentedon Oct 11, 2026
Closing — shipped in PR #239 (merged): item detail carries an additive
collectionsarray via a real reverse lookup, plus aGET /api/v2/capabilities/item-collectionsendpoint and the web Collections row — all present on current main. Native client UI was explicitly deferrable per the issue. It stayed open only because #239 usedRelated issue:instead ofCloses.