[FEATURE] protecting research area collection's AVUs (like Title, Affiliation, etc ...) against changes via imeta

[ccacciari]

Is your feature request related to a problem? Please describe.

Using an icommand like the following one as normal user: imeta rm -C /myZone/home/research-testgroup-1/MD-demo Title "Test location" usr_0_s I can change the collection's AVUs making them inconsistent with the file yoda-metadata.json. The collection belongs to a research group and it has not been submitted for vault yet.

Describe the solution you'd like

It would be nice to have an iRODS rule that prevents that change, protecting those AVUs against mistakes of normal users.

Describe alternatives you've considered

An alternative could be to close the access to iRODS via icommands for normal users, but this seems too restrictive for some use cases.

Additional context

Add any other context or screenshots about the feature request here. Ex. Here's a photo of my cat!

[lwesterhof]

Other alternative solution: Synchronize content of AVUs with yoda-metadata.json, then users can also use the imeta command to modify the metadata.