Citations questions

[psmedia]

Hi! I know citations are tricky, but we're working through things. However this latest file is throwing me for a loop. All our citations are in structured data, either bibtex or DOIs. All the citations show a "1. (and then a newline)" in front of them in the pop-up/modal. Down at the bottom of the webpage, the citation looks ok, but the same number is introduced in the citations in the pdf download, looking like:

Health Emergency Risk Management [Internet]. 2019. Available from: https://apps.who.int/iris/bitstream/handle/10665/340893/WHO-EURO-2019-2378-42133-58035-eng.pdf
↩
2.
1.
Cinar P, Bold R, Bosslet BA, Bota DA, Burgess D, Chew HK, et al. Planning for post‐pandemic cancer care delivery: Recovery or opportunity for redesign? CA A Cancer J Clinicians [Internet]. 2020 Sep 30;71(1):34– 46. Available from: http://dx.doi.org/10.3322/caac.21644
↩

The docx download is also failing, for the same reason?

Is this anything you've seen before? We are not getting this in other pubs.
f06lgvfbmhjtjdz76jawdmvuhoue1wut.pdf

[gabestein]

I haven't seen this before, it's quite odd. Are you using Vancouver in other pubs as well?

[psmedia]

Hi @gabestein - this one is still open for us. We are using Vancouver exclusively. If we include the citation as structured data, we get the weird 1. in the pop-up. If we include the citation as rich text, there's no weird number 1. in the pop-up, but the citations do not export in MS Word format (which we were hoping to use for workflow reasons...)

[gabestein]

Understood. We are trying to track it down, but as I wrote above, we believe it is a bug with the way the library we use to generate citations handles Vancouver, so a fix may not be under our control. I'll let you know when we have a sense of a fix and timeline.

[psmedia]

Do let me know what you find. I would like to have this pinned down.

[psmedia]

Colleagues, all of a sudden our structured data citations are failing, giving us an error. TIming out from the lookup? In general we're seeing an increase in application errors as well, not sure if that is connected to our heavy use of structured-data Vancouver citations.

[gabestein]

That service relies on Crossref, which is having ongoing issues with its public API: https://status.crossref.org/

Unfortunately, there's not a lot we can do until it's stabilized.

[psmedia]

Understood! Thanks.

…

On Thu, 6 Jun 2024 at 11:16, Gabriel Stein ***@***.***> wrote: That service relies on Crossref, which is having ongoing issues with its public API: https://status.crossref.org/ Unfortunately, there's not a lot we can do until it's stabilized. — Reply to this email directly, view it on GitHub <#3057 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFKY6BT2VYKNLZXWVSFTNTZGB4NFAVCNFSM6AAAAABFH26UBSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMOJRGEZDM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gabestein]

A heads up that we've published a hotfix while we sort out the changes to Crossref's API. Pages will load much faster, and if a DOI lookup fails it will show the raw DOI rather than an error. We're working on longer-term approaches, but for now this should get you back to being able to work on those pubs, anyway.