IQSS / IQSS/dataverse

Feature Request: Dataset Download Receipt

Open
#11,459 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Overview of the Feature Request

  • As a Dataset Downloader, I would like to receive a receipt for the dataset I have downloaded that includes dataset information (e.g., title, author, DOI, license) and download date and time.
What kind of user is the feature intended for?

(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

  • Dataset Downloaders
What inspired the request?
  • A Harvard-affiliated faculty member requested a dataset download receipt to document their secondary data reuse and to share with the funder of their research project.
What existing behavior do you want changed?
  • At present, dataset downloaders do not receive any
Any brand new behavior do you want to add to Dataverse?
  • Upon downloading a dataset, Dataset Downloaders would have the option to request an electronic receipt
    of their transaction (e.g., in ASCII, PDF, or some other electronic format).
Any open or closed issues related to this feature request?
  • None that I could find.

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 tracing the existing dataset download flow and the user-facing download behavior described in this issue. Clarify the receipt format, request flow, included metadata, timestamp, and delivery method before implementation. Done means dataset downloaders can optionally request a receipt containing the agreed dataset information and download date and time.

Written by the indexing model from the issue text.

Assessment

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