Sometimes I manually fix some fields that I don’t want to have locally as they appear in the MB database. Later when I refresh those releases to update other tags, manually fixed fields are reverted. I want to remember those fields as fixed for the future (unless I manually change them) but still allow other fields to be updated from MB. In options, we have preserve tags, but it is static and works globally, not per release. On specific release, we have Add to 'Preserve Tags' list, but it is remembered for the current session only. 

I made a plugin that uses preserve_tags field if it exists on track to accomplish this - for example, if track has preserve_tags: album albumartist, it doesn't allow changes to those fields but allow change on other fields. While this works nicely, I think the feature should get integrated for better UI/UX.

The feature would include:

1. In Metadata panel
   1. New context menu option  Add/Remove to/from 'Preserve Tags' list (as a tag). Using this option would add field name in the configured tag as multi value (so it gets separated by `;` in the final string).
   2. Coloring tags preserved in this way differently 
   3. Using strikeout line when local version differs from remote version (the same thing as if you used Use original value option)
2. New option in Options -> Tags - preserve tag field name which is by default preserve_tags

This feature would allow one to pin specific fields the way he wants, while still be able to update releases in the future and have clear visibility on what is going on and why.

Plugin is available here: https://community.metabrainz.org/t/dynamically-preserve-fields-based-on-tag/814578/3