alastair
commented
9 years ago Release type and status come from MusicBrainz. There is some documentation here: https://musicbrainz.org/doc/Release#Status https://musicbrainz.org/doc/Release_Group/Type
The way that the musicbrainz structure works is that a "Release" is an album, normally released in a region and in a certain format (CD, LP). A "Release Group" collects together many copies of the same release that might be from different regions. See for example http://musicbrainz.org/release-group/a106e33b-e440-3ff3-9250-c6408ed73e60 released in different countries and different formats in different years.
In CompMusic we only have 1 release per release-group.
You can see Type in the url above on the right-hand side. You can see Status if you go to a release: http://musicbrainz.org/release/9d4c2605-2590-4d51-ade4-938382ef2622 (look on the right-hand side)
If you access this data through the API you also see the data: http://musicbrainz.org/ws/2/release/9d4c2605-2590-4d51-ade4-938382ef2622?inc=release-groups
<status>Official</status> and <release-group type="Album" ...>
You can get this information through the musicbrainz api by using
mb.get_release_by_id(theid, includes=['release-groups'])
Status and Type are not always set (they can be blank)
We want to add two fields to the data.Release model - status and type and fill them with these values from MusicBrainz. Because we will apply it to all of our styles - carnatic, hindustani, and makam we can do the import in dashboard/release_importer.py. Probably when we create the release object:
https://github.com/MTG/dunya/blob/master/dashboard/release_importer.py#L117
For now we do not need to expose this information anywhere. Once we have it we will do some investigation before choosing the next steps.
We don't currently add release type and status to dunya. This would be useful to see in the api.