Removing identification removes the item from any collections

[crusher11 1101]

Title.

[Neminem 1519]

Why should it not ?

[ebr 16185]

Correct.  Collections are a function of the metadata of the items within them.  If you remove the metadata, you remove it from the collection.

[crusher11 1101]

2 hours ago, jaycedk said:

Why should it not ?

Because it still belongs in the collection I put it in?

[Neminem 1519]

You are removing the identification and there by removing the relationship.

Should be removed.

I half a year, when you go to watch that item, you wonder why it wont play.

Well because you removed the identification.

You would have to return here, and ask why it can't play ¯\_(ツ)_/¯

[Happy2Play 9782]

Removing Identification technically should clear the entire nfo file/all database fields ie the custom <set> you previously applied as Collection info comes from the item not any collection.nfo/xml.

[crusher11 1101]

10 hours ago, jaycedk said:

You are removing the identification and there by removing the relationship.

Should be removed.

I half a year, when you go to watch that item, you wonder why it wont play.

Well because you removed the identification.

You would have to return here, and ask why it can't play ¯\_(ツ)_/¯

Why would different identification prevent it from playing?

9 hours ago, Happy2Play said:

Removing Identification technically should clear the entire nfo file/all database fields ie the custom <set> you previously applied as Collection info comes from the item not any collection.nfo/xml.

It's a "remove identification" button, not a "clear all metadata" button (and indeed it doesn't delete images, which then have to be cleared manually).

[darkassassin07 652]

The id is what's being added to a playlist, not the file linked to that id.

 

Lets say you have a file 'A.mp4' that gets identified as 'example movie'. You add 'example movie' to a playlist and then play it, only to find it's not actually 'example movie'.

You then re-identify 'A.mp4' as 'different example' and add a new file 'A.mkv' which is then correctly identified as 'example movie'. 

'example movie' will still be in the playlist, because that's the id you added.

'different example' will not. Even though it's the same file, it's not the id that was added to the playlist.

 

 

If it was done based on specific files instead of what they've been identified as, every time you replace a movie/episode/file with a different version (upgrading quality, different format, replacing a corrupt file, etc) it would be removed from every playlist.

[bakes82 167]

14 hours ago, ebr said:

Correct.  Collections are a function of the metadata of the items within them.  If you remove the metadata, you remove it from the collection.

When you create a collection does it not use the unique id of the file not the associated identifier.  I’m not sure what point he’s trying to make but I assume it’s a you add a bunch of movies to a collection of western. Then one is mismatched and you remove to fix to the correct name it’s now now longer linked.  If it was a smart list like plex and using actual meta to drive the filter than sure.

[crusher11 1101]

58 minutes ago, darkassassin07 said:

The id is what's being added to a playlist, not the file linked to that id.

 

Lets say you have a file 'A.mp4' that gets identified as 'example movie'. You add 'example movie' to a playlist and then play it, only to find it's not actually 'example movie'.

You then re-identify 'A.mp4' as 'different example' and add a new file 'A.mkv' which is then correctly identified as 'example movie'. 

'example movie' will still be in the playlist, because that's the id you added.

'different example' will not. Even though it's the same file, it's not the id that was added to the playlist.

 

 

If it was done based on specific files instead of what they've been identified as, every time you replace a movie/episode/file with a different version (upgrading quality, different format, replacing a corrupt file, etc) it would be removed from every playlist.

We're not talking about playlists.

[darkassassin07 652]

1 hour ago, crusher11 said:

We're not talking about playlists.

Woops, collections*

Functionally equivalent in this context.

Edited February 23, 2024 by darkassassin07

[crusher11 1101]

No, because collection IDs are stored in an item's NFO file, so it can be renamed, moved, re-identified, and everything else without affecting a thing.

Not sure how playlists work.

[ebr 16185]

10 hours ago, crusher11 said:

It's a "remove identification" button, not a "clear all metadata"

The former implies the latter because, if the metadata was created for the wrong item, then it is wrong once you change what the item is.

[crusher11 1101]

1 hour ago, ebr said:

The former implies the latter because, if the metadata was created for the wrong item, then it is wrong once you change what the item is.

Not necessarily. And images are far more likely to be incorrect than collections are.

In my case, I added an entire box set, multiselected, added them to a collection for the box set, then realised a couple of the movies had been misidentified. The collection information was correct, and I did not expect it to be deleted when I removed the incorrect identification.

[Luke 42080]

I think you can argue this one either way, and both sides have valid arguments.

What we could do is start keeping track of whether a collection was auto-created or manually created, and then the reset feature could only clear out the auto-created ones.