History:Prefer Specific Relationship Types Proposal: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (→‎Examples: Linkify "Writer" AR)
m (CallerNo6 moved page Proposal:Prefer Specific Relationship Types to History:Prefer Specific Relationship Types Proposal: https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3675767/)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This proposal has now passed, see [[Advanced Relationship Style]], however, two lines depend on other changes, those have been left here until the relevant changes happen.
{{Template:proposal
|proposal=295
|discussion=http://lists.musicbrainz.org/pipermail/musicbrainz-style/2010-November/010413.html
|champion=Jeroen
|rfc=2010-11-17
|rfv=2010-12-17
|status=RFV
|ar=
|style=Advanced_Relationship_Style
|trac=
}}


==RFC-251==
This proposal adds the following section to [[Advanced_Relationship_Style|Advanced Relationship Style]]. It also adds a reference to this section to each of the relationship types mentioned below.
When [[Talk:Proposals#RFC-251:_Change_how_we_handle_Engineers_and_their_roles|RFC-251]] is implemented, change:
⚫
* [[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.


to
==Prefer Specific Relationship Types==


⚫
* [[Engineer_Relationship_Type|Engineer]]: prefer selecting the correct information from the Engineer tree.
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:
⚫
* [[Engineer_Position_Relationship_Type|Engineer Position]]: prefer selecting the correct information from the Engineer tree.
* 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:
* [[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]] (after 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.
* [[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]]



===Examples===
and on [[Engineer_Relationship_Type]], change:
* [[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.
* In many cases, the [[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]] relationship types should be used instead. If the Engineer relationship type is either Balance Engineer or Tonmeister, the generic Engineer relationship type should be used, and not one of the more specific Engineer relationship types. For details, see the [[Advanced_Relationship_Style#Prefer_Specific_Relationship_Types|Prefer Specific Relationship Types]] guideline.
* [[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 is used. Once more information becomes available, these can be replaced by Composer and/or [[Lyricist Relationship Type|Lyricist]] relationships.
to

* Be as specific as possible and specify the type of engineering that was performed, but only if you have a source or if you can deduce this information. For details, see the [[Advanced_Relationship_Style#Prefer_Specific_Relationship_Types|Prefer Specific Relationship Types]] guideline.



and to [[Engineer_Position_Relationship_Type]], add:

* Be as specific as possible and specify the type of engineering position that was held, but only if you have a source or if you can deduce this information. For details, see the [[Advanced_Relationship_Style#Prefer_Specific_Relationship_Types|Prefer Specific Relationship Types]] guideline.

Latest revision as of 20:33, 28 August 2016

This proposal has now passed, see Advanced Relationship Style, however, two lines depend on other changes, those have been left here until the relevant changes happen.

RFC-251

When RFC-251 is implemented, change:

to

  • Engineer: prefer selecting the correct information from the Engineer tree.
  • Engineer Position: prefer selecting the correct information from the Engineer tree.



and on Engineer_Relationship_Type, change:

to

  • Be as specific as possible and specify the type of engineering that was performed, but only if you have a source or if you can deduce this information. For details, see the Prefer Specific Relationship Types guideline.


and to Engineer_Position_Relationship_Type, add:

  • Be as specific as possible and specify the type of engineering position that was held, but only if you have a source or if you can deduce this information. For details, see the Prefer Specific Relationship Types guideline.
Retrieved from "https://wiki.musicbrainz.org/index.php?title=History:Prefer_Specific_Relationship_Types_Proposal&oldid=70928"