Server Updates

Changes mainly of interest to MusicBrainz Users The Style Guide has been updated. When moderations fail the ModBot user now adds a note to the moderation stating the reason for the failure; for example, “This album has already been renamed” or “This track has been deleted”.  While moderations remain open, the system now checks periodically … Continue reading “Server Updates”

Changes mainly of interest to MusicBrainz Users

  • The Style Guide has been updated.
  • When moderations fail the ModBot user now adds a note
    to the moderation stating the reason for the failure; for
    example, “This album has already been renamed” or “This track has been
    deleted”. 
  • While moderations remain open, the system now checks periodically to see
    if the moderations prerequisites and dependencies are still valid. 
    If they are not, then the moderation is immediately closed, and the ModBot
    adds a note to explain what happened.  So far this has been
    implemented for the most common moderation types; it will of course be
    extended to include all moderations in future releases.  This change
    should help to solve most of the problems relating to dependencies between
    moderations.
  • Moderation notes can now be longer than 255 characters.
  • The page formerly known as “Browse ‘Various Artist’ Albums” is now known
    as “Browse Releases”, and it can also browse single-artist releases
    too.  For example, you can now browse
    all soundtracks, regardless of artist.
  • When modifying your profile, it is now possible to remove your e-mail
    address from the system.
  • Forgot your password?  We can
    e-mail it to you
    (as long as you know your login name, and you’ve
    previously entered and confirmed your e-mail address).
  • When entering track names, the input fields are now limited to 255
    characters, to match the limitation on the underlying database. 
    Previously sometimes people would enter moderations to change the track
    name to something longer than 255 characters, but the moderation would
    then always fail.
  • When viewing a moderation in detail, you
    can now see votes cast on your own moderations.
  • A “Merge this album” link has been added to the main album display page
    (showalbum.html).  If you get to the “Batch Operation” page with
    fewer than two albums tagged (i.e. “merge” is not available yet), then
    now a “Select more albums” link is also shown.  Hopefully these two
    changes together make it more obvious how to merge albums.
  • The statistics page now includes a breakdown
    of open moderations by moderation type.
  • Your profile page has moved. 
    The “view” and “edit” profile pages are now separate. 
    The “view” page now shows some voting statistics. 
    You can now list other moderators’ votes –
    Try it!
    (Having said that though I’m not really happy with this feature yet,
    since it shows the other user’s vote as being “your” vote,
    and then doesn’t let you vote as a result.  Caveat emptor.)

Specific changes to particular moderations:

  • When adding an artist alias, the system checks that the alias name
    does not already exist (for this, or any other, artist). 
    MusicBrainz does not support duplicate aliases (yet).
  • “Add Artist Alias” mods will fail (possibly before voting is over) if
    the alias name is seen to already exist, or the referenced artist is deleted.
  • “Change Track Artist” mods will fail (possibly before voting is over)
    if the track is deleted or merged away,
    or the track’s artist is changed by some other mod.
  • “Edit Album Name” mods will fail (possibly before voting is over)
    if the album is deleted or merged away,
    or the album’s name is changed by some other mod.
  • “Edit Artist Name” mods will fail (possibly before voting is over)
    if the artist is deleted or merged away,
    or the artists’s name is changed by some other mod,
    or an artist with exactly the same “new” name is found to exist.
  • “Edit Track Name” mods will fail (possibly before voting is over)
    if the track is deleted or merged away,
    or the track’s name is changed by some other mod.
  • “Convert Album to Single Artist” mods will fail (possibly before voting is over)
    if the album is deleted or merged away,
    or the album is moved to another artist (i.e. not “Various Artists”).
  • “Merge Artists” mods will fail (possibly before voting is over)
    if the old artist is deleted or merged away,
    or the old artist’s name is changed by some other mod,
    or the old and new artist are somehow the same,
    or the old artist is “Various Artists” or the “Deleted Artist”,
    or no artist with the “new” name is found to exist,
    or the new artist is the “Deleted Artist”.
  • “Convert Album to Multiple Artists” mods will fail (possibly before voting is over)
    if the album is deleted or merged away,
    or the album is already “Various Artists” (changed by some other mod),
    or the album’s artist is changed by some other mod.

Changes mainly of interest to MusicBrainz Programmers

  • The ‘showtrack.html’ page now also accepts a ‘?mbid=GUID‘ argument,
    like the artist and album pages already did. 
    Try it.
  • Certain URLs can now be used to retrieve both the RDF and the HTML
    versions of the data; which is retrieved depends on the “Accept” HTTP
    header.  Alternatively, the “?content-type” parameter can be
    specified to force the selection of a particular variant.  For
    example:

    The URLs that can be used in this way are:

    • /artist/GUID
    • /album/GUID
    • /track/GUID
    • /trm/GUID
    • /discid/GUID
  • New documentation has been added.
  • Documentation has been updated.

Changes mainly of interest to MusicBrainz Server Programmers

  • When
    InitDb.pl
    runs the various SQL scripts, it now timestamps the
    script output.  By also adding the “–echo” argument (e.g.
    ./admin/InitDb.pl --createdb --echo --import *.tar.bz2)
    the SQL commands are echoed too.  These changes are intended to make
    it easier to see how the import is progressing, and to see why it’s
    taking so damn long 😉
    Also it no longer attempts to create the database user if it already
    exists.
  • The “ModBot” code now lives in its own module, namely
    MusicBrainz/Server/ModBot.pm
    It (via the
    ./admin/CheckVotes.pl
    script) now accepts command line arguments such as “–verbose”. 
    Sadly this doesn’t include “–help” (yet), so just take a peek at the code
    to see what’s on offer.
  • The code which merges artists has moved from
    MOD_MERGE_ARTIST.pm
    into
    Artist.pm
  • The
    FreeDB.pm
    code has been tidied up a little.
  • Sql.pm
    now complains if your use of “AutoCommit”, “Begin”, “Commit” and
    “Rollback” isn’t to its liking.
  • When a change is made to one of the style sheets, just run
    ./admin/UpdateStyleSheetLinks
    to force all clients to reload the style sheets next time around.
  • A bug in
    comp/topmodsbox
    has been fixed whereby if there have been no
    moderations recently (e.g. on a development box), then the cache code
    failed, causing the component to (expensively) re-query the data on every
    request.
  • &DBDefs::DB_STAGING_SERVER is no longer just true or false. 
    If it’s true, it should be set to the name of the type of server this is,
    e.g. “development”, “test”, etc.

Dave Evans