Page MenuHomePhabricator

PubMed source dates with no day
Closed, DuplicatePublicBUG REPORT

Assigned To
None
Authored By
Novem_Linguae
May 25 2022, 10:20 PM
Referenced Files
F35177120: image.png
May 25 2022, 10:20 PM
F35177126: image.png
May 25 2022, 10:20 PM
F35177124: image.png
May 25 2022, 10:20 PM

Description

List of steps to reproduce (step by step, including full links if applicable):

What happens?:

  • Scroll down to "Source date". Will be 2020-12. This is because the PubMed page says "2020 Dec" and has no exact day. However this generates an warning in the {{Cite}} template.

What should have happened instead?:

  • A better behavior would be to automatically add -01 as the day.

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc.:

I thought about filing this as a bug at https://github.com/zotero/translators. However I decided to start here first.

This isn't a one off. A lot of PubMed articles don't have source date days.

image.png (590×763 px, 66 KB)

image.png (234×1 px, 12 KB)

image.png (83×1 px, 10 KB)

Related Objects

Event Timeline

I think this is related to this bug here: T132308. In short, the English Wikipedia (and apparently *only* the English Wikipedia) rejects dates in the YYYY-MM format (when the day is unknown or unspecified) because, they argue, could be mistaken for a date range. For example, 2010-12 could either mean "December 2010" or "2010-2012". As mentioned in that (long) thread, the Citoid team tried to fix it with 2010-12-XX (for example); but although it works in the English Wikipedia, it fails in all others.

I have recently suggested that the Citoid extension could be configured to return YYYY-MM-XX in some Wikipedias, and YYYY-MM in others to fix this. See here.

I thought about filing this as a bug at https://github.com/zotero/translators. However I decided to start here first.

I think you decided wisely. I don't think this would be an issue for the Zotero's repository.

Mvolz subscribed.

We used to add 01 as the day. This made people mad due to "false precision". As has nearly every other way I've tried to resolve this. There is extensive discussion on the other thread if you want to weigh in there!