Skip to main content

Hijacked releases, or: "Why can't people read or check pictures?"

I am going through a few hundred 7" to see if they are already on Discogs (which in itself is already a big task) and I am seeing quite a few that are not on there (so setting them apart to make scans, which is even more work). What I see way too often is so called "release hijacking" where an existing release is changed into a different release. This seriously pisses me off and I have written about it before.

Some examples: someone posts pictures saying "alternate labels" (which according to the guidelines should be turned into a different release) or "better pictures" which turn out to be for a different release altogether (different texts, labels, etc.). Or, they don't read the notes that are for a release that say something like "This is the release with X, for the release with Y, see Z" and then add pictures for the release with Y. Sigh.

What these people do not seem to realise is this vastly reduces the value of the database for everyone. It is another example of the "Tragedy of the commons" as the Discogs database is basically a shared resource. It is shared by the various users: collectors, sellers and buyers. A polluted database means that collectors don't have a correct overview of their collection, sellers no longer have a correct store, and buyers won't be getting the release they are expecting when buying it from a seller.

I see it so often that at times I am even surprised that Discogs works at all. It is also totally unnecessary: the guidelines are quite clear about what should be a new release but it seems that people are simply not reading the guidelines.

It has made me wonder what could be done, apart from having a more active community checking but I haven't come up with the ultimate answer. I think that a partial solution would be to start tagging more data (labels, sleeves) and then having a wizard walk people through a release, for example by asking them questions or offering choices based on the data in the database.

This would require that the data in the database is of good enough quality of course and likely the UI of Discogs would need to be reworked for that. This would be a major and risky operation, as it would break people's habits and you can only do this if the new system is radically better, as people won't appreciate having to change their habits if it means getting a minor improvement. But, if done well it could be worth it.

Comments

Popular posts from this blog

SID codes (part 1)

One thing that I only learned about after using Discogs is the so called Source Identification Code, or SID. These codes were introduced in 1994 to combat piracy and to find out on which machines a CD was made. It was introduced by Philips and adopted by IFPI, and specifications are publicly available which clearly describe the two available SID codes (mastering SID code and mould SID code). Since quite a few months Discogs has two fields available in the " Barcode and Other Identifiers " (BaOI) section: Mould SID code Mastering SID code A few questions immediately popped up in my mind: how many releases don't have a SID field defined when there should be (for example, the free text field indicates it is a SID field)? how many releases have a SID field with values that should not be in the SID field? how many release have a SID field, but a wrong year (as SID codes were only introduced in 1994) how many vinyl releases have a SID code defined (which is impossi

SPARS codes (part 1)

Let's talk about SPARS codes used on CDs (or CD-like formats). You have most likely seen it used, but maybe don't know its name. The SPARS code is a three letter code indicating if recording, mixing and mastering were analogue or digital. For example they could look like the ones below. There is not a fixed format, so there are other variants as well. Personally I am not paying too much attention to these codes (I simply do not care), but in the classical music world if something was labeled as DDD (so everything digital) companies could ask premium prices. That makes it interesting information to mine and unlock, which is something that Discogs does not allow people to do when searching (yet!) even though it could be a helpful filter. I wanted to see if it can be used as an identifier to tell releases apart (are there similar releases where the only difference is the SPARS code?). SPARS code in Discogs Since a few months SPARS is a separate field in the Discogs

Country statistics (part 2)

One thing I wondered about: for how many releases is the country field changed? I looked at the two most recent data dumps (covering February and March 2019) and see where they differed. In total 5274 releases "moved". The top 20 moves are: unknown -> US: 454 Germany -> Europe: 319 UK & Europe -> Europe: 217 unknown -> UK: 178 UK -> Europe: 149 Netherlands -> Europe: 147 unknown -> Europe: 139 unknown -> Germany: 120 UK -> US: 118 Europe -> Germany: 84 US -> UK: 79 USA & Canada -> US: 76 US -> Canada: 65 unknown -> France: 64 UK -> UK & Europe: 62 UK & Europe -> UK: 51 France -> Europe: 51 Saudi Arabia -> United Arab Emirates: 49 US -> Europe: 46 unknown -> Japan: 45 When you think about it these all make sense (there was a big consolidation in Europe in the 1980s and releases for multiple countries were made in a single pressing plant) but there are also a few weird changes: