I fully support Pete's and DJ Doena's ideas on this issue.

The situation as is, where a particular disc can be part of countless box sets, is also confusing the hell out of less experienced users/contributors. Let's think of them too for a change. 

What your ignoring is that this is a database that serves a wide community and is marketed as such, it's not ideal or best practice that multiple people have to alter a profile locally to match what they own.

In some (thankfully rare cases) UPCs are re-used for different films, which can mean having to enter all data, not just alter small amounts.

As for your issue about updating multiple profiles presumably we're talking about cast and crew, cloned profiles wouldn't make this significantly worse. It could instead be a step to reducing the issue, where we have a known link there would be no rationale for not allowing cast and crew updates to be applied to all cloned profiles.

I think there are some  things that would help out alot.

1)  ability for the online to maintain multiple coverart for a given profile.

2) create links within a child profile to take information from the parent.
    For most of my boxsets, the child does not have coverart itself and uses the parent.  If there was a checkbox to link the coverart and casetype to the parent, we would not have to worry about coverart of the child.

3) option within system config to 0 out price for child profiles

4) Ability to link a single diskID to more than 1 parent in the local DB.

I know this will not change the "rerelease on same upc/ean issue" but would eliminate a number of visual problems that we have now.

Quoting CharlieM:

Quote:
If you want a complete program change, I think all profiles should be profiled based upon disc ID.  Then link the ID to the parent UPC/EAN.

If written correctly, the parent then can pull the appropriate info from the child.  Add the coverart, srp price paid, and a couple of other "Set oriented" fields and there you have it.

Charlie

Not sure how you see this working? Only on the basis the disc id isn't unique enough on it's own as publishers sometimes use the same disc in different box sets.

Quoting xyrano:

Quote:

Maybe, a MD5 hash number could help solve that problem, e.g. [DVDP Disc Id].[MD5 hash].
The source for the generated md5 hash number could for instance be; id, label, size of content (if possible) and other attributes taken off the disc programmatically, that could help producing a uniq identifier.

Forgive my ignorance, I only use computers, don't program anything for them, but wouldn't the MD5 hash be the same if the disc was the same?

For example if a film is packaged in two different box sets with exactly the same content on the disc wouldn't the hash figure it creates, by pulling info from the disc, be the same?

As an example the copy of the Omen I own is part of a Blair Witch/The Entity and The Omen boxset (5039036018012) as well as the Omen Trilogy set.

Quoting CharlieM:

Quote:
If you want a complete program change, I think all profiles should be profiled based upon disc ID

I wouldn't recommend that. It could mean that the numbers of Bluray-submission might go down significantly because not everyone has a BD-ROM.

Quoting Lithurge:

Quote:
Quoting xyrano:

Quote:

Maybe, a MD5 hash number could help solve that problem, e.g. [DVDP Disc Id].[MD5 hash].
The source for the generated md5 hash number could for instance be; id, label, size of content (if possible) and other attributes taken off the disc programmatically, that could help producing a uniq identifier.

Forgive my ignorance, I only use computers, don't program anything for them, but wouldn't the MD5 hash be the same if the disc was the same?

For example if a film is packaged in two different box sets with exactly the same content on the disc wouldn't the hash figure it creates, by pulling info from the disc, be the same?

As an example the copy of the Omen I own is part of a Blair Witch/The Entity and The Omen boxset (5039036018012) as well as the Omen Trilogy set.

Yes to all.
If a publisher use the same disc id but say, added extra content to one of them, then WE would have a uniq number for both.

Quoting xyrano:

Quote:
If a publisher use the same disc id but say, added extra content to one of them, then WE would have a uniq number for both.

Unfortunately I'm unable to find the technical specs of Disc-ID but I think the way Ken described them back in the days they aren't really numbers on the disc but a kind of hash build from several factor, size of the disc-image and dates. So every change to an image would result in a different Disc-Id which we have 18.446.744.073.709.551.616 of to choose from.