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

From MusicBrainz Wiki
Jump to navigationJump to search
(Added list of subtypes)
(Incorporated comments from style list)
Line 19: Line 19:
 
* 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 the liner provides no information on which of the subtypes apply, you should do a quick search for sources that provide more specific information.
+
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.
 
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===
 
===Generic Types===
 
The following relationship types are considered 'generic types':
 
The following relationship types are considered 'generic types':
 
* [[Arranger_Relationship_Type|Arranger]]: prefer [[Instrumentator_Relationship_Type|Instrumentator]] and/or [[Orchestrator_Relationship_Type|Orchestrator]]
 
* [[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]] and/or [[Sound_Engineer_Relationship_Type|Sound Engineer]]
+
* [[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]] and/or [[Sound_Engineer_Relationship_Type|Sound Engineer]] /
  +
* [[Engineer_Relationship_Type|Engineer]] (after RFC-251 is implemented): prefer selecting the correct information from the Engineer tree.
* [[Engineer_Position_Relationship_Type|Engineer Position]]
 
  +
* [[Engineer_Position_Relationship_Type|Engineer Position]] (after RFC-251 is implemented): prefer selecting the correct information from the Engineer tree.
 
* [[Performer_Relationship_Type|Performer]]: prefer adding instruments and/or vocal types
 
* [[Performer_Relationship_Type|Performer]]: prefer adding instruments and/or vocal types
 
* [[Proposal:Writer_Relationship_Type|Writer]] (proposed): prefer [[Composer_Relationship_Type|Composer]], [[Lyricist_Relationship_Type|Lyricist]] and/or [[Librettist_Relationship_Type|Librettist]]
 
* [[Proposal:Writer_Relationship_Type|Writer]] (proposed): prefer [[Composer_Relationship_Type|Composer]], [[Lyricist_Relationship_Type|Lyricist]] and/or [[Librettist_Relationship_Type|Librettist]]

Revision as of 14:29, 20 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. It also adds a reference to this section to each of the relationship types mentioned below.

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 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