IQSS / IQSS/dataverse

Feature Request: List emails that sent message via "Contact Owner" button

Open
#12,168 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
List accounts, names, and/or email addresses of users that send an email via the "Contact Owner" button for a given dataset.

What kind of user is the feature intended for?
API User

What inspired the request?
We received a request from one of our users on UNC Dataverse describing this need. Particularly, they'd like "to know who reached out to data owners through the Dataverse to provide them with additional resources for effective collaboration."

What existing behavior do you want changed?
N/A

Any brand new behavior do you want to add to Dataverse?
Admin api endpoint for this functionality; list users that have sent a message via the "Contact Owner" button for a dataset.

Any open or closed issues related to this feature request?
#11088 is related, though not the same feature request.

Are you thinking about creating a pull request for this feature?
We are currently looking into addressing this feature request, though no plans yet!

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 reviewing related issue #11088 and the existing admin API entry points for dataset-related activity. Define the endpoint scope and the information it should return for users who used the "Contact Owner" button; done means the API can list those users for a given dataset with behavior confirmed by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.