Jump to content

Merged TV shows - missing merged IDs in /Items endpoint


Recommended Posts

Posted

I have a TV library with two folders. Option "Automatically merge series that are spread across multiple folders" is ticked.

I have a series that's spanned across two folders in the same library. That series appears only once when querying /Items.

My issue is that internally, Emby has two series ID for that series, as can be seen on the episodes: their SeriesId differ. When querying for the series list, one of those IDs is hidden and we only see the other one in Emby response.

My request to you would be to provide a new option to not merge series so that every individual series shows up in the response.

Current behaviour:

{
    "Items": [
        {
            "Id""A",
            "Path""/path/1",
            "Type""Series",
            ....
        }
    ],
}

Requested behavior with this additional option:

{
    "Items": [
        {
            "Id""A",
            "Path""/path/1",
            "Type""Series",
            ....
        },
        {
            "Id""B",
            "Path""/path/2",
            "Type""Series",
            ....
        },
         ....
    ],
}
 
Is this possible?

 

Another accepted alternative would be that you expose the merged IDs on the Series entity so we know all possible IDs of a merged series.

{
    "Items": [
        {
            "Id""A",
            "Type""Series",
            "MergedIds": [
                "B",
                "C"
            ],
            ....
        }
    ],
}

 

 

On a side note, querying /Items with additional filter Ids=B does return the series (with correct ID).

{
    "Items": [
        {
            "Id""B",
            "Path""/path/2",
            "Type""Series",
            ....
        }
    ],
}
But removing that filter hides that series ID.
Posted
Quote

Requested behavior with this additional option:

{
    "Items": [
        {
            "Id""A",
            "Path""/path/1",
            "Type""Series",
            ....
        },
        {
            "Id""B",
            "Path""/path/2",
            "Type""Series",
            ....
        },
         ....
    ],
}
 

HI, wouldn't this prevent the feature from working entirely?

Posted
Quote

Another accepted alternative would be that you expose the merged IDs on the Series entity so we know all possible IDs of a merged series.

{
    "Items": [
        {
            "Id""A",
            "Type""Series",
            "MergedIds": [
                "B",
                "C"
            ],
            ....
        }
    ],
}

 

Yes this makes more sense.

  • Thanks 1
Posted
12 hours ago, Luke said:

HI, wouldn't this prevent the feature from working entirely?

Not if you add an option such as "UnmergeSeries" to have that new behaviour, as to not break current API behaviour.

Thank you for looking into it.

Posted
53 minutes ago, sephrat said:

Not if you add an option such as "UnmergeSeries" to have that new behaviour, as to not break current API behaviour.

Thank you for looking into it.

Sure, yes. Not having an unmerge button is a bit of a hole in the current behavior.

Posted

Sorry but just to be sure there's no misunderstanding, I'm not talking about a button but an additional option to the Items endpoint.

So that /Items keeps returning the same behaviour

{
    "Items": [
        {
            "Id""A",
            "Path""/path/1",
            "Type""Series",
            ....
        }
    ],
}
But with the new option, /Items?UnmergeSeries=True returns:
{
    "Items": [
        {
            "Id""A",
            "Path""/path/1",
            "Type""Series",
            ....
        },
        {
            "Id""B",
            "Path""/path/2",
            "Type""Series",
            ....
        },
         ....
    ],
}
horstepipe
Posted

@Luke

the latest beta release note

Quote

Fix regressions with tv series folder parsing

is not about this issue, is it?

Best regards

Posted
3 hours ago, horstepipe said:

@Luke

the latest beta release note

is not about this issue, is it?

Best regards

No it's not.

  • Thanks 1
horstepipe
Posted

@TeamB

may I ask how you solve that problem in the Emby4Kodi plug-in?

 

best regards

Posted
6 minutes ago, horstepipe said:

@TeamB

may I ask how you solve that problem in the Emby4Kodi plug-in?

 

best regards

emby4kodi is @quickmic

quickmic
Posted (edited)
2 hours ago, horstepipe said:

@TeamB

may I ask how you solve that problem in the Emby4Kodi plug-in?

 

best regards

e4k always merges series/seasons located on different folders. It uses the PresentationUniqueKey for detection. This key is similar even if the IDs are different.

Edited by quickmic
horstepipe
Posted

Sorry folks I mixed you up 🙂

horstepipe
Posted
45 minutes ago, quickmic said:

e4k always merges series/seasons located on different folders. It uses the PresentationUniqueKey for detection. This key is similar even if the IDs are different.

@sephrat

Would that be possible for Ombi or will this need a bigger development effort?

adminExitium
Posted
On 26/10/2022 at 23:43, Luke said:

Yes this makes more sense.

I wonder if it would be better to add PresentationUniqueKey as a filter for the Items endpoint and it can return all Item objects that have the same key.

 

Seeing something like MergedIds within an Item object seems weird somehow.

  • 2 weeks later...
horstepipe
Posted (edited)

@Luke

any chance that this will be added in this beta circle?

This is mandatory for Ombi to work properly if one uses multiple tv show directories with the same show.

Unbenannt.PNG.e0ff64211d83c7ddcf85956b7fe36eec.PNG

Best regards

Edited by horstepipe
Posted

I don't have an ETA, sorry, but it's certainly possible.

  • Thanks 1
horstepipe
Posted
38 minutes ago, Luke said:

I don't have an ETA, sorry, but it's certainly possible.

Thanks.

So I expect this is going to take awhile.

Could you or anybody else provide a method to find all shows whose seasons/episodes are in two or more folders so I can manually merge them?

Doing this completely by hand would be a pita. 

  • 5 months later...
horstepipe
Posted
On 11/16/2022 at 6:35 PM, Luke said:

I don't have an ETA, sorry, but it's certainly possible.

anything new here? 🙂

Posted
5 hours ago, horstepipe said:

anything new here? 🙂

I don't have an update yet, sorry.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...