The model has a musicbrainz_id and a second_musicbrainz_id -- to support the use case when there are two different Works that are really for our purposes the same song. This works well, but in a few cases there are multiple MusicBrainz works, not just 2.
Extend the model to support multiple MusicBrainz works. One of them should be the default (used to identify the MusicBrainz page for lookups from the client etc.) but they all should add to the same song.
In the Song Detail View, if there are multiple MusicBrainz works linked, the default should go to the "primary", but there should be an affordance to see all of them
The model has a musicbrainz_id and a second_musicbrainz_id -- to support the use case when there are two different Works that are really for our purposes the same song. This works well, but in a few cases there are multiple MusicBrainz works, not just 2.
Extend the model to support multiple MusicBrainz works. One of them should be the default (used to identify the MusicBrainz page for lookups from the client etc.) but they all should add to the same song.
In the Song Detail View, if there are multiple MusicBrainz works linked, the default should go to the "primary", but there should be an affordance to see all of them