MusicBrainz Database/Schema

From MusicBrainz Wiki
Jump to navigationJump to search



Same as our current artist entity, but with new "country" and "gender" attributes.

Artist Credit

List of artists, variations of artist names and pieces of text to join the artist names. Examples:

Release Group

Represents an abstract "album" entity. Technically it's a group of releases, with a specified type. The type is the same as current release type. Examples:


Real-world release object you can buy in your music store. It has release date and country, list of catalog number and label pairs, packaging type and release status. Example:

  • 1984 US release of "The Wall" by "Pink Floyd", release on label "Columbia Records" with catalog number "C2K 36183" and UPC "074643618328", it's an official release and comes with two CDs in jewel case.


Piece of media, included in a release. Contains information about the format, position in the release and an optional title. Has attached CD TOCs. Example:

  • CD1 of the 1984 US release of "The Wall" by "Pink Floyd"
  • CD2 of the 2005 UK release of "Aerial" by "Kate Bush", named "A Sky of Honey"


Simple list of tracks. Tracklists are used by mediums.


This object is not visible to users on its own, only in the context of a tracklist. It contains a link to a recording, title, artist credit and the position on the tracklist.


Represents unique audio data. Has title, artist credit, duration, list of PUIDs and ISRCs. Examples (all are different Recordings):

  • Album version of the track "Into the Blue" by "Moby"
  • Remix "Into the Blue (Buzz Boys Main Room Mayhem mix)" by "Moby"
  • Remix "Into the Blue (Underground mix)" by "Moby"


One layer above recordings ("song", "composition", etc.). While recording represents audio data, work represents the composition behind the recording. Advanced Relationships should be used to link recording and work.

  • Song "Into the Blue" by "Moby" -- all the recordings listed above will be linked to this object


Same as our current label entity.

Database Schema

This diagrams shows the core database tables and relationships between them:


Because we are adding new core entities, and there are plans for adding more, ARs between them need to be optimized. Only the absolutely necessary information is in l_*_* tables, everything else is shared:


Data conversion

Next Generation Schema Next_Generation_Schema/Migration_Plan.

See Next_Generation_Schema/Migration_Notes.

For ARs see Next Generation Schema/Release_Relationships_Conversion and Next Generation Schema/Track Relationships Conversion

Some edge cases are compiled in Next Generation Schema/Conversion_Edge_Cases.

User Interface

Web Service


See Next Generation Schema/Roadmap.