Development/Seeding/Release Editor: Difference between revisions
From MusicBrainz Wiki
< Development | Seeding
Jump to navigationJump to search
mNo edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
Releases may be associated with multiple labels and catalog numbers, so the fields for specifying these is a little different. You must specify a positive integer for the ''n'' part of the field name to specify which label/catalog number pair you are referring to. For example: label.0.mbid and label.0.catalog_number |
Releases may be associated with multiple labels and catalog numbers, so the fields for specifying these is a little different. You must specify a positive integer for the ''n'' part of the field name to specify which label/catalog number pair you are referring to. For example: label.0.mbid and label.0.catalog_number |
||
; |
; labels.''n''.mbid |
||
: The MBID of the label. |
: The MBID of the label. |
||
; |
; labels.''n''.catalog_number |
||
: The catalog number of this release, for label ''n''. |
: The catalog number of this release, for label ''n''. |
||
Revision as of 13:54, 13 December 2010
This page documents a lit of parameters you can post the release editor to "seed" it. All values are optional unless otherwise stated.
Release data
- name
- The name of the release. Non-empty string. Required
- comment
- A disambiguation comment for the release. Non-empty string
- annotation
- Text to place in the releases annotation
- barcode
- The barcode of the release. May be any valid barcode without whitespace
- date.year
- date.month
- date.day
- The date of the release. Each field is an integer
- country
- The country the release was released in. May be any valid country ISO code (for example, GB, US, FR)
- language
- The language of the release. May be any valid ISO 639-2/T code (for example, eng, deu, jpn)
- script
- The script of the text on the release. May be any valid ISO 15924 code (for example, Latn, Cyrl)
- status
- The status of the release, as defined by MusicBrainz. Possible values: official, promotion, bootleg, pseudo
- type
- The type of the release group, if a release group will be created. Possible values: album, single, ep, compilation, soundtrack, spokenword, interview, audiobook, live, remix, other
- packaging
- The type of packaging of the release. Possible values: jewel-case, slim-jewel-case, digipak, paper-sleeve, other
Labels and catalog numbers
Releases may be associated with multiple labels and catalog numbers, so the fields for specifying these is a little different. You must specify a positive integer for the n part of the field name to specify which label/catalog number pair you are referring to. For example: label.0.mbid and label.0.catalog_number
- labels.n.mbid
- The MBID of the label.
- labels.n.catalog_number
- The catalog number of this release, for label n.
Tracklists and Mediums
As with labels above, their may be multiple mediums and tracklists may contain multiple tracks, so again you will need to fill in the n and m parameters accordingly.
- medium.n.format
- Any valid medium format name: may be any one of auto generate me
- medium.n.position
- The position of this medium in the list of mediums. If omitted, it will be inferred from the order of all mediums passed in (which is normally what you want).
- medium.n.name
- The name of medium n (for example "Live & Unreleased")
- medium.n.track.m.name
- The name of track n on medium m
- medium.n.track.m.duration
- The duration of track n on medium m in
MM:SS
form. You may also pass a single integer, which will be interpreted as seconds (milliseconds?)