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
Describe the bug
When you visit the metrics pages on either the holdings summary or on a data portal, the citations list has no link back to the dataset. There is hyperlinked text at the bottom of each citation ("Cites Data: ([Last Name] et al. ([Year])") that appears to provide a link back to the dataset however that text hyperlink is the same as the citation and does not link to a dataset.
I can't verify whether this is also true for the DataOne holdings summary because the view/download/citation metrics weren't loading at the times that I tried to check it
If needed, please discuss ESS-DIVE's resolution timelines and priority with @vchendrix
In case it is helpful, I noticed that this new issue compliments the existing issue #1542
Expected behavior
Clicking on "Cites Data: ([Last Name] et al. ([Year])" within any citation metrics list on ESS-DIVE should take you to an ESS-DIVE dataset.
Screenshots
See in attached screen recording that the hyperlink preview doesn't change no matter where you hover over a citation list item.
citation-metrics-cites-data-bug-demo.mov
Additional context
This bug was brought to our attention by a frequent data contributor and project data manager over Jira: https://ess-dive.atlassian.net/browse/EDSUPPORT-2631. They submitted feedback requesting us to introduce the capability to connect citation metrics to datasets and we discovered the bug while looking into present functionality. This also provides some evidence that this bug is effecting users more broadly. Quoted message from user is listed below:
[We] added two journal paper citations to the dataset:
Rogers A ; Ely K ; Serbin S (2019): Leaf Photosynthetic Parameters: Quantum Yield, Convexity, Respiration, Gross CO2 Assimilation Rate and Raw Gas Exchange Data, Utqiagvik (Barrow), Alaska, 2016. Next-Generation Ecosystem Experiments (NGEE) Arctic, ESS-DIVE repository. Dataset. doi:10.5440/1482338 accessed via https://data.ess-dive.lbl.gov/datasets/doi:10.5440/1482338on 2024-04-02
I noticed the citations while on the NGEE data portal metrics page. I would like to see what datasets these are connected to. I had to go into the article and find the dataset citation to look it up on the ESS-DIVE search to figure it out. There should be some connection rather than just a list. Maybe there is somewhere but I didn’t know where else to look. It would be nice to have some sort of side database for researchers, data managers, or PIs to manage publications / datasets connections. It would also be good to have a standard report to include in the project report metrics.
Describe the bug
When you visit the metrics pages on either the holdings summary or on a data portal, the citations list has no link back to the dataset. There is hyperlinked text at the bottom of each citation ("Cites Data: ([Last Name] et al. ([Year])") that appears to provide a link back to the dataset however that text hyperlink is the same as the citation and does not link to a dataset.
Examples:
If needed, please discuss ESS-DIVE's resolution timelines and priority with @vchendrix
In case it is helpful, I noticed that this new issue compliments the existing issue #1542
Expected behavior
Clicking on "Cites Data: ([Last Name] et al. ([Year])" within any citation metrics list on ESS-DIVE should take you to an ESS-DIVE dataset.
Screenshots
See in attached screen recording that the hyperlink preview doesn't change no matter where you hover over a citation list item.
citation-metrics-cites-data-bug-demo.mov
Additional context
This bug was brought to our attention by a frequent data contributor and project data manager over Jira: https://ess-dive.atlassian.net/browse/EDSUPPORT-2631. They submitted feedback requesting us to introduce the capability to connect citation metrics to datasets and we discovered the bug while looking into present functionality. This also provides some evidence that this bug is effecting users more broadly. Quoted message from user is listed below:
The text was updated successfully, but these errors were encountered: