Dataverse displays to users information entered in certain compound fields in unexpected ways
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
When does this issue occur?
When viewing a dataset page with information entered in the child fields of certain compound fields, where the child fields also include "displayFormats" to control how the information is shown to users.
Which page(s) does it occurs on?
The dataset view pages in the JSF version of Harvard Dataverse and in the Modern UI version of Harvard Dataverse
What happens?
On the JSF version of Harvard Dataverse, the user:
-
Doesn't see the name of the parent field (such as "Geodetic Model")
-
Sees the information in the child fields displayed on separate lines
-
Sees the names of the child fields prepended to the information entered in the child fields, since "#NAME:" is included in those fields' displayFormats
On the Modern UI version of Harvard Dataverse, the user:
-
Doesn't see the name of the parent field (such as "Geodetic Model")
-
Sees the information in the child fields displayed on separate lines
-
Does not see the names of the child fields, even though "#NAME:" is included in those fields' displayFormats
To whom does it occur (all users, curators, superusers)?
All users who see the dataset page on the JSF and Modern UI versions of Harvard Dataverse
What did you expect to happen?
On the JSF and Modern UI versions of Harvard Dataverse, the user:
-
Sees the name of the parent field ("Geodetic Model")
-
Sees the information in the child fields displayed on the same line
-
Sees the names of the child fields prepended to the information entered in the child fields, since "#NAME:" is included in those fields' displayFormats
This is how we expected Dataverse to show users this information when we were designing this part of the dataset page for datasets in the CIESIN collection. See https://github.com/IQSS/dataverse.harvard.edu/issues/400#issuecomment-4143285673.
And this is how we expect Dataverse to display what users enter in the child fields of all compound fields where "#NAME:" is used to help users more easily understand the information.
Which version of Dataverse are you using?
- The JSF version of Harvard Dataverse on
v. 6.10.1 build iqss-4 - The Modern UI version of Harvard Dataverse on
v. 6.10.1 build iqss-4 | frontend version: 371cf9773
Any related open or closed issues to this bug report?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the dataset page in both the JSF and Modern UI versions with compound fields whose child fields use displayFormats containing "#NAME:". Compare the output with the expected parent label, child labels, and same-line formatting; done when both interfaces show the compound field consistently as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100