Difference between revisions of "Style/Recording"

From MusicBrainz Wiki
m
(What should and shouldn't be merged together?)
Line 13: Line 13:
 
A recording is intended to represent unique audio. This means you:
 
A recording is intended to represent unique audio. This means you:
 
* should normally merge recordings with the same [[ISRC]].
 
* should normally merge recordings with the same [[ISRC]].
* should normally not merge recordings with different ISRCs.
+
* shouldn't normally merge recordings with different ISRCs.
 
* shouldn't merge different performances (which includes re-recordings, live versions and versions with different lyrics)
 
* shouldn't merge different performances (which includes re-recordings, live versions and versions with different lyrics)
 
* shouldn't merge different recordings of a performance (e.g. a live bootleg recorded by multiple people)
 
* shouldn't merge different recordings of a performance (e.g. a live bootleg recorded by multiple people)

Revision as of 18:29, 25 December 2011

Status: This is an official style guideline.

Title

See the title guidelines for how to enter the recording's title.

Artist

The artist should usually be the same as the first release of the recording.

What should and shouldn't be merged together?

A recording is intended to represent unique audio. This means you:

  • should normally merge recordings with the same ISRC.
  • shouldn't normally merge recordings with different ISRCs.
  • shouldn't merge different performances (which includes re-recordings, live versions and versions with different lyrics)
  • shouldn't merge different recordings of a performance (e.g. a live bootleg recorded by multiple people)
  • shouldn't merge different edits, mixes, remixes or remasters of a performance.
  • shouldn't merge recordings which have conflicting relationships.

ISRCs

An ISRC should, in theory, correspond to a single recording in MusicBrainz and a recording should correspond to a single ISRC. However, in practice, mistakes are sometimes made. In such cases, annotations are recommended.


Style
Overview
Title Style
Entities
Relationships
Classical
Special Cases/Misc.
Languages