You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Email sent from the contact forms to the contact(s) for a collection, dataset, or datafile can now optionally be cc'd to a support email address. The support email address can be changed from the default :SystemEmail address to a separate :SupportEmail address. When multiple contacts are listed, the system will now send one email to all contacts (with the optional cc if configured) instead of separate emails to each contact. Contact names with a comma that refer to Organizations will no longer have the name parts reversed in the email greeting. A new protected feedback API has been added.
4
+
5
+
## Backward Incompatibilities
6
+
7
+
When there are multiple contacts, the system will now send one email with all of the contacts in the To: header instead of sending one email to each contact (with no indication that others have been notified).
8
+
9
+
## New JVM/MicroProfile Settings
10
+
11
+
dataverse.mail.support-email - allows a separate email, distinct from the :SystemEmail to be used as the to address in emails from the contact form/ feedback api.
12
+
dataverse.mail.cc-support-on-contact-emails - include the support email address as a CC: entry when contact/feedback emails are sent to the contacts for a collection, dataset, or datafile.
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/api/native-api.rst
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1618,6 +1618,8 @@ The fully expanded example above (without environment variables) looks like this
1618
1618
1619
1619
The people who need to review the dataset (often curators or journal editors) can check their notifications periodically via API to see if any new datasets have been submitted for review and need their attention. See the :ref:`Notifications` section for details. Alternatively, these curators can simply check their email or notifications to know when datasets have been submitted (or resubmitted) for review.
1620
1620
1621
+
.. _return-a-dataset:
1622
+
1621
1623
Return a Dataset to Author
1622
1624
~~~~~~~~~~~~~~~~~~~~~~~~~~
1623
1625
@@ -1645,6 +1647,8 @@ The fully expanded example above (without environment variables) looks like this
1645
1647
1646
1648
The review process can sometimes resemble a tennis match, with the authors submitting and resubmitting the dataset over and over until the curators are satisfied. Each time the curators send a "reason for return" via API, that reason is persisted into the database, stored at the dataset version level.
1647
1649
1650
+
The :ref:`send-feedback` API call may be useful as a way to move the conversation to email. However, note that these emails go to contacts (versus authors) and there is no database record of the email contents. (:ref:`dataverse.mail.cc-support-on-contact-email` will send a copy of these emails to the support email address which would provide a record.)
1651
+
1648
1652
Link a Dataset
1649
1653
~~~~~~~~~~~~~~
1650
1654
@@ -4497,3 +4501,29 @@ A curl example using allowing access to a dataset's metadata
4497
4501
4498
4502
Please see :ref:`dataverse.api.signature-secret` for the configuration option to add a shared secret, enabling extra
4499
4503
security.
4504
+
4505
+
.. _send-feedback:
4506
+
4507
+
Send Feedback To Contact(s)
4508
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~
4509
+
4510
+
This API call allows sending an email to the contacts for a collection, dataset, or datafile or to the support email address when no object is specified.
4511
+
The call is protected by the normal /admin API protections (limited to localhost or requiring a separate key), but does not otherwise limit the sending of emails.
4512
+
Administrators should be sure only trusted applications have access to avoid the potential for spam.
4513
+
4514
+
The call is a POST with a JSON object as input with four keys:
4515
+
- "targetId" - the id of the collection, dataset, or datafile. Persistent ids and collection aliases are not supported. (Optional)
4516
+
- "subject" - the email subject line
4517
+
- "body" - the email body to send
4518
+
- "fromEmail" - the email to list in the reply-to field. (Dataverse always sends mail from the system email, but does it "on behalf of" and with a reply-to for the specified user.)
4519
+
4520
+
A curl example using an ``ID``
4521
+
4522
+
.. code-block:: bash
4523
+
4524
+
export SERVER_URL=http://localhost
4525
+
export JSON='{"targetId":24, "subject":"Data Question", "body":"Please help me understand your data. Thank you!", "fromEmail":"dataverseSupport@mailinator.com"}'
4526
+
4527
+
curl -X POST -H 'Content-Type:application/json' -d "$JSON" $SERVER_URL/api/admin/feedback
4528
+
4529
+
Note that this call could be useful in coordinating with dataset authors (assuming they are also contacts) as an alternative/addition to the functionality provided by :ref:`return-a-dataset`.
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/installation/config.rst
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2349,6 +2349,27 @@ See :ref:`discovery-sign-posting` for details.
2349
2349
2350
2350
Can also be set via any `supported MicroProfile Config API source`_, e.g. the environment variable ``DATAVERSE_SIGNPOSTING_LEVEL1_ITEM_LIMIT``.
2351
2351
2352
+
dataverse.mail.support-email
2353
+
++++++++++++++++++++++++++++
2354
+
2355
+
This provides an email address distinct from the :ref:`systemEmail` that will be used as the email address for Contact Forms and Feedback API. This address is used as the To address when the Contact form is launched from the Support entry in the top navigation bar and, if configured via :ref:`dataverse.mail.cc-support-on-contact-email`, as a CC address when the form is launched from a Dataverse/Dataset Contact button.
2356
+
This allows configuration of a no-reply email address for :ref:`systemEmail` while allowing feedback to go to/be cc'd to the support email address, which would normally accept replies. If not set, the :ref:`systemEmail` is used for the feedback API/contact form email.
2357
+
2358
+
Note that only the email address is required, which you can supply without the ``<`` and ``>`` signs, but if you include the text, it's the way to customize the name of your support team, which appears in the "from" address in emails as well as in help text in the UI. If you don't include the text, the installation name (see :ref:`Branding Your Installation`) will appear in the "from" address.
2359
+
2360
+
Can also be set via any `supported MicroProfile Config API source`_, e.g. the environment variable ``DATAVERSE_MAIL_SUPPORT_EMAIL``.
2361
+
2362
+
.. _dataverse.mail.cc-support-on-contact-email:
2363
+
2364
+
dataverse.mail.cc-support-on-contact-email
2365
+
++++++++++++++++++++++++++++++++++++++++++
2366
+
2367
+
If this setting is true, the contact forms and feedback API will cc the system (:SupportEmail if set, :SystemEmail if not) when sending email to the collection, dataset, or datafile contacts.
2368
+
A CC line is added to the contact form when this setting is true so that users are aware that the cc will occur.
2369
+
The default is false.
2370
+
2371
+
Can also be set via *MicroProfile Config API* sources, e.g. the environment variable ``DATAVERSE_MAIL_CC_SUPPORT_ON_CONTACT_EMAIL``.
2372
+
2352
2373
2353
2374
.. _feature-flags:
2354
2375
@@ -3831,3 +3852,4 @@ A true(default)/false option determining whether datafiles listed on the dataset
3831
3852
A true/false (default) option determining whether the dataset datafile table display includes checkboxes enabling users to turn folder ordering and/or category ordering (if an order is defined by :CategoryOrder) on and off dynamically.
3832
3853
3833
3854
.. _supported MicroProfile Config API source: https://docs.payara.fish/community/docs/Technical%20Documentation/MicroProfile/Config/Overview.html
0 commit comments