With the release of the Next Generation Schema in May of 2011 we officially deprecated the use of version 1 of our XML API. Now, 6 years later, we feel that we can finally pull the plug on this version of the API — it receives less than 1% of our Web Service traffic.
On the first release after 1 August 2018 we’re going to remove the Web Service version 1 (ws/1 API endpoint) support. If you are one of the few authors of software that has not updated your software to use the newer ws/2 endpoint, your software’s MusicBrainz functionality will cease to work after 1 August.
We think more than 6 years is enough time for people to upgrade their tools. đ
This small server release brings a new report for recordings, updates URL cleanup, and provides enhancement for guessing lettersâ case in French titles. It also features preliminary changes for further switch to live search, still available for test. The git tag is v-2018-01-24. Thanks again to naiveaiguy and haruute for their contributions!
New Feature
[MBS-9425] – New Report: âRecordings with same name by different artists with same nameâ
So as you might know, I recently joined the MetaBrainz team and my first project was the completion of our long-standing Solr search project to provide live search indexing for the MusicBrainz database.
You can now instantly search for entities that have been updated. There should be a maximum 15 second delay between the database update and the entity changes being reflected on the search.
This implies that once we have ironed out the Solr search we can finally retire the direct database search on the main site and use Solr with its advanced search syntax. For details on the new syntax features you can refer to the Lucene query parser documentation. For details on field types you can refer to our Search Syntax guide.
As I said, the Solr search is still in its alpha stage, thus it can be unstable and have bugs. As such do not depend on it for your critical applications.
Speaking of bugs, here’s where we need your help the most! We want testers to use Solr as extensively as possible and file any bugs you encounter at our Solr Issue tracker. You may encounter bugs like –
Missing fields in the API output for the webservice.
Certain types of queries not working in Solr search that happen to work on the main website.
Missing data/edits/updates not being indexed.
Since we haven’t ported our search analyzers in their entirety, Solr might have worse search results than our main search.
I would like to re-iterate – Solr is still in alpha and not everything is perfect.We need your help to make it so.
Here’s the first release of 2018! Its main changes are listed below. It also brings a few additional small bug fixes and code refactoring, such as changing the sidebar rating and tag UI components to use React. The git tag is v-2018-01-10. Thanks to naiveaiguy and haruute for their contributions!
Bug
[MBS-9370] – Tests race condition triggers error âCouldn’t connect to the rendererâ
[MBS-9578] – Editor private subscriptions/tags/ratings pages should not be linked to
New Feature
[MBS-8206] – New Report: Official/Promotional Releases supporting Disc IDs that don’t have an attached Disc ID
Task
[MBS-9561] – Add Anison Generation to the otherDBs whitelist
[MBS-9566] – Add Brahms IRCAM to the otherDBs whitelist
[MBS-9574] – Add patronage auto-select/cleanup for Drip URLs
Improvement
[MBS-8576] – Show work type description in work editing form
Winter has arrived! And so did the latest release of the MusicBrainz server, bringing updates (React 16.2.0 and Lodash 4.17.4), code refactoring, and a bunch of bug fixes. Thanks to navap for updating the documentation search and to reosarevok for adding La BoĂŽte aux paroles to the Lyrics whitelist. The git tag is v-2017-12-21.
Bug
[MBS-9525] – Database dump sometimes fails to sync to FTP
[MBS-9540] – Release lookup does not return user ratings in json ws
[MBS-9542] – New default iTunes link format (without âidâ characters) is denied
[MBS-9547] – ModBot leaves note with broken unicode
[MBS-9570] – Email header fields with non-ASCII characters are not correctly encoded
[MBS-9577] – Google custom search engine (WikiDocs) is out of date
Task
[MBS-9560] – Add http://laboiteauxparoles.com/ to the lyrics whitelist
Improvement
[MBS-9575] – Make “Enable vinyl track numbers” opt-in for new users
Your favourite time of the year is at hand! No, I don’t mean Christmas, I (obviously) mean the Classical Community Clean Up. Debussy went very well, Mahler was fantastic, and it’s time for a third! Come join us in paying a little special attention to classical masters!
This time around the community has chosen (probably) the world’s only composer who is also a keyboard layout, the titan of Czech music AntonĂn DvoĹĂĄk. We encourage you during this time to not only help the community clean up DvoĹĂĄkâs metadata, but to learn more about DvoĹĂĄk as well.
The clean up events officially last one month (but can be continued until theyâre complete!) and are meant to utilize our communityâs power to clean up our classical metadata. If you are new to MusicBrainz, to classical editing, or both, we have a whole tool box and plenty of advice, tips and tricks to share. We advise you bookmark the tool boxâitâs quite helpful! Our team of classical music enthusiasts will also provide plenty of support on our forums, so come join us!
What we will work on:
Reviewing the existing works to make sure there are no duplicates and the information looks correct, and add any missing works (keep in mind while it is perfectly ok to add lost works, itâd be good to specify theyâre lost so that people donât accidentally use them on recordings).
Check the release list for anything that doesnât follow the classical guidelines. Not only that should be fixed, but thatâs a good sign of the recording and relationship info being incomplete too.
Check the recording list. The only recordings that should be here by the end of the cleanup are of DvoĹĂĄk himself as a performer (probably none, and in any case very few). Anything else being here should have performer relationships added to it if missing, then the artist credits for the recording should be changed to list the main performers (you can use the relevant script for that). Try to fix the whole release the recording is on, even if itâs not all by DvoĹĂĄk! But in the case of a very large compilation, itâs always acceptable to fix only the DvoĹĂĄk content on it.
Add missing DvoĹĂĄk recordings! If you have enough info to add a DvoĹĂĄk release weâre missing, thatâs always useful. Just make sure to try to add as much info as possible from the get go, so we donât have to clean that addition up as well. đ
We recently had 2995 recordings, 781 works and 862 releases under DvoĹĂĄk, and we’re expecting to have many fewer wrongly listed recordings and many more DvoĹĂĄk releases by the end of the month. Donât know where to begin? Join us and ask, let us help you find a jumping in point! Here’s to another great month of Classical Clean Up with DvoĹĂĄk!
As we published at the start of October, during the last month we’ve been trying to clean up our data for Gustav Mahler. October is over now, and you might be wondering how that went. Well, no need to wonder anymore, because our users have made a fantastic job not just of cleaning Mahler’s data up, but of showing us how clean it is!
Our editor stupidname took statistical snaps at the start, the midpoint and the end of the project:
Oct 1st
Oct 18th
Nov 2nd
Recordings
2361
66 (-2295)
11 (-2350)
Tracks
11866
14094 (+2228)
15228 (+3362)
Releases
924
1192 (+268)
1363 (+439)
ReleaseGroups
720
871 (+151)
986 (+266)
As we can see, the existing recordings where mostly cleaned up 18 days in, but a lot of new releases kept being added up until the end of the month.
Additionally, stupidname also checked the amount of recordings for some of the main works by Mahler to see the changes over time (specifically, due to the way our works… err.. work, the data is for one movement of each work rather than the main work itself):
Oct 1st
Oct 18th
Nov 2nd
Symphony no. 1
95
115Â (+20)
120 (+25)
Symphony no. 2
114
145 (+31)
149 (+35)
Symphony no. 3
108
141 (+33)
144 (+36)
Symphony no. 4
68
82 (+14)
85 (+17)
Symphony no. 5
92
93 (+1)
98 (+6)
Symphony no. 6
65
74 (+9)
87 (+11)
Symphony no. 7
76
86 (+10)
96 (+20)
Symphony no. 8
89
108 (+19)
106 (+17)
Symphony no. 9
125
141 (+16)
176 (+51)
Das Lied von der Erde
47
53 (+6)
55 (+8)
Kindertotenlieder
41
52 (+11)
62 (+21)
Lieder eines fahrenden Gesellen
54
63 (+9)
68 (+14)
This data is a bit less precise, because some of these recordings are partial (and the specific organization of Symphony no. 8 makes it especially tricky to count), but it is still a very nice view of how we’ve gotten extra recordings of basically everything!
Our editor loujin made graphs with the amount of edits per editor during the cleanup. There are too many editors for the legend to show them all, but the graph shows that the two biggest contributors by far were ListMyCDs.com (green) and stupidname (light blue), with a bunch of other editors making several hundred edits as well.
And finally, also thanks to loujin, you can see how the cleanup affected the amount of edits done on Mahler (no prizes for guessing which bar it is!):
Thanks to all this hard work, our entry on Mahler should be a particularly good example of the amount and quality of classical data you can get from MusicBrainz, and an inspiration for other composer pages! Thanks so much to everyone, and we’ll be back with more in December!
While the streets of Barcelona were filling up with the referendum conundrum, a bunch of people were spotted chattering and bantering, sometimes with pillows and colorful socks, searching for gelato.
Yes, that bunch of people would be us. đ
Our annual MusicBrainz summit was held on September 30thâOctober 1st in the colorful, lively city of Barcelona. We had people (and chocolates) from nine countries: Spain, India, Germany, UK, USA, France, Estonia, Denmark, and Iceland.
From leftâright, top: Wieland (Mineo), Sambhav (samj1912), Sean (Leftmost Cat), NicolĂĄs (reosarevok), Ben (LordSputnik), JĂŠrĂ´me (loujin), Alastair (alastairp); middle: Leo Verto, Freso, Michael (bitmap), Elizabeth (Quesito), Chhavi; bottom: Yvan (yvanzo), Rob (ruaok), Param (iliekcomputers), Suyash (ferbncode). Laurent (zas) behind the camera.â¨
Having a majority of our team in a room with food obviously lead to lots of productive discussions. We talked about translations, recommendations engines, voting, and packaging. We also talked about SpamBrainz, user scripts being included as part of our projects, documentation, single sign-on for all Brainz, and a bunch of other things.
One of the nice things we could do this summit was to go over our user survey results. As you might remember, we had this banner on our site asking us to take part in a survey. The results gave us a good idea of our community in regards to what language they use, what Brainz project they use more, how do they come to know about us, and so on.
Summit session in progress.
We got to know what you like, but more importantly what you donât. We heard all of you, and we are on it. We will publish a detailed report on that soon.
You cannot be in Barcelona with such a good lot of people and not end up exploring the city. The team ended up cycling on the streets of Barcelona (many times on the wrong side), climbing up to the mosaic-y Park GĂźell, snacking on pinchos and tapas, visiting the Pompeu Fabra University (where our AcousticBrainz project resides) and taking their daily after-lunch strolls through the Arc de Triomf.
Apart from that, some of the record-breaking points from the summit would be:
We had nice colorful pillows with all our kids (we mean, Brainz projects) printed on them. And summit t-shirts too.
The summit was live streamed on our YouTube channel, for all those who couldnât make it. That went pretty well, with only minor technical difficulties, and it provided a good overview (literally! đ ). For those who missed it (or want to rewatch it), the archived streams are available on YouTube.
We finally decided to improve the user experience of our projects (more on the blog about that later).
We worked on a new wonderful Sound Team recording while having a terrace barbeque hosted by Elizabeth.
[soundcloud url=”https://api.soundcloud.com/tracks/344725049″ params=”color=#00cc11&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true” width=”100%” height=”166″ iframe=”true” /]
More gelato was eaten than ever before. (That shouldnât be surprising.)
We’re wrapping up the summit with this blog, but we have all the memories preserved. Find the amazing moments captured by our in-house photographer Zas in his Facebook gallery, and those moments in motion in my own video here:
Boo! Release cycle was interrupted during the MetaBrainz Summit 17 and is now back to the usual period of two weeks. This release contains a lot of code refactoring, some admin tooling, and a few fixes. Optimizations were made to parts of the web service, particularly for JSON and browse requests. Anti-spam measures taken in July have been relaxed, as well as the period of time allowed for auto-editing newly added entities. The git tag is v-2017-10-31.
Bug
[MBS-9313] – Adding first release event should be an auto-edit
[MBS-9513] – User interface locales with country code are not working
This time around the community has chosen the late Romantic composer Gustav Mahler (who was quite the conductor as well!). We encourage you during this time to not only help the community clean up Mahlerâs metadata, but to learn more about Mahler as well.
The clean up events officially last one month (but can be continued until theyâre complete!) and are meant to utilize our communityâs power to clean up our classical metadata. If you are new to MusicBrainz, to classical editing, or both, we have a whole tool box and plenty of advice, tips and tricks to share. We advise you bookmark the tool boxâitâs quite helpful! Our team of classical music enthusiasts will also provide plenty of support on our forums, so come join us!
What we will work on:
Reviewing the existing works to make sure there are no duplicates and the information looks correct, and add any missing works (keep in mind while it is perfectly ok to add lost works, itâd be good to specify theyâre lost so that people donât accidentally use them on recordings).
Check the release list for anything that doesnât follow the classical guidelines. Not only that should be fixed, but thatâs a good sign of the recording and relationship info being incomplete too.
Check the recording list. The only recordings that should be here by the end of the cleanup are of Mahler himself as a performer (probably mostly this piano roll album). Anything else being here should have performer relationships added to it if missing, then the artist credits for the recording should be changed to list the main performers (you can use the relevant script for that). Try to fix the whole release the recording is on, even if itâs not all by Mahler! But in the case of a very large compilation, itâs always acceptable to fix only the Mahler content on it.
Add missing Mahler recordings! If you have enough info to add a Mahler release weâre missing, thatâs always useful. Just make sure to try to add as much info as possible from the get go, so we donât have to clean that addition up as well đ
Donât know where to begin? Join us and ask, let us help you find a jumping in point! Here to another great month of Classical Clean Up with Mahler!