tubearchivist/archived-tubearchivist-plex

Fork 0

mirror of https://github.com/tubearchivist/tubearchivist-plex.git synced 2026-03-23 20:37:11 +00:00

[GH-ISSUE #81] [Feature Request]: Single Season #29

New issue

Open

opened 2026-03-23 20:33:36 +00:00 by mirror · 5 comments

mirror commented

2026-03-23 20:33:36 +00:00

Owner

Originally created by @bnason on GitHub (Oct 6, 2024).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-plex/issues/81

I've read the documentation.

I have read the current limitations, and confirmed that this hasn't been requested as a feature request previously.

Your Feature Request

It would be nice to have the option of having a single season for a channel instead of being broken up by years. Plex can then be set to hide seasons for those with only one season.

Your help is needed!

Yes, I will work on this in the next few days or weeks.

Originally created by @bnason on GitHub (Oct 6, 2024). Original GitHub issue: https://github.com/tubearchivist/tubearchivist-plex/issues/81 ### I've read the documentation. - [X] I have read the [current limitations](https://github.com/tubearchivist/tubearchivist-plex#limitations), and confirmed that this hasn't been requested as a [feature request](https://github.com/tubearchivist/tubearchivist-plex/issues?q=is%3Aissue) previously. ### Your Feature Request It would be nice to have the option of having a single season for a channel instead of being broken up by years. Plex can then be set to hide seasons for those with only one season. ### Your help is needed! - [ ] Yes, I will work on this in the next few days or weeks.

mirror added the

help wanted

enhancement

labels

2026-03-23 20:33:36 +00:00

mirror commented

2026-03-23 20:33:37 +00:00

Author

Owner

@lamusmaser commented on GitHub (Oct 6, 2024):

Acknowledged. I would have to look into how best to do this. Unfortunately, I am unsure if we can do this on a per-channel basis or if this would have to be global for all channels in the library.

I can look into it more, but this will be after some of our other feature requests that are already in progress for research and development.

@lamusmaser commented on GitHub (Oct 6, 2024): Acknowledged. I would have to look into how best to do this. Unfortunately, I am unsure if we can do this on a per-channel basis or if this would have to be global for all channels in the library. I can look into it more, but this will be after some of our other feature requests that are already in progress for research and development.

mirror commented

2026-03-23 20:33:37 +00:00

Author

Owner

@bnason commented on GitHub (Oct 6, 2024):

I may take a stab at this. I'm assuming I will need to modify the Scanner. Since it already is looking at the ta_config.json, I could add some new keys there to control functionality, something like this:

{
    "ta_url": "http://tubearchivist.local",
    "ta_api_key": "xxxxxxxxxxxxxxxx",
    "channels": {
        "channleId": {
            "useSingleSeason": true
        }
    }
}

Honestly rather than having that boolean, I would prefer if it could be a format string that can use the data from get_ta_metadata to generate the value. Since I'm not a python developer, I'm not sure what options are available in the ecosystem to handle that. Do you have any ideas/input/advice on that?

Something like this:
Hard coded 1 for single season
Something like this for year based seasons where metadata is the result from get_ta_metadata:
"{metadata.date.published | format('%Y')}"

{
    "ta_url": "http://tubearchivist.local",
    "ta_api_key": "xxxxxxxxxxxxxxxx",
    "channels": {
        "channleId": {
            "metadata": {
                "season": "1"
            }
        }
    }
}

@bnason commented on GitHub (Oct 6, 2024): I may take a stab at this. I'm assuming I will need to modify the Scanner. Since it already is looking at the `ta_config.json`, I could add some new keys there to control functionality, something like this: ```json { "ta_url": "http://tubearchivist.local", "ta_api_key": "xxxxxxxxxxxxxxxx", "channels": { "channleId": { "useSingleSeason": true } } } ``` Honestly rather than having that boolean, I would prefer if it could be a format string that can use the data from `get_ta_metadata` to generate the value. Since I'm not a python developer, I'm not sure what options are available in the ecosystem to handle that. Do you have any ideas/input/advice on that? Something like this: Hard coded 1 for single season Something like this for year based seasons where `metadata` is the result from `get_ta_metadata`: `"{metadata.date.published | format('%Y')}"` ```json { "ta_url": "http://tubearchivist.local", "ta_api_key": "xxxxxxxxxxxxxxxx", "channels": { "channleId": { "metadata": { "season": "1" } } } } ```

mirror commented

2026-03-23 20:33:37 +00:00

Author

Owner

@jay-oswald commented on GitHub (Jan 7, 2025):

No need for this to be done in this plugin, plex already does this nativatly

On your libary settings, to go advanced, then set seasons to hide, no more seasons at all

@jay-oswald commented on GitHub (Jan 7, 2025): ![image](https://github.com/user-attachments/assets/67f62c95-126d-4e95-898d-0934b600903b) No need for this to be done in this plugin, plex already does this nativatly On your libary settings, to go advanced, then set seasons to hide, no more seasons at all

mirror commented

2026-03-23 20:33:38 +00:00

Author

Owner

@jay-oswald commented on GitHub (Jan 7, 2025):

Just realised you are probably wanting to do this for only some shows, and not others. So my above comment is probbaly not relevant. But I just hide all seasons or everything anyway, so its just a single list of vidoes like youtube.

@jay-oswald commented on GitHub (Jan 7, 2025): Just realised you are probably wanting to do this for only some shows, and not others. So my above comment is probbaly not relevant. But I just hide all seasons or everything anyway, so its just a single list of vidoes like youtube.

mirror commented

2026-03-23 20:33:38 +00:00

Author

Owner

@lamusmaser commented on GitHub (Mar 11, 2025):

I think if this is going to come in, it will be as part of v0.2.0, since we'll be making a lot of major changes to how things are operating and working anyway. Adding this in as a separate functionality that can be added by people will allow them to choose to integrate this.

As noted by @jay-oswald, you can always enable/disable this for the full library, but if you are looking for individual seasons, then I would want this to come through as something the Scanner performs. The Scanner will be able to handle those functions better for the onset, and would be able to change it later if someone modified the list.

@lamusmaser commented on GitHub (Mar 11, 2025): I think if this is going to come in, it will be as part of v0.2.0, since we'll be making a lot of major changes to how things are operating and working anyway. Adding this in as a separate functionality that can be added by people will allow them to choose to integrate this. As noted by @jay-oswald, you can always enable/disable this for the full library, but if you are looking for individual seasons, then I would want this to come through as something the Scanner performs. The Scanner will be able to handle those functions better for the onset, and would be able to change it later if someone modified the list.

mirror referenced this issue

2026-03-23 20:34:17 +00:00

[PR #91] [MERGED] V0.1.7 TA v0.5.0 compatibility #101