Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • 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
  • This page documents a list of URL query parameters you include in a GET request to the artist editor to � * '''Type''' (<code>edit-artist.type_id</code>) corresponds to the <code>artist_type<
    3 KB (419 words) - 14:06, 22 July 2023
  • ...ology]], the release title is the entire text string representing the name of a [[Release]]. It is stored in the release title field. ...parts of ReleaseTitle<code><nowiki></nowiki></code>s and (b) the ordering of these parts.
    5 KB (804 words) - 11:51, 26 May 2015
  • {{Status|Semi-official, but in desperate need of cleanup before it can be truly official.}} ** [[Release Group/Type|Release Group type]]
    7 KB (1,114 words) - 12:10, 8 September 2023
  • This page provides a summary of the important guidelines, please follow the links to the full guidelines wh ...s is usually the choice of a graphic designer, not the artist. So, instead of copying the title from the cover, we follow certain rules to capitalize a t
    8 KB (1,320 words) - 12:49, 30 April 2024
  • ...icates that a creator was the person responsible for designing some aspect of an edition." {edition} is an edition of {work} - {work} has edition {edition}
    13 KB (1,864 words) - 07:39, 25 March 2024
  • This guideline covers release groups of type “Soundtrack”, and the releases, recordings, and works associated with t The title should be just the basic name of the track.
    6 KB (972 words) - 15:45, 16 August 2018
  • | <!-- Affects --> Naming of track titles | <!-- Affects --> Rewrites all of CSG
    67 KB (8,499 words) - 16:06, 29 August 2016
  • This guideline covers release groups of type “Soundtrack”, and the releases, recordings, and works associated with t The title should be just the basic name of the track.
    6 KB (1,022 words) - 12:50, 8 September 2023
  • Examples of releases that are hard to categorise: <ul><li style="list-style-type:none">''Unclear what's so difficult about [[release:d1e417e3-6641-44bf-8a27
    16 KB (2,546 words) - 15:00, 4 May 2014
  • ...ted, searched for, referred to by MBID, and linked to each other through [[Relationship|relationships]] or foreign key constraints in some case. ...entity type has a main table sometimes accompanied by complementary tables of which a few are unique but most are common.
    21 KB (3,347 words) - 18:44, 21 July 2023
  • ...is an interface to the [[MusicBrainz Database]]. It is aimed at developers of media players, CD rippers, taggers, and other applications requiring music ...r User-Agent string in its HTTP request headers. For more details on both of these requirements, please see our [[MusicBrainz API/Rate_Limiting|rate lim
    27 KB (4,241 words) - 16:12, 27 February 2024
  • ...l will be used similarly to the Label objects used in the "release" fields of a release. Enter below a list of features such an object will need.
    25 KB (4,218 words) - 18:49, 27 August 2016
  • ...some fields omitted to keep the examples shorter (additional aliases, part of the release data); in the actual response the data will obviously be includ <area id="45f07934-675a-46d6-a577-6f8637a411b1" type="City" type-id="6fd8f29a-3d0a-32fc-980d-ea697b69da78">
    78 KB (8,119 words) - 20:20, 5 January 2021