Search results

This proposal has now passed, see [[Advanced Relationship Style]], however, two lines depend on other changes, those have been left h ...neric Engineer type should be used, and '''not''' one of the more specific Engineer types.

| '''German''' || '''MusicBrainz relationship''' ...composed ([[rt:d59d99ea-23d4-4a80-b066-edca32ee158f|Composer Relationship Type]])

...aned up], to form the current Engineer Relationship Class, and its various Relationship Types. I propose changing 'Recording Engineer' to 'Recorded By' - this is the most common phrasing of this role, and is a

Status: This entity type was considered for NGS inclusion, but was dropped from the final NGS schema A master is a prototype of a release that depends on the [[Medium Type|MediumType]] of the release. The master itself is not released and not acce

...performer, lyricist, band/choir/orchestra, bandmember, designer, producer, engineer, remixer, … } ** [[Artist/Type|Artist type]] — ?

...e="background:red" | The NGS migration scripts either don't handle this AR type or do something different ! AR Type

...r down to one stereo audio track. More precisely he mixes freshly recorded audio streams together, that were never mixed together before. ...ever). For sake of clarity I define that a compiler ''does not change the audio material''. He just takes tracks and puts them in a sequence. Period. This

...the performing artist, either of whom should then also be given a co-audio engineer credit. ...rtmaster or concertmistress is always also a [[Member Of Band Relationship Type|member of the group]].

...the performing artist, either of whom should then also be given a co-audio engineer credit. ...rtmaster or concertmistress is always also a [[Member Of Band Relationship Type|member of the group]], unless the guest attribute is used.

** [[Release Group/Type|Release Group type]] ** [[Label/Type|Label type]]

For assistance in determining the correct relationship types to use when describing compiling, DJ mixing, mastering, mixing, remas Often a relationship could be added at multiple levels. For example, the liner notes on a releas

...statistics of how many of which type are defined. ([[Advanced Relationship Type|AdvancedRelationshipType]] does have a list, shorter and more aggregated th | album || artist || 20 || was {additional:additionally} audio engineered by || 49

...nships]]. It explains quite well how AR works. The [[Advanced Relationship Type|AdvancedRelationshipType]]s in this text are however outdated proposals. ...torm about missing relationships that we should keep track of in MB. These relationship types as well as the relationships themselves should be user moderatable.

| <h4 style='display: none'>RFC-204: Decommission Don't Make Relationship Clusters</h4> ...& Wikipage --> [[Don't_Make_Relationship_Clusters|Decommission Don't Make Relationship Clusters]]

<ul><li style="list-style-type:none">''Update: Since this page is getting too long to edit, we are moving ...ionship. If you want to see the real mess, I propose you read [[Don't Make Relationship Clusters|DontMakeRelationshipClusters]] (and perhaps also [[Linking Differe

...ted, searched for, referred to by MBID, and linked to each other through [[Relationship|relationships]] or foreign key constraints in some case. Each primary entity type has a main table sometimes accompanied by complementary tables of which a f

| <h4 style='display: none'>RFC-295: Prefer specific relationship types</h4> ...Wikipage --> [[Proposal:Prefer_Specific_Relationship_Types|Prefer specific relationship types]]