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

Style update, 2014-12-03

After skipping a fortnight because of concentrating on the schema change release, here’s the next edition of the style update, with all the changes from the last month. Most of the changes involve adding new medium formats and new place/area relationships, plus making changes and additions related to the new schema change features (events and data tracks).

The biggest change this month is the addition of a classical music titles guideline. This deprecates the old Opera Tracks guideline, and basically just provides a certain amount of standardisation while keeping mostly true to the on-cover titles.

Improvement

  • [STYLE-221] – Add Data CD format(s)
  • [STYLE-354] – Add a new medium format "dts Audio CD" for CD’s that are encodes as DTS streams
  • [STYLE-367] – Add an attribute for performing time to event artists

New Feature

  • [STYLE-344] – Style for classical track titles
  • [STYLE-356] – Add a "part of" event-event relationship
  • [STYLE-371] – "Subseries" relationship (needs MBS-8055 to actually work)

Task

  • [STYLE-349] – Update special purpose track title for data tracks
  • [STYLE-350] – "Engineered at" Place relationship
  • [STYLE-351] – Release group official website wording causes it to be misused
  • [STYLE-352] – Add relationship types for setlist.fm
  • [STYLE-357] – Add event type "clinic"
  • [STYLE-359] – Merge "Videotape" into "Other"
  • [STYLE-360] – Add Playbutton as a medium format
  • [STYLE-361] – Add music card as a medium format
  • [STYLE-363] – Add VinylDisc as a medium format
  • [STYLE-364] – Add DVDplus as a medium format
  • [STYLE-365] – Add 3.5" floppy disk as a medium format
  • [STYLE-366] – Add Edison Diamond Disc as a medium format
  • [STYLE-368] – "Edited at" Place relationship type
  • [STYLE-369] – Disable dates for event relationships
  • [STYLE-370] – Place(/Area)-Recording rel: produced at
  • [STYLE-379] – "remixed at" place-recording/release relationship type

Style update, 2014-11-03

As mentioned when the new style process was announced, at a similar time to every server release post we’ll be publishing a list of what’s changed in style during that period.

The first period of two weeks (or three, in this case) under the process has passed, and these are all the style-related issues that have been accepted and implemented during it. Most of them are very small (mostly adding sites to the whitelist for the Other Databases relationship) although a couple are new relationships or relationships being extended to more entities.

No changes to the guidelines themselves have happened during this period.

  • [STYLE-211] – Allow new allmusic.com release links
  • [STYLE-250] – Add finnmusic.net to the other databases whitelist
  • [STYLE-251] – Add pomus.net to whitelist
  • [STYLE-256] – Add fono.fi to the other databases whitelist
  • [STYLE-269] – Add mixing and mastering to area relationships
  • [STYLE-307] – グラスレ(grass thread/yunisan) as Artist and Label “Other DB” relationship
  • [STYLE-308] – ジャパメタ(japameta) as Artist “Other DB” relationship
  • [STYLE-312] – Add “Deutsche Nationalbibliothek” to whitelist for other databases
  • [STYLE-328] – Add leader/concertmaster artist-release/recording relationships
  • [STYLE-337] – Add IMSLP relationship to artists
  • [STYLE-338] – Add Stage48 Wiki to the other databases whitelist
  • [STYLE-339] – Add CiNii to the other databases whitelist
  • [STYLE-340] – Add NDL to the other databases whitelist

New Guidelines for Recordings

We got this from Ben, who has been in charge of taking this discussion forward:

Since the beginning of the year there has been a lot of discussion about recordings and what exactly they should be used for. After several meetings on IRC and a couple of huge topics on the style mailing list, we’re finally ready to bring in a new definition for recordings, and new style guidelines to go with it!

The new recording definition can be viewed at http://musicbrainz.org/doc/Recording

And the accompanying style guidelines are at http://musicbrainz.org/doc/Style/Recording

The new guideline brings significant changes to the way recordings should be used, so all editors dealing with recordings should take the time to read it.

As a short summary, recordings are now never produced solely through copying or mastering. This means that recordings shouldn’t distinguish between different masters of some audio – in general, a recording will correspond a particular mix or edit. In addition:

– AcoustIDs and ISRCs have been removed from the guideline – they are mostly irrelevant for managing recordings under the new definition.
– Guidelines for audio channels have been introduced.
– Existing guidelines have been expanded.
– Several in-depth examples have been added to explain how recording should be used.

Also, as a result of these changes, the recording-recording remaster relationship type and the artist-recording master relationship type have been deprecated.

Thanks to everyone who was involved on mb-style and in the IRC meetings for your excellent ideas and contributions!

Announcing libmusicbrainz4 releases 4.0.1 and 5.0.0

Andy Hawkins says:

Hi,

I am pleased to announce two new versions of libmusicbrainz:

libmusicbrainz-4.0.2 has been updated to take account of changes made to the server on 15th May 2012. Some interfaces are now marked as deprecated, as they have been extended during the work.

Full documentation is available here:

http://metabrainz.github.com/libmusicbrainz/4.0.2/

The release can be downloaded here:

https://github.com/downloads/metabrainz/libmusicbrainz/libmusicbrainz-4.0.2.tar.gz

(MD5 checksum 5ff62abeca00fdad1bb3a8f99065ae61)

libmusicbrainz-5.0.0 has been introduced to enable the library to be more easily included in Debian due to a conflicting package name. It is identical to libmusicbrainz-4.0.2, with the following exceptions:

1. All include files are now in the musicbrainz5 directory

2. You should now link against libmusicbrainz5 (-lmusicbrainz5)

3. All previously deprecated functions have been removed.

Please note that all future work is likely to only occur on the 5.x library, so this should be used wherever possible.

Full documentation is available here:

http://metabrainz.github.com/libmusicbrainz/5.0.0/

The release can be downloaded here:

https://github.com/downloads/metabrainz/libmusicbrainz/libmusicbrainz-5.0.0.tar.gz

(MD5 checksum 3396e0c66cfacfa1f32abc7cfdbcbe13)

As ever, please report any issues in JIRA at

http://tickets.musicbrainz.org

under the project ‘libmusicbrainz’.

If you have any questions, please post them in the musicbrainz-devel mailing list. I will also attempt to be available on the #musicbrainz-devel IRC channel on Freenode.

New Style Leader and Updated Proposal Process

Nicolás Tamargo (reosarevok) is replacing Kuno Woudt (warp) as style leader. This will allow Kuno to fully concentrate on development, and also allow our other style leader Nikki to dedicate more of her time to testing changes and make it less likely for us to have botched releases.

We are also updating the proposal process, and tying it to the Jira tracker, to avoid the manual updating of the proposal table and problems with two people using the same proposal number by mistake. The updated system is at Proposals – the huge table there has been moved to Proposals/History