Difference between revisions of "Editing Tools"

From MusicBrainz Wiki
m (I'm picky about case correctness, and it's my repository, sooooooo)
(For adding releases: soft redirect to External Resources)
Line 5: Line 5:
 
===Userscripts===
 
===Userscripts===
  
* [http://userscripts.org/scripts/show/36376 Discogs]
+
see: [[External_Resources#User_scripts_.2F_GreaseMonkey_.2F_User_javascripts_.2F_UserJS|Exterenal Resources / User scripts]]
 
 
* [http://userscripts.org/scripts/show/117718 Bandcamp]
 
 
 
* [http://userscripts.org/scripts/show/119410 iTunes]
 
  
 
Userscripts generally only work under [http://getfirefox.com Firefox] with the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey] extension. Google Chrome support can be very hit-or-miss, Opera compatibility is very sparse. Script compatibility under [http://google.com/chrome Google Chrome] is greatly increased when using the [http://www.chromeextensions.org/appearance-functioning/tampermonkey/ TamperMonkey] extension.
 
Userscripts generally only work under [http://getfirefox.com Firefox] with the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey] extension. Google Chrome support can be very hit-or-miss, Opera compatibility is very sparse. Script compatibility under [http://google.com/chrome Google Chrome] is greatly increased when using the [http://www.chromeextensions.org/appearance-functioning/tampermonkey/ TamperMonkey] extension.

Revision as of 22:27, 22 February 2017

There are many talented developers in the MusicBrainz community, and as a result, there are lots of ways to make the task of editing and expanding MusicBrainz data simpler and faster.

For adding releases

Userscripts

see: Exterenal Resources / User scripts

Userscripts generally only work under Firefox with the Greasemonkey extension. Google Chrome support can be very hit-or-miss, Opera compatibility is very sparse. Script compatibility under Google Chrome is greatly increased when using the TamperMonkey extension.

Parsers

Bandcamp, Beatport, and Local File Parsers (with great assistance comes great responsibility)

These parsers are meant to be run at the command line passing in either a URL (Bandcamp release, or Beatport release), or a directory with a set of files. The local file parsers run on all files in a directory with the same extension, and are intended to output a whole release, suitable for copying / pasting into the tracklist page's Track Parser. They are written in Perl, require at least Perl v5.10 and a differing set of Perl Modules based off the particular service. The local file parsers are currently format specific.