In 9 months, it has proven to be useful for updating external links at least.

Documented the project at https://musicbrainz.org/doc/MusicBrainz_Batch_Edits

Renamed the ticket after the final project name “MusicBrainz Batch Edits” (MBBE) instead of initially suggested “MusicBrainz Data Quality” (MBDQ).

Jira project created!

“Data Quality” was a bit too broad as it also included issues that can be addressed directly in MusicBrainz Server or through manual edits. Named it “Batch Edits” instead which is more restrictive but more clear too (by me, reo, and Freso at least).

Check out “MusicBrainz Batch Edits” (MBBE):

• Issues (tasks & sub-tasks only)
• Workflow (simply “To Do” → “In Progress” → “Done”)
• Components hierarchy (mapping MusicBrainz data types)

In review for now, still open to feedback and changes.

The general idea has just been accepted by the weekly meeting.

The main idea is to track mass-editing tasks that would help with fixing MusicBrainz data after changes in MBS code or STYLE guidelines.
These tasks are currently not tracked properly but rather mentioned as comments to MBS/STYLE tickets, in forums, on IRC…
These are one-off tasks to be done by running a bot, even though that might take months to complete.