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

From MusicBrainz Wiki
m (Examples: Linkify "Writer" AR)
m (Generic Types: Linkify RFC-251)
Line 25: Line 25:
 
* [[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]], [[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.
 
* [[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.
* [[Engineer_Relationship_Type|Engineer]] (after RFC-251 is implemented): prefer selecting the correct information from the Engineer tree.
+
* [[Engineer_Relationship_Type|Engineer]] (after [[Talk:Proposals#RFC-251:_Change_how_we_handle_Engineers_and_their_roles|RFC-251]] is implemented): prefer selecting the correct information from the Engineer tree.
* [[Engineer_Position_Relationship_Type|Engineer Position]] (after RFC-251 is implemented): prefer selecting the correct information from the Engineer tree.
+
* [[Engineer_Position_Relationship_Type|Engineer Position]] (after [[Talk:Proposals#RFC-251:_Change_how_we_handle_Engineers_and_their_roles|RFC-251]] is implemented): prefer selecting the correct information from the Engineer tree.
 
* [[Performer_Relationship_Type|Performer]]: prefer adding instruments, orchestra and/or vocal types
 
* [[Performer_Relationship_Type|Performer]]: prefer adding instruments, orchestra 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 19:45, 17 December 2010


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



Proposal number: RFC-295
Champion: Jeroen
Current status: RFV
Initial Discussion [2010-11-17 RFC] [2010-12-17 RFV]


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

Here is a list of "generic types" and examples of preferred specific types:

Examples