Development/Seeding: Difference between revisions
m (it's unbelievable how bad this editor is. like, it displays external links as working but then seems to insert bogus code. why can't everyone just use markdown now?) |
Reosarevok (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
== Add Release == |
== Add Release == |
||
[[ |
You can seed a new release with a POST request. See [[/Release Editor|the release editor seeding documentation]] for details. |
||
== Other pages (Add Artist, Add Label, Add Standalone Recording, etc.) == |
== Other pages (Add Artist, Add Label, Add Standalone Recording, etc.) == |
||
Revision as of 08:36, 17 July 2023
Forms for creating new MusicBrainz entities can be “seeded” with values supplied via POST-ed multipart/form-data body parameters (for the Add Release page) or URL query parameters (for most other pages). Third-party tools that use seeding to make it easier to import data into MusicBrainz are listed at External Resources.
Add Release
You can seed a new release with a POST request. See the release editor seeding documentation for details.
Other pages (Add Artist, Add Label, Add Standalone Recording, etc.)
Non-release forms are seeded via URL query parameters sent via GET requests. The following pages support seeding:
In almost all cases, a form input can be seeded by passing a parameter corresponding to input's name attribute. For example, the Add Artist page's "Name" field is defined in the page source as <input ... name="edit-artist.name" ...>, and a URL like https://musicbrainz.org/artist/create?edit-artist.name=My+Name will initialize the field to the text "My Name".
