Universal Music in the UK just launched their Artist Gateway, a site to showcase their artists and to provide lots of detail about their artists. Universal is using MusicBrainz IDs and data throughout their system to give their site the proper structure and links to elsewhere on the net. To launch it, Universal put out a slick video, complete with a plug for MusicBrainz:
[vimeo http://www.vimeo.com/41151572 w=450&h=253]
This is a huge step for MusicBrainz — in the past the labels didn’t even acknowledge our existence and now they are using our data.
Thanks James Cowdery & crew over at Universal in London!
A potential customer just nudged me about our use of now deprecated CC licenses and a deprecated Public Domain dedication. We should really address these issues and upgrade our data licenses. We are currently using the following licenses:
The move to the CC license version 3 allows us to use the latest and most robust version of the Creative Commons license. If you’d like lots more detail on what this change means, please read the CC version 3 license “brief” explanation.
The CC0 grant improves a number of aspects of our old Public Domain dedication, especially in jurisdictions outside the US. Our current dedication isn’t sufficient to renounce any copyright over the data in some countries. The CC0 grant is an improved version that maximizes the global coverage of our rejection of copyright for our data.
Summary in plain english: We’d like to move to updated, more robust licenses. We are not changing what data is available under which license, nor are we taking away any rights that end users already have.
If you have questions or comments, please post them here. If there are no objections to this change, I will make it effective with our May 15th release.
UPDATE: Fixed an incorrect link that Mike from the Creative Commons pointed out. Thanks Mike!
We’ve talked a bit about our upcoming schema change release, but we hadn’t nailed down the exact date of the release. Now that we’re tangibly close, we’ve settled on the May 15th as the actual release date.
As some of you may know, this summer through Google Summer of Code I’m working on internationalization of musicbrainz-server. As outlined in my proposal, I’m currently looking to find what I call “language liaisons”: folks willing to be the go-to person about a given language for me and other developers.
Auf Deutsch!
What’s expected of liaisons:
Willing to be pestered occasionally, by me or other developers, about language-specific concerns: when adding new features, and thus adding new strings, we’d like to be able to ensure nothing’s added that will need to be changed before it can be translated into a given language.
Willing to file bugs for strings already in the database that are untranslatable, should you find them.
Be on the musicbrainz-i18n mailing list; this will be the main venue for organization and communication about i18n issues.
Ideally, to be an active translator for your language – but this isn’t a requirement, because I’d like to get the widest global coverage I can; even if a language doesn’t currently have a translation, we don’t want to unintentionally sabotage future translators with untranslatable strings!
日本語
I’ll also be determining a (related) list of “target languages” for the summer, with the intention of releasing translation on musicbrainz.org with these languages at the end of the summer. I’ll consider for inclusion on this list languages that are both in active translation on Transifex and have language liaisons.
If you’re interested in being a language liaison, please contact me: ianmcorvidae (at) musicbrainz (dot) org, editor ianmcorvidae, or ianmcorvidae on IRC, and join the mailing list.
We’ve released another set of bug fixes and improvements for the server. Thanks to Joachim LeBlanc, Johannes Weißl and the rest of the MusicBrainz team for helping on this release!
Bug
[MBS-2553] – Change wording for no External Links in the sidebar
[MBS-4041] – Nonexistent elections cause Internal Server Error
[MBS-4544] – Predefined advanced searches on /search no longer work
v4.0.1 of libmusicbrainz4 has now been released. This is primarily a maintenance release to fix a couple of bugs that were reported. Additionally, the code has now moved to GitHub, and can now be found at https://github.com/metabrainz/libmusicbrainz.
The main changes are:
Fixed bug LMB-30 – Unable to access all relation lists on objects with multiple relation lists
The interface has changed as regards to retrieving relation lists, due to LMB-30. Previously, the library only returned the last relation list that was returned in the XML response. The old ‘RelationList’ method on the Artist, Label, Recording, Release, ReleaseGroup and Work classes has been marked ‘deprecated’, and a new ‘RelationListList’ method will return a list of all relation lists for the entity.
For backwards compatibility, the ‘RelationList’ method will operate in the same manner as release 4.0.0, only returning the last relation list.
As ever, please see the enclosed README for details on support and bug reporting. The release is available for download at http://musicbrainz.org/doc/libmusicbrainz.
We’ve had trouble with Toshiba drives and the replacement Western Digital drives are dog slow to the point of being unusable. All the reviews I read for drives are horrible and just about every drive has 4 stars and still has terrible problems.
Can you recommend a 750+GB portable drive that we can buy from Amazon or Newegg?
Sorry for being a week behind on this release, but we’ve just finished pushing out another set of changes. Many thanks to Lukáš Lalinský, Paul Taylor and the rest of the MusicBrainz team for making this release happen! Here’s what we’ve just released:
[MBS-3160] – Add view to artist pages that shows release groups/recordings/etc credited to that artist only (solo releases only – exclude collaborations, feat., etc)
We’re working to add a paid option to our Web Service for commercial users and for end users who would like to have faster access. We’re finally getting close to being able to offer this service and we would like to get some feedback from our users about this.
We are proposing to add “no waiting” access to our web service — this proposed service would:
Allow continuous sequential access to our version 2 web service without delays between calls. You would not be required to have any delays between calls to the web service (our current service requires a 1 second delay between calls)
Still have a global rate limit that may temporarily deny callers access to our web service (with 503 responses) if our service gets overloaded. We would work hard to ensure that our service would not reach this limit, since its a paid service, but we cannot guarantee that.
Not allow concurrent (more than one call at a time) calls to our web service per user. We reserve the right to terminate your service if we find that you are making concurrent calls to our “no waiting” service.
Our existing web service will not be affected by this new service — the existing service will remain free and limited to one request per second as it is now. Initially the new service is intended for end-users who wish to have faster access to our web service. Once we’ve ironed out the kinks in this new service we will offer this service for commercial customers as well.
