CD Stub: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Make singular (Imported from MoinMoin))
 
(add references for CD Baby stub import)
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
A CD stub is an anonymously submitted track list that contains a [[Disc ID|disc ID]], barcode, comment field, and basic metadata like a release title and track names.
=CD Stubs Feature=


All CD stubs are segregated from the main database and are editable by anyone (whether they are logged in or not), however, they don't benefit from core MusicBrainz features such as edit history, permanent unique identifiers ([[MBID]]s), [[Relationships|relationships]], release information (date, country, label, etc.), and much more.
In the Server release on November 23, 2008 MusicBrainz is introducing the concept of a CD Stub. Many times people would like to contribute CD data to MusicBrainz, but would prefer to not learn to be part of MusicBrainz. These people would rather just toss some data into a pile and go on with their lives to listen to their music or rip their CDs. CD Stubs enable users to do just that.


CD stubs were implemented as a means for people to easily contribute data to MusicBrainz when they are unable, or unwilling, to create an account and add a release. They also enable us to store "untrusted" metadata like the CD Baby music catalog<ref>[https://blog.metabrainz.org/?p=278 Should we import all/some of the CD Baby data?] August 7, 2007
With this release people who come to look up a CD, but MusicBrainz does not know about that CD, will be given a choice to either enter the CD as a CD Stub or to join MusicBrainz and to enter the CD into MusicBrainz proper. (This is the red pill/blue pill decision point). Note that users who are logged in to MusicBrainz when looking up a CD will '''not''' be given the option to enter a CD Stub.
</ref><ref>[https://blog.metabrainz.org/?p=394 Imported CD Baby metadata into our CD Stub collection] June 18, 2009
</ref>, and to actively serve all this content without cluttering the main database.


==Process==
During the CD Stub data entry process, the user can choose to import from the data from FreeDB and then review the data and submit it as a CD Stub. Once the data has been entered as CD Stub, the data can be retrieved using the MusicBrainzXMLWebservice for 14 days. After the 14 days we stop serving out this data until another user comes along and attempts to submit the data to MusicBrainz via the web interface. On the web interface the user can review the data and hit submit; after this the data will be served out for another 14 days.


The CD stub process is quite simple.
The goal here is to encourage people to look at the data and for the data to improve as people use it. At the same time the server keeps track of how many times the CD Stub was requested and how many times it was reviewed and re-submitted. This allows us to show the Most Active CD Stubs to MusicBrainz Editors and allow them to import the data into the main MusicBrainz database. This flow of data gives MusicBrainz a real life view of what data is important in the world and it enables MusicBrainz editors to participate in making the database more useful for everyone.


When a disc lookup is performed in [[MusicBrainz Picard]] (or any other tagger that supports MusicBrainz CD stubs) by someone that doesn't have a MusicBrainz account, and there is no match for the [[Disc ID|disc ID]], the user is prompted to either enter the CD as a CD stub, or to create a MusicBrainz account and add it to the main database directly. Either way, the user will be able to retrieve the data and tag their files with it right away. CD stubs are not intended to replace the regular add release process, if a user has a MusicBrainz account the expectation is that they [[How To Add A Release|add a release]] to the database.
Also, this allows us to supplant FreeDB. And it allows us to store ''untrusted'' meta-data like the CD Baby music metadata catalog and to actively serve this content without having all of it in the main database.


CD stubs can also be posted using the [[XML Web Service|XML web service]], dismissing the need for users to interact with their browser.
Please watch this space as we get closer to the release of the server. More technical details will be added here on how to use this new service.


Once the CD stub has been entered, the data can be retrieved by Picard using the [[XML Web Service|XML web service]] for 14 days. After the 14 days, the next user to come along and request the data will be forwarded to the web site where they will review the CD stub and have the option of improving the data before retrieving it and tagging their files with it. After that user reviews the CD stub, its 14 day cycle starts over again.
[[Category:To Be Reviewed]] [[Category:Development]]

<small>'''Note:''' The 14 day cycle doesn't apply to users browsing the data on the website, that can be done at any time with no restriction. The cycle only applies to users requesting the data from the web service.</small>

The goal here is to encourage people to regularly look at the data and for it to improve as people use it. At the same time, the server keeps track of how many requests any CD Stub receives and how many times it's reviewed. This flow of data gives MusicBrainz a real life view of what data is important and enables MusicBrainz editors to migrate some of the more popular CD stubs to the main database. This has proved to be a success as many CD stubs are migrated into the main database each week.

== References ==
<references/>

[[Category:Terminology]] [[Category:To Be Reviewed]]

Latest revision as of 00:44, 27 April 2020

A CD stub is an anonymously submitted track list that contains a disc ID, barcode, comment field, and basic metadata like a release title and track names.

All CD stubs are segregated from the main database and are editable by anyone (whether they are logged in or not), however, they don't benefit from core MusicBrainz features such as edit history, permanent unique identifiers (MBIDs), relationships, release information (date, country, label, etc.), and much more.

CD stubs were implemented as a means for people to easily contribute data to MusicBrainz when they are unable, or unwilling, to create an account and add a release. They also enable us to store "untrusted" metadata like the CD Baby music catalog[1][2], and to actively serve all this content without cluttering the main database.

Process

The CD stub process is quite simple.

When a disc lookup is performed in MusicBrainz Picard (or any other tagger that supports MusicBrainz CD stubs) by someone that doesn't have a MusicBrainz account, and there is no match for the disc ID, the user is prompted to either enter the CD as a CD stub, or to create a MusicBrainz account and add it to the main database directly. Either way, the user will be able to retrieve the data and tag their files with it right away. CD stubs are not intended to replace the regular add release process, if a user has a MusicBrainz account the expectation is that they add a release to the database.

CD stubs can also be posted using the XML web service, dismissing the need for users to interact with their browser.

Once the CD stub has been entered, the data can be retrieved by Picard using the XML web service for 14 days. After the 14 days, the next user to come along and request the data will be forwarded to the web site where they will review the CD stub and have the option of improving the data before retrieving it and tagging their files with it. After that user reviews the CD stub, its 14 day cycle starts over again.

Note: The 14 day cycle doesn't apply to users browsing the data on the website, that can be done at any time with no restriction. The cycle only applies to users requesting the data from the web service.

The goal here is to encourage people to regularly look at the data and for it to improve as people use it. At the same time, the server keeps track of how many requests any CD Stub receives and how many times it's reviewed. This flow of data gives MusicBrainz a real life view of what data is important and enables MusicBrainz editors to migrate some of the more popular CD stubs to the main database. This has proved to be a success as many CD stubs are migrated into the main database each week.

References