Difference between revisions of "History:Prefer Specific Relationship Types Proposal"

From MusicBrainz Wiki
Jump to navigationJump to search
m (→‎Prefer Specific Relationship Types: Change header of generic types list)
(Added examples, refined guideline, added headings)
Line 15: Line 15:
 
==Prefer Specific Relationship Types==
 
==Prefer Specific Relationship Types==
   
You should make a best effort to make the relationship type as specific as possible. This means that you should avoid any of the generic types, if:
+
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
 
* The liner or another source specifies which of the subtypes apply, or
 
* You can easily deduce which of the subtypes apply.
 
* You can easily deduce which of the subtypes apply.
   
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 - 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.
+
In these cases you should use the specific relationship types, and omit a relationship of the generic type. If the liner provides no information on which of the subtypes apply, you should do a quick search for sources that provide more specific information.
   
  +
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.
  +
  +
===Generic Types===
 
The following relationship types are considered 'generic types':
 
The following relationship types are considered 'generic types':
 
* [[Arranger_Relationship_Type|Arranger]]
 
* [[Arranger_Relationship_Type|Arranger]]
Line 28: Line 31:
 
* [[Proposal:Writer_Relationship_Type|Writer]] (proposed)
 
* [[Proposal:Writer_Relationship_Type|Writer]] (proposed)
   
Examples (todo):
+
===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 is created.
* (example liner): liner explains Engineer role
 
  +
* [[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, Imogen is credited using a [[Composer_Relationship_Type|Composer]] relationship.
* (deduce): writer on instrumental track
 
  +
* [[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 is used. Once more information becomes available, these can be replaced by Composer and/or [[Lyricist Relationship Type|Lyricist]] relationships.
* (unclear): controversial writer
 

Revision as of 17:49, 17 November 2010


Status: This page describes an active proposal and is not official.



Proposal number: RFC-Unassigned
Champion: Jeroen
Current status: Unknown



This proposal adds the following section to Advanced Relationship Style.

Prefer Specific Relationship Types

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.

In these cases you should use the specific relationship types, and omit a relationship of the generic type. If the liner provides no information on which of the subtypes apply, you should do a quick search for sources that provide more specific information.

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.

Generic Types

The following relationship types are considered 'generic types':

Examples