The missing space between citation string and doi in the "above the fold" "related publications" field

[chrisjcameron]

The same related publication is formatted differently on different parts of the page. The related publications field above the tab bar is missing a space between the citation string and doi. The metadata tab formats it correctly.

What steps does it take to reproduce the issue? Upload a dataset with related publications

• When does this issue occur? on the main page for a dataset

• What happens? Missing a space between the citation string and doi

• To whom does it occur (all users, curators, superusers)? all users

• What did you expect to happen? consistent format with a space

Which version of Dataverse are you using? 6.6 build v6.6-c6b6dac5c3

Any related open or closed issues to this bug report? none found

Screenshots:

[pdurbin]

@chrisjcameron hi! Thanks for taking the time to open this issue.

I believe this was reported in this issue...

• #11053

... and fixed in this pull request for 6.6:

• #11106

And yet, you're running 6.6. Hmm. 🤔

I took a look at https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/TUSJYB (also 6.6) and there's a space (screenshot below).

Can you reproduce this on https://demo.dataverse.org (also running 6.6)? Thanks!

[chrisjcameron]

Thanks for your response. With some experimentation and inspection, I was able to replicate at https://demo.dataverse.org/dataset.xhtml?persistentId=doi%3A10.70122%2FFK2%2FMHA1DR

If a URL is not provided in the metadata, the doi is appended to the same table data cell as the rest of the citation. If the URL is present, the doi is placed in a separate span element with the url as the href. The CSS changes in 11106 target the <span> element, so that pull request does not address the case where there is a doi provided without a URL.

[pdurbin]

I see, you entered it like this:

And for my reference, he's an additional tool tip:

Let me check with @jggautier to see what he thinks about the different ways people fill in these fields. I feel like this has come up before!

It smells like there's a bug to fix or some docs or tool tips to tweak. 🤔

@chrisjcameron if it's not too much trouble, would you like to test on https://beta.dataverse.org as well? Once you've created an account you should be able to log into https://beta.dataverse.org/spa where the new, React-based UI we're working on is deployed. I'm curious if you see the same behavior there.

[pdurbin]

@jggautier is pretty busy but I found this related comment: https://github.com/IQSS/dataverse/issues/8657#issuecomment-1113563055

@chrisjcameron I think you're putting the right thing under "Identifier". Just the number, not the URL form of a DOI.

Of course, we went back and forth recently about author identifiers. If you select ORCID, for example, do you put just the number or the URL form? As of #11246 we support both.

I missed the PID talk by @qqmyers last week (so many tracks!) but he advocated for both forms.

Personally, I'd like clear tooltips and docs to start. 😄

[pdurbin]

One last thought (crazy idea): ideally, the Dataverse UI would be super smart and let the user paste a single field, perhaps the URL form of a DOI, and other fields would be auto-populated (fetched from doi.org or whatever PID provider). This would reduce the manual effort required. You'd still need to pick a Relation Type manually, of course.

I know we've talked about this somewhere in the many GitHub issues but I thought I'd mention it again. 😄

This isn't something we'd do in the old UI (JSF). Maybe in React (the future): https://github.com/IQSS/dataverse-frontend