Style/Relationships: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (copy before move)
Line 1: Line 1:
{{official style guideline}}
{{Official style}}


⚫
This page outlines general guidelines that should be followed when adding [[Relationships|relationships]]. Many relationships also have their own guidelines which, should they conflict, supersede the ones on this page.


For relationships which link an entity to a URL, see the [[/URLs|URL guidelines]] as well.
{| width="100%"
| style="border:0;" |
{| cellspacing="0" cellpadding="0" style="clear: {{{clear|left}}}; margin-bottom: .5em; float: left; padding: .5em 1.4em .8em 0; background: none; width: {{{width|{{{1|auto}}}}}};" {{#if:{{{limit|}}}|class="toclimit-{{{limit}}}"}}
| __TOC__
|}
{| cellspacing="0" cellpadding="10" style="clear: {{{clear|right}}}; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width: {{{width|{{{1|auto}}}}}};" {{#if:{{{limit|}}}|class="toclimit-{{{limit}}}"}}
| {{AdvancedRelationshipNavigation}}
|}
|}


For assistance in determining the correct relationship types to use when describing compiling, DJ mixing, mastering, mixing, remastering, remixing and sampling, please refer to [[Mix Terminology]].
⚫
This page outlines general guidelines that should be followed when adding [[Advanced Relationships|advanced relationships]].


⚫
==Don't Make Relationship Clusters==
== Guideline Locations and Order of Precidence ==


* See [[Style/Relationships/Do not cluster|Don't make relationship clusters]].
These guidelines apply to all [[:Category:Relationship Type|relationship types]]. In addition, many [[:Category:Relationship Type|relationship types]] have additional guidelines defined by the [[:Category:Relationship Type|relationship type's]] parent [[:Category:Relationship Class|relationship class(es)]], as well as on the [[:Category:Relationship Type|relationship type's]] page itself.
: Example: The [[Amazon Relationship Type]] is subject to:
::# [[Advanced Relationship Style]] and any additional [[:Category:Relationship Type|relationship type]] guidelines it incorporates,
::# any guidelines found on [[:Category:External Resource Relationship Class|External Resource Relationship Class]],
::# any guidelines found on [[:Category:External Website Relationship Class|External Website Relationship Class]],
::# any guidelines found on [[:Category:Affiliate Relationship Class|Affiliate Relationship Class]],
::# and any guidelines found on [[Amazon Relationship Type]].
Any time a conflict between two pages is perceived, the more specific page predominates.
: Example: A guideline on the [[Amazon Relationship Type]] page would supercede one on the [[:Category:External Website Relationship Class|External Website Relationship Class]] page.

⚫
==Don't Make Relationship Clusters==
* See [[Don't Make Relationship Clusters]].


==Crediting an artist's role at the track vs. the release level ==
==Same Artist With Different Names==
* See [[Same Artist With Different Names]].


There are multiple levels at which an artist's role on a song or album can be noted:
==Artist Role Inheritance & Track vs Release crediting==


⚫
# If the relationship is applicable to all tracks on a release, apply it to every work or recording on the release.
There are now multiple levels at which an artist's role on a song can be recorded: you can relate the artist to the song, to the album, or to the band that recorded the song. So it's now non-trivial to figure out the full list of people who should be credited for any given track.
# If the relationship is applicable to all tracks on a release, put it on all the tracks, rather than on the release.
# If the relationship applies to only a few tracks, and you know which ones, apply it only to those works or recordings.
# If you are unsure which tracks a relationship applies to, put it at release level. A basic effort to determine to which tracks the relationship is applicable is appreciated.
⚫
# If the relationship is not applicable to all tracks, and you know which ones it applies to, put it on only those tracks.
# If the relationship is not applicable to all tracks, and you don't know which ones it applies to, put it at release level. A basic effort to determine to which tracks the relationship is applicable is appreciated, however.
# If the credit is release level, and does not apply on a track by track basis (e.g. graphic design for the album's cover), then apply the relationship to the release, not the tracks.
# If the credit is release level, and does not apply on a track by track basis (e.g., graphic design for the album's cover), then apply the relationship to the release, not the tracks.


If you find a release which has release level relationships and you know which tracks the relationships apply to, please fix them.
'''Note:''' There are still releases that do only have release level advanced relationships, predating the discussions as to where Advanced Relationships should be attached. These still need to be corrected. If you find a release with such release level Advanced Relationships that can be moved to the tracks, please fix them.


==Personal and business relationships==
==Prefer Specific Relationship Types==


It not part of MusicBrainz' mission to capture all the aspects of the personal life of artists nor the economic life of the recording industry.
You should make an effort to make the relationship type as specific as possible. This means that you should avoid any of the generic types, if:
* The liner or another source specifies which of the subtypes apply, or
* You can easily deduce which of the subtypes apply.


A person should '''not''' be added to the database only to allow a link to indicate that they went out with, were married to, or were related to an artist. The only exception is when a non-musical person can be connected to two or more artists, allowing those artists to indirectly be linked together.
In these cases you should use the specific relationship types, and omit a relationship of the generic type. If you feel the generic type is more appropriate - for example, if the evidence provides conflicting information, or if no specific information is available - then add your reasons and supporting information to the edit note and an annotation. This will help voters confirm your analysis and will make sure other editors are aware of the background when doing later edits.


Label entries should '''not''' be added solely to represent investors, share-holders, etc. Relationship types which would represent fine-grained ownership details (or the entire economic macrocosm) have not been created, and the existing relationship types should not be misused for the purpose.
===Generic Types===
Here is a list of "generic types" and examples of preferred specific types:
* [[Arranger_Relationship_Type|Arranger]]: prefer [[Instrumentator_Relationship_Type|Instrumentator]] and/or [[Orchestrator_Relationship_Type|Orchestrator]]
* [[Engineer_Relationship_Type|Engineer]]: prefer [[Audio_Engineer_Relationship_Type|Audio Engineer]], [[Editor_Relationship_Type|Editor]], [[Mastering_Engineer_Relationship_Type|Mastering Engineer]], [[Mix_Engineer_Relationship_Type|Mix Engineer]], [[Recording_Engineer_Relationship_Type|Recording Engineer]], [[Sound_Engineer_Relationship_Type|Sound Engineer]] and/or [[Programmer_Relationship_Type|Programmer]]. If the Engineer type is either Balance Engineer or Tonmeister, the generic Engineer type should be used, and '''not''' one of the more specific Engineer types.
* [[Performer_Relationship_Type|Performer]]: prefer adding instruments, orchestra and/or vocal types
* [[Writer_Relationship_Type|Writer]]: prefer [[Composer_Relationship_Type|Composer]], [[Lyricist_Relationship_Type|Lyricist]] and/or [[Librettist_Relationship_Type|Librettist]]


While proposals for new relationships are always welcomed by the Style Council, be forewarned that proposals which would add relationship types to allow tracking finer-grained personal details or company or economic details will face a greater degree of scrutiny.
===Examples===
* [[Artist:fe59ad15-3cd4-4f00-8a79-a0fe9b884dec.html|Larry Luddecke]] recorded and mixed [[Release:c154a6fd-a3b7-4c64-a93e-abe3fd1de897|Old Dogs]], as confirmed by the [http://www.acousticmusic.com/staines/olddogs.htm author's website]. He is linked to the release with [[Recording_Engineer_Relationship_Type|Recording Engineer]] and [[Mix_Engineer_Relationship_Type|Mix Engineer]] relationships. No [[Engineer_Relationship_Type|generic Engineer]] relationship is created.
* [[Artist:328d146c-79f1-4eb6-9e40-8ee5710c14e5|Imogen Heap]] wrote [[Track:ae1e8d02-8b7f-4a18-a39a-63afaef9f077|Earth (instrumental)]]. As this is an instrumental track, the writing credit clearly does not apply to any lyrics or libretto. Instead of a [[Writer_Relationship_Type|Writer]] relationship, Imogen is credited using a [[Composer_Relationship_Type|Composer]] relationship.
* [[Artist:b5ffc3aa-b868-4b88-905f-d73d51dbe51c|Mick Jagger]] and [[Artist:f0ed72a3-ae8f-4cf7-b51d-2696a2330230|Keith Richards]] wrote [[Track:38699ebf-b56c-45c0-9b5b-660ee4173303|You Got Me Rocking]]. As their individual roles [[Wikipedia:You_Got_Me_Rocking|are unclear]] - one might have been primarily working on the lyrics, with the other writing the music - the [[Writer_Relationship_Type|Writer]] relationship is used. Once more information becomes available, these can be replaced by [[Composer_Relationship_Type|Composer]] and/or [[Lyricist Relationship Type|Lyricist]] relationships.


[[Category:Advanced Relationship]]
[[Category:WikiDocs Page]]

Revision as of 08:06, 19 May 2011

Status: This is an official style guideline.

This page outlines general guidelines that should be followed when adding relationships. Many relationships also have their own guidelines which, should they conflict, supersede the ones on this page.

For relationships which link an entity to a URL, see the URL guidelines as well.

For assistance in determining the correct relationship types to use when describing compiling, DJ mixing, mastering, mixing, remastering, remixing and sampling, please refer to Mix Terminology.

Don't Make Relationship Clusters

Crediting an artist's role at the track vs. the release level

There are multiple levels at which an artist's role on a song or album can be noted:

  1. If the relationship is applicable to all tracks on a release, apply it to every work or recording on the release.
  2. If the relationship applies to only a few tracks, and you know which ones, apply it only to those works or recordings.
  3. If you are unsure which tracks a relationship applies to, put it at release level. A basic effort to determine to which tracks the relationship is applicable is appreciated.
  4. If the credit is release level, and does not apply on a track by track basis (e.g. graphic design for the album's cover), then apply the relationship to the release, not the tracks.

If you find a release which has release level relationships and you know which tracks the relationships apply to, please fix them.

Personal and business relationships

It not part of MusicBrainz' mission to capture all the aspects of the personal life of artists nor the economic life of the recording industry.

A person should not be added to the database only to allow a link to indicate that they went out with, were married to, or were related to an artist. The only exception is when a non-musical person can be connected to two or more artists, allowing those artists to indirectly be linked together.

Label entries should not be added solely to represent investors, share-holders, etc. Relationship types which would represent fine-grained ownership details (or the entire economic macrocosm) have not been created, and the existing relationship types should not be misused for the purpose.

While proposals for new relationships are always welcomed by the Style Council, be forewarned that proposals which would add relationship types to allow tracking finer-grained personal details or company or economic details will face a greater degree of scrutiny.

Retrieved from "https://wiki.musicbrainz.org/index.php?title=Style/Relationships&oldid=45346"