Export generated collection to json file. | Voters

Export generated collection to json file.

0xd2c45ed0e65e5edc

A collection's content is dumped to a JSON (preferably the same as the mbdlist format - see below).
{
"movies": [
{
"id": 845781,
"rank": 1,
"adult": 0,
"title": "Red One",
"imdb_id": "tt14948432",
"tvdb_id": null,
"language": "en",
"mediatype": "movie",
"release_year": 2024,
"spoken_language": "en"
},
{
"id": 912649,
"rank": 2,
"adult": 0,
"title": "Venom: The Last Dance",
"imdb_id": "tt16366836",
"tvdb_id": null,
"language": "en",
"mediatype": "movie",
"release_year": 2024,
"spoken_language": "en"
}
],
"shows": []
}
These JSON files can be used to create collections in Jellyfin with the aid of a third-party tool.

A week ago

Yozora

We would probably need to know what data Jellyfin requires from a JSON in order for it to be turned into a collection

0xd2c45ed0e65e5edc

Yozora name, imdb_id, year - that's what I'm using from the json to create the collections. I'm running a modified version of Jellyfin-Auto-Collections that can use locally stored json files from mdblist: https://github.com/ghomasHudson/Jellyfin-Auto-Collections

Yozora

0xd2c45ed0e65e5edc This is quite easily achievable using a Python script:
https://gist.github.com/YozoraXCII/7e5ce3bf622b566cccd5561f3e517c7d
Fill in YOUR-PLEX-URL and YOUR-PLEX-TOKEN. When you run the script, it will ask you for your library and collection name and then produce the JSON.
I have attached an example JSON I produced from one of the collections in my library.

The_Bourne_Collection

0xd2c45ed0e65e5edc

Yozora I don't use Plex, so how am I meant to use this python script? What I'm requesting is for kometa to output a json, that contains title, imdb_id, year, for each collection that it would generate. I'll use Jellyfin-auto-collections with the generated jsons to create collections in JellyFin.

Chaz Larson

0xd2c45ed0e65e5edc
You're posting a request for a product that currently supports only Plex; it doesn't seem outrageous to assume that you are presently using Kometa with Plex and are seeking to migrate collections to Jellyfin.
In Kometa, "a collection's content" is something that exists only in Plex.  There's no way to run Kometa at all without a connection to a Plex server, so there's no way to do this without adding direct support for  Emby/Jellyfin, at which point this feature request isn't needed.
You're already sourcing your collections from MDBList, so which collections are you referring to in this feature request?  Some other sites like MDBlist?  Trakt or the like?
The tool you link to seems to already do that, so what specifically are you asking for that it doesn't already do, that requires Kometa?  This is a sincere question.

0xd2c45ed0e65e5edc

Chaz Larson My primary use of Kometa would be to consolidate data from various sources. The project I linked doesn't offer the same level of consolidation or granular control as Kometa does.
From your response, it appears that Kometa does not cache data like title, year, and imdb/tmdb_id for items from its various sources before passing them on to Plex for identification. 
What data is collected from the sources that could be compiled into a JSON file? 
If I created my own code to find imdb/tmdb_ids, position_in_collection, title, and year would be sufficient information.

Chaz Larson

0xd2c45ed0e65e5edc
It does cache some of that information, but everything it does depends on an initial connection to Plex, since it's all targeted at what's available in Plex.
For example, If one creates a collection based on a letterboxd list, the contents of that list are cached, but Kometa won't even make that request in the first place if there is no Plex server to target.
The data that is collected from the sources varies with the source; Kometa then tried to match things via IDs [tmdb/imdb].

Chaz Larson

0xd2c45ed0e65e5edc
> From your response, it appears that Kometa does not cache data like title, year, and imdb/tmdb_id for items from its various sources before passing them on to Plex for identification. 
This is true, Kometa starts by cataloging what's available in Plex and matching everything to a TMDB ID.  This information is cached.
Then it requests, say, a letterboxd list.  It converts everything in that letterboxd list to TMDB, then it can figure out what things from that list are in Plex and can go into the collection.  It creates the collection and processes the missing items as requested [list them, send them to radarr].  The list that came back from letterboxd is cached.
Sure, it could, at that moment, also spit out a JSON file describing the collection for import to Jellyfin, but it can't get there without Plex, as currently architected.
Everything starts with "What's in Plex right now?"