👁 Image Archives

List of archives Before 2025 Archive 0 (Early bug reports) Archive 1 (May 2008 – Jun 2011) Archive 2 (Jun 2011 – Nov 2015) Archive 3 (Nov 2015 – Jul 2016) Archive 4 (Jul 2016 – Oct 2016) Archive 5 (Oct 2016 – Sep 2017) Archive 6 (Sep 2017 – Oct 2017) Archive 7 (Oct 2017 – Jul 2018) Archive 8 (Jul 2018 – Aug 2018) Archive 9 (Aug 2018 – Aug 2018) Archive 10 (Sep 2018 – Oct 2018) Archive 11 (Oct 2018 – Nov 2018) Archive 12 (Nov 2018 – Jan 2019) Archive 13 (Jan 2019 – Feb 2019) Archive 14 (Feb 2019 – Mar 2019) Archive 15 (Mar 2019 – Jun 2019) Archive 16 (Jun 2019 – Jul 2019) Archive 17 (Jul 2019 – Aug 2019) Archive 18 (Aug 2019 – Oct 2019) Archive 19 (Oct 2019 – Mar 2020) Archive 20 (Mar 2020 – May 2020) Archive 21 (May 2020 – Jul 2020) Archive 22 (Jul 2020 – Sep 2020) Archive 23 (Sep 2020 – Dec 2020) Archive 24 (Dec 2020 – Apr 2021) Archive 25 (Apr 2021 – Jun 2021) Archive 26 (Jun 2021 – Aug 2021) Archive 27 (Aug 2021 – Sep 2021) Archive 28 (Oct 2021 – Dec 2021) Archive 29 (Dec 2021 – Dec 2021) Archive 30 (Dec 2021 – Mar 2022) Archive 31 (Mar 2022 – May 2022) Archive 32 (May 2022 – Jul 2022) Archive 33 (Jul 2022 – Oct 2022) Archive 34 (Oct 2022 – Apr 2023) Archive 35 (Apr 2023 – Aug 2023) Archive 36 (Aug 2023 – Oct 2023) Archive 37 (Oct 2023 – Dec 2023) Archive 38 (Dec 2023 – May 2024) Archive 39 (May 2024 – Nov 2024) Archive 40 (Nov 2024 – Jan 2025) Archive 41 (Jan 2025 – Jul 2025) Archive 42 (Jul 2025 – Dec 2025) Archive 43 (Dec 2025 – Mar 2026) Archive 44 (Mar 2026 – Present)

This page has archives. Topics inactive for 90000 days are automatically archived 1 or more at a time by ClueBot III if there are more than 4.

As of 2026, the active maintainer of Citation bot (merges pull requests on GitHub and does deployments to Toolforge) is AManWithNoPlan. The Citation bot GitHub is https://github.com/ms609/citation-bot.

Note that the bot's creator (Smith609) and assistants (Kaldari and AManWithNoPlan) can go weeks without logging in to Wikipedia. The code is open source and interested parties are invited to assist with the operation and extension of the bot. Before reporting a bug, please note: Addition of DUPLICATE_xxx= to citation templates by this bot is a feature. When there are two identical parameters in a citation template, the bot renames one to DUPLICATE_xxx=. The bot is pointing out the problem with the template. The solution is to choose one of the two parameters and remove the other one, or to convert it to an appropriate parameter. A 503 error means that the bot is overloaded and you should try again later – wait at least 15 minutes and then complain here.

Please click here to report an error.

Or, for a faster response from the maintainers, submit a pull request with appropriate code fix on GitHub, if you can write the needed code.

---

1. Implement support to expand from https://doi.org/10.1093/ww/9780199540884.013.U192476 to {{Who's Who}}
   Example: https://en.wikipedia.org/w/index.php?title=Friern_Hospital&diff=prev&oldid=1167644213
2. Implement support to convert cite web to {{BioRef}} and {{GBIF}}
3. Use https://www.crossref.org/blog/news-crossref-and-retraction-watch/
4. journal/publisher that only differ by 'and' and '&' should be treated as identical https://en.wikipedia.org/w/index.php?title=Congenital_cartilaginous_rest_of_the_neck&diff=prev&oldid=1199200383
5. Free archive.org links such as curl -sH "Accept: application/json" "https://scholar.archive.org/search?q=doi:10.1080/14786449908621245" | jq -r .results[0].fulltext.access_url
6. Use GET instead of POST for better proxy caches when talking to data-bases when possible.
7. Start to convert Google Books URL to "new" format https://www.google.com/books/edition/_/m8W2AgAAQBAJ?gbpv=1&pg=PA379

Identical to § Changing every citation of a publisher's webpage to Cite book above. While the choice of formatting may be questioned (can't the Library Journal review be located somewhere less objectionable than Amazon?) the behaviour here is the same underlying misfeature of altering any webpage citation where a book's bibliographic information is presented, as if the citation was meant to be to content of the book rather than e.g. a publisher's blurb or library listing. I think there are more discussions of this in the talkpage archives here; I used to favour this feature, but I'm no longer so sure it's a net positive. Folly Mox (talk) 11:36, 30 October 2024 (UTC)[]

Apart from User talk:Citation bot/Archive 32 § Web->Book: I don't think that it was right in this case... (May 2022) linked in the thread above, there was some conversation at User talk:Citation bot/Archive 39 § Introduces ref error when citing Penguin publisher website (May 2024). There could be others. I have to go to work. Folly Mox (talk) 13:01, 30 October 2024 (UTC)[]

Changing an incorrect cite journal to cite book [1]: Good (although would have been better as cite conference).

Creating a new CS1 error where there was none before, because it left the paper title in the book title parameter and did not change the journal parameter to a book title parameter: doubleplusungood.

Stop it.

Posting as a message rather than a new bug because this is not a new bug. It is an old bug that has been ignored far too long by the developers (see #Causing template errors, above). It needs to be fixed. —David Eppstein (talk) 23:07, 20 June 2024 (UTC)[]

It's not creating error, it's flagging errors that were already there, but not reported. |journal=FM 2014: Formal Methods was wrong before. That the bot didn't manage to fix it doesn't make it a new error. Now the error is reported. This is an improvement, even though ideally the bot would be able to figure out and fix the error itself. Headbomb {t · c · p · b} 23:11, 20 June 2024 (UTC)[]

INCORRECT. It is creating an error, because formerly readers could see the paper title, see the book title (called a journal, but still formatted in italics the way readers would expect a book title to look), and see that it was a paper in a book with that title. After the edit, readers were presented only with the paper title, formatted as a book title, falsely telling them both in visible appearance and reference metadata that the reference was to an entire book-length work. It is not merely that it is creating CS1 errors, although that is bad enough. It is also making the reference less accurate in both its metadata and in its visible appearance. —David Eppstein (talk) 23:20, 20 June 2024 (UTC)[]

I've gotten really exhausted with this category of error introduced by Citation bot, which I encounter every day I edit. I used to creep its contributions and clean up after it, but I've started just reverting its edits that cause this kind of template error, regardless of any value added, and only sometimes actually fix up the citations myself. Few of the editors who call Citation bot on large sets of pages ever check in after it to see if it's causing errors, so typically no one notices my reverts.I saw a few weeks back that for one subset of conferences (IEEE maybe? or SPIE?) Citation bot has successfully been changing {{cite journal}} to {{cite book}} without introducing errors and growing the backlogs. So there has been a partial fix, but it's pretty frustrating that this known error has been perpetuated in thousands of edits spanning months.Citation bot does not have an approved BRFA task to change citation template types, and changing to {{cite book}} has been the one that's particularly fraught and error-prone ever since support for the aliases of |periodical= was dropped from {{cite book}} a year ago. The easiest thing would be if support were readded, but that seems highly unlikely. I do think that eventually, if this bug isn't fixed, I'll end up asking BAG to ban Citation bot changing template type to {{cite book}}. Disabling the functionality would be an improvement over the current situation. Folly Mox (talk) 00:02, 21 June 2024 (UTC)[]

Still ongoing failure to remove journal= from conversions to cite book, creating new CS1 errors and wasted time for human editors: Special:Diff/1245112056. —David Eppstein (talk) 06:53, 18 September 2024 (UTC)[]

STILL HAPPENING: Special:Diff/1282071056. I swear the bulk of the newly reported CS1 errors that I find on the bambots cleanup listings such as [2] are caused by Citation bot. It is extremely frustrating that the bot is creating reference cleanup work for others rather than preventing others from having to do that work, month after month and year after year, with no hint that the damage will stop. —David Eppstein (talk) 00:05, 26 March 2025 (UTC)[]

Note to maintainers Since this is quite an old report, but we have done some fixes related to {{cite journal}} and {{cite book}} we need to look in to if we fixed this, or if it is still happening. If yes see if we have multiple reports of the same kind to group it in to an issue on github. Redalert2fan (talk) 22:29, 30 December 2025 (UTC)[]

It should be enough to do a pass for new {{cite xxx}} being added in the edit if every other cite was {{citation}} (or {{cite xxx|mode=cs2}}. The exception should be that {{cite arxiv}}, {{cite bioRxiv}}, {{cite citeseerx}}, {{cite medrxiv}}, and {{cite ssrn}} all have |mode=cs2 added to them instead of being converted to {{citation}}.

Same for author2/first2 --> last2/first2. Headbomb {t · c · p · b} 16:21, 15 November 2024 (UTC)[]

This is the same issue as § Changing every citation of a publisher's webpage to Cite book above (September 2023), User talk:Citation bot/Archive 39 § Causing template errors (November 2023), User talk:Citation bot/Archive 39 § A class of new(?) errors (November 2023), User talk:Citation bot/Archive 39 § Introduces ref error when citing Penguin publisher website (May 2024), etc. I believe most of the cases that cause template errors have been fixed this year, but the underlying behaviour has not. Maybe this exact class of parameters wasn't addressed because it includes both |website= and |page=.TBH Citation bot is such a popular and high-volume tool that it might actually be worth holding a centralised discussion about whether this functionality is desired instead of having the same conversation here every few months. Folly Mox (talk) 14:14, 20 November 2024 (UTC)[]

Same here:

https://en.wikipedia.org/w/index.php?title=Root-finding_algorithm&diff=1263375628&oldid=1263149178&variant=en — Preceding unsigned comment added by Dominic3203 (talk • contribs) 01:56, 17 December 2024 (UTC)[]

Even when used as a reliable source for basic information for a work such as release date et al, Amazon pages tend to be erroneously converted (Special:Diff/1263465110, Special:Diff/1265696226) into the ref for the associated work. ミラP@Miraclepine 16:34, 28 December 2024 (UTC)[]

Also: Special:diff/1261279289 at Apollo et Hyacinthus where |last=, |first= and |author-link= are unnecessarily replaced by |last1=, |first1= and |author-link1=. -- Michael Bednarek (talk) 06:33, 5 December 2024 (UTC)[]

Yes, this "also" is the real bug. For multiple authors, making them all numbered does make sense in terms of consistency, but for a single author, replacing |last= by |last1= and so on is in fact WP:EDITORHOSTILE and should be disabled. — Mikhail Ryazanov (talk) 22:40, 17 January 2026 (UTC)[]

It only changes first to first when there are multiple authors. Headbomb {t · c · p · b} 23:09, 17 January 2026 (UTC)[]

Indeed. I thought that I've noticed similar changes recently, but upon examining carefully, I see now that there and in the diff provided above, the structure looks like {{Cite book|title=The Cambridge Mozart Encyclopedia|last=Eisen|first=Cliff|author-link=Cliff Eisen|publisher=Cambridge University Press|year=2006|location=Cambridge|last2=Keefe|first2=Simon P.|author-link2=Simon P. Keefe}}, with a second author present, but at the very end, separated from the first author by many other parameters. This is what WP:EDITORHOSTILE calls "harder to understand". So if the bot renames the author parameters in such cases, I would suggest to also reorder them properly (and reformat with spaces for readability according to WP:EDITORHOSTILE and {{Cite book}}'s TemplateData "format": "{{_ |_=_}}"). — Mikhail Ryazanov (talk) 02:56, 18 January 2026 (UTC)[]

IAU Circular/IAU Circ./IAU Circ and Central Bureau Electronic Telegrams/Cent. Bur. Electron. Telegr./Cent Bur Electron Telegr/CBET have issues, not volumes. The # is the article number/page. This can be parsed directly from the bibcode when present. Headbomb {t · c · p · b} 18:06, 4 February 2025 (UTC)[]

Not quite fixed, still need to do follow up cleanup, e.g. [6]. Headbomb {t · c · p · b} 16:28, 18 February 2025 (UTC)[]

that's will take some time. AManWithNoPlan (talk) 02:09, 28 February 2025 (UTC)[]

Also cosmetic [7]. Headbomb {t · c · p · b} 07:18, 20 February 2025 (UTC)[]

Hi, new here, not sure if this is the right place, but this looks like the same problem (or a very similar one): https://en.m.wikipedia.org/w/index.php?title=Fundamental_theorem_of_calculus&diff=prev&oldid=1288133688 — Preceding unsigned comment added by 158.121.180.24 (talk • contribs) 20:19, 30 April 2025 (UTC)[]

No, that is the bot confusing a book review with the book under review and garbaging a citation to a book by mashing it up with metadata from the book review. It is a severe bug but not the same bug. —David Eppstein (talk) 20:46, 30 April 2025 (UTC)[]

I can't think of a good way to distinguish between review and original work, given some review have all the same metadata that the original work has. In some cases, the review is in fact what is being cited. If possible, I would recommend raising a red flag to signal more careful human review is needed in some cases, such as when the word "review" (or in this case "Books Received") is found on the destination page or perhaps in certain database fields. This red flag might be raised gratuitously in the case of say, literature reviews, but hopefully not enough to produce alert fatigue. -- Beland (talk) 22:07, 2 May 2025 (UTC)[]

Seems due to bad metadata. Headbomb {t · c · p · b} 20:37, 9 May 2025 (UTC)[]

Unfortunately, the diff is no longer accessible, so we can't diagnose the bug anymore. Tagging this for archiving to clean up the talk page. New bug reports will be handled faster to prevent issues like this. --Redalert2fan (talk) 15:37, 28 December 2025 (UTC)[]

In that draft, Citation bot changed this:

{{cite book | last1=Judet | first1=Pierre | date=2014 |chapter=La "Savoie industrielle". Des territoires industriels en mouvements |trans-chapter=The "Industrial Savoy". Industrial territories in motion |chapter-url=https://shs.cairn.info/histoire-economique-et-sociale-de-la-savoie--9782600018289-page-245?lang=fr | title=Histoire économique et sociale de la Savoie de 1860 à nos jours |trans-title=Economic and Social History of Savoy from 1860 to the present | series=Publications d'histoire économique et sociale internationale |publisher=Librairie Droz | pages=245–297 | doi=10.3917/droz.varas.2014.01.0245 | isbn=978-2-600-01828-9 }}

Judet, Pierre (2014), "La "Savoie industrielle". Des territoires industriels en mouvements" [The "Industrial Savoy". Industrial territories in motion], Histoire économique et sociale de la Savoie de 1860 à nos jours [Economic and Social History of Savoy from 1860 to the present], Publications d'histoire économique et sociale internationale, Librairie Droz, pp. 245–297, doi:10.3917/droz.varas.2014.01.0245, ISBN 978-2-600-01828-9

to this:

{{cite book | last1=Judet | first1=Pierre | date=2014 |chapter-url=https://shs.cairn.info/histoire-economique-et-sociale-de-la-savoie--9782600018289-page-245?lang=fr | chapter=Histoire économique et sociale de la Savoie de 1860 à nos jours |trans-chapter=Economic and Social History of Savoy from 1860 to the present | series=Publications d'histoire économique et sociale internationale |publisher=Librairie Droz | pages=245–297 | doi=10.3917/droz.varas.2014.01.0245 | isbn=978-2-600-01828-9 }}

Judet, Pierre (2014), "Histoire économique et sociale de la Savoie de 1860 à nos jours" [Economic and Social History of Savoy from 1860 to the present], Publications d'histoire économique et sociale internationale, Librairie Droz, pp. 245–297, doi:10.3917/droz.varas.2014.01.0245, ISBN 978-2-600-01828-9 {{cite book}}: Missing or empty |title= (help)

—Trappist the monk (talk) 15:50, 28 December 2025 (UTC)[]

thanks, so the original trans-chapter and chapter are removed and the present title and trans-title is changed to trans-chapter and chapter. Redalert2fan (talk) 16:12, 28 December 2025 (UTC)[]

Previous title did contain an error, but new one was worse. This comes from Archive title code. Will look at. AManWithNoPlan (talk) 10:59, 27 June 2025 (UTC)[]

Once we can migrate to PHP 8.4, this will get MUCH better. AManWithNoPlan (talk) 19:58, 1 July 2025 (UTC)[]

@AManWithNoPlan Since we are on PHP 8.4 now, is this fixed? Redalert2fan (talk) 14:50, 11 December 2025 (UTC)[]

@Redalert2fan Hmm, kind of? It's different, but still not right... Jay8g [V•T•E] 22:25, 11 December 2025 (UTC)[]

Same annoying and pointless cosmeticbot behavior still happening nearly a week later: Special:Diff/1301704057, Special:Diff/1301703128 —David Eppstein (talk) 07:32, 21 July 2025 (UTC)[]

Headbomb {t · c · p · b} 01:22, 6 August 2025 (UTC)[]

Should apply to everything that looks like a hyphen in the 5th position, the non-breaking hyphen, endash, emdashes, double hyphens, etc... Headbomb {t · c · p · b} 01:25, 6 August 2025 (UTC)[]

I've noticed this as a semi-frequent pattern. Headbomb {t · c · p · b} 17:35, 25 August 2025 (UTC)[]

To be explicit, the journal name previously used a non-breaking hyphen character (‑) and Headbomb wants an ordinary hyphen (-) instead. The latter is more appropriate because it's fine to put a line break in the name Eighteenth‑Century Studies after "Eighteenth‑". This seems like a very low-priority change that should probably only be done when bundled with other changes. –jacobolus (t) 18:44, 3 September 2025 (UTC)[]

This would affect ~5 articles every month or so. Require bundling with other changes would be pointless, the point is to get rid of those editor-hostile oddities in citations. Headbomb {t · c · p · b} 20:09, 3 September 2025 (UTC)[]

The bot should not be making edits such as special:diff/1309371869 ("Suggested by Headbomb"). It is not important whether or not the citation template has a space before the final }}. The bot should not adjust whitespace like this at all (leave it to humans if someone cares), but it's especially obnoxious if there's no meaningful change whatsoever. –jacobolus (t) 18:23, 3 September 2025 (UTC)[]

Indeed. Headbomb {t · c · p · b} 18:24, 3 September 2025 (UTC)[]

Both linked and unlinked should be TNT'd. Headbomb {t · c · p · b} 01:15, 12 September 2025 (UTC)[]

Also in this edit the URL should have been added as a |chapter-url=. Jonatan Svensson Glad (talk) 14:49, 21 September 2025 (UTC)[]

The bot could be made to make the edit that you requested, but it can't know for all cases if somebody actually intended to cite the webpage or the book. Therefore, I don't think it would be smart to implement it. --Redalert2fan (talk) 21:04, 26 December 2025 (UTC)[]

@Headbomb: I see that Advances in Enzymology and Related Subjects of Biochemistry is indeed not a journal, but shouldn't it be the series? Although in that case the title and series will become the same like this edit.--Redalert2fan (talk) 19:11, 18 October 2025 (UTC)[]

There's bad metadata somewhere, which makes this particularly annoying. The last time I checked, and it was a while back, Advances in Enzymology and Related Areas of Molecular Biology and Advances in Enzymology and Related Subjects of Biochemistry are the same title/series/whatever, the series just got renamed as some point and you end up with titles from different era in the metadata. I don't remember which is new and which is old, or when the switch happened. Headbomb {t · c · p · b} 19:18, 18 October 2025 (UTC)[]

Ah I see, that makes it quite hard to sort it out correctly, I missed that they are actually not the same in the edit in my sandbox. Advances in Enzymology and Related Areas of Molecular Biology was already on the list for not a journal. I've added advances in Enzymology and Related Subjects of Biochemistry to the list so atleast it won't be added as a journal anymore.

Because of the bad metadata there probably are indeed more instances (or will be) where the title is one of them and the series is the other. That's not something I can fix. Redalert2fan (talk) 19:34, 18 October 2025 (UTC)[]

See User:Monkbot/task 21: Replace page(s) with article-number

Headbomb {t · c · p · b} 16:26, 26 September 2025 (UTC)[]

--JBL (talk) 20:20, 24 October 2025 (UTC)[]

This seems like a very similar issue to one raised several months ago. Stepwise Continuous Dysfunction (talk) 18:54, 26 November 2025 (UTC)[]

Well, I did try to look through the old but still-open bug reports to find a match, but there are so many... —David Eppstein (talk) 19:08, 26 November 2025 (UTC)[]

@David Eppstein: Good news, this bug appears to be fixed -- see this test edit based on the diff in your example. Jay8g [V•T•E] 05:42, 30 November 2025 (UTC)[]

You also tested examples where the title= was the book title and the work= was a book series, and all the other permutations, I hope? Just getting this one example right isn't enough to be convincing. —David Eppstein (talk) 05:47, 30 November 2025 (UTC)[]

Well, you'll have to find some examples of that... Jay8g [V•T•E] 06:29, 30 November 2025 (UTC)[]

So no, then. In that case I don't consider the bug fixed.

If you're going to convert cite web to cite book you need all cases correct, not just the one case that triggered the bug report.

Here's an example where cite web should be converted to cite book with the cite web title => contribution and the cite web work => series (and with the book title missing and to be filled in) from Wikidata (where it is given in CS2 form but with the cite web parameter set): Erxleben, Fredo; Günther, Michael; Krötzsch, Markus; Mendez, Julian; Vrandečić, Denny (2014), "Introducing Wikidata to the Linked Data Web", Lecture Notes in Computer Science, Cham: Springer International Publishing, pp. 50–65, doi:10.1007/978-3-319-11964-9_4, ISBN 978-3-319-11963-2, retrieved 2024-08-18

And here's an example where the conversion should go title => title and work => series, from Ricci curvature (where again it is in CS2 form but with the cite web parameter set): Najman, Laurent; Romon, Pascal (2017), "Modern approaches to discrete curvature", Lecture notes in mathematics, Springer (Cham) —David Eppstein (talk) 06:37, 30 November 2025 (UTC)[]

This is what the bot currently does for the first example diff and for the second example no changes will be made. Please check if this is the expected behaviour for the first example. For the 2nd example, since nothing was broken further because nothing was edited that should not be considered a bug in my opinion.

And for housekeeping, even though the exact instance from the report has been fixed since there is some discussion I have removed the fixed tag to prevent archiving. --Redalert2fan (talk) 10:58, 30 November 2025 (UTC)[]

First diff: Incorrect. "Lecture Notes in Computer Science" is the name of a book series. It should not be put into the title parameter. The correct book title is "The Semantic Web – ISWC 2014" or maybe a longer version

"The Semantic Web – ISWC 2014: 13th International Semantic Web Conference, Riva del Garda, Italy, October 19-23, 2014. Proceedings, Part I". This is not in the citation as given (that was the point of giving this example) but the bot should be able to figure it out from the doi. —David Eppstein (talk) 20:12, 30 November 2025 (UTC)[]

Prior to 2025-09-26 the article "Paracelsus" had a "cite book" reference that had parameters "|orig-year=1894" and "|publication-date=1976", but no "|date=" parameter.

On 2025-09-26 07:25 UTC Citation bot modified "|orig-year=1894" to "|year=1894". This caused an ISBN/Date incompatibility error. It should have modified the "|publication-date=1976" parameter.  ~2025-33904-40 (talk) 16:40, 30 November 2025 (UTC)[]

Diff. The second citation. –Novem Linguae (talk) 17:47, 30 November 2025 (UTC)[]

The bot is temporarily limited to editing one page (per user) at a time by the maintainers. This is on purpose per unblock discussion. Single page request should work. Category runs or linked from should not work.

Redalert2fan (talk) 22:06, 2 December 2025 (UTC)[]

to clarify, this is for after the bot is unblocked. Redalert2fan (talk) 22:53, 2 December 2025 (UTC)[]

One of the thoughts behind this is that it is easier to spot incorrect edits / bugs due to the lower maximum volume of edits. It should trigger users to be more careful. Therefore it would be helpful if users pay more attention and check the web interface and the edits that are made.

The idea is to improve the citations, and more correct edits at a slower rate is preferential to a high rate of edits without verification that contain unreported bugs. Redalert2fan (talk) 00:17, 31 January 2026 (UTC)[]

Could be API interaction or the order the bot executed the code due to the citations not being exactly identical that gives the different result.Redalert2fan (talk) 22:50, 30 December 2025 (UTC)[]

As I said on my talk page, I'd be interested to see a consensus somewhere that says that these identifiers shouldn't be included since they can be helpful in cases of linkrot, and there is really no downside to including them. Note that WP:ELNO does not apply to references, and #1 does not say what you seem to be claiming it says. Jay8g [V•T•E] 22:43, 9 December 2025 (UTC)[]

We can distinguish ids as (1) providing a copy of the reference itself, like most dois and some bibcodes, (2) providing a review or abstract of the reference, like MR and zbl, (3) providing nothing beyond the same metadata that is already in the reference, like the ones added in this report. There have been many past discussions on the uselessness of type (3) ids. They do not help readers in cases of linkrot because they provide no different links than the ones here. They do not help readers at all. They merely annoy readers by sending them to a web page that doesn't help them read the reference, and by making it harder for them to find a link that actually goes to the reference. There have been many past discussions on this issue. See e.g. User talk:Citation bot/Archive 41#Useless bibcodes redux and User talk:Citation bot/Archive 42#Bad pmid. But more to the point, see WP:BRD: when your bad edit was reverted, the onus was on you to establish a consensus for the change, rather than just repeating your bot edit to ram it through without consensus. —David Eppstein (talk) 23:26, 9 December 2025 (UTC)[]

Discussion started at Wikipedia_talk:Citing_sources#Does_WP:CITEVAR_prohibit_adding_metadata_to_citations?. Jay8g [V•T•E] 23:52, 9 December 2025 (UTC)[]

• Reported by @Trappist the monk: who noted and undid some sort of error or errors with chaper-url vs chapter vs title. Oddly, the bot's edit summary mentions an "osti" but no osti is changed. Also, the red error text in the citations of that revision says "More than one of |contribution-url= and |chapter-url= specified; More than one of |contribution= and |chapter= specified." but no |contribution-url= or |contribution= fields exist in the citations. Abductive (reasoning) 20:49, 10 December 2025 (UTC)[]

  Umm, I think that you are mistook. Following the bot's edit, This template, has both of |contribution= and |chapter= and has both of |contribution-url= and |chapter-url=. In the wikitext, Ctrl+F search for CITEREFQFFDB Fault 573. Because |contribution= and |chapter= are aliases of one another, only one of those parameters is allowed in any single cs1|2 template. The same restriction applies to |contribution-url= and |chapter-url=.

  As part of that same edit, the bot added |osti=10105840 to this template. In the wikitext, Ctrl+F search for 10105840.

  —Trappist the monk (talk) 23:52, 10 December 2025 (UTC)[]

  Well, there's the report from the field. Abductive (reasoning) 04:11, 11 December 2025 (UTC)[]

It is not always the case that broken dois should be removed. Sometimes they are correct and later become unbroken. So deleting the broken doi would only be acceptable if this process results in finding a replacement doi. —David Eppstein (talk) 08:40, 14 December 2025 (UTC)[]

Agree. I think what Johnjbarton is suggesting here is that Citation bot could in flight look for replacement/valid DOIs for those marked as broken, and replace any found. Then any broken DOIs with no replacement found are left as is. I expect in some cases this will work, but I think most DOI breakage is the link not working but crossref metadata still present and pointing at that DOI i.e. there is no replacement DOI available and it needs journal publisher side fix to their website/database. Rjwilmsi 09:15, 14 December 2025 (UTC)[]

I've encountered three ways the DOI can fail:

1. bad wikipedia value. Personal experience this is the most common.
2. bad DOI database value added by publisher
3. bad publisher website (eg mis-parsing their own URL)

Of course I suppose that a publisher site could simply go away but I've not seen that.

Is there a way to create a list of (broken-DOI/ resolved URLs)? Johnjbarton (talk) 16:37, 14 December 2025 (UTC)[]

I'm not sure why, but on this article the bot has twice converted a "cite web" reference to the RP Photonics Encyclopedia into an inappropriate "cite journal" reference. The site is not a journal. RP does however have DOIs. Is the bot assuming that anything with a DOI must be a journal? That is a poor assumption.--Srleffler (talk) 04:37, 5 January 2026 (UTC)[]

This should convert to {{cite encyclopedia}}, yes. Headbomb {t · c · p · b} 06:12, 5 January 2026 (UTC)[]

Need to investigate if this is just this specific encyclopedia that is wrongly converted, if we need to add it to the data list or if the bot is indeed making a poor assumption based on the DOI. I think there is more encyclopedia stuff reported. --Redalert2fan (talk) 08:45, 5 January 2026 (UTC)[]

@Redalert2fan: Citation Bot used to do this a lot for reasons I could never figure out (it doesn't seem to be related to the DOI). I think the fix was the insanely large NON_JOURNAL_WEBSITES list. Jay8g [V•T•E] 20:06, 6 January 2026 (UTC)[]

It appears that you're using the references more like external links than as references to support specific claims in the article. Also, yes, titles are required for citations; I don't think you're going to get support for removing that requirement (it is certainly not a bug). Jay8g [V•T•E] 19:53, 6 January 2026 (UTC)[]

I don't have a stong feeling about the use of citations vs. links or other aspects of style on History of Programming Languages (conference): I just opted to conform with the style it had before I got there, as I mostly just wanted to add some important missing material, not rework the page. If anyone wants to do such a rework I'm unlikely to object (though I do seem to recall reading that the current consensus tends to favour moving things out of bare hyperlinks into references more than the reverse?) The page certainly needs plenty of work, including the addition of full lists of HOPL I-IV papers with links and/or citations.

But in any case this is not relevant to the bug reported here. The HOPL IV page on the ACM's HOPL website simply is not the HOPL IV issue of PACAMPL or even the webpage for the HOPL IV issue of PACAMPL. They're different things with different citations, and Citation bot obviously should not conflate one with the other.

On the issue of {{cite journal}} Title entries, the problem is that for the most part, individual (whole) issues of academic journals just do not have titles; and a description put together from other bits of citation info is not a title and so can't be offered as one. Now if there were explicitly a consensus that an unstructured text citation can be put in the place of a non-existent title in Title, that would be one thing. But what sign is there of such a consensus? Neither Template:Cite_journal#Title nor Help:Citation_Style_1#Titles_and_chapters even contemplate it.

(All that being said, the specific issue of PACMPL which was cited does have an issue name rather than just an issue number, and that is arguably an issue title or close enough to one, so I have made that the Title in the citation. However this does not resolve the general Citation bot bug reported here: most journal issues do not have names, and in any case the issue name is not the text which got put into Title.) RW Dutton (talk) 18:42, 29 March 2026 (UTC)[]

Closing. Redalert2fan (talk) 11:29, 29 March 2026 (UTC)[]

Please don't close this discussion yet. I do apologise for my slow response, but I've been largely away from WP for a while. RW Dutton (talk) 14:44, 29 March 2026 (UTC)[]

Okay. Redalert2fan (talk) 15:27, 29 March 2026 (UTC)[]

Thanks for this.RW Dutton (talk) 18:44, 29 March 2026 (UTC)[]

Can we please get the bot to stop adding book series and series volume numbers in general, unless they are used consistently among the citations on a particular page and obviously desired by the human editors there? Most of the time writing the book series adds significant clutter without adding reader-relevant value (it's a piece of trivia which is largely irrelevant and does not help the reader locate the book, except in relatively rare examples). –jacobolus (t) 20:08, 29 January 2026 (UTC)[]

Books series and volume should be added when the bot can figure them out. The LNCS volume for instance, is absolutely relevant. Headbomb {t · c · p · b} 20:12, 29 January 2026 (UTC)[]

Also Abductive. Stepwise Continuous Dysfunction (talk) 19:38, 29 January 2026 (UTC)[]

Flipping first and last names seems like it would be error-prone (I imagine it would be roughly as likely for the metadata to be messed up as for the citation in Wikipedia to be messed up, and that's without getting into the issue of different name formats in different countries). Jay8g [V•T•E] 08:16, 26 January 2026 (UTC)[]

Let's please not get the bot trying to replace "at=pp.." to "pages=". Such change has no practical benefit, and lots of edge cases where it could screw up. In particular, "at=pp.." is helpful when including a hyperlink to the page, because it gives a bigger click target for readers, and also "at=§ X, pp. y–z" is routinely helpful. –jacobolus (t) 20:04, 29 January 2026 (UTC)[]

Changing the names around was already decided previously as something we wouldn't do, complex to implement since some languages/scripts do it exactly oposite of each other, and there will be a lot of false positives.

The actual feature request can be implemented, but seeing there is some oposition to it, it should probably be decided first if it is desirerd or not. --Redalert2fan (talk) 15:10, 30 January 2026 (UTC)[]

Ah that's pretty annoying. Going to have to look in to that deeper. --Redalert2fan (talk) 14:27, 26 January 2026 (UTC)[]

It is because bioRxiv and medRxiv are in TEMPLATES_WE_BARELY_PROCESS (name explains itself) not in TEMPLATES_WE_PROCESS (web,news,journal etc.). In TEMPLATES_WE_PROCESS the bot expands, normalizes, and corrects citations with much more “intelligent”/full logic. The logic in this path is designed to suppress edits where only cosmetic changes (including template name capitalization) are present. Unfortunately we can't simple move bioRxiv and medRxiv there. This type of edit will need to specifically be supressed. — Preceding unsigned comment added by Redalert2fan (talk • contribs) 14:40, 26 January 2026 (UTC)[]

That Idea turned out to be not correct. Redalert2fan (talk) 17:45, 26 January 2026 (UTC)[]

only removing |work= as in diff should probably not be done just by itself if there are no other changes. Redalert2fan (talk) 16:00, 26 January 2026 (UTC)[]

On COVID-19, Citation bot keeps adding a display-authors= parameter to one of the references even though there is a cs1 config|display-authors template at the top. This causes a CS1 maintenance message: "CS1 maint: overridden setting". I've reverted Citation bot at least twice on this article but it keeps doing this. This may have happened on other articles too. Velayinosu (talk) 00:06, 29 January 2026 (UTC)[]

Two instances out of three that I see in the history were by Abductive. Stepwise Continuous Dysfunction (talk) 20:06, 29 January 2026 (UTC)[]

Same thing happening over and over again at Ancient North Eurasian. -- LCU ActivelyDisinterested «@» °∆t° 15:43, 10 February 2026 (UTC)[]

Another bad edit unsupervised by User:Abductive. —David Eppstein (talk) 01:45, 30 January 2026 (UTC)[]

The edit looked fine to me. How would an observer deduce that it was bad looking at the diff? Abductive (reasoning) 01:47, 30 January 2026 (UTC)[]

@Abductive: You can install this . Headbomb {t · c · p · b} 01:59, 30 January 2026 (UTC)[]

Okay, I installed it, but isn't the difference between these styles cosmetic? Abductive (reasoning) 02:07, 30 January 2026 (UTC)[]

Ideally {{citation}} would be best, but an alternative solution would be to use {{cite web|mode=cs2|...}}.

The cite preprint templates {{cite arXiv}}, {{cite SSRN}}, {{cite bioRxiv}}, {{cite medRxiv}} with |mode=cs2, would always be better to use than {{citation}} though. Headbomb {t · c · p · b} 01:56, 30 January 2026 (UTC)[]

Not necessary to set |mode=cs2 in individual templates when {{CS1 config|mode=cs2}}. When you do, cs1|2 will add the article to Category:CS1 maint: overridden setting.

—Trappist the monk (talk) 02:10, 30 January 2026 (UTC)[]

For those templates I agree, but this one was a cite web. —David Eppstein (talk) 02:40, 30 January 2026 (UTC)[]

Not that the edits are individually noticeable as bad, but the whole point of the exercise here is to catch the bot's mistakes—and fix them to make a better bot. Humans should not have to clean up the bot's mess, nor a human's mess if the bot can do it. Abductive (reasoning) 21:13, 30 January 2026 (UTC)[]

You trigger the bot, you're responsible to check its edits. Headbomb {t · c · p · b} 05:18, 1 February 2026 (UTC)[]

The question then becomes: Was it actually fixed last time and did something change causing it to return? Is this a slightly different issue than what was fixed before? Or did the maintainer think they fixed it but apparently they did not? (these are just some thoughts from me). Don't want to pressure you with too much of a search, but if you happen to know the previous report that you are referring to it can be useful for reference. Unfortunately the historical descriptiveness of GitHub pull requests for citation bot is rather lacking, so what the "fix" might have been previously will also be a bit of a search if this is a returning issue. Redalert2fan (talk) 00:26, 31 January 2026 (UTC)[]

See User talk:Citation bot/Archive 1 § Bot replaces book reference by journal's book review, User talk:Citation bot/Archive 23 § Book vs book review, User talk:Citation bot/Archive 24 § Bot mangles book citation in today's DYK by merging in metadata from journal review of book, and User talk:Citation bot/Archive 18 § Books and their reviews for four different supposedly-fixed instances of the same sort of problem. —David Eppstein (talk) 01:45, 31 January 2026 (UTC)[]

It could be very well that those instances were indeed fixed, looking at it it seems to be a rare bug indeed since the last report was from you in 2020, although ofcourse that doesn't discount the possibility that it hasn't been happening without anyone noticing. Looking on Github there is indeed code that tries to catch this specific issue, and from the archives it seems to have been made more restrictive over time.

It works uses a scoring system based on the presence of various typical book (and review) citation parameters. If the score is 3 or higher it will think it is a book review.

Investigating this one: The bot correctly detected that the original citation was not a book review using the scoring system, it got a score of 2, therefore it correctly then tried to expand the data for the normal book using the API. But the API incorrectly gave it the data from the book review! After it got that incorrect data the scoring system now gave it a score of 0 and because of that proceeded to add the data.

The question is why did the scoring system give it an even lower score even though the proposed output has more paramters that are consistent with a review? That is the part that needs to be looked in to and fixed. Redalert2fan (talk) 14:02, 31 January 2026 (UTC)[]

Going deeper, it seems like that the code gives a negative 2 score to journal, which is a more likely book review item even though we want to block scores above 3. And it gives positive scores to all items that are present in books. There is probably something wrong with the scoring system or the logic is switched around. A citebook with just an ISBN will get +5 but that is not a book review for sure. Currently a citebook with a journal (which is not even allowed) would end up with a score of 1. Redalert2fan (talk) 15:24, 31 January 2026 (UTC)[]

Bug tracked at: https://github.com/ms609/citation-bot/issues/5420 Redalert2fan (talk) 11:26, 15 February 2026 (UTC)[]

There is code for handling "normal" math which may change current titles. There is special code that actually enforces correct "LaTeX" formatting when adding new titles, I added that some time ago. That new code is explicitly not allowed to edit current LaTeX formatted math even if the current form is wrong, it will throw a warning to the user to check the formatting even though it can succesfully fix it. Running this citation by itself does not give any math related warnings.

The issue here is that the bot fetches data (using the crossref API) which gives the title as "The length of an ''s'' -increasing sequence of ''r'' -tuples" and overwrites the current title - you can verify it if you empty the title parameter and run the bot, it adds the incorrect version. So the bot does not see that the title is similair enough for it to not change it, it thinks the original title and the one it is trying to add are completely different and picks the new one. So there was actualy no math "handling" done on this citation. The title recognition logic needs to be updated.

If the bot thinks the current title and the fetched title are completely different, there is a high likelihood of one or both being problematic in a way that the bot cannot resolve. It should refuse to edit and raise an alert for human attention. It should certainly not guess that it is right and whoever put that title there in the first place was somehow mistaken in doing so. This is especially true for titles containing mathematics formatting for which it is very likely that the online metadata formats the mathematics badly and that the Wikipedia editor who added the citation has corrected the formatting already. —David Eppstein (talk) 22:08, 31 January 2026 (UTC)[]

I actually think for this instance it does not need to give a warning, it should just not have made the edit at all. Correction for this bug is to not overwrite titles using <math>.

And to re-iterate this is not a function of handling of math formatting, the bot can recognise actually poorly formatted mathml mathematics and convert it to correct LaTeX. It does this when adding new titles (no title present), and it warns users for existing poor formatting that should be converted. Titles received from API using incorrect mathml will be recognised so if a user already corrected them to LaTex they will already not be overwritten. Redalert2fan (talk) 22:46, 31 January 2026 (UTC)[]

Further investigation: diff When the citation already contains the journal it keeps the title. Redalert2fan (talk) 23:14, 31 January 2026 (UTC)[]

How we got it is displayed when using the web interface:

>Consult APIs to expand templates

>Using Zotero translation server to retrieve details from URLs and identifiers

>Retrieved info from https://arc-cbbc.nl/2020/05/marjolein-dijkstra-receives-an-erc-advanced-grant/

+Adding work: ARC CBBC

+Adding last1: Heus

+Adding first1: Anne-Lot de

Now where Zotero gets that data from I can't quickly see, a quick page inspection does not have it in the metadata and visually checking an archived version on the wayback machine does also not display an author. --Redalert2fan (talk) 22:16, 31 January 2026 (UTC)[]

This response reflects what I see as a continuing and problematic attitude that when Wikipedia and outside sources like Zotero differ, then Wikipedia is always wrong and Zotero is always right. That is simply untrue. Zotero is as far as I know mostly user-generated content like Wikipedia with no greater reliability than Wikipedia. It should not override Wikipedia content.

If this sounds testy, it is because my watchlist in the last few days has consisted largely of Citation bot edits, checking those edits has consumed far too much of my editing time, and I have been finding far too high an error rate in those edits. Erroneous edits by Citation bot should be rare, so rare that I find at most maybe one a month or so. When I find many different errors in one day or a few days, it indicates that something has gone very wrong in Citation bot development and that the bot is turning into a net negative for the project, wasting more editor time than it saves. —David Eppstein (talk) 22:24, 31 January 2026 (UTC)[]

Not to discount any of the feelings about the bot you posted here, that is all fair.

The translation server from zotero is used to "to retrieve details from URLs and identifiers" - Quoting: "The Zotero Translation Server is a Node.js-based service that allows users to leverage Zotero’s translator library to extract metadata from websites, DOIs, or ISBNs " and "Zotero uses so-called “translators” to detect and import data from websites. For citation bot it is used to fetch webdata from the webpage, it does not use user-generated content. Redalert2fan (talk) 22:59, 31 January 2026 (UTC)[]

"Heus, Anne-Lot de" is the proper Dutch spelling. Not valid for Flanders, though. I asked this at Dutch wiki, since I'm not a native speaker of Dutch.

See nl:Wikipedia:De kroeg/Archief/20240902. tgeorgescu (talk) 02:30, 2 February 2026 (UTC)[]

Even as a native speaker of Dutch it is kind of strange, but correct indeed. So nothing to fix for that part. Will check the metadata issue. Redalert2fan (talk) 11:21, 29 March 2026 (UTC)[]

• This is for an 1873 article in Philosophical Transactions of the Royal Society of London. I believe that the volume is the year, and note that the bot did not add the year. I also note that the bot did not make this "correction" when it edited History of the metre in December, and there were no intervening edits. Abductive (reasoning) 22:04, 31 January 2026 (UTC)[]

I woke up this morning to find another 18 bad changes to work= (duplicating publisher or in some cases replacing publisher), on my watchlist alone: [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53]. I have blocked citation bot until this is changed to stop. Occasionally when publisher= already exists the addition of work= is a good change; far more often it is incorrect. At least one of these bad edits also included the problem of adding an author who is not the actual author of a piece of text but merely the staff member who uploaded it to a web page, already reported last March in § Far too aggressive in using hidden web page metadata and apparently never fixed.

There were many more useless bot edits adding bibcodes that do not provide any useful information, and at least one undo on my watchlist of such an edit by another editor; that is not a blocking offense in my mind but see Wikipedia talk:Citing sources § Proposal to stop adding Bibcode values to citations unless they provide information for an ongoing discussion that seems to be trending against doing that.

These were all at the initiative of User:Abductive and there have been suggestions above that Abductive be topic-banned from using Citation bot. Perhaps someone should start a WP:ANI thread to discuss that. But this problematic work= issue goes beyond Abductive's edits; if it weren't them it would be someone else. —David Eppstein (talk) 20:03, 1 February 2026 (UTC)[]

I looked at each one of the diffs that you provided. {{citation}} assumes (always has) that in the absence of a work parameter (|journal=, |magazine=, |newspaper=, |periodical=, |website=, |work=), the source it is citing is a book so renders the citation accordingly: the value in |title= is italicized. For example, this from Natalie Crawford (one of only three working urls among the listed diffs):

{{citation|url=https://www.usafa.af.mil/News/Article/619534/2012-thomas-d-white-national-defense-award-goes-to-rand-corporation-official/|title=2012 Thomas D. White National Defense Award goes to RAND Corporation official|date=November 15, 2013|first=Veronica|last=Ward|publisher=United States Airforce Academy|access-date=2023-03-19}}

Ward, Veronica (November 15, 2013), 2012 Thomas D. White National Defense Award goes to RAND Corporation official, United States Airforce Academy, retrieved 2023-03-19

If we follow that citation's title link, we see that the cited source is not a book but rather a news article on a website. A quoted upright title is the correct format for such sources. Replacing |publisher= with either of |website= or |work= instructs {{citation}} to render a properly formatted citation:

{{citation|url=https://www.usafa.af.mil/News/Article/619534/2012-thomas-d-white-national-defense-award-goes-to-rand-corporation-official/|title=2012 Thomas D. White National Defense Award goes to RAND Corporation official|date=November 15, 2013|first=Veronica|last=Ward|website=United States Airforce Academy|access-date=2023-03-19}}

Ward, Veronica (November 15, 2013), "2012 Thomas D. White National Defense Award goes to RAND Corporation official", United States Airforce Academy, retrieved 2023-03-19

I random-sampled three of the listed articles with dead urls:

Xiaoyu Luo: dead link archive snapshot

Sharon Goldwater: dead link archive snapshot

Sylvia de Neymet: dead link archive snapshot

None of those sources are books so using {{citation}} in book mode is incorrect. For these three citations (and the Airforce Academy source), the bot, while perhaps imperfect in its execution, was correct in applying a work parameter for these sources. Perhaps that is also true for the others in your list?

—Trappist the monk (talk) 23:18, 1 February 2026 (UTC)[]

No, adding work=The Royal Society of Edinburgh to a citation that already includes publisher=Royal Society of Edinburgh (on Xiaoyu Luo) is not correct. It is redundant, uninformative, and misplaced because the royal society is an organization not the name of a work that they publish. If you think that this citation needs a work to satisfy some obscure formatting requirement, you are wrong and your opinion here is discountable. A dogmatic belief that a one-size-fits-all template is somehow calling this a book and formatting it wrong because of that is your belief only. And using a badly-programmed bot to enforce your wrong opinion to the exclusion of all others, grinding everyone else down with thousands of edits clogging up their watchlists, is the oppopsite of the consensus process that Wikipedia follows. This citation is merely a citation to a thing with a single-level title rather than a two-level title/work contribution/title (or whatever) pair of titles. If the citation template formats all such things as book, in a way that creates incorrect appearance of citations, then that is also a bug in the citation template but it in no way obviates the problematic behavior of Citation bot. And in this case the bot somehow conjured up the name of the work from a deadlink, so I am skeptical about the source of its information as well as about the quality of the results. An archived copy reveals that it would be reasonable (although, I believe, not necessary), to put work=Fellows. Needless to say that is not what the bot did. —David Eppstein (talk) 23:54, 1 February 2026 (UTC)[]

Again, Trappist is wrong on this, the US Airforce Academy is the publisher, not the website/work. Headbomb {t · c · p · b} 00:23, 2 February 2026 (UTC)[]

I fully support blocking the bot until these issues are addressed. The idea is to eventually allow free rein to all users to run massive jobs, which of course would exponentially increase the errors. Users would be getting blocked from using the bot every day. Abductive (reasoning) 00:29, 2 February 2026 (UTC)[]

I would also support a temporary indefinite block on the bot until we can address the above issues. It has caused some duplication errors in the past, especially with the work and publisher parameters. sjones23 (talk - contributions) 02:08, 2 February 2026 (UTC)[]

To be clear my block was intended only as temporary. It was indefinite only because I have no idea how long it might take to resolve these issues. —David Eppstein (talk) 08:38, 2 February 2026 (UTC)[]

That is clear, last time it was a 72 hour block that had to be changed in to an indefinite one untill fixed as well. Redalert2fan (talk) 14:49, 2 February 2026 (UTC)[]

Block reported on Github as well. Specific bug was already reported but nobody picked up fixing it (last check 1 Feb). Tracking added to this section. Redalert2fan (talk) 14:56, 2 February 2026 (UTC)[]

Is the idea really that we want to enable more large batches of unsupervised work? I'd rather the bot be available for small supervised edits than always getting banned because of the unsupervised edits run amok.   — Chris Capoccia 💬 00:06, 10 February 2026 (UTC)[]

Batch work is a godsend when you have targetted issues and worklists. The issue here is that Abductive constantly abuses that feature and sends the bot on unsupervised, unreviewed, untargetted random trawls. Headbomb {t · c · p · b} 00:40, 10 February 2026 (UTC)[]

It's also breaking {{citation|journal=}} by changing |title= to |chapter=. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 12:59, 2 February 2026 (UTC)[]

Are the various bugs listed in this section caused by newly added code, or are they bugs that have existed for a while and are only being reported now (presumably because of a sudden high number of them)? I ask because I am curious about the release and testing of new code. Is there a test page of citations that revised code runs against before being released? Or that could be used to agree on a desired outcome via discussion here? Mike Christie (talk - contribs - library) 13:26, 2 February 2026 (UTC)[]

The various bugs are most likely due to a lack of maintenance over the past ~2 years. The current maintainers do not seem to have the time to respond to and fix all the bugs. Anyone can help out on at: https://github.com/ms609/citation-bot should they be able to code in PHP. All proposed updates will/are still currently checked by @AManWithNoPlan

The test suite of the bot can be found at: https://github.com/ms609/citation-bot/tree/master/tests/phpunit/includes Redalert2fan (talk) 14:25, 2 February 2026 (UTC)[]

When the bot got blocked last time and I dived in to submitting patches to this repo, I was expecting it to be abandonware. Turns out the maintainer, AManWithNoPlan, is not very active on wiki but is extremely active on GitHub, constantly writing patches, approving patches (my patches all got merged within 1 day), and deploying the bot. So I would not say that this repo is inactive or that the maintainer is overwhelmed. I think it is well maintained.

The bot has an extremely big and thorough automated test suite. It takes over half an hour to run, running thousands of tests and testing external APIs. –Novem Linguae (talk) 19:07, 2 February 2026 (UTC)[]

The back end indeed is very well maintained, perhaps my message gave a wrong impression. I was intending to refer to bugs reported on this page.

And good news, the test suite no longer takes 30 minutes, it still does all the same tests as before but I managed to enable multiple process execution so it now only takes 7-8 minutes. Redalert2fan (talk) 19:20, 2 February 2026 (UTC)[]

Hehe no worries. I think it's normal for any complex software to have hundreds of open tickets, and for only the biggest bugs to get prioritized. –Novem Linguae (talk) 19:26, 2 February 2026 (UTC)[]

For the last few days before the block my watchlist was overrun by huge numbers of Citation bot edits. For the last day I can still see in its entirety on my watchlist, February 1, among still-visible changes on my watchlist, 90 out of 189 of the edits were made by Citation bot, mostly or entirely "Suggested by Abductive". The bot was blocked mid-day my time so the rate of changes was even higher on earlier days. It is unclear to me whether the greatly increased rate of problems was caused by changes to the bot code, changes to the underlying sources from which the bot draws its metadata, or just the extremely high rate of bot activity caused by Abductive's runs. —David Eppstein (talk) 18:45, 2 February 2026 (UTC)[]

Abductive's not the only one who used Citation bot. Some of us had to fix up some of the errors made after running that bot. sjones23 (talk - contributions) 18:49, 2 February 2026 (UTC)[]

That's why I said "still-visible changes". The 18 I linked at the top of this thread were from that day, for instance, but I didn't count them this time because they were no longer visible on my watchlist after edits by me and/or others. —David Eppstein (talk) 18:55, 2 February 2026 (UTC)[]

I figured that would be the case. sjones23 (talk - contributions) 18:56, 2 February 2026 (UTC)[]

Ok, I checked. 89 of the 90 were suggested by Abductive; one was by Headbomb (who I should say has always used the bot responsibly and not on the large-scale unsupervised fishing expeditions we tend to see from Abductive). —David Eppstein (talk) 19:01, 2 February 2026 (UTC)[]

"Some of us had to fix up some of the errors made after running that bot."

Yes, but because we unleash the article on specific articles, and we check after the bot, we catch and fix those as they come, and report issues as they arise. The occasional thing can slip by (as evidenced by DE's find above). You only have to look in the archives to find hundreds of my bug reports and tweak requests over the years. Abductive, OTOH, triggers the bot willy nilly on as many articles as possible and rarely if ever checks for errors. Headbomb {t · c · p · b} 21:49, 2 February 2026 (UTC)[]

Since the errors above all stem from {{citation}}, maybe the bot could temporarily stop touching {{citation}} while things are resolved? Headbomb {t · c · p · b} 21:50, 2 February 2026 (UTC)[]

That's not true of § issue and volume can't both be #163 and § Should not add useless nii.ac.jp and infoscience.epfl.ch urls above, at least. But there may be an observer effect here: I am reporting on things from my watchlist, which is disproportionately articles I have written, which disproportionately use Citation Style 2. The frequency of those issues among all articles may be very different. —David Eppstein (talk) 23:15, 2 February 2026 (UTC)[]

I mean there are other bugs, but they definitely disproportionally affect {{citation}}. The amount of bad edits I see accross articles using mainly CS1 style is well under 5%. And likely well under 1% too. Headbomb {t · c · p · b} 02:48, 3 February 2026 (UTC)[]

@Headbomb: In any case, the {{Citation}} part might need to be changed to match the appropriate online sources we've been using like {{Cite web}}, {{Cite news}}, {{Cite press release}}, {{Cite journal}} and so on. sjones23 (talk - contributions) 08:28, 12 February 2026 (UTC)[]

Some of this seems like really trivial bickering. For the first case above, Patricia Grambsch, does it really matter whether Mayo Clinic is publisher or work? If anything, the publisher is Mayo Foundation for Medical Education and Research and it doesn't seem that wrong to say the website is Mayo Clinic. Also the whole URL is a page not found. A little disputable annoyance about publisher vs work turns into a major issue because a particular editor is sending the bot off on thousands of articles and not checking anything. Is that really a constructive way to use the bot?  — Chris Capoccia 💬 01:00, 6 February 2026 (UTC)[]

Regarding the Mayo Clinic's website, it is a work published by Mayo Foundation for Medical Education and Research. sjones23 (talk - contributions) 08:12, 12 February 2026 (UTC)[]

I do think fully blocking the bot isn't super helpful when a lot of the issues are a bit semantic. Not being able to run the bot as it is, is a net-loss for the project. Lee Vilenski ^{(talk • contribs)} 21:15, 17 February 2026 (UTC)[]

Semantic issues are exactly the sort of decisions the bot should not be usurping from humans. And I think the bot is still available for individual edits, just not for the sorts of unsupervised and indiscriminate mass runs perpetrated by Abductive. —David Eppstein (talk) 22:15, 17 February 2026 (UTC)[]

If it is, it isn't where I'm clicking to use it. Run on a single page just says it is blocked. Lee Vilenski ^{(talk • contribs)} 22:55, 17 February 2026 (UTC)[]

You can invoke the bot yourself, see WP:UCB. Headbomb {t · c · p · b} 23:02, 17 February 2026 (UTC)[]

Oh, I usually use the web interface at [54] on a single page which doesn't work. Lee Vilenski ^{(talk • contribs)} 23:04, 17 February 2026 (UTC)[]

After the previous unblock the max pages was set to 1 - see "Bot limited to only single page request". This is why you were able to do (only) a single page request upon till this new block (and not multiple pages and categories).

Now that the bot is blocked again using the bot via the interface is not possible at all, even for single pages, since it uses the bots account.

However, you can use the functions of the bot via the citation expander gadget (see WP:UCB). Edits will be made under your account, you will get an edit preview to see the changes that will be made on the page you use the gadget. Redalert2fan (talk) 12:23, 18 February 2026 (UTC)[]

I get "Error: Citations request failed" when I use the gadget. Stefen 𝕋ower ^{Huddle • Handiwerk} 00:02, 19 February 2026 (UTC)[]

Did you enable the gadget, went to the page you want to work on, press "edit" to go to the edit window and then press the "citations" button? 👁 Image

When using the gadget you will not go to outside of wikipedia, you stay on the page you want to edit. "Error: Citations request failed" is a message only displayed on https://citations.toolforge.org/ if you run the bot directly from there or when you use the "expand citations" from the toolbar, because that activates the bot to run on that page.

If the gadget doesn't work (or there is nothing to fix) you will just get an edit preview with "(No difference)". Redalert2fan (talk) 12:46, 19 February 2026 (UTC)[]

The gadget was already enabled, and I did the rest, and got the error message. Stefen 𝕋ower ^{Huddle • Handiwerk} 21:05, 19 February 2026 (UTC)[]

On a specific page or on multiple pages? Redalert2fan (talk) 10:36, 20 February 2026 (UTC)[]

I ran it on Hunter S. Thompson. I tend to give up when it fails the first time. :) Stefen 𝕋ower ^{Huddle • Handiwerk} 20:52, 20 February 2026 (UTC)[]

Thanks for sharing the page, I see the error message as well now. That should not be happening, but is not related to the bot being blocked. Instead there is something on that specific page that causes the bot to fail and by extension the gadget as well. Redalert2fan (talk) 21:18, 20 February 2026 (UTC)[]

Thank you for reviewing that. Do you have any idea what that something could be so I can comb through the article for it? Stefen 𝕋ower ^{Huddle • Handiwerk} 21:28, 20 February 2026 (UTC)[]

I couldn't find anything quickly, but I've asked AManWithNoPlan if he can use debug on that page to see what is wrong. Redalert2fan (talk) 11:43, 21 February 2026 (UTC)[]

The file size (page size) was exceeded for the gadget. It has a lower limit than the bot itself to prevent time outs. The limit has been raised, so larger pages can be run with the gadget, but of course it is more likely that they will time out.

Why does the gadget time out more often on larger pages? Because webbrowsers will time you out, the bot does not have this issue. Redalert2fan (talk) 16:44, 21 February 2026 (UTC)[]

Thank you for the follow-up. I'll try this on some other articles soon. Stefen 𝕋ower ^{Huddle • Handiwerk} 20:19, 21 February 2026 (UTC)[]

so do I install the script to get this working on my own ...content editor find this very useful timesaver versus the trivial things that are being discussed that really relate to cosmetic edits. Moxy🍁 00:10, 19 February 2026 (UTC)[]

You can activate the gadget on your account or install the script, then you can use the "citations" button as explained above. That will make it so you get a preview of what the bot would propose to change on the page. Downside compared to the bot itself is that on pages with a lot of references it is slower and can time out, and that not all of the fixes that the bot can do will be made with the gadget. But in general it will work fine. Ofcourse, you are required to check the edits before publishing them. Redalert2fan (talk) 12:53, 19 February 2026 (UTC)[]

I see a lot of interest here from folks to get the bot unblocked. I would suggest that, to make this actionable, some combination of the following steps be performed:

• What to fix
  • Make progress on the reason the bot was blocked ("Issues with work parameter in templates"), either by commenting out the code causing this problem as a stopgap measure, or fixing it properly: https://github.com/ms609/citation-bot/issues/5301
  • Ask Abductive to stop using the bot, or topic ban them from using the bot, or harden the bot's defenses against mass usage. (May have already been partially done, since the bot can only be summoned to edit one page at a time now.)
• Who/how to unblock
  • Have a conversation with the blocking admin HJ Mitchell
  • Create a thread at WP:BOTN and work towards getting consensus and, if needed, a formal close (WP:ANRFC)

–Novem Linguae (talk) 03:05, 25 March 2026 (UTC)[]

• Since I've been mentioned, I will say what I've said before. This bot was checking approximately 5 articles a minute, and fixing something like 500,000 citations a year, and it couldn't keep up with the need. Over time, the error rate crept up from 'very low' to 'low', and corrective actions were not taken. If this bot is restarted with the underlying errors not fixed, users will complain again, and perhaps blame and demand the topic banning of whoever activated the bot, even if they reported the errors. One user even said that using the bot "randomly" was somehow bad. Abductive (reasoning) 06:26, 25 March 2026 (UTC)[]

  @Novem Linguae I'm not the blocking admin, I just disabled the autoblock. :) HJ Mitchell | Penny for your thoughts? 11:11, 25 March 2026 (UTC)[]

  Ah, misread. Looks like the blocking admin is David Eppstein. –Novem Linguae (talk) 11:20, 25 March 2026 (UTC)[]

  Yes. Has anything happened on issue 5301? And the reply above makes clear that "ask Abductive to stop using the bot" is not going to work because Abductive appears to believe that the only problem is bugs in the bot, not their indiscriminate use of it. —David Eppstein (talk) 16:56, 25 March 2026 (UTC)[]

What always happens is that editors discover the bot, and begin using it on categories and batches. Then more editors discover the bot, and pretty soon the bot is running nearly all the time. It must be made to be nearly error-free, or users will be calling for topic banning those editors too. Abductive (reasoning) 19:00, 25 March 2026 (UTC)[]

Categories and batches are specifically disabled by maintainers with the reasoning stated multiple times here on the talk page. But to re-iterate some of the reasons: Reducing the amount of edits so bugs can be handled better, and ensuring that users will be more likely to check their edits for bugs, since they either get the full bot output in the web interface or an edit preview using the gadget. Category and batch runs will not be activated until it is established that the maintainers (perhaps with help of others) can handle maintaining the bot.

I've stayed out of referring to individual users so far. But you have been using the single page request feature so often that it basically becomes a category or batch run. I think its safe to say you are the biggest user of this feature and for sure that doesn't have to be a bad thing per se, as long as you check your edits for bugs. But right now it is kind of counter to the intention of the feature, and since we are all well aware of the current state of the bot perhaps not what should be done. I think the only other big user of single page requests in the mean time is Headbomb, who frequently reverts bad edits and reports bugs they find.

Conclusion: With categories and batches disabled until the bot is working correctly, and intended (or good) use of the single page request, I can hardly see for calls for topic banning of other editors in the mean time. Redalert2fan (talk) 11:54, 27 March 2026 (UTC)[]

On categories... could the whitelisted ones at least be allowed? Category:CS1 errors: DOI or Category:CS1 maint: unflagged free DOI are highly unlikely to be problematic. Headbomb {t · c · p · b} 13:31, 27 March 2026 (UTC)[]

I`ll investigate that. I guess some of the maintenance categories we whitelist have been filling up, but usually they won't have a large amount of pages I assume. Just have to make sure we don't allow the bot to queue up a million pages by accident, since its going to have to bypass the normal page category limit. Redalert2fan (talk) 14:41, 27 March 2026 (UTC)[]

Pull: https://github.com/ms609/citation-bot/pull/5495

Will only work via direct URL activation, not pasting the category in the web interface. And bot will need to be unblocked first before this can be used. Redalert2fan (talk) 19:47, 27 March 2026 (UTC)[]

Implemented - Will need to see if you can use it after bot is unblocked. Redalert2fan (talk) 12:20, 28 March 2026 (UTC)[]

@Headbomb Looks like the whitelisted categories are working, right? Redalert2fan (talk) 07:26, 30 March 2026 (UTC)[]

So far, yes. Shame lists of pages aren't enabled yet, but I suppose it's just a limitation we'll have to live with unless/until they can be per-user disabled. Headbomb {t · c · p · b} 07:36, 30 March 2026 (UTC)[]

I think whitelisted categories is a good first initial test. Normal categories and lists we probably will raise step by step, but only if the bot behaves. I understand the wish and reasoning for per user disabling but I feel like that's not up to me to implement. Implementing a very basic allowance for certain users to bypass limits might be easier, as in "these specific users are okay to bypass the normal limit" and I think I can manage that. However, then there also needs to be a fair process for who gets to be on the list, and someone to manage it. Unfortunately something cool like IAbot has with usergroups is not something I can do. Ideal scenario is that the bot works good, and we just raise the limits. Redalert2fan (talk) 09:25, 30 March 2026 (UTC)[]

No pull request for 5301 have been submitted by anone, so it can be assumed that no work has been done on it. Redalert2fan (talk) 09:36, 26 March 2026 (UTC)[]

I`ll start with implementing the most basic fix which is to adjust add_if_new('work', ...) to not add work= when publisher= is already present for certain templates.

That should stop the bot from doing most of the things we grouped in to issue 5301. Since it is quite a broad and simple safety net it might cause us to loose out on some improvements on some citations, but I think getting the bot up and running again and possibly refining the handling later is preferred.

Will suggest to implement this and test it in the next few days. Redalert2fan (talk) 11:31, 27 March 2026 (UTC)[]

Update on the progress: Code adjusted to not add work when publisher is present. 12 different bug reports processed and implemented in the bot test suite. 11 passed and 1 marked as wont fix (not related to the block), 2 different work issues not related to block also fixed and included in the patch. Also added a warning in web interface to check publisher field for correctness if bot skips adding work. Tomorrow I will continue on with testing the 18 diffs provided in the initial block message above here. Should all pass in bot test suite I will submit the patch for approval, and then as a double verification test all the citations from the bug reports marked with Issue 5301 in my sandbox. After that I think an unblock could be considered. Redalert2fan (talk) 21:57, 27 March 2026 (UTC)[]

Split up in to 30 reports (30+ citations) and added to internal bot test suite on fork for testing. Let's see if they pass. Redalert2fan (talk) 20:48, 28 March 2026 (UTC)[]

Pull submitted for implementation: https://github.com/ms609/citation-bot/pull/5497

When implemented will test all reported citations in my sandbox with gadget to verify bot functions as expected. Redalert2fan (talk) 10:07, 29 March 2026 (UTC)[]

All citations from all issues related to 5301 triple tested. As far as I can see all fixed. Redalert2fan (talk) 17:53, 29 March 2026 (UTC)[]

• Investigated all work-related issues tagged with #5301 and split up into 30 different reports (30+ citations)
• Discovered Trivy, PHPStan and PHP Phan tests of bot suite were broken. Implemented fixes: PR #5492 and PR #5494. Bot test suite now functions correctly again.
• Implemented broad fix for block reason: when publisher= is present work= is no longer added. PR #5497
• Strip en-dash and pipe taglines from Zotero for publisher/Work – will prevent “promotional” sections being added. PR #5497
• Added specific override for sportsworldi.com PR #5497
• Added drive.google.com to ZOTERO_AVOID_REGEX – “Google Drive” was already blocked as a title, but now metadata from Google Drive will no longer be used for any automatic citation additions (was already present for Google Docs). PR #5497
• Fix for other block reason: Implemented suppression for Zotero incorrectly parsing eatcs.org posting admin as "author" PR #5497
• Added warning in the web interface for when bot skips adding author= when publisher= is present, asking users to check if the current use of publisher= is correct. This should attract attention to manually change publisher= to work= where appropriate. PR #5497
• Temporarily added citations from all reports as tests to the internal bot test suite to verify processing after the broad fix. 29 passed, one failed (issue with the test itself, now fixed). Afterwards condensed the number of tests to those needed to safeguard the new changes. PR #5497
• Tested all full articles included in reports submitted on talk page using &ignore_block=1 via web interface (cannot write, only shows what output would be) - Passed
• Pasted individual citations in my sandbox and used gadget to see edit preview. Expected outcome: “no difference” (or only changes without work= ) - Passed

I think the bugs for Issue 5301 should be fixed now. If more needs to be done let me known, and otherwise if somebody else could format an unblock request that would be great. --Redalert2fan (talk) 18:02, 29 March 2026 (UTC)[]

–Novem Linguae (talk) 02:07, 30 March 2026 (UTC)[]

• @HJ Mitchell: - okay to unblock? PhilKnight (talk) 02:50, 30 March 2026 (UTC)[]

  I think @David Eppstein was the blocking admin. HJ Mitchell just turned off autoblock since it's a bot. –Novem Linguae (talk) 04:17, 30 March 2026 (UTC)[]

  Ok, unblocked. As I wrote in my unblock edit summary, I think the changes (and especially not adding work= when publisher= is present) go a long way toward resolving the problems on the technical side. As I also wrote, the problems are also behavioral as well as technical (editors abusing the bot by making large indiscriminate runs and not checking the results) but those can be handled on an individual-editor basis. —David Eppstein (talk) 05:29, 30 March 2026 (UTC)[]

  Should any further technical issues related to this block pop up I have plenty of time this week to adjust things. Otherwise I'll try to pick up as many of the other ones in the mean time. Redalert2fan (talk) 07:22, 30 March 2026 (UTC)[]

The exact pattern can be tweaked...

https://onlinelibrary.wiley.com/doi/abs/10.1002/9780470132494.ch23 can be wiley.com ... ends in .ch# or has (whatever)/10.#/<ISBN13>.ch#

Headbomb {t · c · p · b} 08:42, 5 February 2026 (UTC)[]

|format=pdf is added by the template so is not needed. The authors are correct. The work/publisher bug is reported above. Headbomb {t · c · p · b} 04:04, 7 February 2026 (UTC)[]

Umm, |last1=John |first1=Gilliland is definitely wrong at ref 40 (permalink).

—Trappist the monk (talk) 19:10, 7 February 2026 (UTC)[]

It mixed last and first, yes. Headbomb {t · c · p · b} 01:06, 8 February 2026 (UTC)[]

Investigationn: UNT Digital Library metadata provides names in "Family, Given" order but Zotero misparses them, placing the family name in firstName and the given name in lastName Redalert2fan (talk) 13:56, 2 April 2026 (UTC)[]

[PR 5516] for the author swap. Redalert2fan (talk) 14:31, 2 April 2026 (UTC)[]

Swap works but another surprise was hidden in there. The existing swap handler corrected field order but left the trailing comma in lastName, causing format_author("Gilliland,, John") to lose the forename entirely. Working on further fix. Redalert2fan (talk) 19:19, 2 April 2026 (UTC)[]

PR 5517. Redalert2fan (talk) 22:20, 2 April 2026 (UTC)[]

* 10.1002/lol2. (L&O Letters) full open access Headbomb {t · c · p · b} 07:17, 12 February 2026 (UTC)[]

There's also for Limnology and Oceanography and subjournals

• 10.1002/lno. (If they are older than 3 years, e.g. February 2023) L&O
• 10.1002/lob. (If they are older than 3 years, e.g. February 2023) L&O Bulletin
• 10.1002/lom3. (If they are older than 3 years, e.g. February 2023) L&O Methods

*10.4319/lo. (all older than 3 years old, so all are free access) L&O

• 10.1002/loe2. (all older than 3 years old, so all are free access) L&O e-Lectures
• 10.4319/lol. (all older than 3 years old, so all are free access) L&O e-lectures
• 10.1215/21573689 (all older than 3 years old, so all are free access) L&O Fluids
• 10.1215/21573698 (all older than 3 years old, so all are free access) L&O Fluids
• 10.4319/lom. (all older than 3 years old, so all are free access) L&O Methods

Headbomb {t · c · p · b} 07:41, 12 February 2026 (UTC)[]

Also,

• 10.21105 (Open Journal) Headbomb {t · c · p · b} 18:17, 12 February 2026 (UTC)[]

Just to confirm I see you put 10.1002/lol2. here but 10.1002/lol2 (without the .) in Module:Citation/CS1/Configuration/sandbox, which one is correct? --Redalert2fan (talk) 20:37, 12 February 2026 (UTC)[]

same for loe2 Redalert2fan (talk) 20:43, 12 February 2026 (UTC)[]

With dots. I fixed it. Headbomb {t · c · p · b} 21:27, 12 February 2026 (UTC)[]

In the module, the incipits of the doi suffix are treated as lua patterns (similar to regex). In lua patterns, like regex, a dot matches any character. If you really mean lol2. instead of loc2a, for example, then the lua pattern should be lol2%..

—Trappist the monk (talk) 22:40, 12 February 2026 (UTC)[]

Tweaked. Dots is what is meant. Feel free to correct. Headbomb {t · c · p · b} 23:17, 12 February 2026 (UTC)[]

And I'm personally not sure if there is support for "If they are older than 3 years" as in If the bot checks that so I'm just holding off on those for now. --Redalert2fan (talk) 20:37, 12 February 2026 (UTC)[]

Look for code around PNAS dois, with prefix 10.1073/pnas. There's a 6 month embargo on those, which I believe the bot handles (implemented around Aug 2021). Headbomb {t · c · p · b} 21:29, 12 February 2026 (UTC)[]

Nothing for special DOI handling comes up after a quick search for PNAS. Only specific handling for this is fixing capitalization.

10.1073/pnas is not in the free DOI list either. It is on a list of DOI's that need to be periodically checked by a human. It also is used in the a single test of the test suite for PMID and PMC expansion from a DOI. But all those things do not seem relevant to any embargo. Redalert2fan (talk) 00:13, 13 February 2026 (UTC)[]

Well then let's make that a feature request. Headbomb {t · c · p · b} 02:10, 13 February 2026 (UTC)[]

Would probably require extra external API interaction(s) Redalert2fan (talk) 11:57, 13 February 2026 (UTC)[]

Patch for DOI's without any time limitations: https://github.com/ms609/citation-bot/pull/5476. Put a strike trough in the text above to mark which ones are done. --Redalert2fan (talk) 12:44, 13 February 2026 (UTC)[]

Start with moving Free DOIs out of bad_data and give them their own location. PR 5505 Redalert2fan (talk) 20:02, 30 March 2026 (UTC)[]

• Sangeetha, V. J.; Dutta, Sayantani; Moses, J. A.; Anandharamakrishnan, C. (2022), "Zinc nutrition and human health: Overview and implications", eFood, 3 (5) e17, doi:10.1002/efd2.17
• Berthou, Christian; Iliou, Jean Paul; Barba, Denis (2022), "Iron, neuro-bioavailability and depression", eJHaem, 3 (1): 263–275, doi:10.1002/jha2.321, PMC 9175715, PMID 35846210

Headbomb {t · c · p · b} 01:50, 19 February 2026 (UTC)[]

I need the incorrect spelling as well for both. Redalert2fan (talk) 12:57, 21 February 2026 (UTC)[]

Any that isn't eFood and eJHaem? Like Efood, EFOOD, EFood, or EJHAEM, EJHaem, Ejhaem, ... Headbomb {t · c · p · b} 15:13, 21 February 2026 (UTC)[]

The code is set up so that a specific incorrect capitalization from a list, case sensitive, gets replaced with the corrected capitalization. That is instead of a case of insensitive recognition. Could probably be done smarter, but it is not.

So to keep the list shorter as far as I see, only the specific incorrect capitalization made by the bot is added, instead of all possible incorrect capitalizations. Redalert2fan (talk) 16:39, 21 February 2026 (UTC)[]

Was added to specifically be a series back in 2019, see User_talk:Citation_bot/Archive_19#Better_series_handling:_Antibiotics_and_Chemotherapy. Not sure if that was your intention back then but the pull request that was implemented added Antibiotics and Chemotherapy to JOURNAL_IS_BOOK_SERIES forcing it to be a book series. I can remove it from there and it should be processed a a journal again. Let me know how to proceed. Redalert2fan (talk) 17:44, 21 March 2026 (UTC)[]

@Redalert2fan: I see.... the difference is that A&C with the DOI 10.1159/... is a book series from Karger, while A&C with the DOI 10.24411/... or 10.37489/... is the Russian journal. Headbomb {t · c · p · b} 18:20, 21 March 2026 (UTC)[]

Is one version a lot more common than the other? In the current configuration the bot doesn't have code to handle this. Redalert2fan (talk) 09:38, 26 March 2026 (UTC)[]

The series (10.1159/.) is much more commonly encountered. Headbomb {t · c · p · b} 10:18, 26 March 2026 (UTC)[]

Thanks, I'll have to think about implementing some special code to handle this one then Redalert2fan (talk) 21:59, 27 March 2026 (UTC)[]

Right now all 10.1140/epjc are marked free. This is my fault, only those after 2014 should automatically be tagged. I will be reviewing potential mistakes manually. Headbomb {t · c · p · b} 13:19, 29 March 2026 (UTC)[]

Understood, Automatic tagging depended on date is not implemented yet (as you requested earlier). I will remove 10.1140/epjc from the list until that is implemented. Redalert2fan (talk) 13:24, 29 March 2026 (UTC)[]

I know you're a bot, not a person but I thought I'd acknowledge your return to activity which I just noticed occurred two dqys ago. Thanks to all of the editors who helped patch up any problems that existed. Liz ^{Read! Talk!} 02:05, 2 April 2026 (UTC)[]

+1 Warm Regards, Miminity (Talk?) (me contribs) 13:31, 3 April 2026 (UTC)[]

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Citation_bot&oldid=1346888964"