read_discover results drop external identifiers (tv browse, collection members) #2

Closed
opened 2026-09-19 08:19:34 +01:00 by gronod · 1 comment
Owner

Summary

read_discover projections return items with identifiers: [] even though upstream results carry provider IDs. Affected media cannot be passed to read_media details or write_request_create, breaking the discover→request workflow.

Environment

Reproduction

read_discover {"action":"browse","media":"tv","category":"popular","page":{"limit":5}}
read_discover {"action":"browse","media":"tv","category":"anticipated"}
read_discover {"action":"browse","media":"tv","category":"trending"}
read_discover {"action":"collection","collection_id":8091}

Expected

Each item carries at least one usable identifier (e.g. tmdb, tvdb, tvmaze, imdb).

Actual

Items have valid titles/artwork but identifiers: []. Example: Reacher from TV popular browse has no identifiers. Alien collection members likewise have identifiers: [].

Likely cause

projectSearchMedia only extracts theMovieDbId, theTvDbId, imdbId, seriesId. The v2 browse routes (/api/v2/Search/tv/{category}/{pos}/{amt}) and collection member records appear to carry the provider id under a different field (likely id), which is never read — so all identifiers drop out.

Correlation IDs

3aaa9c876dec34de15c91924 (tv popular), 7eefb545cfe32a53ca17e61c (tv anticipated), 796080cb5ffbc22cef2db6b9 (collection), d57965b84fa21b6727185c53 (tv trending)

## Summary `read_discover` projections return items with `identifiers: []` even though upstream results carry provider IDs. Affected media cannot be passed to `read_media` details or `write_request_create`, breaking the discover→request workflow. ## Environment - Binary: deployed darwin-amd64 build from `develop` @ `d047d76` - Ombi: 4.53.10 (https://ombi.i3omb.com), JWT auth ## Reproduction ```json read_discover {"action":"browse","media":"tv","category":"popular","page":{"limit":5}} read_discover {"action":"browse","media":"tv","category":"anticipated"} read_discover {"action":"browse","media":"tv","category":"trending"} read_discover {"action":"collection","collection_id":8091} ``` ## Expected Each item carries at least one usable identifier (e.g. `tmdb`, `tvdb`, `tvmaze`, `imdb`). ## Actual Items have valid titles/artwork but `identifiers: []`. Example: `Reacher` from TV `popular` browse has no identifiers. Alien collection members likewise have `identifiers: []`. ## Likely cause `projectSearchMedia` only extracts `theMovieDbId`, `theTvDbId`, `imdbId`, `seriesId`. The v2 browse routes (`/api/v2/Search/tv/{category}/{pos}/{amt}`) and collection member records appear to carry the provider id under a different field (likely `id`), which is never read — so all identifiers drop out. ## Correlation IDs `3aaa9c876dec34de15c91924` (tv popular), `7eefb545cfe32a53ca17e61c` (tv anticipated), `796080cb5ffbc22cef2db6b9` (collection), `d57965b84fa21b6727185c53` (tv trending)
gronod added this to the M3 — Identity projection (discover → media → request) milestone 2026-09-19 08:58:01 +01:00
Author
Owner

Fixed in #21 — v2 browse/collection members now emit id under the origin namespace (tmdb) when theMovieDbId is absent.

Fixed in https://git.i3omb.com/gronod/ombi-mcp/pulls/21 — v2 browse/collection members now emit `id` under the origin namespace (`tmdb`) when `theMovieDbId` is absent.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Reference: gronod/ombi-mcp#2