Style update, 2015-01-13

It’s been, well, a bit too long, but here we go with a new entry of “What has changed in Style”!

The two bigger changes to previous usage here involve pseudo-releases and live bootlegs: Pseudo-releases should only contain basic data in most cases and bootlegs should only be renamed if they have no title.

Improvement

  • [STYLE-165] – Add Russian text to Style/Language/Russian
  • [STYLE-408] – Add a “Play” work type

New Feature

  • [STYLE-292] – Add “Licensee” relationship
  • [STYLE-374] – “Founded” Artist-Place relationship type
  • [STYLE-388] – Add {instrument/vocal} to Event-Artist performance relationships
  • [STYLE-400] – Add a release-area (and place?) “manufactured in” relationship
  • [STYLE-403] – Add “formerly attributed to” work-artist relationship

Task

  • [STYLE-342] – Define how pseudo-releases should be used
  • [STYLE-391] – Postponed Events
  • [STYLE-405] – Update live bootleg style now that we have events and places

Sub-task

  • [STYLE-103] – Update once audiobooks style is passed

Server update, 2015-01-12

Our first release of the new year is out today, containing the usual set of editing bug fixes and improvements. There’s also a small new feature in the release editor that allows propagating the release title and artist credit to the release group.

Anyone experiencing failures in InitDb.pl after upgrading DBD::Pg to version 3.5.0 will want to get this update, since it contains a workaround.

Thanks very much to chirlu, navap, nikki, and the MetaBrainz team for their work on today’s release.

The git tag is v-2015-01-12 and the full changelog is below.

Bug

  • [MBS-4904] – Edit search automatically focuses text fields on page load
  • [MBS-8025] – Spurious "performance" entries in work search results
  • [MBS-8032] – Internal server error applying problematic add ISRC edits
  • [MBS-8047] – Applied merge release groups link has broken links
  • [MBS-8099] – Edit search automatically focuses text fields when changing dropdowns
  • [MBS-8108] – Edit removing track with track mbid redirect can’t close
  • [MBS-8116] – Place edit form acts on outdated parse-coordinates responses
  • [MBS-8126] – InitDb.pl fails with newest DBD::Pg

Improvement

  • [MBS-2895] – Make it possible to propagate release changes to the release group
  • [MBS-6162] – Mention mbslave in INSTALL
  • [MBS-7498] – Recognise Deezer URLs
  • [MBS-7733] – Recognise and clean up 7digital.com URLs
  • [MBS-7924] – Match e-onkyo, hd-music and ototoy URLs with "purchase for download" relationship type
  • [MBS-8077] – Clean up mobile Soundcloud and ReverbNation URLs
  • [MBS-8078] – Match and clean up Google Play URLs
  • [MBS-8080] – Show CAA-down warning also when the Archive is down completely

New Feature

  • [MBS-7688] – Add autoselect for Vine URLs

Task

  • [MBS-5671] – MBServer internal code using old search json format should use new format

Editing: Making MusicBrainz better

Over the past few weeks I’ve received a number of emails from people who are concerned about some editors who are losing sight of some basic principles behind editing data in MusicBrainz. I wanted to chime in and remind people of some of the principles that should guide how we all get along when we edit data in MusicBrainz.

First and foremost is:

Be polite and give people the benefit of the doubt that they are doing the right thing.

I don’t have to explain being polite. Yes, we all have our bad days — that is a given. But if you’re having a bad day, stop editing MusicBrainz and step away from your computer. Go outside! When you do edit, please be kind to your fellow editors.

Giving people the benefit of the doubt that they are doing the right thing is also important. The vast majority of people who edit MusicBrainz have good intentions and you should assume that to be the case.

Second, edit to make the database better. Vote yes if an edit makes the data better.

This one is a lot more vague, since “better” is a subjective term. We should accept edits that are “good enough” and avoid asking people to make “perfect” edits.

Edits fit into four categories:

  1. Edits that makes things better (perfect or not)
  2. Edits makes things different (but neither are better)
  3. Edits that contain some correct things and some incorrect things
  4. Edits that are outright wrong (existing data is better)

The first type should clearly get a yes vote. For the second, if it doesn’t make things worse, abstain and leave a comment. The third is a judgement call and I would suggest applying this heuristic:

Unless it takes more time to fix the edit than to make a new one, vote yes.

Clearly, the fourth type deserves a no vote.

That brings me to the final topic for now: No votes. A no vote is a very strong expression that has potentially chilling effects that may prevent people from editing again. A no vote should be considered the last resort. Use a no vote if you can’t find another way to resolve an edit.

Finally, some tips for auto editors: If you see an edit that is not perfect, approve it and fix it.

Auto editors are supposed to set the tone for the project and auto editors should practically never vote no on something. You have more powers than fellow editors, so please use your powers for good!

Thanks and happy (and polite) editing!

Picard 1.3.2 released

Picard 1.3.2 is now available on the Picard download page. This again is only a small maintenance release which mainly updates the OS X build to fix crashes some users experienced with Picard 1.3.1. Here is the complete list of fixes:

Bug

  • [PICARD-681] Fixed tags from filename dialog not opening on new installations
  • [PICARD-682] Picard 1.3.1 crashes on OSX on start

For Ubuntu users we have also finally updated our stable PPA.

Server update, 2014-12-29

This release is quite small because it overlapped with the holidays, but contains a fix for an annoying guess-case issue in the release editor that several people reported. Thanks to chirlu for the rest of the bug fixes listed here!

The git tag is v-2014-12-29.

Bug

  • [MBS-4668] – Edit search loses selections when the page number is too high
  • [MBS-8064] – Can’t add documentation to migration-created relationship types
  • [MBS-8086] – Guess case for release title does not trigger an edit
  • [MBS-8091] – Can’t fix non-normalized artist credits

Picard 1.3.1 released

This is a maintenance release, mostly bug fixes. All users are encouraged to upgrade.

Binary packages are available at http://picard.musicbrainz.org/downloads/

Bug

  • [PICARD-273] – Picard should use the correct Accept header when talking to web services.
  • [PICARD-589] – Picard refuses to load files if any path component happens to be hidden
  • [PICARD-642] – ConfigUpgradeError: Error during config upgrade from version 0.0.0dev0 to 1.0.0final0
  • [PICARD-649] – Windows installer sets working directory to %PROGRAMFILES%\MusicBrainz Picard\locale
  • [PICARD-655] – Last.fm plus tooltip help elements are all messed up
  • [PICARD-661] – Regression: Tagger script for cover art filename does not work anymore
  • [PICARD-662] – Retrieving collections causes AttributeError: release_list
  • [PICARD-663] – Artist name makes it impossible to save

Improvement

  • [PICARD-658] – Support the new pregap and data tracks
  • [PICARD-659] – Set the originalyear tag when loading a release
  • [PICARD-665] – Web service calls to ports 80 and 443 do not need explicit port specification. 443 should be automatically made https.

Server update, 2014-12-15

We’ve released another server update today, though a fairly modest one, since bigger changes have been happening in the background with embedding JSON-LD into our pages and switching our JavaScript over to browserify. A few more edit types have been made auto-edits for everyone, as detailed in the changelog below. There’s additionally been some misc. UI changes, and a fix to output artist genders in the JSON webservice.

Thanks to chirlu, nikki, reosarevok, and the MetaBrainz team for their hard work on today’s release.

The git tag is v-2014-12-15.

Bug

  • [MBS-7916] – “Set track durations” preview is broken for single-track mediums
  • [MBS-8008] – “Add Event” (entity) and “Add Event” (release event) share the same translation string
  • [MBS-8044] – Map doesn’t zoom when pasting coordinates
  • [MBS-8066] – “Date” field wraps inconsistently in different browsers
  • [MBS-8082] – Gender missing on artist lookup (JSON)

Improvement

  • [MBS-7478] – Make more use of HTML5 form field types
  • [MBS-7970] – Replace guess case bubbles with icons next to the fields
  • [MBS-7973] – Make remove alias/ISRC/ISWC edits auto-edits for auto-editors
  • [MBS-7975] – Make move disc ID edits auto-edits
  • [MBS-8045] – Update link_event to include dates