Also, looking at how to resolve MBS-1228, I started to think about "dynamic lists" which would depend on the parent entity. For example for areas, I'd really like to have all artists that have area set to Slovakia (or one of its sub-areas) in one collection, so the list wouldn't be static, but it would update every time someone adds or removes Slovakia (or its sub-area) from one of the artists.

Recently, I've been editing (pretty much all) of the releases from an electronic music label called "Monstercat" and I'd like to be able to do similar thing with labels. If you add a label to one of your collection lists and set (let's say "also work with sub-entities"), it would behave as if you've added all of its (currently 350+) releases to your collection, so the notifications wouldn't only cover edits to the label and catalog number edits, but also any edit done to the releases associated with the label. And same as with the area suggestion, the collection would update every time someone adds or removes the label from any of the releases.

Adding these artists/releases manually is definitely not feasible in the long run and this "inheritance of sub-entities" could be extended to more stuff like works (not sure if you get notification edits for all recordings associated with a work).

How come I haven't found this ticket sooner?! I would really love if we could replace subscriptions with collections. I would also love if there were per-collection notification settings, so you wouldn't need to risk flooding your inbox if you want to be more engaged with your favorite entities. I created a quick mockup for the settings. It could use better wording, but it should be understandable that I wanted to let people choose which e-mails they would receive, which edits they would see after clicking on "My Data/Edits for Subscribed Entities" and which entities would be displayed after clicking on "Editing/Reports". Here is the mockup: http://i.imgur.com/cc1lApy.png.

Regarding editor subscriptions, I see them as a different thing. Editors are also quite different from core entities, so hypothetical editor collections would need quite a bit of special treatment. I linked MBS-3237 mostly for completeness.

I'm all for this, as you might expect given that I mentioned it when making MBS-8004.

For the subscribe me preference, I don't think implementing this would depend on an option. We would need to migrate the existing subscriptions to something, so I imagine we'd be creating something like "My subscribed artists" anyway, and we would want it to just work for new users without requiring that they first set up a set of collections. That's not to say it wouldn't be nice for people to be able to change it, I just don't think it's a necessity.

I think it would partially resolve MBS-1228. The main issue seems to be that not all edits which directly link an entity to an area actually get linked to the area's edit history, e.g. add relationship does, but not add release, add label or add place.

A secondary issue regarding MBS-1228 is that we don't link edits for parts to the parent, so edits to areas within another area won't get linked to the parent area. This isn't specific to areas though, it's true of all the part of relationships (e.g. works), so I think it's a separate problem to MBS-1228.

How do you see editor subscriptions working?