[mb-style] RFC: Change BoxSetNameStyle
Andrew Conkling
andrew.conkling at gmail.com
Mon Mar 24 21:10:01 UTC 2008
On Mon, Mar 24, 2008 at 5:00 PM, Chris B <chris at whenironsattack.com> wrote:
> On 24/03/2008, Frederic Da Vitoria <davitofrg at gmail.com> wrote:
> > I disagree completely. I don't care if a CD was released as a 2 CD, 3
> CD, 70
> > CD or 45 billions CD box set, as long as it was sold separately. These
> kind
> > of box sets are purely commercial technicalities, and IMO this is
> discogs'
> > work, not MB's.
>
> right! i agree with this and similar sentiments. if we want to index
> everything seperately, then it seems trite to single out boxsets, when
> a true 'index everything' system would involve so much more. i really
> think it is essential we first have a 'release groups' or similar
> system to start wholesale separating of boxsets/individual issues.
>
> if an editor has good reason for adding a boxset seperately then
> that's cool. eg, i doubt these 160CD sets are available separately
> *entirely*. once one is only available in the set than you are well
> within your rights to add the whole set, as they're needed for
> context. see that classic example: prince "The HIts/The B sides".
>
> BoxSetNameStyle and the 'alias' system of merging artists are some of
> my 'favourite' features of MBz, and why i use it for tagging against
> discogs data (which you can use in certain taggers).
A few people have this sentiment, but isn't the behavior proposed in the RFC
already what we do for TranslationTransliterationRelationshipType? I think
Lauri put it aptly:
On Mon, Mar 24, 2008 at 8:16 AM, Lauri Watts <krazykiwi at gmail.com> wrote:
> This is at least as valid a reason to duplicate an album as any pseudo
> release is, I think. Maybe more valid.
I don't particularly like that we (have to) do that, but it seems like the
best way to cover a wide userbase.
The (key) thing I like about this proposal (and the
TranslationTransliterationRelationshipType way too) is that we're not just
straight-up duplicating data; we're duplicating it in a trackable way. The
AR in the TTRT lets us know which are the duplicated PseudoReleases so that
when NGS comes and saves us all from music index chaos, we have a way to
track them down and fix them. The same would apply here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.musicbrainz.org/pipermail/musicbrainz-style/attachments/20080324/b86e3c59/attachment.htm
More information about the Musicbrainz-style
mailing list