Feature Request: ability to restrict editing of certain metadata fields

[donsizemore]

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.

[qqmyers]

FWIW: Dataverse currently supports "Protected" metadata blocks, where a key is required to edit them by API, and they do not appear in the UI edit pane (they are still publicly visible as is all metadata currently). If those don't address your use case: DANS is considering supporting development of 'admin-only' blocks where only super users/some other privileged role are allowed to edit - let me know/report here if you plan to start implementing, want to coordinate, etc., and I'll try to remember to do the same if/when DANS starts development.

[pdurbin]

Related:

• Feature Request/Idea: Allow creation of 'invisible' or 'internal' metadata #9209