IQSS / IQSS/dataverse

Publish Dataset Disclaimer Text problematic for repositories whose liaisons review publication requests

Open
#12,370 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Feature: https://guides.dataverse.org/en/6.10/installation/config.html#publishdatasetdisclaimertext

In the TDR multi-institutional Dataverse repository, our institutions choose from three levels of curation, described here: https://texasdigitallibrary.atlassian.net/wiki/x/E4CkJQ

Initially, we wanted to activate this Publish Dataset Disclaimer text for our users; however, our institutional liaisons who require liaison review prior to publication pointed out that they would have to click this attestation. Instead, they would prefer that the the attestation is clicked by the author when they request publication in institutions where this level of curation is required.

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 with the Publish Dataset Disclaimer Text configuration described in the linked Dataverse installation guide and trace the publication-request flow for repositories requiring liaison review. Compare when the author and liaison interact with the attestation, then define the behavior so the author confirms it when requesting publication while the liaison can complete review without doing so.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.