User:BarryPlatt

From MusicBrainz Wiki

Barry Platt

Barry Platt [ MB: bplatt | IRC: bplatt | Wiki: BarryPlatt ]

MusicBrainz editor based in Cambridge, UK, with interests in a variety of areas including soundtracks.



Track/Release Advanced Relationship Types

There has been some discussion on musicbrainz-style surrounding the issue of ARs having different meaning at release level to track level. A consensus seems to be forming that Artist-Release ARs should be used when we have knowledge about an artist's contribution to a release but aren't able to identify the specific tracks to which that contribution applies. It has become clear however that some ARs have a distinct meaning at release level compared to track level, so there is a conflict between a release-level AR applying at that level because it actually applies to the release, or because it applies to an unknown subset of the tracks on the release.

BrianFreud has categorized the ARs into three types, defined as:

Type 1
Some ARs apply best at only the track level, if there's solid info to support that it does apply to that specific track, but end up in release-level ARs as "fuzzy" data when the specific track(s) are unable to be (yet) identified.
Type 2
Some ARs apply only at the release level, and not to any track, and are not ever "fuzzy" at this level.
Type 3
Some ARs can apply at either level - photography, liner notes, production, etc.

The following tables enumerate the AR hierarchy for track/release ARs and assigns types to each of the possible ARs.

Artist to Track/Release

Note that there is a small variation between the AR list for artist-track and artist-release ARs - specifically "wrote the libretto" doesn't apply to tracks, "produced material that was sampled in" includes the instrument tree for tracks but not releases and "had tribute album" only applies to releases.

Advanced Relationship Release Track Type Note
compilations An album compilation is different to a track compilation
compiled Y Y 3 See CompilerRelationshipType, Compilation Relationship Class.
I'm not experienced with the kind of releases or tracks that use CompilerRelationshipType. I'm a bit baffled how the role of "the tracks and the sequence" (definition of compiler) is different of product manager or business manager for the overall release. I think the AR's definition should be improved. Still, as this AR is written, I agree it's Type 3. --JimDeLaHunt 2008-01-17
DJ-mixed Y Y 3 See MixDJRelationshipType, Compilation Relationship Class.
I'm not experienced with the kind of releases or tracks that use MixDJRelationshipType. I don't see how the role of MixDJ for the Release is different from the role of MixDJ for all of the Tracks individually. Maybe there is a clear answer, and I'm just uninformed. I think the AR's "very messy and possibly outdated" discussion section could be improved. Still, as this AR is written, I agree it's Type 3. --JimDeLaHunt 2008-01-17
performance
{additionally} {guest} performed Y Y 1
performed {additional} {guest} {instrument} on Y Y 1
performed {additional} {guest} {vocal} vocal on Y Y 1
{orchestra} orchestra {additionally} performed Y Y 1
{additionally} conducted Y Y 1
performed {additional} chorus master on Y Y 1
has tribute album(s) Y 2
remixes
{additionally} remixed Y Y 1
produced material that was {additionally} sampled in Y 2 If this, and the following, were combined I'd suggest they would be Type 1
produced {instrument} material that was {additionally} sampled in Y 1
composition
{additionally} composed Y Y 1
{additionally} wrote the libretto for Y 1
{additionally} arranged {instrument on} Y Y 1
provided {additional} {instrument} instrumentation for Y Y 1
{additionally} orchestrated Y Y 1
{additionally} wrote the lyrics for Y Y 1
production
{additionally} {co-}{executive }produced Y Y 3 Production on a release isn't the same as production on a track
{additionally} {co-}{executive }engineered Y Y 3 Engineering on a release isn't the same as engineering on a track
{additionally} audio engineered Y Y 3
{additionally} mastered Y Y 3
{additionally} sound engineered Y Y 3
{additionally} live sound engineered Y Y 3
{additionally} {co-}mixed Y Y 3
{additionally} recorded Y Y 3
{additionally} programmed {instrument on} Y Y 1 I have a sense this might be better in the performance tree
{additionally} edited Y Y 3
has a miscellaneous role on Y Y 3 These are edge cases, conceivably any of them could apply at either level
provided legal representation for Y Y 3
provided booking for Y Y 3
provided artist & repertoire support for Y Y 3
provided {additional} creative direction on Y Y 3
provided {additional} art direction on Y Y 3
provided {additional} design/illustration on Y Y 3
provided {additional} graphic design on Y Y 3
provided {additional} photography on Y Y 3
provided travel arrangements for Y Y 3
published Y Y 1
provided merchandising for Y Y 3
wrote {additional} liner notes for Y Y 3

Release to Release/Track

Most of these have equivalents as Track-Track ARs, but are invalid as Track-Release or Release-Track ARs, so I consider them type 2 ARs for the purposes of this discussion rather than type 3.

Advanced Relationship Release Track Type Note
compilations
is a DJ-mix of Y 2 Has equivalent track-track AR
covers or other versions
is the earliest release of Y 2 Has equivalent track-track AR
is a live performance of Y 2
is a remaster of Y 2 Has equivalent track-track AR
is a cover of Y 2 Has equivalent track-track AR
is the original for the transl{iter}ated track listing Y 2
remixes
is a remix of Y 2
is a mash-up of Y 2
has/had {additional} {instrument} samples taken from Y 1

Track to Track

Most of these have equivalents as Release-Release ARs, but are invalid as Track-Release or Release-Track ARs, so I consider them type 1 ARs for the purposes of this discussion rather than type 3.

Advanced Relationship Track Type Note
compilations
is a DJ-mix of Y 1 Has equivalent release-release AR
is a compilation of Y 1
is a medley of Y 1
covers or other versions
is the earliest release of Y 1 Has equivalent release-release AR
is a remaster of Y 1 Has equivalent release-release AR
is the earliest version of Y 1
is a cover of Y 1 Has equivalent release-release AR
remixes
is a remix of Y 1 Has equivalent release-release AR
contains {additional} samples from Y 1
is a mash-up of Y 1

Label to Release/Track

My sense is this is type 1, but can anyone give an example where to publish a release might have a different meaning than to publish some or all of the tracks on a release? If so, type 3.

Advanced Relationship Release Track Type Note
published Y Y 1

URL to Release/Track

These are included for completeness. Very few can be applied at both track and release level, and I'm not sure there's ever a situation we'd want those ARs to be fuzzy.

Advanced Relationship Release Track
links to affiliates
has Amazon ASIN Y
has cover art at Y
discography
has a review page at Y
production
was recorded by studio at Y
contains miscellaneous support from Y
has legal representation by Y
was booked by Y
has artist & repertoire support by Y
has creative direction by Y
has art direction by Y
has design/illustration by Y
has graphic design by Y
has {additional} photography by Y
has travel arrangement by Y
was published by Y
has merchandising by Y
get the music
is available for download under the Creative Commons {license} license at Y
can be purchased for mail-order at Y
can be purchased for download at Y Y
can be downloaded for free at Y Y
other databases
has tabs on OLGA at Y
is a soundtrack for the movie with an IMDb page at Y
has a Wikipedia page at Y
has a Discogs page at Y
has a MusicMoz page at Y

Template:lang en-native