Right now, when a program submits multiple barcodes via the webservice, they are grouped into a single edit. It was decided in MBS-803 to group them into a single edit, but no reasoning was given, as far as I can tell. I think it would be better to submit each barcode as a separate edit.

The reason is basically because these are completely independent changes affecting completely separate releases. It's unlikely that anyone will know all the releases involved to be confident in voting yes. And when some of the data is wrong, there's no way to accept only the correct parts.

For example, the edits this year which submitted multiple barcodes were:

• https://musicbrainz.org/edit/21074889 - no voted
• https://musicbrainz.org/edit/21016088 - failed
• https://musicbrainz.org/edit/20746953 - failed
• https://musicbrainz.org/edit/20716355 - no voted and then cancelled
• https://musicbrainz.org/edit/20487605 - failed
• https://musicbrainz.org/edit/20485354 - failed

While this isn't a large number of edits, it does suggest to me that grouping them is not the right approach.