yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Amend DESIGN.md for the title detail surface #142

New Issue
Closed
opened 2026-08-23 19:40:08 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-23 19:40:08 +01:00
Owner
Copy Link
Copy Source

DESIGN.md is silent on poster art, cast, ratings, external links and trailers,
and §2 lists "actor/director following" as a non-goal. Every issue in the Rich
metadata milestone depends on a section that says what this surface is, in the
same way #117 amended the document before the TV work landed.

Add §9.6 "Title detail", and amend §9.2 for the enriched search row. Record the
decisions taken during planning:

  • TMDB is the only metadata source. The rating shown anywhere is TMDB's
    vote_average with its vote_count. No OMDb, no IMDb or Rotten Tomatoes
    scores — they would need a second upstream, a second key and a second thing
    that can be down.
  • Images are hotlinked from image.tmdb.org. The API returns TMDB path
    fragments, never URLs; the browser composes the URL and chooses the size.
    There is no image proxy and no image cache in the service.
  • Rich detail is not persisted. It is served through arr-meta's existing
    24-hour response cache. The single exception is poster_path,
    backdrop_path and vote_average, stored on movies and series and
    written by the daily metadata refresh, so library views render without a
    TMDB call.
  • Cast is the top 10 billed, each with profile photo, actor name and
    character name, linking out to that person's TMDB page. This does not
    contradict §2: nothing about a person is stored, tracked or searched on. The
    non-goal is following people, not naming them.
  • External links are TMDB always, IMDb for movies, TVDB for series — all
    three from ids the app already holds — plus a Rotten Tomatoes search link,
    which is a query URL and not a resolved title page.
  • Trailers resolve on click. TMDB's search responses carry no videos, so a
    trailer key costs a detail call. Rendering a chip on every row and resolving
    the one that is clicked keeps that cost at one call, and the 24h cache makes
    a repeat free.
  • A movie detail page exists at /movies/{id}, mirroring the shape the
    series detail view (#129) takes. The release deck becomes a section of it and
    /movies/{id}/releases keeps resolving.
  • The library view is a poster grid with a list toggle, the list keeping
    the derived-status columns §4.2 built it around.

Non-goals to state explicitly in the section, because they are the adjacent
scope most likely to creep: no watch providers, no recommendations or similar
titles, no collections, no person pages inside the app, no review text.

Document only. No code changes in this issue.

DESIGN.md is silent on poster art, cast, ratings, external links and trailers, and §2 lists "actor/director following" as a non-goal. Every issue in the Rich metadata milestone depends on a section that says what this surface is, in the same way #117 amended the document before the TV work landed. Add §9.6 "Title detail", and amend §9.2 for the enriched search row. Record the decisions taken during planning: - **TMDB is the only metadata source.** The rating shown anywhere is TMDB's `vote_average` with its `vote_count`. No OMDb, no IMDb or Rotten Tomatoes scores — they would need a second upstream, a second key and a second thing that can be down. - **Images are hotlinked** from `image.tmdb.org`. The API returns TMDB path fragments, never URLs; the browser composes the URL and chooses the size. There is no image proxy and no image cache in the service. - **Rich detail is not persisted.** It is served through arr-meta's existing 24-hour response cache. The single exception is `poster_path`, `backdrop_path` and `vote_average`, stored on `movies` and `series` and written by the daily metadata refresh, so library views render without a TMDB call. - **Cast** is the top 10 billed, each with profile photo, actor name and character name, linking out to that person's TMDB page. This does not contradict §2: nothing about a person is stored, tracked or searched on. The non-goal is following people, not naming them. - **External links** are TMDB always, IMDb for movies, TVDB for series — all three from ids the app already holds — plus a Rotten Tomatoes *search* link, which is a query URL and not a resolved title page. - **Trailers resolve on click.** TMDB's search responses carry no videos, so a trailer key costs a detail call. Rendering a chip on every row and resolving the one that is clicked keeps that cost at one call, and the 24h cache makes a repeat free. - **A movie detail page exists** at `/movies/{id}`, mirroring the shape the series detail view (#129) takes. The release deck becomes a section of it and `/movies/{id}/releases` keeps resolving. - **The library view is a poster grid** with a list toggle, the list keeping the derived-status columns §4.2 built it around. Non-goals to state explicitly in the section, because they are the adjacent scope most likely to creep: no watch providers, no recommendations or similar titles, no collections, no person pages inside the app, no review text. Document only. No code changes in this issue.
naps62-yolo added this to the Rich metadata milestone 2026-08-23 19:40:08 +01:00
naps62-yolo added the area/infradifficulty/easytype/chorephase/6-tv labels 2026-08-23 19:40:08 +01:00
naps62-yolo added phase/5-ui and removed phase/6-tv labels 2026-08-23 19:42:54 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/infra difficulty/easy phase/5-ui type/chore
Milestone
No items
No Milestone Rich metadata
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#143 arr-meta: title detail with credits, videos and external ids
yolo/arr
#145 Store poster_path, backdrop_path and rating on movies and series
yolo/arr
Reference: yolo/arr#142
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?