Instead of using {{retracted|{{PMID|123456}}}}, the new code is {{retracted|pmid=123456}}. It also supports |bibcode=, |doi=, |pmid=, and |pmc=. Headbomb {
t ·
c ·
p ·
b} 18:00, 22 January 2019 (UTC)reply
@
Headbomb: Thanks for the heads up! Bot progress is still waiting on some conversations regarding the data source, but I hope to continue with development soon :)
Sam Walton (
talk) 18:12, 22 January 2019 (UTC)reply
I figured it'd just be more reliable to have dedicated parameters, and support multiple ones, than have a general
WYSIWIG field where people could put a lot of crap in it. Headbomb {
t ·
c ·
p ·
b} 18:16, 22 January 2019 (UTC)reply
@
Samwalton9: While the Retraction Watch thing is going on, you could also consider using PUBMED directly. It'll be medicine-centric, but it'll be a good start. For example
PMID23432189 links to a retraction notice at
PMID29897867 (and mentions an erratum in "N Engl J Med. 2014 Feb 27;370(9):886"). Likewise
PMID29307074 links to an erratum at
PMID30798464.Headbomb {
t ·
c ·
p ·
b} 09:06, 25 February 2019 (UTC)reply
@
Headbomb: Yes, that was my original plan - to create a fresh database by querying the Pubmed and Crossref APIs for papers flagged as retracted and keeping it updated. From my understanding, RetractionWatch take this data and do further cleanup to ensure that everything flagged as a retraction indeed is a retraction, and they therefore have a more reliable data source. That said, if I don't hear from them soon and find some time to work on this I'll go ahead with the original plan for now.
Sam Walton (
talk) 09:27, 25 February 2019 (UTC)reply
You might want to add support for this to the bot too. Headbomb {
t ·
c ·
p ·
b} 01:05, 16 February 2019 (UTC)reply
How to avoid an edit warring bot
Hi!
Is this enough to hinder the bot form tagging the same citation again, or is there some way to stop the bot from editing one specific citation again? (
t)
Josve05a (
c) 22:39, 28 April 2019 (UTC)reply
Great point on potential edit warring. I've disabled tomorrow's bot run and will ensure it won't edit war before restarting it. Hadn't considered this. I'm not sure about Outdated publication though - while it's a good idea I'm not sure how feasible it will be to have the bot be able to distinguish between that and a retraction given that the Crossref data (and their own definition) simply flags them as retractions. I'm a little confused by the undo, however. @
BallenaBlanca: As far as I can tell the tag was correct - Cochrane issued a retraction of
this review on the basis that it was outdated, and the retraction notice is located
here, so the
template links to the retraction notice (the latter). Could you explain what you mean by this not being the retracted article?
Sam Walton (
talk) 23:15, 28 April 2019 (UTC)reply
Hi! I understand that this can be confusing. I will try to explain it.
We have a 2008 Cochrane review. This is what the bot labeled by mistake. It is valid:
WITHDRAWN: Gluten- and casein-free diets for autistic spectrum disorder.
Millward C1, Ferriter M, Calver SJ, Connell-Jones GG.
But what happened? In reality, no new RCT was made since 2008. Therefore, this 2019 review did not bring anything new. That was the reason for its withdrawal.
@
BallenaBlanca: To clarify, the new revision (the second 'publication' linked there) is the retraction notice, right? As such, it's what the bot linked to. If we want to continue linking to a retracted article (in this case because it was only retracted due to being outdated), shouldn't the way forward be to use the |intentional=yes field of the retracted template, rather than reverting that template addition entirely?
Sam Walton (
talk) 09:00, 29 April 2019 (UTC)reply
"To clarify, the new revision (the second 'publication' linked there) is the retraction notice, right?" No, it is not the retraction notice of the 2008 review.
There are two different reviews: one of 2008, which has not been withdrawn, and another one of 2019, which has been withdrawn.
Explained in other words. The Cochrane made a new revision on the same subject. The conclusions are identical to those of 2008 because, during these eleven years, there have been no new studies that meet the criteria to be included in the systematic review. Therefore, a new review does not make sense. It is duplicating the same article. That's why they withdrawn the new 2019 paper.
Look at the two papers, each one identified with its own PMID and doi, and published on different dates: PMID 18425890 (2008 Apr 16) and PMID 30938835 (2019 Apr 2). They are identical. It is absurd to publish two identical papers. See the data of the withdrawn article, it is the one published in April 2019
[9]
Sorry if I'm not explaining myself correctly. The language barrier makes it more difficult for me .... --
BallenaBlanca 🐳 ♂
(Talk) 21:26, 29 April 2019 (UTC)reply
@
BallenaBlanca: Ah! I understand now, thank you for explaining in detail, I appreciate it. It's strange that these are logged in Crossref as retractions, given that the retraction should be issued for the "updated-but-not-actually" review rather than the outdated review, but I guess that's the data we have to deal with. Do you think it would make sense to simply blacklist Cochrane Systematic Reviews from the bot's operation? It seems like a rough approach, we'd miss a genuine retraction of one of those reviews, but I'm not sure there's a better way given how these are recorded in Crossref.
Sam Walton (
talk) 22:06, 29 April 2019 (UTC)reply
You are welcome! Thank you very much for your effort and your kindness.
I do not think that's necessary, but it's just my opinion. I have not reviewed all the bot notices, just a few of them, but the ones I have seen are correct (with this exception).
@
Samwalton9: in the meantime, possibly untag the Cochrane retractions? Headbomb {
t ·
c ·
p ·
b} 00:30, 1 May 2019 (UTC)reply
@
Samwalton9: It's sad to see that this caused you to stop the bot compleatly...any plans on the future?
Jonatan Svensson Glad (
talk) 02:23, 15 December 2019 (UTC)reply
Wikidata
@
Samwalton9: If you ever get this bot up and running again, perhaps it can be adjusted to also do edits such a
this.
Jonatan Svensson Glad (
talk) 16:56, 31 March 2020 (UTC)reply
@
Josve05a: Is this still likely to be useful, do you know?
Mdann52 (
talk) 17:28, 28 May 2024 (UTC)reply
Given that 4 more academic years has passed, and I don't see a bot having done such edits in sight, I'd wager a yes.
Jonatan Svensson Glad (
talk) 19:31, 28 May 2024 (UTC)reply
However, given their new public database, I'm sure someone will make something with the data - given enough time and encouragement :)
Jonatan Svensson Glad (
talk) 19:40, 28 May 2024 (UTC)reply
I've reviewed this today - there appears to be an error in the datasource on this one, rather than the bot doing anything unexpected. I will try and get in touch with them to confirm. I can add a crossref check back in if these sort of errors are common.
Mdann52 (
talk)
Fixed in the code with
PR2. I spotted these while it was running - test of changed code
here.
Mdann52 (
talk) 06:23, 27 May 2024 (UTC)reply
12 appears to have been a case which the bot wasn't set up for where an expression on concern and a retraction would be issued, I've fixed the assumption that led to this being missed.
Mdann52 (
talk) 07:04, 27 May 2024 (UTC)reply
It added {{Retracted|doi=10.1091/mbc.E14-11-1497-retraction|pmid=35041471}} a few too many times. Headbomb {
t ·
c ·
p ·
b} 01:32, 9 June 2024 (UTC)reply
@
Headbomb bot didn't seem to like tables due to a recursion in the regex. Will deploy fix tomorrow.
Mdann52 (
talk) 20:08, 10 June 2024 (UTC)reply
Possible issue
In
this edit RetractionBot doesn't notice that a citation is already tagged with the retracted template. Thanks,
Sunrise(
talk) 04:22, 17 June 2024 (UTC)reply
@
Sunrise: - fixed this morning - looks like all the whitespace confused the code handling detecting previous templates.
Mdann52 (
talk) 05:36, 17 June 2024 (UTC)reply
Instead of using {{retracted|{{PMID|123456}}}}, the new code is {{retracted|pmid=123456}}. It also supports |bibcode=, |doi=, |pmid=, and |pmc=. Headbomb {
t ·
c ·
p ·
b} 18:00, 22 January 2019 (UTC)reply
@
Headbomb: Thanks for the heads up! Bot progress is still waiting on some conversations regarding the data source, but I hope to continue with development soon :)
Sam Walton (
talk) 18:12, 22 January 2019 (UTC)reply
I figured it'd just be more reliable to have dedicated parameters, and support multiple ones, than have a general
WYSIWIG field where people could put a lot of crap in it. Headbomb {
t ·
c ·
p ·
b} 18:16, 22 January 2019 (UTC)reply
@
Samwalton9: While the Retraction Watch thing is going on, you could also consider using PUBMED directly. It'll be medicine-centric, but it'll be a good start. For example
PMID23432189 links to a retraction notice at
PMID29897867 (and mentions an erratum in "N Engl J Med. 2014 Feb 27;370(9):886"). Likewise
PMID29307074 links to an erratum at
PMID30798464.Headbomb {
t ·
c ·
p ·
b} 09:06, 25 February 2019 (UTC)reply
@
Headbomb: Yes, that was my original plan - to create a fresh database by querying the Pubmed and Crossref APIs for papers flagged as retracted and keeping it updated. From my understanding, RetractionWatch take this data and do further cleanup to ensure that everything flagged as a retraction indeed is a retraction, and they therefore have a more reliable data source. That said, if I don't hear from them soon and find some time to work on this I'll go ahead with the original plan for now.
Sam Walton (
talk) 09:27, 25 February 2019 (UTC)reply
You might want to add support for this to the bot too. Headbomb {
t ·
c ·
p ·
b} 01:05, 16 February 2019 (UTC)reply
How to avoid an edit warring bot
Hi!
Is this enough to hinder the bot form tagging the same citation again, or is there some way to stop the bot from editing one specific citation again? (
t)
Josve05a (
c) 22:39, 28 April 2019 (UTC)reply
Great point on potential edit warring. I've disabled tomorrow's bot run and will ensure it won't edit war before restarting it. Hadn't considered this. I'm not sure about Outdated publication though - while it's a good idea I'm not sure how feasible it will be to have the bot be able to distinguish between that and a retraction given that the Crossref data (and their own definition) simply flags them as retractions. I'm a little confused by the undo, however. @
BallenaBlanca: As far as I can tell the tag was correct - Cochrane issued a retraction of
this review on the basis that it was outdated, and the retraction notice is located
here, so the
template links to the retraction notice (the latter). Could you explain what you mean by this not being the retracted article?
Sam Walton (
talk) 23:15, 28 April 2019 (UTC)reply
Hi! I understand that this can be confusing. I will try to explain it.
We have a 2008 Cochrane review. This is what the bot labeled by mistake. It is valid:
WITHDRAWN: Gluten- and casein-free diets for autistic spectrum disorder.
Millward C1, Ferriter M, Calver SJ, Connell-Jones GG.
But what happened? In reality, no new RCT was made since 2008. Therefore, this 2019 review did not bring anything new. That was the reason for its withdrawal.
@
BallenaBlanca: To clarify, the new revision (the second 'publication' linked there) is the retraction notice, right? As such, it's what the bot linked to. If we want to continue linking to a retracted article (in this case because it was only retracted due to being outdated), shouldn't the way forward be to use the |intentional=yes field of the retracted template, rather than reverting that template addition entirely?
Sam Walton (
talk) 09:00, 29 April 2019 (UTC)reply
"To clarify, the new revision (the second 'publication' linked there) is the retraction notice, right?" No, it is not the retraction notice of the 2008 review.
There are two different reviews: one of 2008, which has not been withdrawn, and another one of 2019, which has been withdrawn.
Explained in other words. The Cochrane made a new revision on the same subject. The conclusions are identical to those of 2008 because, during these eleven years, there have been no new studies that meet the criteria to be included in the systematic review. Therefore, a new review does not make sense. It is duplicating the same article. That's why they withdrawn the new 2019 paper.
Look at the two papers, each one identified with its own PMID and doi, and published on different dates: PMID 18425890 (2008 Apr 16) and PMID 30938835 (2019 Apr 2). They are identical. It is absurd to publish two identical papers. See the data of the withdrawn article, it is the one published in April 2019
[9]
Sorry if I'm not explaining myself correctly. The language barrier makes it more difficult for me .... --
BallenaBlanca 🐳 ♂
(Talk) 21:26, 29 April 2019 (UTC)reply
@
BallenaBlanca: Ah! I understand now, thank you for explaining in detail, I appreciate it. It's strange that these are logged in Crossref as retractions, given that the retraction should be issued for the "updated-but-not-actually" review rather than the outdated review, but I guess that's the data we have to deal with. Do you think it would make sense to simply blacklist Cochrane Systematic Reviews from the bot's operation? It seems like a rough approach, we'd miss a genuine retraction of one of those reviews, but I'm not sure there's a better way given how these are recorded in Crossref.
Sam Walton (
talk) 22:06, 29 April 2019 (UTC)reply
You are welcome! Thank you very much for your effort and your kindness.
I do not think that's necessary, but it's just my opinion. I have not reviewed all the bot notices, just a few of them, but the ones I have seen are correct (with this exception).
@
Samwalton9: in the meantime, possibly untag the Cochrane retractions? Headbomb {
t ·
c ·
p ·
b} 00:30, 1 May 2019 (UTC)reply
@
Samwalton9: It's sad to see that this caused you to stop the bot compleatly...any plans on the future?
Jonatan Svensson Glad (
talk) 02:23, 15 December 2019 (UTC)reply
Wikidata
@
Samwalton9: If you ever get this bot up and running again, perhaps it can be adjusted to also do edits such a
this.
Jonatan Svensson Glad (
talk) 16:56, 31 March 2020 (UTC)reply
@
Josve05a: Is this still likely to be useful, do you know?
Mdann52 (
talk) 17:28, 28 May 2024 (UTC)reply
Given that 4 more academic years has passed, and I don't see a bot having done such edits in sight, I'd wager a yes.
Jonatan Svensson Glad (
talk) 19:31, 28 May 2024 (UTC)reply
However, given their new public database, I'm sure someone will make something with the data - given enough time and encouragement :)
Jonatan Svensson Glad (
talk) 19:40, 28 May 2024 (UTC)reply
I've reviewed this today - there appears to be an error in the datasource on this one, rather than the bot doing anything unexpected. I will try and get in touch with them to confirm. I can add a crossref check back in if these sort of errors are common.
Mdann52 (
talk)
Fixed in the code with
PR2. I spotted these while it was running - test of changed code
here.
Mdann52 (
talk) 06:23, 27 May 2024 (UTC)reply
12 appears to have been a case which the bot wasn't set up for where an expression on concern and a retraction would be issued, I've fixed the assumption that led to this being missed.
Mdann52 (
talk) 07:04, 27 May 2024 (UTC)reply
It added {{Retracted|doi=10.1091/mbc.E14-11-1497-retraction|pmid=35041471}} a few too many times. Headbomb {
t ·
c ·
p ·
b} 01:32, 9 June 2024 (UTC)reply
@
Headbomb bot didn't seem to like tables due to a recursion in the regex. Will deploy fix tomorrow.
Mdann52 (
talk) 20:08, 10 June 2024 (UTC)reply
Possible issue
In
this edit RetractionBot doesn't notice that a citation is already tagged with the retracted template. Thanks,
Sunrise(
talk) 04:22, 17 June 2024 (UTC)reply
@
Sunrise: - fixed this morning - looks like all the whitespace confused the code handling detecting previous templates.
Mdann52 (
talk) 05:36, 17 June 2024 (UTC)reply