Open onnesoom opened 1 month ago
A question: Is the content of episodes.json unified for all software?
A question: Is the content of episodes.json unified for all software?
There are two primary approaches to saving metadata:
These services typically automatically fetch metadata from the internet. Users can edit this data if desired, but the process is lengthy. The .nfo files used by these services generally look like this:
Drawbacks of this method:
episodes.json
file (and some services like Jellyfin will recognize it), only the "episode_number" key is consistently recognized. Other keys, such as "name," may vary (e.g., Jellyfin can detect the "name" key even if it's named "title").Overall, the lack of third-party tools for creating metadata and the dependency on specific databases are significant limitations.
These services save metadata in a single JSON file with a consistent structure, as described in the original issue. There are multiple third-party software tools available to produce this type of JSON data. For instance, you can even use ChatGPT to generate the necessary JSON:
ChatGPT
Advantages of this method:
Downside:
For chatgpt , u need to add custom instructions from settings , thats it .
Additional information I forgot to add : the format for the T00:00:00
Part is THH:MM:SS
Current Functionality of the App
The app currently displays the names of all files within a folder in alphabetical order and presents the full file names. However, which can be inconvenient in several situations:
Long File Names
If the files have long names, they will be displayed in full. This can consume excessive screen space and make it difficult to recognize the episode numbers.
Non-Alphabetical or Non-Chronological Order
If the files are not downloaded from the same source (e.g., SubsPlease, Ember, ACG.rip), they will appear unorganized and unsorted. This lack of order is not ideal.
Presence of episodes.json
In modern media servers and library apps (e.g., Jellyfin, Plex, Emby, Aniyomi), media folders often contain an
episodes.json
file. The current model does not detect or display the corresponding episode names from this file.The format of
episodes.json
is as follows:In this format:
episode_number
corresponds to the detected episode number. This key must be present in the JSON file, while the rest are optional for additional information editing.name
corresponds to the title to be shown.date_upload
indicates the date and time of the episode's release.scanlator
provides additional information such as the episode description or whether the episode is a filler.Sources:
Improvements with Episode Number Recognition
Adding episode number recognition to the app will provide several benefits:
episodes.json
file, showing titles, upload dates, and additional information like scanlator notes.