metadata tab: doi link in related publications field should hyperlink

[sbarbosadataverse]

In the demo site: if you click on the metadata tab, the doi link in "related publications" does not hyperlink, although in the summart view of the dataset page, it does.

see both images:
summary provides hyperlink

metadata tab does not:

[djbrooke]

Thanks @sbarbosadataverse.

@jggautier - let's catch up about this next week. I think the preferred solution to this issue is #1625.

[pdurbin]

What's weird is that #2814 has a screenshot of it working.

[pdurbin]

The URL for "Related Publiction" works fine on https://dataverse.ada.edu.au/dataset.xhtml?persistentId=doi:10.4225/87/JUDY2Y running Dataverse 4.6.1. Here's a screenshot:

[jggautier]

@jggautier - let's catch up about this next week. I think the preferred solution to this issue is #1625.

@djbrooke and I chatted about this issue. The suggestion in #1625 would go beyond fixing this bug.

As far as I can tell, in Dataverse 4.16, related publication URL is the only URL field (a field that expects a URL) that isn't displayed in the Metadata tab as a clickable link. Keyword vocab, producer and distributor URLs are all still clickable when displayed in the Metadata tab.

[djbrooke]

Thanks @jggautier and @pdurbin! Will move to the Ready column for us to take on in an upcoming sprint.

[djbrooke]

@jggautier - can you add in the additional information that you mentioned during sprint planning? Also, let's discuss the old issue from @pameyer regarding opening links in a new window.

[jggautier]

Sure. I just mentioned that the only change in the citation.tsv that I could see between the Dataverse version ADA's repository is using, 4.6.1, and the more recent versions, is that the html attribute target="_blank" was added to the display format of the url fieldtypes.

(Although we didn't think that could be the source of the regression.)

Also, this is the case for other repositories running recent Dataverse versions, like UNC: https://dataverse.unc.edu/dataset.xhtml?persistentId=hdl:1902.29/11878

The old issue from @pameyer about adding another html attribute is #4717

[scolapasta]

The low level issue is the displayformat for publicationURL in the database is set to: #VALUE instead of <a href="#VALUE" target="_blank">#VALUE</a>

If you change that value in the DB it works correctly.

So the real question is how did this get changed in the DB? (and is anything else incorrect)

@jggautier looked at the TSV and it is correct there. So the bug is likely in the API that reads and parses the TSV.

(the upshot is that we could manually update this as a quick fix, but we should find the root cause so that it doesn't occur in the future if/when we reload the TSV)