Commented Submission Guide

[Discussion] Guideline Update 2009 - Completed. (2010)
[Discussion] Guideline Changelog (2010)
[Discussion] Guideline Changelog (2013)

Database Guidelines 1. General Rules

◾ 1.1. Valid Information
◾ 1.2. Capitalization & Grammar
◾ 1.3. Required Fields For A New Submission
◾ 1.4. Unique Releases
◾ 1.5. Splitting items already in the database into unique releases
◾ 1.6. Submission Notes
◾ 1.7. Errors, Missing, And Conflicting Information
◾ 1.8. Languages
◾ 1.9. Unicode, Links, Formatting, and HTML
◾ 1.10. Conduct Whilst Using The Database
◾ 1.11. Guideline Updates

RSG §1.1.1.
You must have the exact release in your possession when you make a release submission.
Basing your submission only on information from websites, images, or anywhere else is forbidden, as is entering information for planned releases that haven't been manufactured.

Items can be submitted before the official release date, but you must at least one scan or photograph of the physical copy in your possession. Without visual proof, the submission may be removed until a valid image can be provided.

[RSG §14.1.4.]
Valid information should never be removed from a submission. If there is valid information in the wrong field, it should be moved to the correct field, not deleted.

RSG §1.1.2.
Sources of information external to the release itself may be added, but the physical 📌 [or digital] release must always be the main source. External sources of the information (for example websites, books, etc.) must be declared in the submission notes, explained in the Release Notes, and be verifiable as far as possible. Unsubstantiated information may be removed or rejected. External information should only be entered where it adds to the release information (for example, track names where none are given on the release). This is to ensure that only verified real releases are entered, and the data is as close as possible in relation to the physical 📌 [or digital] release. Please see the credit section for how to enter credits that are sourced externally.

[RSG §10.7.1.]
Credits that do not appear on the release can be added only under certain circumstances. The (credible) credit source must be stated in the submission notes, and the credit must be labeled with [Uncredited] in brackets after the credit role.
If other text is used in the credit brackets, the 'Uncredited' must have a comma separating it from the other text.

RSG §1.1.3.
Any item on an audio format (as given on the formats list page) is potentially eligible for inclusion to the Discogs database. Discogs only catalogs items that have been released to the general public, either as commercially sold items, or as free give-aways.
Items that are duplicated on recordable or readily reproducible media (for example CDr, MP3, or Cassette) will be held under closer scrutiny than items that are replicated on non-recordable media (for example vinyl records and 'pressed' CD's). Please include as much information as possible with the submission to establish the validity of borderline cases.

RSG §1.1.3.a.
Video: Only video items that have audio as the main focus are allowed, where "audio" is either one or more complete studio recordings, one or more complete live performances. If the item still makes sense with the picture turned off, it will probably be acceptable.
Please ask in the Database Forum if you are unsure whether to submit a video or not, especially for borderline cases. There is now Filmogs for films!

RSG §1.1.3.b.
MP3, ogg-vorbis, and other file based formats: Discogs only catalogs items that have been released to the general public, either as commercially sold items, or as free give-aways. Only entire releases may be submitted, not individual tracks from (for example) an album.
Due to the relatively recent emergence of digital labels, and the variety of those labels, digital releases may be held under closer scrutiny for inclusion to the database than items that are replicated on physical media (for example vinyl records and 'pressed' CD's). Please follow other s advice, and ask in the Database forum if you are not sure.

The guidelines for digital releases may be subject to further change and review.

[RSG §6.5.1.]
Computer file based formats follow the same basic rules as for physical media. File-based releases are scrutinized similarly to CDrs and Cassettes, due to the ease of creation, duplication and distribution.

To provide verification of stand-alone file based releases, please provide (in the submission notes) a URL to the purchase or location, or some description of how you obtained the files. In other words, how can someone else get this release?

[RSG §6.5.4.]
Bootleg, counterfeit, or pirated files are not eligible for submission to Discogs.

[RSG §6.15.3.]
The following are approximate definitions only:

Bootleg: Unauthorized recordings of live performances/broadcasts.
Counterfeit: Recordings which are copied or distributed without authority, and which are packaged to resemble the original as closely as possible.
Pirate: Recordings which are copied or distributed without authority, and which are usually packaged differently to the original.

RSG §1.1.3.c.
Audio formats that don't contain audio (for example blank picture discs) are eligible for inclusion as long as they have a label / catalog number.

RSG §1.1.4.
List any items that were initially sold as a package (by the record company) as one release, no matter what the packaging. Packaged items that are also released individually are treated as separate releases. Items where we are uncertain if they were sold as a package can be entered as separate items. Items that are obtained after the sale via a coupon or other method should be entered as individual releases.

RSG §1.2.1.
The standard Discogs rule for artist and label names, ers, release and track titles, format free text field, index track titles, credits, and headings, is the first letter of each word is capitalized.
Track Positions can usually be represented exactly as on the release.

All other text (Release Notes, comments etc) should follow standard English capitalization rules.

RSG §1.2.2.
Exceptions;

RSG §1.2.2.a.
Artist names which have consistently unique letter-casing will be accepted with proof that the artist uses that spelling consistently and intentionally. This also applies to artist name particles (e.g. van, von, di, de, la, etc.), which can be in lower case if the artist spells it that way consistently.

RSG §1.2.2.b.
Acronyms, and initialisms should follow what is written on the release, including any punctuation if used.

RSG §1.2.2.c.
Abbreviations, contractions and hyphenations should start with a capital letter. The rest of the word's capitalization should follow as on the release, except where all caps have been used, which should be turned to lower case.

RSG §1.2.2.d.
Intentional capitalization of abstract release or track titles can be entered as on the release. An abstract title is defined as a word or series of characters that doesn't have a meaning in any language.

RSG §1.2.2.e.
Roman numerals should be entered using standard uppercase letters I, V, X, L, C, D, M

RSG §1.2.3.
When using a slash between two words, please use a space on either side of it, for example: ABC Song / XYZ Song.

RSG §1.2.4.
Please use a typewriter apostrophe ( ' ) instead of a typographic apostrophe ( ’ ) or accent marks ( ` , ´ ). If these are used in artist names, they may be used as part of an artist name variation.

RSG §1.3.1.
Releases cannot be submitted to the database unless they contain a certain minimum of information:

RSG §1.3.1.a.
Required:

a) Credits are required for the main artist when they have one of the following roles:
DJ Mix, Compiled By, or Presenter.

k) If any further information is needed to distinguish a Unique Release, that information is required to be entered as well. See the RSG §1.1.1. for details.

RSG §1.3.1.b.
Optional:

a) Style (apart from in the Electronic genre)

RSG §1.3.2.
Generally, the more information you can enter for a release, the better. Once you are comfortable with how to enter the basic required information, try to enter as much information as possible. For example, crediting everyone involved with the release, listing all other relevant information stated on the release cover / booklet / label, etc.

RSG §1.3.3.
Please explain in the Submission Notes field if your submission lacks required information, or some aspect of the release might bring up questions for someone who doesn't know the release.

[RSG §14.1.3.]
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §1.4.1.
Discogs allows the entering of all versions of a release, such as white labels, reissues, different artwork, format variations, colored vinyl, different manufacturers etc. In order for these to be accepted, you must provide enough information to distinguish the different versions of a release.

It may be important to provide as much information as possible for major label releases, such as barcodes, matrix numbers, publishing/copyright dates, and any other identifiable marks. Note that different matrix numbers or barcodes may not necessarily mean that a separate release should be entered, please ask in the forum if in doubt.

RSG §1.4.2.
If the difference is subtle, you must explain the difference in the Release Notes, or with images, or by any other effective means, in order that future s can tell their versions apart by referring to the entry in Discogs. For example; reissues that cannot be told apart from the original issue cannot be entered as a unique release - unique releases must have a means of identifying them as such!

[RSG §11.1.1.]
Release Notes is a free text field. It is used to add any factual, objective notes about the release, or to list information that cannot be entered into other dedicated fields.

RSG §1.4.3.
Items such as cut outs (where a normal release has a section of the sleeve cut, denoting a price cut item), items that have otherwise been marked or altered after manufacture, differences in releases with hand-made artwork that are part of the same edition, and individually numbered items on otherwise identical copies will not be allowed as unique releases.

RSG §1.4.4.
Manufacturing variations should not be counted as a unique release.
For example:

a) Different stampers / matrix numbers for the same edition
b) Manufacturing tolerance based variations in the shades of label paper or ink color
c) Mislabelings such as: (correct) labels misapplied to incorrect sides, two of the same labels, or missing labels
d) Unintended vinyl coloration caused by variation in vinyl stock, etc.

would not count as a unique release. If in doubt, ask in the Database Forum.

RSG §1.5.1.
If a release is currently for a retail release and also a white label / promo, the existing release should be kept for the retail version, and the white label / promo should be made as a new submission.

RSG §1.5.2.
If a release contains multiple versions (for example, different colored vinyl versions, reissues, or different country or region versions), the most common version should remain as the existing release, and the less common versions should be split off into new releases.

RSG §1.5.3.
You MUST have the version you're creating in your possession whilst splitting. Do not use the existing Release Notes as proof of the different versions. If there are multiple different versions of a release, and you only have one of them, only submit the one you have.

[RSG §1.1.1.]
You must have the exact release in your possession when you make a release submission. [...]

RSG §1.5.4.
The existing release should be updated after a new version is accepted to the database to make it clear it does not represent the newly added version. For example, if there is a note stating the record is also available as a pink vinyl promo and the pink vinyl promo is now a separate release, the notes need to be removed from the original submission.

RSG §1.5.5.
Do not keep credits that are not present on the version of the release you are submitting.

[RSG §10.7.3.]
The 'copy to draft' function duplicates the release information including the credits, so a different version of the release can be entered. Please ensure that the credits you copy across this way are correct and valid. All credits that are not written on that version of the release should be removed.

RSG §1.5.6.
Be careful with the format and track numbering. If copying a CD for a vinyl version, make sure the tracks are numbered in such a way that represent which tracks are on each side, and make sure any track-specific credits in the release-wide credit section are updated accordingly. Also watch for track order changes when changing formats.

RSG §1.5.7.
Be careful with the release date, as promotional releases are almost always available before the retail versions, and should not keep the original release date. If no release date information is present on a release variation, or you cannot find reliable information elsewhere, you could assume that the year would be the same. If the retail version came out at the beginning of a calendar year, you could assume the promo came out the year prior. But if you are uncertain, do not include a release date.

RSG §1.6.1.
This section must be used to describe your submission or update. For example, on new submissions, you could disclose the source of the information, say you have checked all the links, and describe or explain anything out of the ordinary etc. For edits, please provide a brief description of the edit, and note the source of the information.

RSG §1.6.2.
To provide verification of stand-alone file based releases, please provide a URL to the purchase or location, or some description of how you obtained the files. In other words, how can someone else get this release?

RSG §1.6.3.
For self-released Not On Label submissions, whether on consumer-grade recordable media or not, please provide some information about how you came to own a copy. Was it sold by mail-order, at gigs, online or out of a car boot? How many other copies would you estimate there are? Any information that helps voters determine its eligibility will be helpful.

RSG §1.6.4.
Please describe anything that may be potentially confusing about your submission (such as new artists or labels to the database, typos on the release, etc). You may also use this section to respond to comments from other s or to clarify information. Good submission notes help greatly in both ing the information was added or updated correctly, and for the future when reviewing the release/artist/label history.

RSG §1.6.5.
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §1.7.1.
The general principle of entering information into Discogs is to reflect what is written on the release as much as possible. When the information printed on the release does not match the audio on the release, we enter the actual audio content, and outline the error in the Release Notes.
It is important at all times to communicate the errors and nature of the correction with other s, using the Release Notes and the submission notes. Any doubts should be discussed in the Database forum. If the doubt remains, the release should not be updated, but the doubt can be noted in the Release Notes.

RSG §1.7.2.
Artist names, if the credited artist is totally incorrect, should be changed to the correct artist, and the correction explained in the Release Notes. Spelling and other errors in artist names must not be corrected, but instead be entered using the Artist Name Variation (ANV) function.
Any suspected artist name spelling error can be explained in the Release Notes, but this isn't mandatory.

RSG §1.7.3.
Track titles and release titles must be entered as they appear on the release (please note specific instructions at the Database Help Forums.

If the track is completely misidentified, the track's correct title should be entered. Reasonable proof must be provided for the error correction to be accepted (for example, that you hold the release and have checked the audio content). We require that the mislabeled track is 100% verifiable as an unaltered copy of the original track in order to allow a name correction. Any title error that is corrected should be mentioned in the Release Notes.

RSG §1.7.4.
Incorrect tracklists should be changed to reflect what is really on the release, the errors that have been corrected must be entered into the Release Notes.

RSG §1.7.5.
For conflicting information printed on different parts of the release, the most complete and correct version should be chosen. If it is not apparent which is the most complete and correct, the boldest version should be chosen (for example, the artist name on the cover of the release, the tracklist on the rear of the release etc). Again, any differences must be explained in the Release Notes. Please see the title guidelines for specifics of how to choose the right title.

RSG §1.7.6.
Missing or damaged parts - A submission can be made when the submitter possess a release with missing or damaged parts (for example, a missing sleeve, a missing disc, or a torn label). The submitter must have enough of the release in their possession to reasonably guarantee the basis of the submission is correct. There must be clear Release Notes and submission notes left stating the missing parts that were not available at the time of submission.
External information can be used to fill in missing information in this case (for example, tracklists), but the submitter must state what information has been externally sourced, and cite the source. The information must be reasonably seen to be accurate; if there is doubt or disagreement, please ask in the Forum.

[RSG §11.1.1.]
Release Notes is a free text field. It is used to add any factual, objective notes about the release, or to list information that cannot be entered into other dedicated fields.

[RSG §14.1.3.]
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §1.8.1.
The default language of Discogs is English. However, Discogs s Unicode and allows releases in any language and character set. Releases must be submitted in the language used on them, they should not be translated or transliterated.

RSG §1.8.2.
Some releases may have entire sections of text duplicated in multiple languages - for example the tracklistings on some classical releases. You can either pick one language to enter, or you can enter all the languages. The preference goes to all languages being entered.

RSG §1.8.2.a.
When picking one language, use the primary language on the release (probably the same language that is used in the small print). If there is no clear primary language then use the English version. If there is no English version then use the language version that the releasing labels country uses.

RSG §1.8.2.b.
When entering multiple languages, enter titles into the fields using an “ = ” between languages. Enter any main and track artist name translations in separate artist fields with " = " in the er, using ANVs as appropriate. For credits, please just pick one name using 1.8.2.a.
(Release example)

RSG §1.9.1.
All text should be entered using Unicode where applicable.

RSG §1.9.1.a.
In the notes field, links to Discogs artists, Labels, Releases, and Master Releases should be entered using the Discogs Text Formatting.

RSG §1.9.1.b.
Text formatting using HTML or Discogs Text Formatting should not be used in any other parts of the release data.

RSG §1.9.2.
A few releases are entered using HTML in the tracklisting, this is now deprecated and should be updated. Please ask in the help forums before updating.

RSG §1.9.3.
Transcribing graphic design decisions, such as reverse letters, additional punctuation, letter substitution etc, should be avoided. An exception is the "Metal umlaut", which (due to its widespread use) is acceptable (for example, Motörhead).

RSG §1.9.4.
Use the Unicode strikethrough for catalog numbers and any other applicable area. There is an external site that helps you create this.

RSG §1.10.1.
Please be helpful and polite to other people. Do your best to submit according to the guidelines. Take care when altering the data, explain your edits when needed, respect the database, be open to discussion, and ask in the forums regarding any difficult areas if necessary.

[RSG §14.1.3.]
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §1.10.2.
Never submit false releases and updates, releases from memory, releases from internet sites etc. Do not curse, lose your temper, call names, or otherwise cause the submission process to be unpleasant or frustrating for others. You should never continue submitting a release or update that you have been advised is incorrect, or flood the site with incorrect or malicious submissions, updates, comments, spam etc., or otherwise attempt to corrupt the data, or cause obstruction to the submission and review processes.
Discogs reserves the right to take whatever action necessary to protect the database and the general Discogs community from such behavior.

RSG §1.10.3.
Please don't do updates just to change the order of data (such as in the format or credit fields). Only do updates to correct or add information.

[RSG §14.1.2.]
If you want to do the same type of edit over many releases, post a message in the Database forum stating your intentions. This will ensure your updates are acceptable before you do them, and may help you get votes faster. Link to the discussion on each of your edits, so other voters can read what is discussed.

RSG §1.11.
The list of changes made to the guidelines is available in he Guideline Changelog, at http://discogs.versitio.com/help/forums/topic/356624

Related Topics:

◾ Database Guidelines 4. Label / Catalog
◾ Database Guidelines 5. Barcodes & Identifiers
◾ Database Guidelines 14. Updating Information
◾ Database Guidelines 18. Updating An Artist Profile
◾ Database Guidelines 19. Updating A Label Profile
◾ Database Guidelines 21. Contributor Improvement Program (CIP)
◾ Database Guidelines 22. FAQ for Artists And Labels
◾ Extended Database Glossary
◾ [Discogs] Contributing to Discogs
◾ [Discogs] Quick Start Guide
◾ [Discogs] Finding The Information On A Release
◾ [Discogs] Reviews & Discussion
◾ [Discogs] s in Contributor Improvement Program (CIP)
◾ [Discogs] Of Service
◾ [Discussion] Frequently Asked Questions (FAQ) (April 2008)
◾ [List] Incorrectly capitalized artist and label names
◾ [Group] Database Mentors and Protégés

Database Guidelines 2. Artist

◾ 2.1. Adding Artists
◾ 2.2. Artist Fields [Main Artist]
◾ 2.3. Special Artists
◾ 2.4. Artist Naming Conventions
◾ 2.5. Artist Name Variation (ANV)
◾ 2.5.12. Artist Name Variation (ANV) FAQ
◾ 2.6. The Field and Artist Collaboration
◾ 2.7. Main Artist Credits
◾ 2.8. Eponymous Artists
◾ 2.9. Crediting Unnamed Groups
◾ 2.10. Crediting Non-Specific Groups
◾ 2.11. Solo Artist Plus A Generic Band Of Musicians
◾ 2.12. (guideline removed)
◾ 2.13. Compound Artist Names
◾ 2.14. Merging Artists
◾ 2.15. Renaming Artists
◾ 2.16. Artist Page Sorting

[18. Updating An Artist Profile]

[18.0.] [Invalid Artist]
[18.1.] Real Name
[18.2.] Profile
[18.3.] URLs
[18.4.] Aliases
[18.5.] In Groups
[18.5.6.] [Submission Notes]
[18.6.] Reviews
[18.7.] Images

RSG §2.1.1.
On Discogs, the credits entered in the Artist and Credits fields (on the submission form) are assigned to Artist Profiles. The name used on the artist profile is the "Primary Artist Name" or PAN (the root name without any variation).
It is important to try to keep artist names as organized as possible, so please use the search function for all of the artist names you enter on your submission. As soon as the 'submit' button is pressed, any new artist will have a page created listing the release.
It helps to fill out a new artist profile with the basic details of the artist straight away (for example, "Saxophone player from New York.").

RSG §2.1.2.
When creating a new artist, the name entered should match the name as credited on the release (following Discogs capitalization rules). If the printed credit has an error you may enter the correct name (with an ANV) - but reliable sources MUST be cited.

RSG §2.1.3.
The Primary Artist Name (PAN)
A) Is the stage name for performing artists and should be the most relevant version of the artist’s name. Examples: Prince, Lady Gaga, The Allman Brothers Band

B) For artists without a consistent & concurrent stage name or for non-performing artists (engineers, writers, etc.) the PAN should be the name as presented on the majority of releases. However, when consistently credited with initials or a partial name, the complete name should be the PAN if reliable sources are provided. Examples:
Credit: David = PAN David Hachour
Credit: Wly = PAN Wally Traugott
Credit: HL = PAN Heino Leja

RSG §2.1.4.
An artist's Primary Artist Name (PAN) should be the Latin transliteration of their name if a Latin transliteration exists and is used on the majority of their releases.

RSG §2.1.5.
When an artist is billed as [Artist Name] of [Band] only the artist name is credited. The band may be mentioned in the Release Notes.
Example: Just For Today / Don't Put It Off Till Sunday

RSG §2.1.6.
An Artist Name Variation (ANV) is the way the PAN is presented on the release itself. (see RSG §2.5.)

RSG §2.1.7.
A single individual, group, or other entity can have multiple names (PANs) which do not reference each other (the stage name, surname or the mononym if that is the name by which the artist is professionally known). These can be linked as Aliases (see RSG §18.4.1).

A) Aliases are created when an artist is credited with totally different names.
Richard Starkey = Ringo Starr
Dr. Winston O'Boogie = John Lennon
U2 = The Dalton Brothers
Davey Dream = David Robert Jones = The Actor (2) = The Rebels (12) = Ziggy (32) = David Bowie

B) Aliases are created when changing a surname. Removing or adding a surname can be a form of change.
Pål Waaktaar = Pål Waaktaar Gamst = Paul Waaktaar-Savoy
Madonna = Madonna Louise Ciccone = Madonna Ritchie
Beyoncé = Beyoncé Knowles = Beyoncé Knowles Carter

C) Exceptions are allowed when an artist uses various names interchangeably, (in)consistently, and concurrently. In these cases an ANV may be more appropriate using the full name as PAN.
ANV Elvis = PAN Elvis Presley
ANV Kylie = PAN Kylie Minogue
ANV Carrie Holzman = PAN Carrie Holzman Little

If in doubt; please ask in the forum as there may be “edge” cases.
See RSG §2.15.3 for renaming artist. See RSG §2.5.2 for more information on ANV's.

RSG §2.2.1.
The artist field at the top of the submission form is where we put the main artist for the release. This is considered to be the artist or artists named on the front cover of the release, or otherwise billed as such.

RSG §2.2.2.
More than one main artist can be entered by adding another artist field. This is done by clicking the 'Add artist' button (the large 'X' button removes the field). When you add another artist field this way, you will see that another field is added beside the existing artist field. This is called the " field" and is for adding words or symbols that the two artists together, for example 'And', 'Featuring', '/', ',' etc. Please don't leave the field empty. If there is no used on the release, just enter a comma.

The 'Add ANV' button is for the Artist Name Variation function, which is explained further down this page.

RSG §2.2.3.
There is no limit to the number of artists that can be listed as 'Main Artist', but the release itself must show the intention that the artists are to be taken as the main artists on the release (or to list the artists in a way that doesn't allow us to differentiate). See RSG §2.3.1 for special use cases for when no specific artist is credited on a release.

RSG §2.2.4.
Artist honored on tribute releases
A. When the honored artist name is the release title or part of the release title, this artist is not a main artist, instead you may use an appropriate credit.

Example: Songs Of The Beatles and The Bee Gees

B. When the honored artist name is credited or featured on the cover separate from the title, this artist is a main artist (as well as any others using the field).

Example: The 30th Anniversary Concert Celebration

C. Releases of classical music or soundtracks where only the name of the composer is mentioned on the cover and the release has no other title are not to be treated as Tribute / Cover type releases but as eponymous / self titled albums/compilations as per §3.2.1.

Examples: Ludwig Van Beethoven - Ludwig Van Beethoven, Andrew Lloyd Webber - Andrew Lloyd Webber, John Williams (4) - John Williams

If in doubt; please ask in the forums.

RSG §2.3.1.
The following artist names are used as generic pages when the credit isn't for a specific artist:

a) Various can be used when there are several different artists on a release, and no one is billed as the main artist. (Please also review RSG §2.2.3.)
Example: Various - 100% Reggae 3

b) Unknown Artist should be used for releases and tracks for which an artist is not credited and cannot be otherwise determined.
Example: Unknown Artist - Untitled

c) No Artist should be used for releases and tracks where there is no artist performing, such as radio / TV ments, movie samples, blank tracks, sound effects, field recordings, etc., and for which an artist is not credited and cannot be otherwise determined.
Example: No Artist - Sound Effects No. 1

d) Traditional - Used for traditional songs that are credited as such on the release.
Only to be used for composition type credits.
Example: Leslie Sarony - The Old Sow / On Ilkla Moor Baht ‘At

e) Folk - Used for folk songs that are credited as such on the release.
Only to be used for composition type credits.
Example: Comedy Harmonists* - How Can It Be / Must I Then

f) Anonymous - Used for artists who are credited as 'anonymous' on the release.
Example: Anonymous - Ophiolatreia

RSG §2.4.1.
Different Artists with the same name (for example, two artists named "John B") should be entered as "John B" and "John B (2)".
The (2) is not part of the name but is used to distinguish the two artists. If you need to create a third, use (3) and so on. (0) and (1) are never used.

Never swap about the suffixes, once an artist is designated a numerical suffix, the artist must remain with that suffix. The suffix has no relation to popularity or historical order.

[ANV F.A.Q.]
Q - Is John Smith an ANV of John Smith (3) - i.e. do we add in an ANV just so that the release page displays without the suffixed number applied to differentiate artists with the same names in Discogs?

A – No, please don't use the ANV function for this. [...]

RSG §2.5.1.
In order to link variations of an artists name, but keep the same artist profile, Discogs uses a system called Artist Name Variation, or ANV. The ANV is set directly on the submission form, click the small plus sign beside the artist field to open the ANV field. Please see the Quick Start ANV guide for an example of how ANVs are created. At Discogs we call the main artist name (the root name without an ANV) the 'Primary Artist Name', or PAN. For example, discogs.versitio.com/artist/David+Bowie is the PAN for David Bowie.

RSG §2.5.2.
ANVs should be used for variations in an artist name such as nicknames, language-based differences (translations), initials, acronyms, abbreviations, diminutives, homophones and corruptions. An ANV must be directly related or recognizable as derived from the artist's name (stage, full, composite, surname or a mononym by which the artist is professionally known). The existing Primary Artist Name (PAN) MUST be entered as it currently appears in the Database, with any name variation on the release added as the ANV (the ANV cannot exist on its own).

- Nicknames: (example: ANV Antoine Domino = PAN Fats Domino)
- Translations: (example: ANV Михаил Тараканов = PAN Mikhail Tarakanov)
- Initials: (example: ANV W.S. Bruford = PAN Bill Bruford)
- Acronyms: (example: ANV ELO = PAN Electric Light Orchestra)
- Homophones: (example: ANV Jonny Flower = PAN Jonathan Flaugher)
- Abbreviations: (example: ANV Grand Funk = PAN Grand Funk Railroad)
- Diminutives: (example: ANV Bazza = PAN Barry Farmer)
- Corruptions: (example: ANV Eilrahc Nedah = PAN Charlie Haden)

RSG §2.5.3.
merged with RSG §2.1.7

RSG §2.5.4.
ANVs should not be used for any fundamental name changes, such as surname changes. In these cases, an Alias is more appropriate. If in doubt, do not create an ANV.

RSG §2.5.5.
Do not use the ANV field on unlinked credits.

RSG §2.5.6.
The Primary Artist Name should be the most relevant version of the Artists Name. For example, when the artist has a "recording name" it should be the Primary name, and the variations found in the releases fine print should be the ANV.

RSG §2.5.7.
Typography and punctuation - ANV's can be entered to reflect what is on the release. Variations in punctuation, spelling, spacing, etc., are allowed, providing they exist on the release. Variations in accents are allowed. However, using Cyrillic and other such Unicode fonts to reflect graphic design decisions such as reverse letters or emulated cursive writing should not be done.

RSG §2.5.8.
You can use ANVs on Special Artists (Various, Traditional, Anonymous, etc.) as long as the ANV is a variation or translation of it, and the ANV is printed on the release.

RSG §2.5.12.
Q - Is John Smith an ANV of John Smith (3) - i.e. do we add in an ANV just so that the release page displays without the suffixed number applied to differentiate artists with the same names in Discogs?

A – No, please don't use the ANV function for this.

Q - If John Smith and John Smith (2) both use the ANV John Smith Jr., must a suffix be applied to one of the ANVs to show John Smith Jr. (2)?

A - No, this is not necessary as the 2 instances of John Smith Jr. create 2 different URLs based on the main Discogs artist entries. Searches and artist indexes will be adapted to show the main artist that an ANV is connected to.

Q - Does ANV replace Aliases?

A - No, aliases remain as a way of identifying totally different names used by an artist.

Q - Should an ANV be used for a one-off alias that is not a variation upon an existing artist name?

A - No, an Alias is appropriate here.

Q - Are ANV's to be used for misspellings, punctuation, typos etc?

A - ANV's can be entered to reflect what is on the release. Variations in punctuation, spelling etc are allowed, providing they exist on the release. Variations in accents are allowed. However, using Cyrillic and other such Unicode fonts to reflect graphic design decisions such as reverse letters should not be done.

Q - What else needs to be done when ANV is being used?

A - As with all submissions, s should provide full submission notes justifying why they have added the information in a certain way. Voters will seek confirmation of the validity of an ANV via these comments, so please provide this information up front to ensure your submissions are processed as quickly as possible.

RSG §2.6.1.
The field is used for the words that link two or more artist names together, such as 'Vs.', 'Meets', 'And', '&', 'W/', and 'With' . Abbreviations are accepted if they appear that way on the release. The field can also be used to enter separators (such as commas or slashes), if they appear on the release.
Please don't leave the field empty. If there is no used on the release, use a comma, or for 'split' type releases where the artists aren't collaborating, use a forward slash "/".
See 1.8.2.b regarding entering translations.

[RSG §1.2.1.]
The standard Discogs rule for artist [...] names, ers [...] is the First Letter Of Each Word Is Capitalized. [...]

RSG §2.6.2.
Collaborative artists should be split into their individual names except when the combined name was intended and can be verified as the group name (for example Stock, Aitken & Waterman). Verification can be found, for example, in official external websites, biographies, and discographies.

RSG §2.6.3.
Artist collaborations which are one-off recordings should be listed as separate artists. If this one-off collaboration becomes an ongoing recording team then they can be updated to one artist entry later.

RSG §2.6.4.
Never create or credit a collaborative artist in any credit field, with the exception that some collaborative artists have already been created and used solely on writing or production credits. Please continue to use them, please do not attempt to split these unless there has been extensive agreement from other s in the forums.
In the case of multiple artist / collaborative artist combinations in the credits, always split them into all their individual artists unless there is clear evidence that a combined artist name was intended to be legally credited for the role.

RSG §2.7.1.
When a main artist or track based main artist is credited on a release for the following, a credit must also be added into the credit section:

a) DJ Mix
b) Compiled By
c) Presenting Artist (Presenter)

RSG §2.8.1.
Artists with the same name as their groups, bands, or projects should be listed in the database as separate artists - (for example Frank Sinatra) should not be treated as bands, 'In Groups' for the backing musicians should not be applied to them.

RSG §2.9.1.
Sometimes, a release will credit a group of people or performers involved in the release, such as Chorus, Choir, Orchestra, Ensemble, Cast, Company etc, but not give them a proper artist name. When entering such vague groups, a full artist name of the group should, if possible, be taken from the release, film, show, etc title, and added to the front of the group, for example; the Chorus from the musical Paint Your Wagon should be credited like this:

"Paint Your Wagon" Chorus

When entering the details on the release, it is acceptable to use the ANV function to display the original performer credit, so for example it can be like this:

"Paint Your Wagon" Chorus ANV Chorus

Since an artist is created by doing this, the original submitter of the release should try to add at least a brief description of the group in the Artist Profile. For example, for the above example, this would be an acceptable description: "An unidentified group of chorus singers that appear in the "Paint Your Wagon" movie and subsequent soundtrack recordings."

This method should not be used when the group is used in conjunction with a named artist, this should be added as one artist, for example Count Basie And His Orchestra.

RSG §2.10.1.
If a group of people are credited that aren't specific (for example: tribes, nations etc), credit them as an artist, and place the following in the artist profile:

"Discogs notice: This artist does not refer to a specific group of named individuals (such as a band or musical group) but rather defines the collective term for [details of group].

Please use this artist name (or any language variation thereof, via an ANV) for the [group name]."

RSG §2.10.2.
The 'In Groups' function can be used if the non-specific group is a subset of a larger non-specific group, but specific artists and groups cannot be linked as part of a non-specific group.

RSG §2.11.1.
A Solo Artist + Generic Band Of Musicians is entered as a new group with the solo artist as a member, for example:

◾ Quincy Jones And His Orchestra
◾ Louis Armstrong And His Band

Please make sure to add the solo artist as a member of that group using the In Groups function on the solo artists page.

RSG §2.13.1.
When an artist is presented as "Name1 (Name2)" or "Name 1 AKA Name 2", the name before the brackets or 'aka' is considered the focal credit and should be credited - do not use an ANV for these situations.

If the name in brackets, or after 'aka', is an alias then it can optionally be credited on a separate line. If the name in brackets is not a direct alias of the artist, it cannot be added as a credit, but can be mentioned in the Release Notes.

[RSG §2.5.8.]
If there is a case whereby there are two Artist Name Variations present on a release for the same credit (for example there is D. Bowie on the cover for a vocal credit, and D. H. Bowie on the label for the vocal credit), only one can be entered.
The submitter should choose one based on such things as viability of the names, clarity and fullness of the data, and existing names already used in the database.

RSG §2.14.1.
You must edit each release if one artist is being represented by two or more artist pages. Make sure your edits are correct and reflect the name that is is printed on the release, using Artist Name Variations if needed.
Never swap about the suffixes, once an artist is designated a numerical suffix, the artist must remain with that suffix. The suffix has no relation to popularity or historical order. If in doubt, ask in the forum database topic.

[RSG §14.1.2.]
If you want to do the same type of edit over many releases, post a message in the Database forum stating your intentions. This will ensure your updates are acceptable before you do them, and may help you get votes faster. Link to the discussion on each of your edits, so other voters can read what is discussed.

RSG §2.14.2.
Only duplicate artists should be merged. Make sure you explain in the Submission Notes what you are trying to achieve.

[RSG §14.1.3.]
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §2.14.3.
If your edits are going to remove all entries from an artist page, please make sure to update that page to remove all 'in groups', 'aliases', the profile, real name, and the links before editing the last release. Please make sure to transfer any relevant information over to the remaining profile.

RSG §2.15.1.
You must edit each release to rename an artist. Make sure your edits are correct and reflect what is printed on the release, using Artist Name Variations if needed.
Never swap about the suffixes, once an artist is designated a numerical suffix, the artist must remain with that suffix. The suffix has no relation to popularity or historical order. If in doubt, ask in the forum database topic.

RSG §2.15.2.
If your edits are going to remove all entries from an artist page, please make sure to update that page to remove all 'in groups', 'aliases', the profile, real name, and the links before editing the last release. Please make sure to transfer any relevant information over to the remaining profile.

RSG §2.15.3.
Swapping or changing existing PANs must be presented with solid evidence and agreed upon with a clear consensus in the Forum (on a case-by-case basis) before any updates are made. A need for corrections can include:

A. The existing PAN is assigned to multiple artists.
B. There are multiple profiles for a single artist that should be merged.
C. Artists' names were created with wrong spelling, abbreviations, typos, incomplete name, missing accents or diacritics.

Preference should be given to the accuracy of the database, with consideration to how the majority of releases indicate the name, what will be easiest for all s of Discogs, and which primary name would accommodate the most variations.

These PANs can be corrected observing the guidance of RSG §14.1.2. regarding mass-edits.

Sections

◾ Releases
◾ Tracks Appear On
◾ Unofficial Releases
◾ Credits

Sub-Sections

Releases are sorted in the the sub-sections by looking to see if the release fits into a sub-section, working from the top to the bottom of a list. Note that the order of the list is not the same as the final order as displayed on the artist page - for example, the artist page list start of with albums, whereas we look at whether the release fits into the videos section first when we are deciding which sub-section to sort it into.

Master Releases

On the Artist Pages, we extract a format summary for every MR (this is currently hidden). This format summary is extracted from all the contained releases. We use this summary to place the entire MR in the correct subsection.

For Releases and Unofficial Releases

◾ Videos - For releases where every format/description line (apart from lines starting Box Set or All Media) contains one or more of the following tags: format names; DVD, DVDr, HD DVD, HD DVDr, Blu-ray, Blu-ray-R, CDV, Betamax, VHS, Video 2000, Laserdisc, SelectaVision. Format descriptions; Video, VCD, SVCD, DVD-Vid. Must NOT contain format descriptions DVD-Audio, DVD-Data, Audio.

◾ DJ Mixes - Tagged as Mixed AND main artist has DJ Mix credit

◾ Compilations - Tagged as Compilation, all releases in a MR must be tagged as 'Compilation'

◾ Albums;

◾ ◾ Tagged with Album or Mini-album

◾ ◾ Items tagged with LP but not with Single, Maxi-Single, or EP

◾ ◾ IF format = (all analog formts) AND (number_tracks >= 7 AND total_tracktime if available >= 30 minutes), OR (total_tracktime >= 30 minutes), AND format does not include EP, Maxi-Single, or Single.

◾ ◾ IF format = (all digital formats) (number_tracks >= 8 AND total_tracktime if available >= 44 minutes), OR (total_tracktime >= 44 minutes), AND format does not include EP, Maxi-Single, or Single.

◾ Singles & EPs - Tagged with Single, Maxi-Single, EP, 12", 7", 10", Mini, Minimax

◾ Miscellaneous - For everything else.

For Tracks Appear On

◾ Videos - For releases where every format/description line (apart from lines starting Box Set or All Media) contains one or more of the following tags: format names; DVD, DVDr, HD DVD, HD DVDr, Blu-ray, Blu-ray-R, CDV, Betamax, VHS, Video 2000, Laserdisc, SelectaVision. Format descriptions; Video, VCD, SVCD, DVD-Vid. Must NOT contain format descriptions DVD-Audio, DVD-Data, Audio.

◾ Mixes - Tagged as Mixed.

◾ Compilations - Tagged as Compilation, all releases in a MR must be tagged as 'Compilation'

◾ Albums;

◾ ◾ Tagged with Album or Mini-album

◾ ◾ Items tagged with LP but not with Single, Maxi-Single, or EP

◾ ◾ IF format = (all analog formts) AND (number_tracks >= 7 AND total_tracktime if available >= 30 minutes), OR (total_tracktime >= 30 minutes), AND format does not include EP, Maxi-Single, or Single.

◾ ◾ IF format = (all digital formats) (number_tracks >= 8 AND total_tracktime if available >= 44 minutes), OR (total_tracktime >= 44 minutes), AND format does not include EP, Maxi-Single, or Single.

◾ Singles & EPs - Tagged with Single, Maxi-Single, EP, 12", 7", 10", Mini, Minimax

◾ Miscellaneous - For everything else and releases tagged as Jukebox, Transcription and Tour Recording.

For Credits

The sub-sections are taken from the headings as listed at the credits list

◾ Remix
◾ Vocal
◾ Instruments & Performance
◾ Writing and Arrangement
◾ Featuring & Presenting
◾ Conducting & Leading
◾ Production
◾ DJ Mix
◾ Technical
◾ Visual
◾ Acting, Literary & Spoken
◾ Management

Analog and Digital Formats

For the album section, we use the following lists:

Analog Formats

◾ Vinyl
◾ Acetate
◾ Flexi-disc
◾ Lathe Cut
◾ Shellac
◾ Edison Disc
◾ Cylinder
◾ 8-Track Cartridge
◾ Cassette
◾ Microcassette
◾ Reel-To-Reel

Digital / Video Formats

◾ CD
◾ CDr
◾ CDV
◾ DVD
◾ DVDr
◾ HD DVD
◾ HD DVD-R
◾ Blu-ray
◾ Blu-ray-R
◾ Betamax
◾ VHS
◾ Video 2000
◾ Laserdisc
◾ SelectaVision
◾ Minidisc
◾ MVD
◾ UMD
◾ Datassette
◾ Floppy Disk
◾ File
◾ Memory Stick
◾ Hybrid
◾ All Media
◾ Box Set
◾ DAT
◾ DCC

Related Topics:

◾ Database Guidelines 1. General Rules
◾ Database Guidelines 14. Updating Information
◾ Database Guidelines 18. Updating An Artist Profile
◾ Database Guidelines 19. Updating A Label Profile
◾ Database Guidelines 22. FAQ for Artists And Labels
◾ Extended Database Glossary
◾ [Discogs] Contributing to Discogs
◾ [Discogs] Quick Start Guide
◾ [Discogs] Finding The Information On A Release
◾ [Discogs] Reviews & Discussion
◾ [Discogs] Of Service
◾ [List] Incorrectly capitalized artist and label names
◾ [Group] Group: Database Mentors and Protégés

Database Guidelines 3.Title [Release Title]

◾ 3.1. Title
◾ 3.2. No Obvious Title
◾ 3.3. Double A Sided Releases
◾ 3.4. Interpreting Track Titles As Release Titles
◾ 3.5. Releases Of Combined Titles

RSG §3.1.1.
Use this field to enter the main title of the release.

► [Image] Title field

RSG §3.1.2.
Enter the title as close to the way it appears on the release as possible, following the general Discogs guidelines for capitalization.

[RSG §1.2.1.]
The standard Discogs rule for [...] release and track titles [...] is the First Letter Of Each Word Is Capitalized. [...]

RSG §3.1.3.
Sometimes the title is different on the cover, on the spine etc. It is best to use the title on the cover, but also consider what is going to be most useful to other s, so the most complete title is better no matter where it appears. In rare cases, it may be necessary to make up a compound title from the various versions of the title on the cover, spine, label etc.

Use the Release Notes field to mention any important differences.

RSG §3.1.4.
Subtitles should be entered into the title field. If the release doesn't have its own separators, please use parentheses brackets: Title (Subtitle)
If there is doubt as to whether text on the release is a subtitle or not, try referring to other releases or the artist or label websites.

RSG §3.1.5.
Do not use quotation marks around the whole release title. Scare quotes can be used, but are a rare occurrence (for example, David Bowie - "Heroes").
Titles that use quotes to denote and separate the title of a film, play, TV show, and other such names from the rest of the title (for example, Mancini Plays The Theme From "Love Story"), are acceptable.

RSG §3.1.6.
Do not transcribe words that serve as an introduction and are not intended to be part of the title:

Ziltoid The Omniscient
(Title appears on release as: Devin Townsend Presents Ziltoid The Omniscient)

If the form in which the title appears on the release is considered to be important for identification, please list it in the Release Notes.

[RSG §11.1.1.]
Release Notes is a free text field. It is used to add any factual, objective notes about the release, or to list information that cannot be entered into other dedicated fields.

RSG §3.2.1.
If the release is an album with no obvious title, and there is no explicit evidence of it being untitled or given a title externally, use the artist's name as the title (in other words, assume it is eponymous or self-titled).

RSG §3.2.2.a.
If the release is a single or EP, without a picture sleeve: Use the main track title as the title for the release. If no main track title can be discerned by the physical release (A side, plug side, side 1, etc.) use both titles separated by an " / ". If there is external evidence of a main track title, use that title with an explanation in the release notes as to its source.

RSG §3.2.2.b.
If the release is a 78, and there are track titles on each side of the record, use both track titles as the title for the release, separated by a slash. Do not use a single track title as the release title unless there is proof the record was referred to by a single title on its release by the record label / artist.

RSG §3.2.3.
If there is good evidence of an external title being given to the release, use that title with an explanation in the Release Notes as to its source.

RSG §3.2.4.
If there is no track information, or other source of a title, or if other sources point to the release being untitled, use "Untitled".

RSG §3.3.1.
For double A-sided releases, or releases that are split between two artists, and that do not have a given title, use both track titles separated by a slash. A double A-sided single is one on which the titles of all tracks are featured on the packaging with equal prominence, or a single that was otherwise marketed as having more than one featured track, such as a reissue single containing a pair of previous hits. The labels on such releases often designate their sides as 'A' and 'AA', rather than 'A' and 'B', or have no side designations at all. When a B-side title appears on the front of a singles packaging in diminished type, especially when preceded by b/w (which means 'backed with'), it generally indicates the release is not double A-sided.

RSG §3.3.2.
Pre 1965 releases are unlikely to be double A side releases - http://en.wikipedia.org/wiki/A-side_and_B-side#Double_A-side

RSG §3.4.1.
Two titles listed on the front with equal prominence should be listed as the release title.

RSG §3.4.2.
Two titles listed on the front but with one more prominent than the other: normally, only the more prominent title should be entered as the release title, but external sources can be taken into .

RSG §3.4.3.
Two titles listed on the front but with 2nd title preceded by b/w (backed with) or c/w (coupled with): both track titles and the can normally be entered, but again, external sources can be taken into .

RSG §3.4.4.
One title listed on the front, one listed on the back along with credits for both sides: the B side track title should not be entered in the release title.

RSG §3.4.5.
There is no limit to the number of artists that can be listed as 'Main Artist', but the release itself has to show the intention that the artists are to be taken as the main artists on the release (or to list the artists in a way that doesn't allow us to differentiate).

RSG §3.4.6.
Singles without sleeves should only list the A side as the title, unless it is a double A sided release. However, if they have two separate artists, one each side, please list both track titles in the main title as on this release.

RSG §3.5.1.
Please see Back to Back as a good example of how to enter two artists on one release.

Related Topics:

◾ Database Guidelines 1. General Rules
◾ Database Guidelines 14. Updating Information
◾ Extended Database Glossary
◾ [Discogs] Contributing to Discogs
◾ [Discogs] Quick Start Guide
◾ [Discogs] Finding The Information On A Release

Database Guidelines 4. Label / Catalog

◾ 4.1. Labels And Companies
◾ 4.2. Label And Company Names
◾ 4.3. Label And Company Naming Conventions
◾ 4.4. Not On Label
◾ 4.5. Legacy Label Names

◾ 4.6.1. Unofficial Release Label And Company Names
◾ 4.6.2. Label And Company Definitions
◾ 4.6.3. Merge
◾ 4.6.4. Rename

◾ 4.7. Catalog Number
◾ 4.7.11. Shadow Catalog Number

◾ 4.8. Multiple Labels And Catalog Numbers
◾ 4.9. Matrix Number
◾ 4.10. Distributors
◾ 4.11. DIDX and other DID_ Codes

◾ 4.12. Release Models:
◾ 4.12.1. Minimum
◾ 4.12.2. Small To Medium
◾ 4.12.3. Major
◾ 4.12.4.

RSG §4.1.1.
This field is used for the label, series, record company, and other companies involved in the release. If the required label or company is not in Discogs yet, it will be created when you submit.

RSG §4.1.2.
Normally, listing the main label (usually the largest brand or logo on the release) is sufficient for cataloguing purposes. You can optionally list other companies mentioned on the release. Sometimes, the only way to describe a Unique Release is to mention one or more of these companies, in this case, it becomes mandatory to add it.

RSG §4.1.3.
In these guidelines, we use the word "company" as shorthand for any brand, business, copyright holder, studio, factory, and any other such entity.

[RSG §1.2.1.]
The standard Discogs rule for [...] label names [...] is the First Letter Of Each Word Is Capitalized. [...]

RSG §4.2.1.
Please check (using the search function) for slight variations in the name (for example with or without 'Records' on the end). For example; "EMI Records Ltd" and "EMI Records Limited" are the same company and should be listed on the same page, whereas EMI Music Australia Pty Ltd is a separate company and should be entered on its own page. Note that these companies will probably appear on a release along with the Label (brand) 'EMI', which should be added separately.

RSG §4.2.1.a.
For smaller 'independent' labels and companies, such a variation is usually unintentional, so you can normally adjust the label name to match the existing Discogs entry. Please make a note of any adjustments in the Release Notes and the submission notes.

[RSG §11.1.1.]
Release Notes is a free text field. It is used to add any factual, objective notes about the release, or to list information that cannot be entered into other dedicated fields.

[RSG §14.1.3.]
Even if it seems obvious, always try to explain your update fully using the submission notes. This will always be appreciated by other s, and is vital when we need to look back over the submission data's history.

RSG §4.2.1.b.
For larger 'major' labels and companies, any difference may be significant, in of defining a separate branch, brand, or company. These should be entered as on the release, unless there is proof that it is simply a variation for the exact same brand or company.

RSG §4.2.2.
The responsibility is on the wishing to combine label or company names to provide proof that the entity they are trying to combine is indeed one and the same.

RSG §4.3.
For labels and companies that share the same name, we need to distinguish them so they are listed correctly on separate pages in the database:

RSG §4.3.1.
A number in parentheses should be used to differentiate labels, such as "Label Name", "Label Name (2)", "Label Name (3)" etc.
For example, if the existing Liberation Records is not the same as the one on the release you are adding, please check for possible alternatives using the search. If none of the existing labels match the label on the release you are submitting, please create a new one by incrementing the appended number (if any), beginning with "(2)". "(0)" and "(1)" are never used.

Never swap about the suffixes, once a labelis designated a numerical suffix, the label must remain with that suffix. The suffix has no relation to popularity or historical order.

RSG §4.3.2.
For generically named locations such as "Parish Church", or for companies which share the same name, and where the location is usually listed on the release, list the location as part of the name to differentiate them. For example, "Parish Church, Portland". Generally, the town or city is enough to add to the name. For locations in the United States (and possibly other countries), The town / city and state is the standard format, and can be entered like that (for example, Firehouse Recording Studios, Pasadena, CA). Try to go by what is commonly entered on the releases where possible.

RSG §4.3.3.
Locations within locations, for example, "Studio 1, Abbey Road Studios" should usually be entered into the Release Notes.

RSG §4.3.4.
Company branches that need to be differentiated, and consistently state their location, can be entered that way.

RSG §4.3.5.
If there is no other way of distinguishing two different companies, then the usual (2), (3) etc suffixes should be used as per artist and label names. "(0)" and "(1)" are never used.

RSG §4.3.6.
Sometimes, an artist will also have a role that is a company role - such as copyright. At the moment, this will create two pages (an /artist one and a /label one). This is fine. If you can, try to match up the names so they are the same - for example, if the artist is "ArtistName (4)", then use that exact name including the bracketed number for the company name.

RSG §4.4.1.
Releases which have no discernible label, such as self-released albums, limited edition tour merchandise, white labels, bootlegs, etc. should be listed under the "Not On Label" meta-label. This is done by typing "Not On Label" into the Label field.

Before using Not On Label, please check for any catalog number or other markings that could associate a release with a particular label, or labels. Often, white label records can be tied back to a label by the catalog numbers found in the run-out grooves, and some CDs with limited information present might include a label logo, if no catalog number is clearly present.

RSG §4.4.2.
Not On Label pseudo-labels have been created to gather distinct set of releases without labels. The most common groupings are based on similar content and catalog numbers, and by artist:

a) Not On Label (Artist Name) - for unofficial releases containing music by a certain artist
b) Not On Label (Artist Name Self-released) - for music released specifically by an artist, as found on tours and made available via personal websites.

Legacy issue #1 - Not On Label (Series Name Series) was used for material with a clear pattern but no actual label name associated, like sequential catalog numbers and similar content, or the inclusion of an email address. These should now be entered with the label as a plain 'Not On Label', and the series name in the series field.

Legacy issue #2 - The original naming scheme for these pseudo-labels was 'Series/Artist Name' (White), implying that the associated releases were white labels.

Any remaining legacy entries using this scheme can be updated when found.

RSG §4.4.3.
If the artist has a numbered suffix at the end, use that suffix when creating Not On Label (ArtistName) and Not On Label (ArtistName Self-released) type pseudo-labels. For example, if the artist is "Bob (4)", then use "Not On Label (Bob (4))". If the label name is already taken, please use the next subsequent open position instead.

RSG §4.5.
The label catag system at Discogs has been adjusted over the years to allow a greater degree of accuracy when adding the labels and companies involved in a release. In the past, 'false' labels were created by combining both the branding and company on a release. This was especially common for major label releases, which can have many labels and companies involved.

Please be aware of this when submitting, don't automatically change the information presented on your release to 'fit in' with what is currently listed on Discogs for major labels. Always ask in the database forum if you are in doubt.

RSG §4.6.1.
Care should be taken with counterfeit recordings, which are packaged to resemble the original as closely as possible. Often, the packaging will include the original label and company names. Enter these items using a separate label.

For example, if the original label is "Label Name", and the suspected counterfeit contains this label name, it should be entered as "Label Name (2)" (or the next available number) - thereby creating a different label. The profile of this label should be filled out to explain its circumstances.

[RSG §4.3.1.]
[...] "(1)" is never used. [...]

[RSG §6.5.4.]
Bootleg, counterfeit, or pirated files are not eligible for submission to Discogs.

[RSG §6.15.3.]
The following are approximate definitions only:

a) Bootleg: Unauthorized recordings of live performances/broadcasts.
b) Counterfeit: Recordings which are copied or distributed without authority, and which are packaged to resemble the original as closely as possible.
c) Pirate: Recordings which are copied or distributed without authority, and which are usually packaged differently to the original.

RSG §4.6.2.
The following are definitions for all the tags that can be selected in the label and company section.

Label - Brand or imprint used by the record company to identify their releases. The label on a release can usually be identified by having a prominent logo. Labels are usually important to enter in a submission - if a release has a label or labels mentioned, they are required to be entered.

Series - A branded series of releases. These will usually be a number of releases on one label, carrying a distinct extra branding indicating a series. The most common and sure way of knowing if something is a series is when the word 'series' appears in the name, for example, "Silver Spotlight Series". The word can also appear on the back of the release, or externally on official websites or publications.

Sometimes, it is not apparent whether the branding is meant to be a series or a label, for example "Talkin' Loud Classics". Treat it as a label until there is proof it should be a series.

Compilations that are sequentially numbered can be added as a series. They are usually on one label, contain tracks by different artists, only have one version of each release, possibly two or three, and have a common theme running through their titles / artwork / tracks. Larger 'volume compilations' may have a redesign during their lifespan, but the theme will remain - usually in the title.

Releases that are not a series include numbered or otherwise ordered original works by an artist, for example, Led Zeppelin l / IV, Beethoven's Symphony No.1 / 2 / 3 / 4 / 5 etc, Selected Ambient Works 85-92 and Selected Ambient Works Volume II.

If the releases are connected in some manner, but have no branding on the releases, then are not considered a series - for example, Blue Note Revisited".

Other words can be used to indicate a series, for example, "collection".

If the releases in the series have a number associated with them, this can be entered into the 'catalog number' field ajacent to the series name. Enter the numbering as it appears on the release, for example, "Vol. One", "Part 6". When possible, don't repeat the series name in the series number, for example, "The Greatest Hits '92 - Vol. 4" would be entered as "'92 - Vol. 4" .

Record Company - Legal trading entity. These are not always mentioned on the release. Please use the specific "Copyright (c)", "Phonographic Copyright (p)", or other tags instead when used on the release (this is quite common). Most have a limited company type in their name, such as "Sony BMG Music Entertainment (UK) Ltd". Larger 'Major labels' have a complicated hierarchical structure, with a global company, under which they have regional companies, which then have labels and series. For releases on the 'major labels', it is sometimes necessary to enter the company to describe a unique release. In all other cases, entering the company isn't required, but entering this information is still beneficial.

Licensed To - The company that has received permission from another company to make the release. (Can sometimes also be worded 'Licensed By', but be careful, so can 'Licenced From).

Licensed From - The company that has given permission to another company to make the release.

Licensed Through - Usually indicated by these words - a company that is an intermediary in the licensing process.

Marketed By - The company that is involved in maximizing the sales of the release.

Distributed By - The company that manages the wholesale distribution of the release.

Manufactured By - A general term for making the physical release, this term is used a lot of the time to indicate the company that oversaw the manufacturing process, rather than the company that physically did the manufacturing, but the role can be used by either if it is used on the release.

Exported By - The company that ships the release from the original country or area of distribution, to other countries or areas.

Produced For - Indicated on the release by these words.

Recorded By - Indicated on the release by these words, or a similar expression, meaning company activity. This role can include credits to a mobile recording studio.

Manufactured For - Indicated on the release by these words.

Phonographic Copyright (p) - Indicates the copyright holder of the recording.

Copyright (c) - Indicates a copyright holder. Can be for images, logos, lyrics, layout, liner notes, and anything else using the © symbol or the term 'Copyright'.

Made By - A generic manufacturing role.

Pressed By - The manufacturing plant that presses vinyl, CDs etc.

Duplicated By - The manufacturing plant that duplicates CDr, cassettes etc.

Printed By - The printer duplicates the sleeves, labels, booklets, covers and all other printed material on the release.

Published By - Usually indicated by these words. The copyright holder of the published score.

Recorded At - The sound studio, venue, or event where the music / audio was recorded.

Engineered At - Another way of giving the name of the sound studio where the music / audio was recorded.

Produced At - The studio where the release was produced. Do not confuse this with manufacturing.

Overdubbed At - The sound studio where the music / audio was overdubbed.

Mixed At - The sound studio where the music / audio was mixed down from multitrack to a final (usually, stereo) mix.

Remixed At - The sound studio where the music / audio was remixed.

Mastered At - The mastering studio.

Lacquer Cut At - Part of the mastering process where an acetate lacquer is cut from the final mix.

Glass Mastered At - Part of the mastering process where a CD or DVD is etched onto a glass plate from the final mix.

Designed At - The design studio that produces the artwork for the release.

Filmed At - The film studio where the release was filmed.

RSG §4.6.3.
You must edit each release if one label is being represented by two or more label pages. Make sure your edits are correct and reflect what is printed on the release. Never swap about the suffixes, once a label or company is designated a numerical suffix, they must remain with that suffix. The suffix has no relation to popularity or historical order. If in doubt, ask in the database forum.

[RSG §14.1.2.]
If you want to do the same type of edit over many releases, post a message in the Database forum stating your intentions. This will ensure your updates are acceptable before you do them, and may help you get votes faster. Link to the discussion on each of your edits, so other voters can read what is discussed.

RSG §4.6.4.
You must edit each release to rename a label. Make sure your edits are correct and reflect what is printed on the release. Never swap about the suffixes, once a label or company is designated a numerical suffix, they must remain with that suffix. The suffix has no relation to popularity or historical order. If in doubt, ask in the database forum.

[RSG §14.1.2.]
If you want to do the same type of edit over many releases, post a message in the Database forum stating your intentions. This will ensure your updates are acceptable before you do them, and may help you get votes faster. Link to the discussion on each of your edits, so other voters can read what is discussed.

RSG §4.7.1.
The catalog number is usually the most prominent number printed on the release - often on the spine, on the back cover, and on the label etc. The catalog number should be entered directly as it appears on a release - it shouldn't be altered for conformity with other catalog numbers listed on the label page.

RSG §4.7.2.
A catalog number is required for every label entered. Where no catalog number exists, you must enter "none" into the catalog number field (note the lower case n). For other companies on the release, leave the catalog number field blank, unless there is a sequential identifying number that relates directly to the company.

RSG §4.7.3.
If the catalog number appears in different formats on the release (for example "ABC-001" and "abc1"), or there are two or more catalog numbers, enter all the versions of the catalog number in separate catalog number fields. To do this, click the [+] button to add extra label / catalog number rows. You must always enter the label as well.
Any variation in the catalog number can be entered as an additional number, including capitalization variations. However, the variations are only required to be entered if they would produce a new shadow catalog number.

RSG §4.7.4.
Be aware that Amazon ASIN codes (prefix: B000) used as catalog numbers may indicate the submitter has taken the information from Amazon, and not from the release itself.

It is forbidden to use any source except from the release itself as the primary source of information, please see the Universal Records and subsidiaries / sub-labels can have a similar catalog number prefix.

ASIN codes should be entered under 'Barcode And Other Identifiers' - see RSG 5.2.j.

RSG §4.7.5.
Please be careful not to add Label Codes or Distribution Codes into the catalog number field. More information about these codes can be found on the wiki Label Codes page and Distribution Codes page.
These codes can be entered under 'Barcode And Other Identifiers' - see help/submission-guidelines-release-barcode

RSG §4.7.6.
Sometimes individual discs in a multi-CD or multi-LP set will have their own numbers printed on them, separate from the main catalog number on the packaging. These numbers can be entered in the 'Barcode And Other Identifiers' section (see help/submission-guidelines-release-barcode ) and / or the company, when it is a sequential identifying number that relates directly to the company (see 4.7.2):

[RSG §4.7.2.]
A catalog number is required for every label entered. Where no catalog number exists, you must enter "none" into the catalog number field (note the lower case n). For other companies on the release, leave the catalog number field blank, unless there is a sequential identifying number that relates directly to the company.

[RSG §4.8.1.]
It is possible to list more than one label on a release. This should be used for a t release between two or more labels, or where an individual release has multiple catalog numbers on one label. This should not to be used for the same release being re-issued by a different label. This would require a unique Discogs entry.

RSG §4.7.7.
Sometimes individual tracks on a vinyl release will have their own ID numbers printed on the labels, usually in a smaller font, and sometimes in parentheses, separate from the main catalog number of the release. These numbers should be entered in the 'Barcode And Other Identifiers' section- see help/submission-guidelines-release-barcode.

RSG §4.7.8.
Multiple catalog numbers should be entered for a single item intended to be sold under different numbers in different territories (such as on many WEA releases in UK+Europe), regardless of whether corresponding, single-catalog number items exist for each territory.

RSG §4.7.9.
Look out for catalog numbers in typographic artwork, including those possibly accidentally left on an item by a licensee label. For example, Japanese re-releases of albums sometimes use the artwork in its entirely. Try not to enter the 'old' catalog number.

RSG §4.7.10.
Often the matrix number will be the catalog number followed by a side identifier, for example ABC-001-A and ABC-001-B, where the catalog number is ABC-001. Catalog numbers can be derived from the matrix numbers in these cases provided there is good evidence for it being correct - for example, the extracted catalog number matches the catalog number format on the label's other releases.

[RSG §1.9.4.]
Use the Unicode strikethrough for catalog numbers and any other applicable area. There is an external site that helps you create this.

RSG §4.7.11.
Shadow Catalog Number is a feature that reformats the catalog number for sorting and searching purposes. There is no direct involvement with it, it is automated and invisible. The following method is used site wide to work out the Shadow Catalog Number:

Transform all lowercase letters to uppercase.
Add an extra 'spacer zero' onto the end of the catalog number. If a 'number dash single number' or 'number space single number' is detected at the end of the cat#, move that number in there instead of the zero.
Strip out all characters except for letters and numbers.
Separate groups of numbers from groups of letters using tab characters.
Pad all number groups out to sixteen digits wide ("90241" becomes "0000000000090421", etc.)

RSG §4.8.1.
It is possible to list more than one label on a release. This should be used for a t release between two or more labels, or where an individual release has multiple catalog numbers on one label. This should not to be used for the same release being re-issued by a different label. This would require a unique Discogs entry.

[RSG §4.7.6.]
Sometimes individual discs in a multi-CD or multi-LP set will have their own numbers printed on them, separate from the main catalog number on the packaging. These numbers can be entered in the 'Barcode And Other Identifiers' section (see help/submission-guidelines-release-barcode ) [...]

RSG §4.8.2.
If a release has both sub label and parent label catalog numbers, they should all be listed, in order to complete the relevant discographies. If it was released on multiple labels but one label was more involved in the release, list that label first.

RSG §4.8.3.
For each label field that is added a catalog number field will also be added. These must be completed. The sequence of catalog numbers should match the sequence of label fields, for example if three labels are listed the catalog number assigned by the label in the third label field should be added to the third catalog number field. If all labels used the same catalog number this should be added to all catalog number fields.

RSG §4.8.4.
Where an individual release has multiple catalog numbers on one label, the first catalog number field should contain the catalog number that best matches the label’s catalog system. It helps to mention the location of the multiple catalog numbers on the release in the Release Notes.

RSG §4.9.1.
A matrix number (sometimes derived from the catalog number) is used during manufacturing to keep track of the process, for example to mark the sides of a record. Usually, the matrix number is inscribed in the run out groove of a record, or in the center of a CD. Note that other information can be inscribed in these areas as well, such as the Mastering engineer or plant identifier. Matrix numbers can be entered under the 'Barcode And Other Identifiers' section - see help/submission-guidelines-release-barcode

RSG §4.9.2.
If there is no apparent catalog number on the release, please enter the matrix number/s, barcode, or other identifiers in the 'Barcode And Other Identifiers' section. Information on Jamaican matrix numbers can be found in the post at http://discogs.versitio.com/help/forums/topic/131564

RSG §4.10.1.
Sometimes, a Distribution Code will appear on the release. Please don't enter these as catalog numbers, they can be entered using the 'Other' tag in the 'Barcode And Other Identifiers' section - see help/submission-guidelines-release-barcode.
Label codes, distribution or price codes are sometimes prefixed with country abbreviations or indicators. Please enter these in the description field only, not as part of the code itself. More information on Distribution Codes can be found in the Discogs wiki.

this forum thread for more details.

► [Image] Smallest

RSG §4.12.1.
This chart shows the process stripped to the bones. The artist records their work, duplicates and packages it themselves, and then sells it direct to the public. Labels, distributors, manufacturers, and retail outlets are removed from the path entirely.

The release will be 'Not On label' at Discogs, unless the artist creates a label name for the release.

► [Image] Medium

RSG §4.12.2.
This chart shows an idealized path for the artist's release, from the recording studio through to the public.

The label here is one and the same as the record company, they both have the same name and are the same entity.

This is a standard path for releases on small or medium sized labels operating in probably one country or territory. Non-major label releases in the rock, folk, and jazz genres are likely to follow a path close to this. If you substitute the recording studio for the artist's own studio, the model also fits a lot of electronic releases.

Note the gray path representing an 'import'. The importer will be another business in another territory, that buys a certain number of copies of the release from the distributor, and has their own distribution path in the separate country or territory. The import will be exactly the same release, it is physically shipped to the importer.

These releases are usually reasonably easy to catalog on Discogs - there will be one label for the release.

► [Image] Major label

RSG §4.12.3.
This is one of a myriad of possibilities for a major label release. The main difference that drives this model is the release is manufactured and sold in different places by different companies.

The label here is really only a brand. It is used by the record company to give a distinct identity to the release.

Once the part of the company that deals with the logistics of creating the release (recording, mastering, packaging) finishes that stage of the process, the release master is then sent to separate regional branches of the record company for manufacturing. These regional offices are likely to be in different countries or territories around the world. The master package will include the audio and any artwork required to replicate the release during manufacturing. One of the main benefits of doing it this way, rather than just shipping imports, is costs are kept down by manufacturing close to where the item will be sold, rather than shipping container loads of releases around the world.

If the record company doesn't have a branch in a particular territory, it may license the release to another company in that territory, and they will arrange the manufacturing and distribution of the release. This company could be a record label (and associated brand), or it could be a distributor, manufacturer, or any other company that has the ability to organize the manufacturing and distribution of the release.

Usually, each separate branch of the chain will include their name on the release, as well as the label (brand) name. Also, manufacturers and distributors may be mentioned on the release artwork.

These releases are the hardest to catalog clearly on Discogs. The most factual method is to list the record company regional branch, licensee, or other entity as well as the label (brand) on the release.

► [Image] Digital release

RSG §4.12.4. This is a model for digital releases - MP3s, WAVs, AACs etc as sold at online shops such as iTunes, Beatport, Juno etc.

It is apparent that the structure is similar to the major label release structure above. However, there are a number of differences. The label / record company have a much smaller role, and the (online) distributor and (online) shops a much larger one.

The digital distributor can also act as a record company / label and publisher.

There is no manufacturing. The digital file is ed down the chain in various stages of preparation for sale. The final version of the file only comes into being once it is encoded, which is often done by the online shop.

Related Topics:

◾ Database Guidelines 1. General Rules
◾ Database Guidelines 14. Updating Information
◾ Database Guidelines 18. Updating An Artist Profile
◾ Database Guidelines 19. Updating A Label Profile
◾ Database Guidelines 22. FAQ for Artists And Labels
◾ Extended Database Glossary
◾ [Discogs] Contributing to Discogs
◾ [Discogs] Quick Start Guide
◾ [Discogs] Finding The Information On A Release
◾ [Discussion] Index - Printing companies (May 2014)
◾ [Discussion] Recorded At (June 2013)
◾ [Discussion] Frequently Asked Questions (FAQ) (April 2008)
◾ [List] Incorrectly capitalized artist and label names
◾ [List] And-we-make-records-too
◾ [List] Recording/Mixing/Mastering Studios
◾ [List] concert halls, opera houses, theaters, arts centers & other venues
◾ [List] Churches
◾ [List] Academic and public electroacoustic/electronic music studios
◾ [List] Universities
◾ [List] Festivals
◾ [Website] Official USPS Abbreviations

Database Guidelines 5. Barcodes & Identifiers

◾ 5.1. How To Enter
◾ 5.2.a. Barcodes
◾ 5.2.b. Label Code
◾ 5.2.c. Matrix / Run-Out
◾ 5.2.d. SID codes
◾ 5.2.e. Pressing Plant ID
◾ 5.2.f. Distribution Code
◾ 5.2.g. Price Code
◾ 5.2.h. SPARS Code
◾ 5.2.i. Depósito Legal
◾ 5.2.j. ASIN
◾ 5.2.k. ISRC
◾ 5.2.l. Rights Society
◾ 5.2.m. 'Other'
◾ 5.9. description field
◾ 5.10. 'none'
◾ 5.11. stickers

RSG §5.1.
This section allows you to enter any identifying numbers and codes such as barcodes, matrix numbers, and other such information. These fields are optional information for a submission, but please bear in mind that the more information that is included, the easier it is to keep the database correct, and it increases the usability of the data for everyone.

First, click the "Add barcode or identifier" button. You'll then see the fields to be filled in:

► [Image] Barcode fields 1

Select the type of identifier you want to enter from the drop down. You can then enter the identifier in the second field. Click the "Add description" button to open the 'Description' field, if needed.

► [Image] Barcode fields 2

Use the "Add barcode or identifier" button to add another row. You can add as many rows as you need.

► [Image] Barcode fields 3

RSG §5.2.
The following are definitions for all the tags that can be selected in the barcode and other information (BaOI) section.

RSG §5.2.a.
Barcodes can be sourced from both the barcode text (the numbers printed below the barcode) or by reading the barcode itself with a barcode scanner. If there is a discrepancy between these two sources, both barcode variations can be entered into separate barcode fields.

Usually, the human readable code will include spaces, dashes, or other characters. These characters only serve to make the barcode easier to read, they are not necessary for computers to parse. Ultimately, the barcode can be entered both ways on the same release, please do not delete one version in favor of the other. When entering as-on-release text barcodes, please add all characters present.

The 'Description' field can be used to indicate the source of the barcode, for example "Text" (the numbers printed below the barcode) and "Scanned" (when using a barcode scanner to read the code). In the case of multiple barcodes on a release, they can all be entered in separate barcode fields - please use the 'Description' field to provide any further information, if possible.

RSG §5.2.b.
Label Code is a four or five digit code prefixed with LC. GVL started on 1st May 1976 to allocate Labelcodes 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 "LC 0125". Please be careful not confuse this with catalog or matrix numbers.

RSG §5.2.c.
Matrix / Run-Out information is often stamped in the run out grooves of records, or in the inner ring of CDs. Vinyl run out etchings can also contain mastering engineer / mastering studio / pressing plant information (often as initials), and extra text. This information should all be added to one 'Matrix number' field.

Matrix Numbers and other run out information can also be extracted from the whole run out inscription, and added as further 'Matrix Number' fields with descriptions and / or expanded upon in the notes as the submitter sees fit.

Matrix numbers can also be found printed on the label, often without the stamper version etc, this can be added in a separate field if desired.

There can be large gaps between different sections of a releases run out inscriptions. Please only use a space to denote such gaps, as using other separators may cause problems for people searching for a specific data string.

One edition of a release may have many different matrix numbers on individual copies - especially for major label releases. These are considered manufacturing variations for the purposes of cataloguing on Discogs, and not unique releases, so one Discogs 'release' may contain multiple variations in matrix numbers etc. For smaller releases, or in special cases, the matrix variation may indicate a unique release / edition, so please ask in the Database Forum Topic if in doubt.

RSG §5.2.d.
SID codes (Source Identification Codes) were gradually introduced in 1994 by the International Federation of the Phonographic Industry (IFPI) in order to help combat piracy. The mastering SID code is usually found in the matrix area/mirror band of a CD. The mould SID code is usually found in the mould/hub of a CD molded into the plastic of the disc.

The mastering SID code identifies the machinery used to make the glass master. The mould SID code identifies the plant where the CD was pressed. SID codes should not be used to identify manufacturing plants or glass mastering facilities however as the codes may transfer from owner to owner of the equipment and/or pressplant.

A SID Code consists of the letters IFPI, followed by either four or five additional characters, which may be alphabetical or numerical. A mastering SID code must always start with the letter 'L'. A mould SID code can start with any letter apart from 'I', 'O', 'S' and 'Q'.

Though untypical, some releases may have the SID codes repeated in the matrix string itself. Rarer still, a release may sometimes have more than one mould SID code. Further details about SID codes and their implementation can be found here.

A release with SID codes cannot have been made before 1994. If the date cannot be established with a citation or an adequate explanation, the date should be left blank.

When entering SID codes, please do not transcribe the logo as iƒpi. Lowercase ifpi should be used instead.

RSG §5.2.e.
Pressing Plant ID is an identifier code presented on the release which identifies the pressing plant it was pressed at. If known, please also add the pressing plant to the LCCN section as well.

RSG §5.2.f.
Distribution Code is a certain kind of code which appears on releases in addition to one or more obvious catalog numbers. Please only use where the nature has been confirmed and do not confuse with the more frequent Price Codes.

RSG §5.2.g.
Price Code is an identifier assigned to determine the price of an audio carrier. Price codes can appear in various kinds, e.g. two letters and three digits (BA100, PM 500), circled letters (Ⓐ or Ⓦ), as "series" (Serie Azul, Série Artistique), 1 or 2 letters (M, AC), 2 or more digits, often after a dash (-213, 0812), etc.

RSG §5.2.h.
SPARS Code is a three letter code developed by the Society Of Professional Audio Recording Services (SPARS) that appears on compact discs and records.

RSG §5.2.i.
Depósito Legal or Legal Deposit is a code assigned by a government's copyright office or central library. The prefix, sometimes printed as D.L., should be added to the free text field.

RSG §5.2.j.
ASIN is the Amazon Standard Identification Number. This is a unique identification number assigned by Amazon.com and its partners for product identification within the Amazon.com organization. Please provide submission notes that point to the relevant release on Amazon.
This number should only be applied to releases manufactured by Amazon (CD-Rs), physical releases exclusive to Amazon, and digital files sold by Amazon.

RSG §5.2.k.
ISRC or International Standard Recording Code. As these apply to individual tracks, please use the description field to note which position it applies to. These should only be added when they are printed on the physical release or can be extracted from the release via software. Please do not add these from internet sources.

country guideline page. An example is "ASCAP".

RSG §5.2.m.
The 'Other' field can be used for any other identifying number or code on the release.

RSG §5.9.
The description field can be used to add any further information regarding the identifier, such as the identifier type, any descriptive text associated with it, its location on the release, or anything else that seems significant. If an identifier is associated with only a subset of the total labels on the release, you can include the exact label name/s it is associated with.

RSG §5.10.
'none' can be entered into any field to indicate the absence of an identifier, but only when this is needed for differentiation of the release from other versions.

RSG §5.11.
If information is taken from stickers that have been applied after manufacture (for example by the distributor), please declare it is a sticker in the description, and add any further information available (for example, the company name).

Related Topics:

◾ Database Guidelines 1. General Rules
◾ Database Guidelines 4. Label / Catalog
◾ Database Guidelines 14. Updating Information
◾ Database Guidelines 19. Updating A Label Profile
◾ Extended Database Glossary
◾ [Discogs] Contributing to Discogs
◾ [Discogs] Quick Start Guide
◾ [Discogs] Finding The Information On A Release
◾ [List] Creative Barcodes
◾ [List] Messages on run-out grooves
◾ [List] Rights Societies incorrectly used as Labels
◾ [Group] Group: Database Mentors and Protégés

Database Guidelines Formats list)

◾ 6.1. Format

◾ 6.2. Eligible Formats:

◾ 6.3. Physical Media
◾ 6.4. Video
◾ 6.5. MP3, ogg-vorbis, And Other File Based Formats

◾ 6.6. LP versus 12"
◾ 6.7. CD versus CDr
◾ 6.8. CD Matrix

◾ 6.9. Format Descriptions:

◾ 6.10. Album, Mini-Album, EP, Mixtape, Maxi-Single and Single
◾ 6.11. Limited Edition
◾ 6.12. White Labels, Promos and Test Pressings
◾ 6.13. Stereo
◾ 6.14. LP
◾ 6.15. Unofficial Releases
◾ 6.16. Compilation
◾ 6.17. Reissue and Repress
◾ 6.18. Shaped Vinyl Size
◾ 6.19. All Media & Box Set
◾ 6.20. Tour Recording