IQSS / IQSS/dataverse

Feature Request: ability to configure admin/curator-only externaltools

Open
#11,694 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request

One reason we haven't enabled the Data Curation Tool in our production installation was concern over allowing data owners to edit variable-level metadata. Our Research Data Preservation Archivist asked if there were some way to offer the tool, but only to site administrators.

What kind of user is the feature intended for?

Superuser, Curator(?)

What inspired the request?

Concern over allowing any data owner to edit variable level metadata with the data curation tool.

What existing behavior do you want changed?

We would like to offer some external tools in an admin-only fashion.

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

We would like to offer some external tools in an admin-only fashion.

Any open or closed issues related to this feature request?

Nothing came back in my search, but I'm not great at that.

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

We would like to, but this seems like it would require input on permissions models and the availability of externaltools.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by clarifying the permissions model and how external tools are made available. Determine which roles should access admin/curator-only external tools and how data-owner access must remain restricted. Done means the approved external tools are available to administrators or curators without granting that access to ordinary data owners.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.