[mailing] Re: [mb-users] Label codes

Don Redman donredman at gmx.de
Tue Jun 28 12:40:59 UTC 2005


On Tue, 28 Jun 2005 01:05:59 +0200, Age Bosma wrote:

> Marco Sola wrote:
>> On Monday, June 27, 2005 10:20 PM,
>> Lauri Watts <krazykiwi at gmail.com> wrote:
>>
>>> Catalogue numbers: Internal per-label (not guaranteed to be unique,
>>> but generally so) identifiers of different releases.
>>
>>> Label Codes: One per *label*, will be on many releases, as it
>>> identifies everything they have released.
>>   Pardon, a big misunderstanign by me.  Btw I found this one an info  
>> even more unuseful to collect.
>>
>
> Why is this info be useless to collect? The same could be said of  
> releases dates or release countries if you're not interested in those.  
> What the hack, why even bother subdividing tracks into albums? What's  
> the point in knowing on which album a track is released if you have the  
> track and band name anyway?
>
> Just like it's important for a music info db to collect the info  
> mentioned above imo it's also important to know which record label  
> released a specific album. It's general info about a release and  
> therefor of value for a music info db.

Uh, calm down.
Actually the info that definetly *is* useful to collect is the *label*.  
MusicBrainz does not offer this at all and this is pretty strange. I do,  
however, doubt that someone will write the code to suport labels. Instead  
the next logical step after AdvancedRelationships is something like  
AdvancedEntities. With such a tool any new entity (like work/symphony,  
label, studio, club/location) could be added and then related to existing  
entities.

I fear that this will take some time to come up. What should we do in the  
meantime? Ignore labels alltogether?

   DonRedman



-- 
Words that are written in CamelCase refer to WikiPages:
Visit http://wiki.musicbrainz.org/ the best MusicBrainz documentation  
around! :-)



More information about the MusicBrainz-users mailing list