IQSS / IQSS/dataverse

Feature Request: make publisher configurable below the instance-level

Open
#12,142 2 comments 1 reaction 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
Currently, the name of the root directory (for us: heiDATA) is used across the entire instance as publisher in the automatically generated citation, e.g.:

Gockel,` Bettina. 2024. “Camera Work. A Photographic Quarterly – Eine Digitale Edition.” heiDATA. https://doi.org/doi:10.11588/DATA/ZBPWHG.

The variable ":InstallationName" has been introduced to set a different value as publisher but that would still affect the whole instance.

Our use case is that part of our instance is used as a domain specific repository (for our "Fachinformationsdienst" (specialized information service) arthistoricum). The publisher should be arthistoricum there rather than heiDATA.

It would be great if one could configure the publisher at dataverse level. Nice to have (but secondary to that) would be to use the distributor in the citation of each dataset if a value is given in the distributor name field and come back to the value configured for the dataverse if no info is found.

As far as I can see, we are not the only ones who would be interested in making the behavior of Dataverse configurable in this regard. Previously discussed solutions included, for example, the already described process of using the value actually entered in the respective dataset from the distributor metadata field for the citation or (as in a previous Dataverse version) using both the root directory and the specific collection (in this case, arthistoricum.net@heiDATA and heiDATA). However, as far as I can see, these solutions have not been implemented.

What kind of user is the feature intended for?
Anyone citing datasets, admins, depositors.

Any open or closed issues related to this feature request?
Yes:
open: https://github.com/IQSS/dataverse/issues/9613#issuecomment-1561138553
closed:

Are you thinking about creating a pull request for this feature?
No, regrettably.

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

No files or tests are named. Start by reviewing issue 9613 and the linked closed issues, then trace citation generation and the distributor metadata field. Done means defining and implementing dataverse-level publisher configuration, with the requested distributor fallback behavior resolved explicitly.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.