Metadata auto-enrichment pipeline: enrich on ingest #4
Reference in New Issue
Block a user
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?
After a file is ingested, the ingest service should publish a NATS event that triggers the metadata service to look up TMDb/OMDb metadata and write it back to the catalogue (title, overview, poster, tmdb_id, etc). Design: new NATS subject 'media.ingested', metadata worker subscribes, looks up by filename/title heuristic, patches catalogue via internal PUT. Needs the TMDb and OMDb providers to be wired up first (issues #1 and #2).