IQSS / IQSS/dataverse

Feature Request/Idea: Use Commands effect changes for Embargo and Retention Period

Open
#10,536 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Overview of the Feature Request

New features for embargoing files and setting retention periods were added recently. at least in the api version of these features the updates are done without a command - permissions are checked manually as well as the action log. (possibly ui as well - I haven't looked)

What kind of user is the feature intended for?
Code Infrastructure

What inspired the request?
QA review of the file retention feature

What existing behavior do you want changed?

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

Any open or closed issues related to this feature request?

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 locating the API implementation for file embargoes and retention periods and check whether the UI also performs these updates. Compare those paths with existing command-based changes, including permission checks and action logging. Done means the relevant updates consistently use commands and preserve those checks and logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design
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.