[mb-style] RFC: Allow multiple ISWC codes per musicbrainz Work

Nikki aeizyx at gmail.com
Fri Jul 29 21:10:49 UTC 2011


Aurélien Mino wrote:
> So my prerequisites to this proposal are:
> - adding a second ISWC should be strongly discouraged in the user 
> interface (including when you're going to merge works with different ISWCs)
> - have a way to easily split a work (like what is proposed here: 
> http://tickets.musicbrainz.org/browse/MBS-2095)

I've made a couple of tickets for those points:
* http://tickets.musicbrainz.org/browse/MBS-3116 (Warn when merging 
works with different ISWCs)
* http://tickets.musicbrainz.org/browse/MBS-3117 (Add a "split" option 
for works)
We can make these dependencies of 
http://tickets.musicbrainz.org/browse/MBS-2885 (Allow more than one ISWC 
per work)

Do you (or anyone else) have any ideas about how we can discourage 
adding multiple ISWCs?
I would probably suggest a button (similar to adding a second label in 
the release editor). When you click it, it would add another field, but 
also show a warning and a confirmation box asking the person to confirm 
that these are really for the same work. If it's possible we could also 
make adding a second ISWC always require voting.

Nikki



More information about the MusicBrainz-style mailing list