Style / Old style practices

Status: This is an official style guideline.

This page talks about the things we used to do, but no longer need to now that the data can be entered properly.

The limitations of the structure of the database has often meant that we couldn’t enter data in the most logical way and we needed to find other ways to enter the data. Since the database is very large, it can take quite some time for the data to be fixed when guidelines change or new features are added, so you may come across some of the things described on this page. If you do, feel free to help fix it.

There were a few things which were particularly problematic in the past:


To handle releases with multiple discs, we developed a style (Disc Number Style) to standardise the disc numbers and disc titles. People would also often add links to the other discs in the annotation. Later, a “part of a set” relationship was added to link the discs together. You may still see releases using “(disc n)” in the title, with links to the other discs in the annotation or with those relationships if they haven’t been fixed yet.

Examples of Disc Number Style:


Originally, in order to reduce the number of one‐off collaborations in the database, we had a style guideline which said to enter a track such as “Song Name” by “Artist A & Artist B” as “Song Name (feat. Artist B)” by “Artist A”. This was particularly controversial and was eventually removed, but you may still find collaborations credited in this way.

After that, we allowed people to add collaborations as new artists with a name such as “Artist A & Artist B”, and had a “collaboration” relationship to link to the artists involved.

With the introduction of artist credits, we can link to multiple artists and we don’t need to use separate collaboration artists. Many of the existing collaborations with collaboration relationships were converted into artist credits, but you may still see some which couldn’t be automatically converted. You may also see ones that didn’t have the proper relationships at all.

Release events

At first, instead of having a separate entry for each release, every version with the same track listing was part of the same entry and that entry had multiple release events which consisted of both a date and a country. Later, support for labels, catalogue numbers, barcodes and formats was added and the date and country were made optional.

The way the data was stored also meant that a release could only have one release title, so if a later version had a slightly different title, we couldn’t store that information. Releases also only had one status, so we couldn’t mark certain release events as promos or bootlegs either.

Lastly, release relationships also belonged to the release and not to specific release events. There was no way to say which release event that relationships such as cover art, ASIN, Discogs or purchase relationships belonged to, so you may find releases where these links are on the wrong releases.


We often use annotations to store information which doesn’t fit into the database at the time. There are far too many things to list here, so this is just a list of some of the most common things you're likely to see. Of course, once data has been entered properly, it can be removed from the annotation.

Some things which annotations have been used for include:

Earliest release relationship

Originally it wasn’t possible to share recordings (then called tracks) between releases. If a recording was identical, they could be linked with the “earliest release” relationship. Most of these were automatically merged, but there were some which weren’t. Now that recordings can be merged, if they’re the same, they should simply be merged.

Title Style
Special Cases/Misc.