Re: [mb-style] Composition/Performer/Production ARs at Release or Track level? - PROPOSAL

[Barry Platt]

Hi -

This is more-or-less the conclusion I was coming to as there's clear
benefit to allowing some kind of "fuzzy" release-level ARs.  Indeed,
this is really why I started this thread as I saw major problems with
the two incompatible approaches that were being used in the DB.

An approach I'd considered suggesting was to add a "fuzzy" boolean on
release-level ARs which could be used to indicate that they shouldn't be
propagated, but that probably complicates the data model with
insufficient benefit.

Brian's suggested approach of considering release-level ARs fuzzy by
default would seem to be the best one, but obviously (as discussed
extensively in IRC) this does mean that many release-level ARs *that
were entered on the understanding that they would be propagated down*
now won't.

There may be some value to implementing a helper UI that allows existing
release-level ARs to be reassigned down to all the tracks, possibly with
some new reports to facilitate identification of such ARs (for example
search for Add Artist-Release AR edits by editor).  Neither of those
things should get in the way of clarifying what we conclude to be the
*correct* way that ARs should be used however.

Regards,
Barry