Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • ...'artist'' ([[rt:d59d99ea-23d4-4a80-b066-edca32ee158f|Composer Relationship Type]]) ...shipType]]) or was orchestrated by ''artist'' ([[Orchestrator Relationship Type| OrchestratorRelationshipType]])
    9 KB (1,016 words) - 23:19, 30 April 2014
  • ...99d47-23a7-4c28-bfcf-0607a562b644|transliteration/translation relationship type]]. As such, they shouldn't duplicate all the information already available ...releases for a pseudo-release currently exist in MusicBrainz (because the editor adding the pseudo-release wasn't able to add a release in the original lang
    1 KB (185 words) - 17:23, 5 October 2020
  • ...ptions (or the equivalent of these) would be presented to the Relationship Editor: ...which is defined to use the description field would now, when ARs of that type are displayed, display the description text as the link text, rather than t
    7 KB (1,134 words) - 15:11, 12 March 2010
  • ...: see [[rt:a3005666-a872-32c3-ad06-98af558e99b0|the documentation for that relationship]] to find more info on when each of the attributes should be used. When lin ...lease to works [[How to Use the Relationship Editor|using the relationship editor]], or do it from the recording page with [[How_to_Add_Relationships#The_.22
    5 KB (893 words) - 09:57, 17 August 2022
  • ...: see [[rt:a3005666-a872-32c3-ad06-98af558e99b0|the documentation for that relationship]] to find more info on when each of the attributes should be used. When lin ...lease to works [[How to Use the Relationship Editor|using the relationship editor]], or do it from the recording page with [[How_to_Add_Relationships#The_.22
    5 KB (793 words) - 00:12, 11 January 2017
  • For relationships, such as [[Sibling Relationship Type|SiblingRelationshipType]], which are transitive, it would be nifty if the s ...to be done once. Essentially, it all boils down to this question: Why are relationship clusters, if done correctly the first time, a bad thing? -- [[Brian Schweit
    4 KB (625 words) - 20:14, 16 May 2011
  • ...rited (except [[rt:ca8d3642-ce5f-49f8-91f2-125d72524e6a|Parts Relationship Type]], that would be too recursive). # Adding a new page [[Work/Relationship Inheritance in Works Trees]], with the text on the main page
    14 KB (2,115 words) - 22:27, 28 August 2016
  • <ul><li style="list-style-type:none">[[Image:Attention.png]] '''Status: In limbo for 14 months now (2005-0 <ul><li style="list-style-type:none">'' 2005-8-22: open [[User:Keschte|Keschte]]''
    10 KB (1,491 words) - 19:58, 25 October 2011
  • This page documents a list of parameters you can POST to the release editor to “seed” it. All values are optional unless otherwise stated. ...a new release group which will have the name of the release by listing its type(s)
    8 KB (1,257 words) - 10:20, 5 October 2023
  • ..., but lower level entities should generally only be related to one of each type of higher level entity. ...quently than for recordings, due to the more objective nature of a mix. An editor must make an edit to associate a track with a mix, and this edit is subject
    6 KB (1,060 words) - 14:51, 9 January 2013
  • 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
    7 KB (1,190 words) - 08:02, 3 June 2022
  • ...y'' | '''Jim DeLaHunt''' [ MB: [http://musicbrainz.org/user/Jim%20DeLaHunt Editor:Jim DeLaHunt] | IRC: ''none yet'' | Wiki: JimDeLaHunt | Last.fm: ''none yet ...roposal: ''[[Proposal:Work/Relationship Inheritance in Works Trees|RFC-339 Relationship Inheritance in Works Trees]]'' (2011/October)
    10 KB (1,515 words) - 19:18, 10 March 2016
  • and a recording-to-recording relationship (which currently has to be added in the recording's which is related to the original work by a "based on" type, with the appropriate credits.
    4 KB (552 words) - 18:28, 28 May 2013
  • MusicBrainz::Server::Data::Relationship->_load 0.25070 MusicBrainz::Server::Data::Editor->_get_by_keys_append_sql 0.15582
    23 KB (2,883 words) - 01:17, 17 September 2012
  • [http://tickets.musicbrainz.org/browse/MBS-2234 MBS-2234: New edit type to split recordings] is not necessarily high-level, since it's just a tool, ...with a specific sound) and the "mixists" (who want to make full use of the relationship-sharing option recordings provide by grouping all versions of the same trac
    4 KB (620 words) - 16:34, 10 December 2012
  • I'm [[editor:azertus|azertus]] and a proud citizen of [http://www.gent.be Ghent] in [htt Wording on merge releases pages doesn't reflect the type of merge (append or complete merge) being performed. --11:08, 7 June 2011 (
    4 KB (548 words) - 14:57, 4 May 2014
  • | <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]]
    67 KB (8,499 words) - 16:06, 29 August 2016
  • <ul><li style="list-style-type:none">-- [[Brian Schweitzer|BrianSchweitzer]] 05:52, 17 June 2007 (UTC) <ul><li style="list-style-type:none">-- [[Brian Schweitzer|BrianSchweitzer]] 05:55, 17 June 2007 (UTC)
    8 KB (1,300 words) - 07:57, 15 March 2009
  • ...that data is already available to React components that render artist/work Relationship tabs, === Push the URL relationship editor to the next level ===
    17 KB (2,649 words) - 18:59, 16 March 2021
  • ...brainz.org/ws/1/tag/?id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11&entity=artist&type=xml&tags=waga,poly,klepto] ...have applied previously. This will require an HTTP authorization with your editor name and password. This can be done via the command line and the wget progr
    10 KB (1,401 words) - 07:54, 23 May 2015
View ( | ) (20 | 50 | 100 | 250 | 500)