I suggest the following practice for box sets:

Mother profiles should NOT contain:
Genres, (Production Year), Country of origin, Studios, Video Formats, Features, Audio Tracks, Subtitles, Cast, Crew, Easter Eggs.

Child profiles should NOT contain:
DVD Release, Case Type, SRP, Overview, Cover Scans.

This applies to typical box sets with more than one movie spread on separate discs not otherwise sold separately so that the child profile sould be registered by Disc ID, not a separate UPC#. One example could be the Die Hard Trilogy sold as one digipak with 3 discs.

There will of course allways be a few exceptions to this, but as a general rule, I think this would be the best practice.

That sounds a bit strange to me. The mother profile has Genres, Production Year the one from the oldest included childfilms, Country of origin. I agree no Studios, but Media Companies. Video Formats I did put it in if all childprofiles have the same, f.e. 1.85:1 Widescreen. If the childfilms have different sizes then leave it empty.  I agree with no Features, except if there are f.e. Postcards included you may put it there, no Audio Tracks, Subtitles, Cast and Crew is the rules and I agree.

Why should childprofiles not have a DVD Release? It's the same as in the Mainprofile. Also case type is needed. If I search a film, get it in the results then I like to know when it is released and in what kind of case it is, as I see not the Mainprofile at this time. SRP is always 0.00 in childprofiles, Overview must be there, same reason as above. Often Mainbox has only a very little Overview for each film. Here you may take the full overview from another single released profile that describes the childprofile film better. Finally, we need the Coverscans also in the child, how would this look without, ugly ugly ugly.

Think the actual rules for main- and childprofiles are perfect, I see no reason to change anything.

The only thing I agree with you on the child profiles is if they are disc ID based they should not have the SRP

Children should also be UPC based IF the box set contains the separate films in UPC based packaging, otherwise Disc ID


Parent profiles should contain the production year based on the rules. And the MC


http://www.invelos.com/dvdpro/contributions/Rules.aspx?display=boxsets

I don't care. I do not have any parent/child profiles in my collection. One movie = one profile, and that's all.

Quoting superted:

Quote:
I don't understand why you guys have such a problem with this. I don't want to have wrong scans, release dates, SRP, and so on.

You seem to assume that the child profiles only belong to one mother profile. They very often do not.

Besides, it is unneccesary redundancy.

What I suggested is pretty basic for those of you who have worked with information modeling and relational databases.

How do you handle child profiles that are also standalone profiles?

Quoting SwissFilm:

Quote:

Why should childprofiles not have a DVD Release? It's the same as in the Mainprofile. Also case type is needed. If I search a film, get it in the results then I like to know when it is released and in what kind of case it is, as I see not the Mainprofile at this time. (...) Finally, we need the Coverscans also in the child, how would this look without, ugly ugly ugly.

No, it is not necessarily the same as the Mainprofile. Would you like to see the data/scans from your own box set, or from a different one...?

Quoting Scooter1836:

Quote:

Children should also be UPC based IF the box set contains the separate films in UPC based packaging, otherwise Disc ID

As specified in the first post, my suggestions only apply to child profiles registered with Disc ID. Child profiles registered with UPC# should be treated as usual.

Quoting DoubleDownAgain:

Quote:

But disagree with your take on the child.  In my experience most of children only belong to one profile.  But agreed it isn't uncommon for the same DiscID to be associated with several different Parents.

I have literally several hundred child profiles that are originally registered on a different box set than mine. Because of this, the data in these child profiles are completely wrong.

Quoting DoubleDownAgain:

Quote:

I don't see why you'd want blank information.  For those Children all you have to do is copy the Release date, casetype, Cover scans from the parent.  Which you would have to do anyways if they were blank by default.

I would rather have blank information, than wrong information. Besides the information is already in the mother profile. To put the data in both mother and child profiles would be redundancy, which should be avoided in the database.

Quoting superted:

Quote:


I would rather have blank information, than wrong information. Besides the information is already in the mother profile. To put the data in both mother and child profiles would be redundancy, which should be avoided in the database.

Well feel free to talk with Ken about cleaning up the data model and rewrite the application around it.

When a disc ID based child is re-used across multiple box sets the only things that would be different are the case type, MC, release date, overview and images.  Simple enough to deal with in your local until Ken can get around being able to vary this data across releases.

You would rather have no data, but a lot more of the community would rather have data and tweak and lock the small number of fields until an enhancement can be made.

To do what you ask several rules would have to be re-written, so it probably won't happen

Quoting Scooter1836:

Quote:
You would rather have no data, but a lot more of the community would rather have data ...

I don't know how you know what wants the community... In my case, I prefer blank field than wrong data. A blank field is easy to see and you can fill it. An error in a field is more difficult to see rapidly. That is why I generally prefer to build my own profiles than download them with their collection of errors.