Add collection/franchise ingestion

Collections were bare stubs (name only) lazily created the moment a movie's belongs_to_collection reference was seen. Adds a real ingest_collection pipeline: TMDb's /collection/{id} for overview and poster/backdrop artwork, plus ordered CollectionMovie membership -- linking only movies already ingested into Aurora, the same never-fabricate-a-stub rule movie recommendations already follow. get_or_create_collection now refreshes name/overview on an existing stub instead of only creating, guarded so a bare movie-stub call (overview=None) never clobbers real data a full ingestion already filled in. New POST /api/v1/admin/ingest/collection endpoint and ingest_collection_task; GET /api/v1/collections/{id} needed no changes since its read path (collection_service.py) already assembled the full detail shape. Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-09-05 08:37:27 -05:00
parent 4af4ba40ef
commit 892f78016c
15 changed files with 460 additions and 1 deletions
@@ -60,7 +60,14 @@ and a movie studio have the same shape (name, logo, country, parent
 company), so a separate `Network` entity would just duplicate columns.
 `collections` (franchises) are first-class, with their own artwork and
 `collection_relations` for shared-universe links between collections
-(section 9).
+(section 9). A collection starts as a bare name-only stub the first time
+movie ingestion sees a `belongs_to_collection` reference; its real overview,
+poster/backdrop, and ordered `collection_movies` membership are filled in by
+`app/services/ingestion/collection_ingestion.py:ingest_collection`
+(`POST /api/v1/admin/ingest/collection`), which — like recommendations —
+only links movies Aurora has already ingested rather than fabricating stubs
+for the rest of the franchise. `collection_relations` and `collection_series`
+exist in the schema for future use but nothing populates them yet.

 ## Artwork / Videos