IQSS / IQSS/dataverse

Feature Request/Idea: Inform users that their message (from 'Contact' or 'Contact Owner') has actually been sent

Open
#8,719 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Component: JSF Feature: Notifications Type: Bug User Role: Guest
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
Users should receive a confirmation / a message to confirm, in one way or another (or several), that their message was actually sent either to a dataset owner or to a Dataverse admin contact after they have completed the form with the 'Contact' or 'Contact Owner' buttons:

———————————————————————————————

cont1

———————————————————————————————

cont2

———————————————————————————————

What kind of user is the feature intended for?
All users using the GUI.

What inspired the request?
When we're tired or not 100% focussed, it can be easy to doubt whether we have just clicked the 'Send' or the 'Cancel' button. Further, connection problems can short-circuit completing and validating a form on a website (we click 'Send', the page reloads, sometimes leading to a 404). If there is no formal confirmation, there is literally no way for the user to be 100% sure their communication has been handled up to the very last stage of the procedure.

What existing behavior do you want changed?
Not so much changed but inspired from existing features:

  1. The webpage could reload and a colored banner (the Alerts), just like the ones already in use, could notify users that their message was properly sent.
  2. And/or there could also be an email notification with a copy of the message that was just sent.

Any brand new behavior do you want to add to Dataverse?
That doesn't sound absolutely necessary to me, though there is talk in some issues of new pop-up notifications.

Any related open or closed issues 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 GUI forms behind the “Contact” and “Contact Owner” actions and review the related issues 5610 and 3300. Determine whether confirmation should use an alert, an email, or both, then define and test the expected behavior for successful submission and connection or validation failure.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.