History:Change Default Data Quality Proposal
ChangeDefaultDataQualityProposal
Please note that the data quality setting implies nothing about the musical quality of the artist or the release, nor does this proposal imply any denegration of the editing abilities of the editor who creates or edits a release.
The Problem
Problem 1: Too many open edits.
Problem 2: Too few voters voting on those edits.
Problem 3: Too many inexperienced editors editing without knowledge of the relevant style guidelines.
Result 1: Too many "add release" edits slipping into the database without having been voted in or out.
Result 2: Too many other edits to releases slipping in without proper vetting, allowing for releases to slowly "degrade" in overall quality as time passes.
Currently, all releases enter the database at normal quality.
All added releases enter the database, if not voted down. All edits to releases are applied, if not voted down. All ARs attached to edits are applied, if not voted down.
This proposal attempts to address these problems by making two changes in how quality levels for releases work.
Data Quality
From DataQuality:
The data quality idea has the following goals:
- Establish a method to determine the quality of an artist and the releases that belong to that artist. This provides consumers of MusicBrainz a clue about the relative quality rating of the data in the database.
- Provide fine grained control over what efforts are required to edit the database and to vote on those edits.
- Provide editors with a means to allow easier editing of data that is deemed to be of poor quality.
- Provide editors with a means to make it harder to edit data that is considered to be of good quality.
- Reduce the overall number of edits in the system by making the requirements to pass an edit suited for each edit type.
