Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • This is a proposal to add a "sub-" attribute to the [[Publisher Relationship Type]]. ...have a locale selection drop-down menu like [[Alias|Aliases]] have, since sub-publishers typically only have rights to entities in select countries or re
    1 KB (190 words) - 21:20, 3 May 2014
  • ..., you should add a "Sub Optimal Credits" section to the annotation for the entity. ...inz allows, and indicate what that relationship exactly represents in the "Sub Optimal Credits" section. If it is not possible, leave it uncredited (but r
    2 KB (250 words) - 12:28, 24 September 2018
  • * An album consisting of two discs is stored as two separate [[Album Entity|AlbumEntities]] in the db. But I don't want to store the release date twice ...tity|SubEntity]] (the [[Sub Entity|SubEntity]] inherits data of its [[Main Entity|MainEntity]] only in the display - therefore DisplayInheritance).
    9 KB (1,481 words) - 17:16, 28 August 2016
  • ...rently allows to enter: some tips for entering this data can be found in [[Sub Optimal Credits]]. * Miscellaneous editing warnings or information: for example if the entity name presents some specific spelling and/or capitalization difficulty, or w
    3 KB (565 words) - 19:14, 23 May 2015
  • ...rm or another. The initial text on this page all migrated from [[Advanced Entity]]. See [[Advanced Entity]] for older proposals, and [[Data Elements For Advanced Relationships|DataE
    4 KB (668 words) - 22:03, 27 August 2016
  • == Entity Types == : Release groups are an abstract "album" entity. Technically it's a group of releases, with a specified type.
    4 KB (566 words) - 14:55, 29 December 2023
  • == Entity Types == : Release groups are an abstract "album" entity. Technically it's a group of releases, with a specified type.
    4 KB (549 words) - 11:58, 3 December 2018
  • {{note}} Do not split a musical entity into smaller pieces based on track splits, tempo markings, lyrics or other Occasionally different editions of the same work have different number of sub-parts. Examples include some piano sonatas by Beethoven; one edition has tw
    7 KB (1,145 words) - 10:10, 10 August 2013
  • {{note}} Do not split a musical entity into smaller pieces based on track splits, tempo markings, lyrics or other In unnumbered operas (Wagner, for instance), sometimes an act is the smallest entity you can enter. See "excerpts" below for how to deal with popular arias and
    7 KB (1,138 words) - 14:21, 23 April 2018
  • One [[Release Entity|ReleaseEntity]] can have multiple Release Data Sets. One Release Data Set s ** [[Label Entity|LabelEntity]] ID (Label/Distributor reference)
    6 KB (994 words) - 19:14, 28 August 2016
  • Each Location should be an entity. Locations should have a “parent” field – but not be relate-able to o ...ted to other genres - “<genre1> is a sub-genre of <genre2>”, “<genre2> has sub-genre <genre1>”, (“<genre1> inspired <genre2>”? - sideways link).
    13 KB (2,105 words) - 21:07, 2 September 2013
  • ...ing it easy to use. The first is achieved by splitting albums into several entity types which can be re-used and combined/linked. The latter is the challenge ==Entity Types==
    16 KB (2,643 words) - 19:19, 28 August 2016
  • ...d (p), manufacturing, etc.). This is also the only way a meaningful parent/sub-label hierarchy can be established. * Only show "core" edits to an entity in its editing history; for instance, *no* recording edits in a release his
    3 KB (435 words) - 20:26, 16 April 2013
  • :Aliases are name variants associated with a given [[#entity|entity]]. Their main use has been to improve search results (e.g. a search for "Py ...ed to store information that doesn't fit elsewhere in MusicBrainz. Most [[#Entity|entities]] have an annotation field.
    17 KB (2,550 words) - 01:57, 29 February 2016
  • *#*2 levels: “main genre”, “sub genre(s)” *Ben’s “genre entity” proposal
    10 KB (1,588 words) - 19:19, 1 June 2014
  • ...recording is this song’s a recording session’s take, and we have some new sub sets of masters, cuts and mixes, as well as a DON’TKNOWWHICH catch-all sp ...milar master level to nikki's proposal, and the addition of a higher level entity to group alternate versions, possibly with AR movement to reduce redundant
    11 KB (1,820 words) - 23:49, 10 January 2013
  • We have 13 resources on our API which represent core [[Entity|entities]] in our database: On each entity resource, you can perform three different GET requests:
    27 KB (4,241 words) - 16:12, 27 February 2024
  • ...lso to albums and artists (see [[Album Rework|AlbumRework]] and [[Advanced Entity|AdvancedEntity]]). This group functioning as a representative can be used a ...mixing''' and '''mastering'''<ref>Note that in Shepard's original text the entity which is now called "master" was called "track".</ref>.
    22 KB (3,637 words) - 16:59, 28 August 2016
  • ...ertos which are a complete sub-works of the 4 seasons, which is a complete sub-work of the larger publication) ...y we'd want to do it? One group is a sub-category of singles, the other a sub-category of albums... -- [[Brian Schweitzer|BrianSchweitzer]] 23:24, 20 Jun
    34 KB (5,944 words) - 19:16, 28 August 2016
  • Jazz has its slang, and its own corpus of formal and informal concepts, sub-genres and styles denominations, etc... This page is a modest attempt at li ...ions. To some extent, it's also the end of '''jazz''' as a somewhat unique entity (both from a sociological and musical point of vue). Consequently, the comm
    19 KB (3,212 words) - 17:10, 13 December 2016