| Registered: July 29, 2007 | Reputation:  | | Posts: 482 |
| | Posted: | | | | The Case
1 case containing 2 seasons on 5 discs (2x4 epsiodes for one season, 2x4 epsiodes + 1x2 episodes for the other season)
The Existing Profile
1 parent profile (no cast/crew data)
2 child profiles under discID from first disc per season (cast/crew data for whole season)
those discID based child profiles contain all discs per season
parent EAN1 contains children DISC1 and DISC3
child DISC1 discIDs: DISC1, DISC2
child DISC3 discIDs: DISC3, DISC4, DISC5
This seems to me as a logical division between seasons which could be done locally but is not meant to be a global entry.
I would think there should be either 1 parent with 5 children or just 1 profile at all.
I do have to admit I like the benefit of how the existing profile
a) divides the seasons and
b) affects the profile count in my database.
Also I don't like disc based profiles for TV shows and avoid them whenever I can.
So, is this a valid profile structure?
I have 4 profiles in my database that fit that description and 1 similar one (1 Box, 3 seasons (1 case per season, 2 discs per case) 1 EAN for the box, no EAN for the cases)
Another question: Is 'series devised by' to be entered as 'developed by' or not at all? | | | | Last edited: by yeshee |
|
| Registered: May 19, 2007 | Reputation:  |  Posts: 5,715 |
| | Posted: | | | | No, this is not valid. Season profiles are allowed only if each season has its own UPC/EAN.
If I understand it correctly, there should be one profile for the complete series (using the UPC and including all information for all episodes and discs). Further more disc level profiles for all five discs (based on the discIDs, equally side by side) could be created, but need not to be. | | | | Complete list of Common Names • A good point for starting with Headshots (and v11.1) |
|
| Registered: July 29, 2007 | | Reputation: | | Posts: 482 |
| | Posted: | | | | That's what I thought, thanks |
|