'Label Code' definition in guidelines is incorrect and needs to be changed
Started by jweijde over 3 years ago, 38 replies
-
jweijde edited 29 days ago
RSG §5.2.b. states:
5.2.b.Label Codeis a four or five digit code prefixed with LC. GVL started on 1st May 1976 to allocate Label codes to labels in order to uniquely identify them. Codes are currently assigned by GVL to companies engaged in music recording that are located in the countries of the EU. Please enter the whole code as it appears on the release including the 'LC' prefix, if present. An example is "LC0125". Please be careful not confuse this with catalog or matrix numbers.
.
The information in this guideline is incorrect. Label codes were not introduced to "uniquely identify" labels.
They were introduced by GVL as a tool to identify the person or company the payments for neighbouring rights should be distributed to. GVL is an organisation tasked with distributing these payments to rights holders that ed with them.
Saying it uniquely identifies labels, incorrectly suggests that label codes can be used to determine the label of a release. It also gives the GVL data more credit than due - GVL is not a registry for label names.
They are also not assigned to any company engaged in music recording that is located in the EU. They are only assigned to those that with GVL.
The current proposal is to change it into the following:
Label Code
This is a four or five digit code, usually prefixed with 'LC'. Please enter the whole code as it appears on the artwork including the 'LC' prefix, if present. An example is "LC0125" or "LC 14666".
Label codes are used to identify the person or company certain royalty payments should be distributed to in . They do not identify the label of a release. For instructions how to identify the label, see RSG §4.1.2 and RSG §4.6.2.
In rare cases, it can occur that the catalog number of a release starts with 'LC'. An example are some US releases on the Epic label. These catalog numbers should not be entered as 'Label Code'. When matrix data contains a label code, the label code can be entered as 'Label Code' and as part of the matrix data.
Background
Label codes were introduced in in May 1976 by GVL, a rights management organisation. The goal was to improve the process of royalty payments. Each rights holder - a performer or producer of sound recordings - that signs up with GVL is assigned a 'label code'. Rights holders put the code on releases so that those that need to pay royalties can use it when making payments.
Even though GVL indicates label codes are allocated to one label, the same label code can appear on releases with different labels. The label name ed with GVL for a certain label code also regularly does not match the label name used on a release the label code is found on. The GVL database also lists a 'Hersteller' for each label code. This is the rights holder or the representative of the rights holder in . This is not neccesarily the record company that owns the label. For these reasons, information from GVL should not be used to determine the label of a release, the label name or the parent company.
Diognes_The_Fox can you please change this ?
Edit: minor change to wording
Edit2: rewrite after comments -
jweijde edited over 3 years ago
Clogwhistle
I don't understand the term "neighbouring".
This is mostly about royalties for radio play and public performance.
Clogwhistle
Have you sourced the bulk of the text of paragraphs 2 and 3 from some external source?
Bssed on information found at https://gvl.de/ , at https://labelrecherche.gvl.de/ and on releases found on Discogs.
You can also read about it at https://en.wikipedia.org/wiki/GVL_(copyright_collection_society)
There is also some information about what GVL does in Billboard Magazine from 1974-6. I don't have those references at hand right now. -
Show this post
Neighbouring Rights are effectively payments to the people who play on or produce music that is performed on radio, TV etc. A very healthy income stream.
GVL also oversee other income streams that benefit the master owner. -
Show this post
I'm 100% in favour of this change BTW -
Show this post
Opdiner
I'm 100% in favour of this change
Same here. +1 -
Show this post
Opdiner
I'm 100% in favour of this change BTW
+1 -
Show this post
jweijde
The proposal is to change it
+1 -
Show this post
+1 to changing the guideline text. -
Show this post
Very well put, +1 -
Show this post
jweijde
Label Code This is a four or five digit code prefixed with LC.
This also needs to be changed. Label codes are mostly prefixed with LC, but not exclusively/always. For quite a number of years the Italian label Splasc(h) Records simply used the four-digit "7691" to denote the label code. -
Show this post
MartinR
Label codes are mostly prefixed with LC, but not exclusively/always. For quite a number of years the Italian label Splasc(h) Records simply used the four-digit "7691" to denote the label code.
Thanks, I'll update the text shortly. -
Show this post
+1 from me. Clear improvement. -
Show this post
Count me in for this change. -
Show this post
Hey oh, another constructive discussion / proposal under the radar because not enough hubris, I guess?
+1 for whatever puts an end to "LC = label" despite what's actually on the release -
Show this post
+1
Yes please! -
Show this post
Thanks for the .
MartinR
Label codes are mostly prefixed with LC, but not exclusively/always.
added the word "usually".
Any other improvements? -
Show this post
jweijde
The proposal is to change it
+1 -
Show this post
Bump to keep alive. -
Show this post
Can I just suggest that, if you use the term "neighboring", that it be explained, as I wouldn't have had the faintest idea what it meant unless Opdiner had explained it, and I daresay, people will misconstrue it. Otherwise use a different term. -
Show this post
Good that you mention that. I think it can still be improved. -
Show this post
I’d replace “the payments for neighboring rights” with “public performance royalties” or even just “certain royalty payments”.
I’d also suggest clarifying that if a label code actually appears in a matrix code, it should be recorded there as well as in its own field. The current proposed text makes that ambiguous. -
Show this post
I have updated the proposal in the OP based on the latest comments.
Please review :-) -
Show this post
+1 for proposal, but I'd scrap entirety of paragraphs 2 and 3.
The background info is not needed for guidelines and paragraph 1 already notes that label codes alone is an inaccurate way of finding the label. -
Show this post
trance-of-the-ages
The background info is not needed for guidelines and paragraph 1 already notes that label codes alone is an inaccurate way of finding the label.
3rd paragraph contains some extra instructions though -
Show this post
jweijde
3rd paragraph contains some extra instructions though
Ah true. It's not directly about entering BAOI, but I can see why you noted it.
I think that the first few lines of paragraph 1 are what almost all people will look for when they look up this guideline, so I'd still lose the background info and just keep the instructions to not use label code to determine label/LCCN, but I guess it doesn't really hurt to keep it either. -
Show this post
Bump.
Is the proposal in the first post OK or should it be condensed ? -
Show this post
Bump. welcome. -
Show this post
I would put the last paragraph as the second paragraph so that everything that is actual instructions are first. I would then put a header stating that the rest is background information so that people don't have to read further if they don't want to. -
Show this post
Like this
Label Code
This is a four or five digit code, usually prefixed with 'LC'. Please enter the whole code as it appears on the release including the 'LC' prefix, if present. An example is "LC0125". Do not enter them as catalog or matrix numbers.
Please note that when a label code is part of the matrix data, it should be entered as such too. In rare cases, catalog numbers can also start with 'LC' (for example some US releases on Epic).
Label codes are used to identify the person or company certain royalty payments should be distributed to in . They do not identify the label of a release. For instructions how to identify the label, see RSG §4.1.2 and RSG §4.6.2.
Background
Label codes were introduced in in May 1976 by GVL, a rights management organisation. The goal was to improve the process of royalty payments. Each rights holder - a performer or producer of sound recordings - that signs up with GVL is assigned a 'label code'. Rights holders put the code on releases so that those needing to pay royalties can use it when making payments.
Even though GVL indicates label codes are allocated to one label, the same label code can appear on releases with different labels. The label name ed with GVL for a certain label code also regularly does not match the label name used on a release the label code is found on. The GVL database also lists a 'Hersteller' for each label code. This is the rights holder or the representative of the rights holder in . This is not neccesarily the record company that owns the label. For these reasons, information from GVL should not be used to determine the label of a release, the label name or the parent company.
This also indicates that the first two paragraphs need some rewording and clarification as it currently states:
1. Do not enter as cat or matrix
2. Enter as matrix. -
Show this post
Relvet, good suggestions. Here's an update:
Label Code
This is a four or five digit code, usually prefixed with 'LC'. Please enter the whole code as it appears on the artwork including the 'LC' prefix, if present. An example is "LC0125" or "LC 14666".
In rare cases, it can occur that the catalog number of a release starts with 'LC'. An example are some US releases on the Epic label. These catalog numbers should not be entered as 'Label Code'. When matrix data contains a label code, the label code can be entered as 'Label Code' and as part of the matrix data.
Label codes are used to identify the person or company certain royalty payments should be distributed to in . They do not identify the label of a release. For instructions how to identify the label, see RSG §4.1.2 and RSG §4.6.2.
Background
Label codes were introduced in in May 1976 by GVL, a rights management organisation. The goal was to improve the process of royalty payments. Each rights holder - a performer or producer of sound recordings - that signs up with GVL is assigned a 'label code'. Rights holders put the code on releases so that those needing to pay royalties can use it when making payments.
Even though GVL indicates label codes are allocated to one label, the same label code can appear on releases with different labels. The label name ed with GVL for a certain label code also regularly does not match the label name used on a release the label code is found on. The GVL database also lists a 'Hersteller' for each label code. This is the rights holder or the representative of the rights holder in . This is not neccesarily the record company that owns the label. For these reasons, information from GVL should not be used to determine the label of a release, the label name or the parent company. -
Show this post
Still looks good to me. -
Show this post
+1
Looks good to go -
jweijde edited 29 days ago
Ok, let's finalize it.
Diognes_The_Fox, can you please change RSG §5.2.b to the following:
Label Code
This is a four or five digit code, usually prefixed with 'LC'. Please enter the whole code as it appears on the artwork including the 'LC' prefix, if present. An example is "LC0125" or "LC 14666".
Label codes are used to identify the person or company certain royalty payments should be distributed to in . They do not identify the label of a release. For instructions how to identify the label, see RSG §4.1.2 and RSG §4.6.2.
In rare cases, it can occur that the catalog number of a release starts with 'LC'. An example are some US releases on the Epic label. These catalog numbers should not be entered as 'Label Code'. When matrix data contains a label code, the label code can be entered as 'Label Code' and as part of the matrix data.
Background
Label codes were introduced in in May 1976 by GVL, a rights management organisation. The goal was to improve the process of royalty payments. Each rights holder - a performer or producer of sound recordings - that signs up with GVL is assigned a 'label code'. Rights holders put the code on releases so that those that need to pay royalties can use it when making payments.
Even though GVL indicates label codes are allocated to one label, the same label code can appear on releases with different labels. The label name ed with GVL for a certain label code also regularly does not match the label name used on a release the label code is found on. The GVL database also lists a 'Hersteller' for each label code. This is the rights holder or the representative of the rights holder in . This is not neccesarily the record company that owns the label. For these reasons, information from GVL should not be used to determine the label of a release, the label name or the parent company. -
Show this post
Diognes_The_Fox please implement this. -
Show this post
Edited to fix my smartphone typing.
jweijde
Label codes are used to identify the person or company certain royalty payments should be distributed to in .
Maybe reword slightly as does not seem to read clearly.
Otherwise +1