Data quality: We want your feedback!

The release locking concept has been around for quite some time and has been debated at great lengths. After a couple of long calls Don and I reworked the concept into the data quality concept. The idea is relatively simple:

  • Each artist and each release in MusicBrainz now has a quality indicator that shows the quality of the data: Unknown, low, normal or high.
  • Data that is marked with low quality should be easy to change.
  • Data with normal quality should take about the same amount of effort to change as it takes now.
  • Data with high quality should be harder to change, to avoid incorrect changes to good data.
  • Each edit type will define the number of votes required to pass, the duration votes stay open, what to do if an edit receives no votes, and if a vote is an auto edit.

This new feature will allow us to edit sloppy data faster, tune the editing system to fit better with how people use it and it will allow us to prevent accidental edits to good data. Now we need to your help in testing this system and giving us feedback about the various edit levels.

If you would like to help, please read the data quality wiki page, view the new edit information page and then test the new features on the staging server. Each artist and release page now has a Change Quality link that will allow you to change the quality of the artist/release. Once those are changed, the edit system will behave according to the values set forth in the edit information page. Please note that the change artist/release quality edits are currently autoedits, which will be changed once we’re done testing the bulk of this new system. For right now we’re making it easy to change the data quality for testing purposes.

To start testing, head over to the staging server. Add any bugs you find to the bug tracker. Or post your feedback in the comments.

Beta Period for Style Guidelines (aka Don's suggested new style evolution procedure)

In the last month the Style Council has worked on a couple of guidelines for classical music, and the first one of these is nearly ready: The OperaTrackStyle will describe how track titles for Operas should be written.

There were also discussions about how to make the style-changing process simpler and less tiresome. Now Aaron suggested to use “Don’s suggested new style evolution procedure” to make this new guideline official.

So, I suppose, I should explain a bit what that procedure would be. The explanation is attached as a podcast, since I still cannot type too much.