Jump to content

User talk:Mike Peel/Archive 30

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 25←Archive 28Archive 29Archive 30Archive 31Archive 32→Archive 35

Wikidata weekly summary #288

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Result views in the Wikidata Query Service UI can now be configured with options (phabricator:T155973, Special:Diff/580233265/596922582)
    • Worked more on introducing the concept of sub.entities in the APIs in order to make edits to Forms persistent
    • Worked on edit summaries for edits to Forms

You can see all open tickets related to Wikidata here.



Infobox map errors

There is a problem with Template:Infobox power station, being discussed here: Template talk:Infobox power station#Is this template broken?. But among the power stations there are a few telescopes and World Heritage Sites with broken maps. It looks like the same error, but I can see no recent changes anywhere that caused it, here or on Wikidata. It’s possibly buried deep in a template. As you worked on both templates you might have a better idea. Here’s the non-power station articles with errors.

--JohnBlackburnewordsdeeds 19:45, 27 November 2017 (UTC)

Thanks for the heads-up. It looks like another editor fixed it before I could get to it. :-) Thanks. Mike Peel (talk) 20:47, 27 November 2017 (UTC)

This Month in Education: November 2017

Wikipedia Education globe
Wikipedia Education globe
This Month in Education

Volume 6 | Issue 10 | November 2017

This monthly newsletter showcases the Wikipedia Education Program. It focuses on sharing: your ideas, stories, success and challenges. You can see past editions here. You can also volunteer to help publish the newsletter. Join the team! Finally, don't forget to subscribe!

In This Issue


From the Community

Hashemite University continues its strong support of Education program activities

Wikicontest for high school students

Exploring Wikiversity to create a MOOC

Wikidata in the Classroom at the University of Edinburgh

How we defined what secondary education students need

Wikipedia Education Program in Bangkok,Thailand

Shaken but not deterred

Wikipedia workshop against human trafficking in Serbia

The WikiChallenge Ecoles d'Afrique kicks in 4 francophones African countries


From the Education Team

A Proposal for Education Team endorsement criteria

In the News

Student perceptions of writing with Wikipedia in Australian higher education

Cochrane Update bot

Hi Mike Peel. Thank you very much for offering to help with the Cochrane update bot. Unfortunately, I don't have a copy of the code. @Doc James:, do you know where we can find the actual code that the previous volunteer used? RexxS provided us with more information about dexbot here on his talk page. James, do you know if the Cochrane update bot has gone through an approval process already? Thanks again for offering to help Mike. It is a pleasure meeting yet another friendly Wikipedian! JenOttawa (talk) 01:30, 22 November 2017 (UTC)

User:Ladsgroup runs the bot. I will ask if he can share the code. Doc James (talk · contribs · email) 01:44, 22 November 2017 (UTC)
That would be great. Thanks Doc James.JenOttawa (talk) 01:53, 22 November 2017 (UTC)

This is the code, it's super straightforward Ladsgroupoverleg 15:10, 26 November 2017 (UTC)

Thank you Ladsgroup. We greatly appreciate all your help putting this together and running the bot. It has been a useful tool for us, and volunteers have now completed almost all of the updates that were flagged in August! Mike Peel, is there anything else that I can help with? Do you think that this would be feasible for you? If there is anything that I can do to help, please let me know. Thank you again to both of you! JenOttawa (talk) 15:23, 27 November 2017 (UTC)

OK, so it runs on my desktop, which is a good start. :-) I've put a copy at [1], and I've just been doing some test runs. I've added some caching code so that it only fetches a given report once to check if it's been updated, which speeds it up a little. Hopefully [2] and [3] are the desired edits.

I have a few questions @JenOttawa, Doc James, and RexxS::

  • When starting it up, it says "WARNING: API warning (search): The regex search timed out, only partial results are available. Try simplifying your regular expression to get complete results. Retrieving 50 pages from wikipedia:en." - @Ladsgroup: any idea how to improve this?
  • It currently updates Wikipedia:WikiProject Medicine/Cochrane update/August 2017 - wouldn't it be better to post updates at Wikipedia:WikiProject Medicine/Cochrane update instead? Also, would it help if it auto-archived lines marked with  Done at the start of the run?
  • If <!-- No update needed --> exists anywhere in the page, it doesn't do an update, even if that's not associated with the reference that needs updating. Would it be feasible to change this to e.g. <!-- No update needed: 10484104 --> (where '10484104' is the pubmed ID), or would that break too many pages?
  • I'll run this by the Bot Approval Group shortly, and after that I'll set Pi bot to run the script on the 1st of every month, is that OK or would a different date/frequency be better?

Thanks. Mike Peel (talk) 22:14, 27 November 2017 (UTC)

Hi Mike, thanks for doing all this work.
  • In the past, when Ladsgroup ran a new version of the bot, it created a new bot page with the date. I am not sure exactly how it works, but my understanding is that each time the bot was run, it re-did all the previous "update needed" tags making a new project page with all the Cochrane updates needed across Wikipedia. If you have the bot set up to add only new reviews to the most recent version (Aug17) and remove the  Done PMIDs, that is great. Adding to the August page is actually helpful, as the vounteers already have this link and are presently accessing it. Doc James do you agree with me here?
  • I appreciate you offering to run it once a month. This is helpful.
  • no-wiki's: I believe this is in place in case an editor wants to cite an outdated Cochrane review in a historical context within an article. I am glad that you noticed this, as it means we could be missing some updates. If you can make it more specific for Cochrane reviews, that would be great.

Thanks again, JenOttawa (talk) 14:14, 28 November 2017 (UTC)

Yes the "<!-- No update needed -->" is for the times when we want to use an old review. Not often but sometimes. Doc James (talk · contribs · email) 15:23, 28 November 2017 (UTC)
OK, archiving is now coded up, and I've run it once manually. I've also now submitted the bot request. Please have a look at both and let me know if there are any problems! Thanks. Mike Peel (talk) 21:00, 28 November 2017 (UTC)
Hi Mike, thanks for taking care of all this admin work involved with setting this up. I noticed the one new review added to the August page here, and that it archived all the updates marked  Done. Once you run the bot automatically will it pull the up the additional updates? I would expect at least 20, as it has been nearly 4 months since we have run it. I also looked at your proposal and it looks great. The in-text "update needed" tag looks good as well. Is there anything else that you want me to look at? Thanks again, JenOttawa (talk) 18:26, 30 November 2017 (UTC)
Do you have any suggestions on what to do in the case of the "withdrawn" cochrane review. There can be various reasons that Cochrane marks their reviews in this manner, not all negative. For now, I will leave the citation as the most recent non-withdrawn review, however I do not want to mark this with a "done" or put a no-update needed tag in the article, in case Cochrane comes out with a newer non-withdrawn review. I can also just leave these in the list for now, as they are not very frequent.
e.g: The one citation added to list was this one, and the newest, 2016 version, has been withdrawn.
Article Acupuncture (edit) old review PMID:27145001 new review PMID:27852100 - 22:07, 27 November 2017 (UTC)
Thanks! JenOttawa (talk) 18:30, 30 November 2017 (UTC)
@JenOttawa: I only ran the code up to the point where it made its first edit, hence why only one update was posted - the first run by Pi bot will do the rest. I was wondering about the 'withdrawn' status of the update. What happens when a new update is posted that isn't withdrawn - does the replacement ID in the first article get updated to the non-withdrawn one, or does the withdrawn one get a replacement ID? Would it help if there was a separate way of tracking the uses of ones that have been marked as withdrawn (both current refs and updated refs)? It might be best to talk to others and let me know what the ideal process would be here, and I can see if I can add code that does that. Thanks. Mike Peel (talk) 21:04, 1 December 2017 (UTC)
Great points. I think it makes separate to separate these tasks, but I am open to suggestions! I am not certain the answer to your question regarding an update to a withdrawn review, I will look into it. I have access to an excel doc on file with DOIs for all withdrawn reviews to date (for future use). All looks good (from what I can see with the bot). I have volunteers ready to go, so your work is very helpful for our project! If I can help you with anything else, please let me know. JenOttawa (talk) 21:10, 1 December 2017 (UTC)

ArbCom 2017 election voter message

Hello, Mike Peel. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)

Wikidata weekly summary #289

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Wikidata will get dedicated database resources, and go read-only for 30 minutes on 9th January 2018 (phabricator:T181645)
    • There were no RDF dumps last week due to problems generating them, investigation is still going on (phabricator:T181385)
    • Improved the threshold for ORES on Wikidata (phabricator:T180450)
    • Working on fixing a regression after a change in MediaWiki core that makes edit links show up on diff pages (phabricator:T181807)
    • More work on persistent editing of statements on Forms of a Lexeme (specifically phabricator:T180467)
    • Improved size of the diff that we sent to Wikipedia and co for changes happening on Wikidata. This is one more needed step towards only showing meaningful edits in the watchlists and recent changes there. (phabricator:T113468)

You can see all open tickets related to Wikidata here.


This Month in GLAM: November 2017



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Administrators' newsletter – December 2017

News and updates for administrators from the past month (November 2017).

Administrator changes

added Joe Roe
readded JzG
removed Ericorbit • Perceval • Thingg • Tristanb • Violetriga

Guideline and policy news

  • Following a request for comment, a new section has been added to the username policy which disallows usernames containing emoji, emoticons or otherwise "decorative" usernames, and usernames that use any non-language symbols. Administrators should discuss issues related to these types of usernames before blocking.

Technical news

Arbitration

Miscellaneous

  • Over the last few months, several users have reported backlogs that require administrator attention at WP:ANI, with the most common backlogs showing up on WP:SPI, WP:AIV and WP:RFPP. It is requested that all administrators take some time during this month to help clear backlogs wherever possible. It should be noted that AIV reports are not always valid; however, they still need to be cleared, which may include needing to remind users on what qualifies as vandalism.
  • The Wikimedia Foundation Community health initiative is conducting a survey for English Wikipedia contributors on their experience and satisfaction level with Administrator’s Noticeboard/Incidents. This survey will be integral to gathering information about how this noticeboard works (i.e. which problems it deals with well and which problems it struggles with). If you would like to take this survey, please sign up on this page, and a link for the survey will be emailed to you via Special:EmailUser.
Sent by MediaWiki message delivery (talk) 20:58, 2 December 2017 (UTC)

Wikidata weekly summary #290

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff

You can see all open tickets related to Wikidata here.


The Signpost: 18 December 2017

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 06:28, 18 December 2017 (UTC)

Wikidata weekly summary #291

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Additional languages for monolingual values got approved by the language committee: ami (Amis), bnn (Bunun), fos (Siraya), ppu (Papora / Hoanya), pwn (Paiwan), pyu (Puyuma), ssf (Thao), trv (Seediq / Taroko), uun (Pazeh) (see gerrit:374052, phab:T144272)
    • More work on caching constraint results so we can enable the constraints checks for all logged-in users by default
    • Fixed a bug when edit links showed up in diff views (phabricator:T181807)
    • Final step towards being able to store statements on Forms of a Lexeme
    • Disabled RDF support for Lexemes as the mapping isn't defined yet (phabricator:T182660)
    • Adding some more smart tracking for Lua usage so we better know which properties from an item are used on a Wikipedia article even when the whole item is loaded (phabricator:T179923)

You can see all open tickets related to Wikidata here.

Cochrane bot updates

Hi Mike, I just wanted to follow up on our conversation about the Cochrane Update bot. We were discussing withdrawn reviews. I have started to look into this, but have not yet found a solution. Are you waiting for this response before the bot runs fully, or is it scheduled for the first of the month? Thanks again for all your help. Jenny JenOttawa (talk) 03:32, 9 December 2017 (UTC)

Hi @JenOttawa: I'm currently waiting for the bot approval group, see Wikipedia:Bots/Requests for approval/Pi bot 3 (which is taking longer than I expected, maybe @Headbomb: can help?). Once that's there then I'll set it running to do a one-off update, then schedule it to run on the 1st of each month. If there's a solution to the withdrawn reviews, then I'm happy to implement it, but I don't see this as an issue that stops the bot from running (since the work-around is to leave them in the pending queue until a non-withdrawn update is available). Thanks. Mike Peel (talk) 10:31, 9 December 2017 (UTC)
Thanks for the update Mike. JenOttawa (talk) 02:03, 10 December 2017 (UTC)

Hi Mike, congrats on getting the bot up and running! I noticed that it is doing all the "withdrawn" reviews first. Just wondering if this was supposed to happen. This is great that they are included in the bot updates. We did not have them before, it used to just pull all the PMIDs of updated reviews. Thanks again for all your help with the approval process and behind the scenes work getting this up and running. I will be contacting the volunteers and we will get started tackling the new list! JenOttawa (talk) 21:08, 12 December 2017 (UTC)

@JenOttawa: I'm surprised that so many "withdrawn" reviews are being returned, I don't think I changed anything in the code that made it more or less likely for these to be fetched. If you/others can have a look at them and figure out how best to deal with them, that would be good! Thanks. Mike Peel (talk) 21:15, 12 December 2017 (UTC)
It is great that it is pulling the withdrawn reviews, these can be easily updated manually on Wikipedia, and it is great to clean up the articles. Once it is finished we will see how it works for the non-withdrawn updated reviews (about 20 per month). There are about 300 withdrawn reviews in total for all cochrane reviews (not sure of time frame on this number). They are pretty rare, maybe a handful a year? Thanks again, Jenny JenOttawa (talk) 21:50, 12 December 2017 (UTC)
I only saw the "finished product" the other times the updates were performed, so I am not sure of the order that the bot flagged the updates. I can see that it is still plugging away pulling the withdrawn reviews alphabetically. JenOttawa (talk) 21:52, 12 December 2017 (UTC)
OK. It is still running, hopefully it will finish overnight. Thanks. Mike Peel (talk) 22:06, 12 December 2017 (UTC)

Hey Mike. Can you get your bot to not put updates when the update is withdrawn? [4]

Added [5] Thanks for taking this on :-) Doc James (talk · contribs · email) 04:37, 13 December 2017 (UTC)

Also can you get the bot to add the pmid for the most recent version?
For example https://wiki.riteme.site/w/index.php?title=Croup&type=revision&diff=815112213&oldid=807292961
The next update is withdrawn but the one after that in 2013 is good.
:-) Doc James (talk · contribs · email) 04:43, 13 December 2017 (UTC)
Can you run the bot on the prior edits to remove the unneeded ones?
And might be good to run some practice runs. Doc James (talk · contribs · email) 05:07, 13 December 2017 (UTC)
@JenOttawa and Doc James: Can you decide how best to handle the withdrawn cases, and I'll code that up? The bot stopped part-way through last night when trying to fetch a page from nih.gov to check, so I also need to improve the robustness of that part of the code I've made a change to that part of the code to avoid the issue. Thanks. Mike Peel (talk) 19:15, 13 December 2017 (UTC)
I've added some code that will catch cases where the updated version has itself been updated (but it won't check for a third level), so that should catch cases like [6]. I can check to see if the new one has 'WITHDRAWN' in it, and not update in that case, if that's what both of you want me to do. Thanks. Mike Peel (talk) 20:14, 13 December 2017 (UTC)
Basically we are looking for the most recent not "withdrawn" paper :-) Doc James (talk · contribs · email) 05:03, 14 December 2017 (UTC)
If I exclude any update that contains "<h1>WITHDRAWN:" in the HTML, then I think that will do what you want, @Doc James. It does mean that cases where the currently-used reference has been withdrawn without an update that hasn't been withdrawn will not be flagged, is that OK? @JenOttawa: any comments? Thanks. Mike Peel (talk) 23:36, 18 December 2017 (UTC)
Yes I think that should be good. Doc James (talk · contribs · email) 23:53, 18 December 2017 (UTC)
That makes sense to me. I have an excel doc with all the withdrawn reviews, I can go manually and make sure that the reviews that are withdrawn are replaced with the most recent review. Thanks very much! JenOttawa (talk) 01:32, 19 December 2017 (UTC)

Wishes

It's that time of the year again, Mike. No fancy template, but just wishing you all the best for the holidays and the new year. It's probably a lot warmer where I am than where you are 😎 Kudpung กุดผึ้ง (talk) 09:15, 21 December 2017 (UTC)

@Kudpung: Thanks, same to you! Mike Peel (talk) 15:08, 23 December 2017 (UTC)

Merry Christmas!

Merry Christmas Mike Peel!!


Hi Mike Peel, I wish you and your family a very Merry Christmas and a very Happy New Year,
Thanks for all your help and contributions on the 'pedia! ,
   –Davey2010 Merry Xmas / Happy New Year 13:44, 23 December 2017 (UTC)

@Davey2010: Thanks, same to you! Mike Peel (talk) 15:09, 23 December 2017 (UTC)

Wikidata weekly summary #292

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Due to the Christmas and New Year's Eve holidays, no deployment will happen before January 3rd.
    • Monolingual language codes for Old French (fro) and Middle French (frm) added (phabricator:T181823)
    • Finishing touches on storing statements on Forms
    • No longer checking constraints on the property example statements (phabricator:T183267)
    • More work on caching constraint check results so we can roll out constraint checking for all logged in users

Seasons' Greetings

...to you and yours, from the Great White North! FWiW Bzuk (talk) 04:35, 24 December 2017 (UTC)

@Bzuk: Thanks, same to you! Mike Peel (talk) 14:26, 26 December 2017 (UTC)

Holiday Season!

Hi Mike, I just wanted to wish you a nice Christmas holiday. Thank you again for your help getting the bot up and going. Hope you have a chance to relax and enjoy the holiday season. Kind regards, Jenny

JenOttawa (talk) 15:48, 26 December 2017 (UTC)

Retrieved from "https://wiki.riteme.site/w/index.php?title=User_talk:Mike_Peel/Archive_30&oldid=818356988"