Feature Request: ability to restrict editing of certain metadata fields

Overview of the Feature Request

We would like to define an institution-specific metadata block (mostly administrative tracking) and pre-populate these fields on dataset creation, all by API. We then want to allow researchers access to edit most other metadata fields, but restrict editing of certain fields to superusers.

What kind of user is the feature intended for?

API User, Curator, Depositor, Superuser

What inspired the request?

Proposed workflow in which a dataset will be programmatically created, then allow researchers to upload files and edit some metadata fields but not all.

Any brand new behavior do you want to add to Dataverse?

More granular permissions on metadata editing.

Any open or closed issues related to this feature request?

Not that I could find, except maybe #9950

Are you thinking about creating a pull request for this feature?

We would like to, unless someone beats us to it.

Start by reviewing the requested API workflow and the related issue #9950, then locate how Dataverse currently handles metadata editing permissions for API users, curators, depositors, and superusers. Done would require a concrete design and implementation for institution-specific metadata, pre-population on dataset creation, and granular restrictions on which metadata fields researchers may edit.