User talk:RexxS/Archive 38

The above two ANI's.
What I will say (after commenting on the first and having to bite my tongue on the second) is that it will be very difficult for me to defend your actions in the future. In the first instance you revert out an editor's change to the status quo and BRD and general editing policies/guidelines supports you in this. In the second you revert back in an editors change to the status quo in what is already an amazing contentious subject whenever it rears its ugly head. BRD does not support this. Frankly for adding an infobox to a music-based article, especially in that genre, it will always be contentious. The community of infobox-arguers (on both sides) has shown over the years it is incapable of solving their disputes through standard discussion due to the entrenched positions, so a formal moderated !vote is the best way to keep the discussion civil. Only in death does duty end (talk) 11:28, 3 August 2017 (UTC)
 * (watching:) Infoboxes have been contentious for classical music composers (last discussed for Pierre Boulez in January 2016, and I had enough then), but not for compositions, see Mozart and Britten recent TFAs, or a bit longer ago another Requiem for TFA. --Gerda Arendt (talk) 11:43, 3 August 2017 (UTC)
 * That is, at best, wishful thinking Gerda. Infoboxs in general are contentious. If you need to quibble over 'well it is for composers but not for compositions' then you are clutching at straws. And that in particular is the sort of argument that people who are anti-infobox will just reject out of hand. Only in death does duty end (talk) 11:59, 3 August 2017 (UTC)
 * Look at the Mozart concerto, and it's review: anything contentious? - Look: I add infoboxes, and if I am reverted, I forget it. Normally. In this case, I was reverted like vandalism, and just questioned why. Some of the old fighters seem to love argument. --Gerda Arendt (talk) 12:26, 3 August 2017 (UTC)
 * Thank you for your advice and sentiments, and I do understand what you're saying. However, in the second case, my restoration of the infobox came as a consequence of a single editor (the IP in question) removing the infobox four times in quick succession against three other editors (not including me) who wished to see it included. BRD had gone out of the window long before I arrived, and I was unwilling to see an action supported by several other editors stonewalled by a single objector. I do believe that in this case, an infobox improves the article, and I've taken the time to lay out my reasoning on the article talk page. I do accept that on the talk page, other editors such as Ceoil had raised concerns without specifically objecting, but the IP who was regularly reverting had not made a single constructive comment there. In the circumstances, I don't regret engaging strongly with him, even if I do feel a tinge of shame in descending to his level. At the end of the day, one has to make a decision about where to draw the line in tolerating bad behaviour such as the IP demonstrates. I draw mine pretty close to zero-tolerance for the attacks he made on two of our most respected and well-intentioned women editors on that page. Any other approach would empower him to continue his malignant attacks.
 * I'm afraid that I must disagree, though, with your suggestion that infoboxes in general are contentious. They are not: not only do they appear in well over half of our articles, they are an integral part of three-quarters of our Featured Articles, although I maintain that there are certainly cases where, on balance, an infobox does not improve an article. If you're interested in why I reach those conclusions, please take a look at User:RexxS/Infobox factors, a work in progress, where I'm attempting to collate as many factors as I can find that influence whether an infobox improves an article or not. If you feel you have any insights to add, then please do so. --RexxS (talk) 13:49, 3 August 2017 (UTC)
 * It's not the infobox that's contentious; just the posting of it. That's it. &mdash; fortuna  velut luna  13:52, 3 August 2017 (UTC)
 * Indeed,, and that's a pity in itself. Nevertheless, articles – even ones that benefit dramatically from an infobox – do not come with one "ready-made", so somebody has to compose one and post it. For some editors, crafting it carefully is a labour-of-love: "Quicquid Venus imperat / Labor est suavis / Que nunquam in cordibus / Habitat ignavis". --RexxS (talk) 14:16, 3 August 2017 (UTC)
 * What Fortuna said. My personal opinion on infobox's is 'sometimes good, sometimes bad, consensus should be sought on the talkpage'. What irked me about the above is that, its quite disingenuous to argue your reversion of a break from the status quo is valid and cite BRD, then turn around and revert your own preferred break from the status quo into an article. Unless its vandalism or obviously incorrect (neither of which applied in the above two cases) the correct process is to go to the talk page and hash it out there once BRD has started. That it relates to an infobox is just an added annoyance for why said talkpage discussion is probably going to go downhill quickly if anyone notices it. If someone decided to remove that infobox and you (or someone else) decided to take it to ANI in much the same way as Lynn did over the horse matter, what response would you expect? Only in death does duty end (talk) 14:41, 3 August 2017 (UTC)
 * My opinion is that nobody needs to seek consensus before making an edit that they feel improves an article. Only if it is challenged should there be any need for debate. Nowhere in the two arguments you refer to have I cited BRD. I don't need essays to bolster common sense, and "status quo" is merely the first line of defence for article OWNers - it's almost always masking an ability to make a reasoned argument in favour of a position. In the first argument, I disagreed that LynWysong's gutting of an introductory paragraph was an improvement, and said so as soon as I restored the previous version. In the second argument, I was unwilling to see a single objector remove a valid edit made by three other editors four times. That's not how we write articles on Wikipedia. The IP's only objection to the edit was that it was an infobox. Not that it was against policy, nor that it made the article worse, just that it was an infobox. I've engaged constructively on that article talk page to explain why I feel an infobox improves the article; the IP has done nothing but attack others. Frankly, it's about time that the practice of posting to ANI to try to remove any opposition from a content debate was banned. Because in those two cases, that's exactly what happened. --RexxS (talk) 15:08, 3 August 2017 (UTC)
 * My opinion is that nobody needs to seek consensus before making an edit that they feel improves an article. Only if it is challenged should there be any need for debate. Nowhere in the two arguments you refer to have I cited BRD. I don't need essays to bolster common sense, and "status quo" is merely the first line of defence for article OWNers - it's almost always masking an ability to make a reasoned argument in favour of a position. In the first argument, I disagreed that LynWysong's gutting of an introductory paragraph was an improvement, and said so as soon as I restored the previous version. In the second argument, I was unwilling to see a single objector remove a valid edit made by three other editors four times. That's not how we write articles on Wikipedia. The IP's only objection to the edit was that it was an infobox. Not that it was against policy, nor that it made the article worse, just that it was an infobox. I've engaged constructively on that article talk page to explain why I feel an infobox improves the article; the IP has done nothing but attack others. Frankly, it's about time that the practice of posting to ANI to try to remove any opposition from a content debate was banned. Because in those two cases, that's exactly what happened. --RexxS (talk) 15:08, 3 August 2017 (UTC)

url
https://doc.wikimedia.org/mediawiki-core/master/php/DairikiDiff_8php_source.html

All the best: Rich Farmbrough, 20:04, 9 August 2017 (UTC).

To boil a kettle free

 * Thiotimoline

All the best: Rich Farmbrough, 00:17, 10 August 2017 (UTC).

Lua help on svwiki
Hello, I saw on the Skills board that you could help with Lua. I am trying to copy Q from meta to svwiki, but we don't have the function getLabel in any of our Wikidata modules. I tried to copy a part but it didn't work. Can you please help me? Ainali (talk) 17:53, 10 August 2017 (UTC)
 * I'm sorry I wasn't around today, as I was in the Medicine meetings. I'd be happy to help, so perhaps you could look for me at one of the Wikidata talks during the day on Friday? --RexxS (talk) 03:37, 11 August 2017 (UTC)
 * Thanks, but I think I fixed it last night. Ainali (talk) 11:34, 11 August 2017 (UTC)
 * Thanks, but I think I fixed it last night. Ainali (talk) 11:34, 11 August 2017 (UTC)

Newcomer productivity study
Hi RexxS, thanks for making the challenging point about references being the only indispensable skill for newcomers. Here's the study I drew upon when asking my own question: http://jodischneider.com/pubs/opensym2014.pdf Adamw (talk) 15:41, 11 August 2017 (UTC)

Facto Post – Issue 3 – 11 August 2017
{| style="position: relative; margin-left: 2em; margin-right: 2em; padding: 0.5em 1em; background-color:	#7FFFD4; border: 2px solid #00FFFF; border-color: rgba( 109, 193, 240, 0.75 ); border-radius: 8px; box-shadow: 8px 8px 12px rgba( 0, 0, 0, 0.7 );"
 * Facto Post – Issue 3 – 11 August 2017

 

Wikimania report
Interviewed by Facto Post at the hackathon, Lydia Pintscher of Wikidata said that the most significant recent development is that Wikidata now accounts for one third of Wikimedia edits. And the essential growth of human editing. Impressive development work on Internet-in-a-Box featured in the WikiMedFoundation annual conference on Thursday. Hardware is Raspberry Pi, running Linux and the Kiwix browser. It can operate as a wifi hotspot and support a local intranet in parts of the world lacking phone signal. The medical use case is for those delivering care, who have smartphones but have to function in clinics in just such areas with few reference resources. Wikipedia medical content can be served to their phones, and power supplied by standard lithium battery packages.

Yesterday Katherine Maher unveiled the draft Wikimedia 2030 strategy, featuring a picturesque metaphor, "roads, bridges and villages". Here "bridges" could do with illustration. Perhaps it stands for engineering round or over the obstacles to progress down the obvious highways. Internet-in-a-Box would then do fine as an example.

"Bridging the gap" explains a take on that same metaphor, with its human component. If you are at Wikimania, come talk to WikiFactMine at its stall in the Community Village, just by the 3D-printed display for Bassel Khartabil; come hear talk at 3 pm today in Drummond West, Level 3.

Link

 * Plaudit for the Medical Wikipedia app, content that is loaded into Internet-In-A-Box with other material, such as per-country documentation.

Editor. Please leave feedback for him. If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Opted-out of message delivery to your user talk page. Newsletter delivered by MediaWiki message delivery MediaWiki message delivery (talk) 10:55, 12 August 2017 (UTC)
 * }

Invite
Would you like to comment on my proposals on Village Pump (Idea lab)? -- Pankaj Jain Capankajsmilyo (talk · contribs · [//tools.wmflabs.org/xtools-ec/?user=Capankajsmilyo&project=en.wikipedia.org count])  08:10, 13 August 2017 (UTC)

Question about Lua
Hi! I didn’t manage to talk to you at Wikimania until now, maybe tomorrow we could find a moment?! I need to use Lua on German WP for fixing and improving a specific template and wanted to hear an expert advice on the doability of the proposal. If not tomorrow, I will probably come back to it soon here on the talk page. Best regards, XanonymusX (talk) 03:25, 13 August 2017 (UTC)
 * Hi,, I'll be in the lighting talks (s38) all morning today, and then w13, s43, and probably r8 in the afternoon. If you can find me, we can take some time in the hackathon space to look at what you want to do. Cheers --RexxS (talk) 12:29, 13 August 2017 (UTC)

Cambridge
Hi Doug. The editathon you lead the training at features here..... and there are few pix of you too! Carol features and a great interview we filmed with Peggy. Hope you enjoyed Wikimania! regards Victuallers (talk) 11:12, 14 August 2017 (UTC)

Small caption in infobox
Hi, the main infobox image caption at Solar eclipse of August 21, 2017 was unreadably tiny, so I made to remove the  - but although the caption is now larger than before, it's still only 10.287px in MonoBook. How come it's smaller than the 11.176px of, for example, the caption of Reading Southern railway station, which uses ? -- Red rose64 &#x1f339; (talk) 22:39, 21 August 2017 (UTC)
 * Text in an infobox is 90% of normal font size (i.e. 90% of 12.7px in Monobook = 11.43px). However the caption has an additional CSS style 'captionstyle' set to another 90% in line 136, so the text is rendered at 90% of 90% of 12.7px in Monobook = 10.287px. I'll disable that. --RexxS (talk) 01:13, 22 August 2017 (UTC)
 * It's now 11.43px, . I didn't spot that extra styling - it wasn't in the  attribute of the . -- Red rose64 &#x1f339; (talk) 07:27, 22 August 2017 (UTC)
 * It's now 11.43px, . I didn't spot that extra styling - it wasn't in the  attribute of the . -- Red rose64 &#x1f339; (talk) 07:27, 22 August 2017 (UTC)

Template:Infobox pier
Can you offer a bit of advice? I was trying to get an inline map to display on Brighton Palace Pier (I've heard of people getting lost trying to find it from the station on foot, as if "follow the seagulls until your feet start to get wet" might be a clue) but doesn't seem to want to do them. At the moment, I've hacked in as it does do this, but it throws out some of the useful fields on the other infobox, such as length (useful statistic for a pier, not so much for a building). Any other ideas what I can do? Ritchie333 (talk) (cont)  21:21, 3 August 2017 (UTC)


 * Something like  in  should work - I previewed it in a test edit at Southport Pier, and it looked ok. Robevans123 (talk) 22:22, 3 August 2017 (UTC)
 * Thank you, Rob, that looks like an improvement. What do you think, Ritchie? Optionally, I recently made a template overlaid images that allows you to overlay one image over another that might come in useful for unusual cases, but it would require a bit of fiddling to make use of. Infobox pier has a parameter extra that could be used. You could have fun having an inlaid map with an inlaid map, or just use the background on its own which can be cropped, scaled and shifted to taste. --RexxS (talk) 18:23, 4 August 2017 (UTC)
 * All I did was remember that the syntax for map images can be quite different in different infoboxes - sometimes you have to give the full file name, sometimes just key parts... I do like the inlaid images - it's something the BBC website use quite often in its location maps. See http://static.bbci.co.uk/searchassets/img/ec/2010/05/south_west_wales.jpg for a ready made example. Robevans123 (talk) 20:44, 4 August 2017 (UTC)
 * All I did was remember that the syntax for map images can be quite different in different infoboxes - sometimes you have to give the full file name, sometimes just key parts... I do like the inlaid images - it's something the BBC website use quite often in its location maps. See http://static.bbci.co.uk/searchassets/img/ec/2010/05/south_west_wales.jpg for a ready made example. Robevans123 (talk) 20:44, 4 August 2017 (UTC)

Map syntax
"the syntax for map images can be quite different in different infoboxes" This is a ludicrous situation. we've resolved t for some other fields (images and "alt text" are pretty standard now). Is anyone up for working with me on standardising this? The first step would be to gain consensus on what is best pracice... Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 11:24, 22 August 2017 (UTC)

Facto Post – Issue 4 – 18 September 2017
{| style="position: relative; margin-left: 2em; margin-right: 2em; padding: 0.5em 1em; background-color:	#7FFFD4; border: 2px solid #00FFFF; border-color: rgba( 109, 193, 240, 0.75 ); border-radius: 8px; box-shadow: 8px 8px 12px rgba( 0, 0, 0, 0.7 );"
 * Facto Post – Issue 4 – 18 September 2017

 

Editorial: Conservation data
The IUCN Red List update of 14 September led with a threat to North American ash trees. The International Union for Conservation of Nature produces authoritative species listings that are peer-reviewed. Examples used as metonyms for loss of species and biodiversity, and |theoretical discussion of extinction rates, are the usual topics covered in the media to inform us about this area. But actual data matters. Clearly, conservation work depends on decisions about what should be done, and where. While animals, particularly mammals, are photogenic, species numbers run into millions. Plant species lie at the base of typical land-based food chains, and vegetation is key to the habitats of most animals.

ContentMine dictionaries, for example as tabulated at d:Wikidata:WikiFactMine/Dictionary list, enable detailed control of queries about endangered species, in their taxonomic context. To target conservation measures properly, species listings running into the thousands are not what is needed: range maps showing current distribution are. Between the will to act, and effective steps taken, the services of data handling are required. There is now no reason at all why Wikidata should not take up the burden.

Links

 * What Makes a Good Collaborative Knowledge Graph: Group Composition and Quality in Wikidata (paywall)
 * Wikimedia and the free knowledge ecosystem by Maria Cruz
 * Another Year Again: 2017 this time (long), blog by Joe Wass of CrossRef
 * Attack of the 50 Foot Blockchain, blog by User:David Gerard
 * WikiTribune in beta

Editor. Please leave feedback for him. If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Opted-out of message delivery to your user talk page. Newsletter delivered by MediaWiki message delivery MediaWiki message delivery (talk) 14:46, 18 September 2017 (UTC)
 * }

Here we go again
Yes, here we go. I can't find the carousel for my edit notice, to add MONGO glaciers. I do remember it's somewhere unexpected... but that turns out not to be enough. :-( Bishonen &#124; talk 09:33, 17 September 2017 (UTC).
 * It's at Module:RexxS. The Many Glacier pic looks stunning. --RexxS (talk) 19:13, 17 September 2017 (UTC)
 * Thank you. (So not in your userspace at all. :- I'd better make a commented-out note about it in the edit notice itself. Did you see the Bird Woman Falls? Bishonen &#124; talk 19:20, 17 September 2017 (UTC).
 * Wow! --RexxS (talk) 19:22, 17 September 2017 (UTC)
 * "#€%&/&%€#"!!! Why won't the tab key work, and why does the list look right in edit mode and Preview, and horrible when saved? I seem to remember this happened last time also, and it kind of... righted itself after a while. Which seems very odd. But could you check, please? Bishonen &#124; talk 19:35, 17 September 2017 (UTC).
 * Actually the edit notice is cheerfully showing a glacier, even though the list is all hither and thither. I'll never understand these things! Bishonen &#124; talk 19:39, 17 September 2017 (UTC).
 * Yes, the indents don't mean anything in Lua; it's just to make things easier to read. Unfortunately I tend to use an external editor for editing programs, so I didn't think about the embedded tabs and the inability of the Wikipedia editor to insert them in an obvious manner (i.e. using the Tab key). The easiest way using the Wikipedia editor is to copy one of the lines (including the leading tabs), then paste it and change the filename.
 * Adding one more to test. Yes, that looks fine. I'd definitely better put those instructions into the edit notice! Thanks, Doug. Bishonen &#124; talk 19:55, 17 September 2017 (UTC).
 * Web browsers typically use the tab key to switch between clickable items; these might be links or, in this case, input items (such as edit box, edit summary, etc.) in a form. Is the glacier really that blue? -- Red rose64 &#x1f339; (talk) 20:24, 17 September 2017 (UTC)
 * Is it, MONGO? Yeah, I noticed the tab made it jump to the next field. And, RexxS... [A little embarrassed: ] I was inspired to change the top image on my page, too — enough with the scary hippo admin — but of course (bitterly) I wasn't able to centre the caption nicely. Help, please? Then I'm done, I promise. Bishonen &#124; talk 20:30, 17 September 2017 (UTC).
 * Probably the easiest way of centring captions and the like is to use the center template. Done for you, . --RexxS (talk) 23:11, 17 September 2017 (UTC)
 * Looks very nice with the three little users canoodling. Buuuut... the edit notice won't work because there's a "Lua error" in Module:RexxS. That's what it says. :-( You'll see it if you click "edit" on my page. Bishonen &#124; talk 22:23, 20 September 2017 (UTC).
 * Sorry,, that was my fault. Today I added some general snippets of code for extracting and converting coordinates in that module and I should have commented out the bits that don't make sense in Wikipedia. Fixed now! --RexxS (talk) 23:16, 20 September 2017 (UTC)
 * And now the Grus Canadensis dance again! Bishonen &#124; talk 23:29, 20 September 2017 (UTC).
 * Looks very nice with the three little users canoodling. Buuuut... the edit notice won't work because there's a "Lua error" in Module:RexxS. That's what it says. :-( You'll see it if you click "edit" on my page. Bishonen &#124; talk 22:23, 20 September 2017 (UTC).
 * Sorry,, that was my fault. Today I added some general snippets of code for extracting and converting coordinates in that module and I should have commented out the bits that don't make sense in Wikipedia. Fixed now! --RexxS (talk) 23:16, 20 September 2017 (UTC)
 * And now the Grus Canadensis dance again! Bishonen &#124; talk 23:29, 20 September 2017 (UTC).

Alternate row colours in Lua
Hi! While our Canadian creation is now finished and working (at least on testwiki, I have to wait for TemplateStyles to be released in the other wikis as well before going live there), I just had to write a new module for another (music-related) template, because the old one reaches the template limit on de:Madonna (Künstlerin)/Auszeichnungen für Musikverkäufe. Now, de:Modul:Vorlage:AfM-Tabelle is already working, as tested on the talk page, but I can’t figure out how to give alternate colours to the rows (inside the loop, see line 41 of the module). I get why it won’t work like this, but can’t think of another solution (except for the one with TemplateStyles, using testwiki:Template:Chart.css). Do you have an idea on how to get it working? Thanks in advance and best regards, XanonymusX (talk) 23:43, 23 September 2017 (UTC)
 * Hi, it's nice to hear from you again! Your method in the module is sound, but you forgot the '=' in " " in lines 43 and 45. It's also best to make sure that the  markup for a new row begins on a new line, so include " " just to make sure. Finally, I had to reverse the order of the striping to match the fixed first row colour. Anyway, I think it's all working now if the tests at de:Modul Diskussion:Vorlage:AfM-Tabelle are representative. Keep up the good work! Cheers --RexxS (talk) 00:41, 24 September 2017 (UTC)
 * Thank you for the quick fix! Now I get why it didn’t show any effect at all, of course. In order to ensure correct alternation also when sorting, I’ll switch to my CSS when TemplateStyles is available, but for now this works fine! I will go live with the template today. Thanks again, XanonymusX (talk) 10:36, 24 September 2017 (UTC)
 * Thank you for the quick fix! Now I get why it didn’t show any effect at all, of course. In order to ensure correct alternation also when sorting, I’ll switch to my CSS when TemplateStyles is available, but for now this works fine! I will go live with the template today. Thanks again, XanonymusX (talk) 10:36, 24 September 2017 (UTC)

Thank you for edits re Hereford Arizona Observatory
Thank you for your recent edits on "Hereford Arizona Observatory" - and the related "Q40787894" (as well as your recent comments on the Village Pump at => "Village pump (technical)") - however - it seems that the altitude value no longer displays in the  on the "Hereford Arizona Observatory" page - Questions => is there some fix for this? - or maybe just leave the altitude value out? - in any regards - Thanks again for your recent comments and edits - and - Enjoy! :) Drbogdan (talk) 15:54, 24 September 2017 (UTC)
 * Indeed it doesn't and I've just spent the last hour trying to track down why. It seems that  works if the value on Wikidata is in metres, but   gives nothing if the value on Wikidata is in feet. I'm loathe to change the Wikidata back to metres as the source is US and it specified feet as the principal unit. I'd rather try to figure out why convert isn't working as I expected it to. However, if I can't fix it, then we should re-edit  to restore feet. I hope you'll be prepared to bear with me for another hour or so, while I try to work through the code in Module:Convert and its sub-modules to find a reason. I'll just bring this to the attention of  in case they have seen the problem before.
 * Specifically:
 * in gives:
 * in gives:


 * → m undefined
 * → ft undefined
 * → undefined undefined
 * in gives:
 * in gives:


 * → m undefined
 * → ft undefined
 * → undefined undefined
 * Should I have expected that, John, Mike? --RexxS (talk) 16:10, 24 September 2017 (UTC)
 * This is weird. It works fine at Kopernik Observatory & Science Center... Thanks. Mike Peel (talk) 16:23, 24 September 2017 (UTC)
 * Ah, found it. Please use the unit of feet rather than talking about anatomical structures. ;-) Thanks. Mike Peel (talk) 16:28, 24 September 2017 (UTC)
 * For my part, in reply to comments by User:RexxS above => Yes - no problem whatsoever - take all the time you like - seems the altitude values should be a bit more in agreement I would think ( ie, 1,423 m (4,670 ft)/"Hereford Arizona Observatory" text VS 4,670 ft (1,420 m)/"Q40787894" data ) - Thanks for your comments and all - and - Enjoy! :) Drbogdan (talk) 16:31, 24 September 2017 (UTC)
 * Thank you,, well spotted! – naturally the Ajax on Wikidata is just small enough for me to misclick on and then disappear leaving no obvious indication (apart from a link, I suppose, but who spots that at my age?). If you really wanted to do some subtle vandalism, that would be a corker! --RexxS (talk) 17:03, 24 September 2017 (UTC)
 * Thank you,, well spotted! – naturally the Ajax on Wikidata is just small enough for me to misclick on and then disappear leaving no obvious indication (apart from a link, I suppose, but who spots that at my age?). If you really wanted to do some subtle vandalism, that would be a corker! --RexxS (talk) 17:03, 24 September 2017 (UTC)

AfC
Doug, you now have access to the AfC helper script - if ever you need it for some reason or another. To install see WikiProject Articles for creation/Helper script. Chris (Kudpung กุดผึ้ง (talk) 11:54, 26 September 2017 (UTC))
 * Thanks, . It will be useful for me to see how it works – so I can make informed comments! – and it might even urge me into finding the time to do some AfC reviews. All the very best. --RexxS (talk) 13:11, 26 September 2017 (UTC)

Administrators' noticeboard/Incidents
There is currently a discussion at Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. - F ASTILY   23:48, 26 September 2017 (UTC)
 * What happened to Before posting a grievance about a user here, please consider discussing the issue with them on their user talk page. as requested at the top of Administrators' noticeboard/Incidents? Or do you think that normal dispute resolution doesn't apply to you? --RexxS (talk) 00:22, 27 September 2017 (UTC)
 * What happened to Before posting a grievance about a user here, please consider discussing the issue with them on their user talk page. as requested at the top of Administrators' noticeboard/Incidents? Or do you think that normal dispute resolution doesn't apply to you? --RexxS (talk) 00:22, 27 September 2017 (UTC)

Dear Rex

In the sight of Almighty God and Jimbo I do hereby and hereinafter solemnly authorize you add "" to any image where you feel I may have forgotten to do so. May the light of the Lord shine down upon you while you are doing this, and smite in a very unpleasant part of their anatomy anyone who questions your Divine authority to do this. Giano   (talk) 11:16, 28 September 2017 (UTC)
 * Thank you . For my part I promise I will only use my superpowers to do good in support of Justice, Freedom, and the Wiki way of life. Cheers --RexxS (talk) 12:46, 28 September 2017 (UTC)
 * Oh no. It's the funny bone isn't it? Being smitten in the funny bone is the worst.  G M G  talk   22:14, 28 September 2017 (UTC)
 * Oh no. It's the funny bone isn't it? Being smitten in the funny bone is the worst.  G M G  talk   22:14, 28 September 2017 (UTC)

Nomination for deletion of Template:Infobox biosphere reserve
Template:Infobox biosphere reserve has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Ten Pound Hammer • (What did I screw up now?) 00:13, 30 September 2017 (UTC)

Finding pages using a specific template
Hi RexxS, As the Go-to-guy for the apocrypha of templatology, could you advise me on how to find which articles in a WikiProject use a template such as for? Cheers, &middot; &middot; &middot; Peter (Southwood) (talk): 18:47, 1 October 2017 (UTC)
 * Try something like this. Nikkimaria (talk) 19:36, 1 October 2017 (UTC)
 * Thank you, . That's spot-on! for what it's worth, note that searching for the canonical template name like   is better than any shortened versions (e.g.  ) because it also finds all the redirects like   and  . I get 24 results – hope that's what you wanted. --RexxS (talk) 20:03, 1 October 2017 (UTC)
 * Thanks, I think that will do the job perfectly. you have nailed it in one. You have a most interesting, useful and amusing collection of talk page stalkers, which is probably why I am also one. Probably less interesting, useful and amusing than some, but, hey, we do what we can. &middot; &middot; &middot; Peter (Southwood) (talk): 20:50, 1 October 2017 (UTC)
 * Thanks, I think that will do the job perfectly. you have nailed it in one. You have a most interesting, useful and amusing collection of talk page stalkers, which is probably why I am also one. Probably less interesting, useful and amusing than some, but, hey, we do what we can. &middot; &middot; &middot; Peter (Southwood) (talk): 20:50, 1 October 2017 (UTC)

Using Infobox_biosphere_reserve
Dear Mr S

I'm trying to us Template:Infobox_biosphere_reserve in articles but its not displaying correctly, it just says [UNESCO Biosphere entry], any ideas?

Thanks

--John Cummings (talk) 14:52, 3 October 2017 (UTC)
 * I assume that you mean the attempt you made in Great Nicobar Biosphere Reserve? If so, then the first problem is that WikidataIB is designed to produce 'opt-in' infoboxes by default. That means that at every article where you want to use the Wikidata functionality, you need to add the parameter ALL. The second problem is that almost all of the statements in are unsourced. WikidataIB is designed to filter out unsourced statements by default. I've updated Template:Infobox biosphere reserve to accept a switch to modify that behaviour, so you also need to add no to each page where you want to import unsourced statements from Wikidata. Previewing   now shows five items imported from Wikidata, although the layout is still a bit of a mess. Is that enough to get you started? --RexxS (talk) 16:50, 3 October 2017 (UTC)
 * I assume that you mean the attempt you made in Great Nicobar Biosphere Reserve? If so, then the first problem is that WikidataIB is designed to produce 'opt-in' infoboxes by default. That means that at every article where you want to use the Wikidata functionality, you need to add the parameter ALL. The second problem is that almost all of the statements in are unsourced. WikidataIB is designed to filter out unsourced statements by default. I've updated Template:Infobox biosphere reserve to accept a switch to modify that behaviour, so you also need to add no to each page where you want to import unsourced statements from Wikidata. Previewing   now shows five items imported from Wikidata, although the layout is still a bit of a mess. Is that enough to get you started? --RexxS (talk) 16:50, 3 October 2017 (UTC)


 * Yes, perfect thank you. On Saturday I will go back and add references to all the statements.
 * Thanks again
 * --John Cummings (talk) 18:22, 3 October 2017 (UTC)

Go ahead
Do as you see fit. I will not edit in fear of your threat(s). Toddst1 (talk) 21:57, 9 October 2017 (UTC)
 * Who gives a shit how you edit? I certainly don't. For what it's worth, that wasn't a threat, it was a promise. --RexxS (talk) 22:04, 9 October 2017 (UTC)
 * Who gives a shit how you edit? I certainly don't. For what it's worth, that wasn't a threat, it was a promise. --RexxS (talk) 22:04, 9 October 2017 (UTC)

Worshop throttled
Please advise. Testing486 (talk) 10:50, 11 October 2017 (UTC)
 * I'm on Skype and IRC right now (#wikipedia-en & #wikimedia-uk IRC channels). Let me know if the problem persists. --RexxS (talk) 11:45, 11 October 2017 (UTC)
 * I'm on Skype and IRC right now (#wikipedia-en & #wikimedia-uk IRC channels). Let me know if the problem persists. --RexxS (talk) 11:45, 11 October 2017 (UTC)

Bilbo
https://github.com/OpenEdition/bilbo − Pintoch (talk) 15:29, 15 October 2017 (UTC)

Talkback
Possible solution found for the no ping plague. TonyBallioni (talk) 00:26, 15 October 2017 (UTC)
 * Thank you,, I'm definitely receiving notifications again now. --RexxS (talk) 13:14, 16 October 2017 (UTC)
 * Thank you,, I'm definitely receiving notifications again now. --RexxS (talk) 13:14, 16 October 2017 (UTC)

Facto Post – Issue 5 – 17 October 2017
{| style="position: relative; margin-left: 2em; margin-right: 2em; padding: 0.5em 1em; background-color:	#7FFFD4; border: 2px solid #00FFFF; border-color: rgba( 109, 193, 240, 0.75 ); border-radius: 8px; box-shadow: 8px 8px 12px rgba( 0, 0, 0, 0.7 );"
 * Facto Post – Issue 5 – 17 October 2017

 

Editorial: Annotations
Annotation is nothing new. The glossators of medieval Europe annotated between the lines, or in the margins of legal manuscripts of texts going back to Roman times, and created a new discipline. In the form of web annotation, the idea is back, with texts being marked up inline, or with a stand-off system. Where could it lead? ContentMine operates in the field of text and data mining (TDM), where annotation, simply put, can add value to mined text. It now sees annotation as a possible advance in semi-automation, the use of human judgement assisted by bot editing, which now plays a large part in Wikidata tools. While a human judgement call of yes/no, on the addition of a statement to Wikidata, is usually taken as decisive, it need not be. The human assent may be passed into an annotation system, and stored: this idea is standard on Wikisource, for example, where text is considered "validated" only when two different accounts have stated that the proof-reading is correct. A typical application would be to require more than one person to agree that what is said in the reference translates correctly into the formal Wikidata statement. Rejections are also potentially useful to record, for machine learning.

As a contribution to data integrity on Wikidata, annotation has much to offer. Some "hard cases" on importing data are much more difficult than average. There are for example biographical puzzles: whether person A in one context is really identical with person B, of the same name, in another context. In science, clinical medicine require special attention to sourcing (WP:MEDRS), and is challenging in terms of connecting findings with the methodology employed. Currently decisions in areas such as these, on Wikipedia and Wikidata, are often made ad hoc. In particular there may be no audit trail for those who want to check what is decided.

Annotations are subject to a World Wide Web Consortium standard, and behind the terminology constitute a simple JSON data structure. What WikiFactMine proposes to do with them is to implement the MEDRS guideline, as a formal algorithm, on bibliographical and methodological data. The structure will integrate with those inputs the human decisions on the interpretation of scientific papers that underlie claims on Wikidata. What is added to Wikidata will therefore be supported by a transparent and rigorous system that documents decisions.

An example of the possible future scope of annotation, for medical content, is in the first link below. That sort of detailed abstract of a publication can be a target for TDM, adds great value, and could be presented in machine-readable form. You are invited to discuss the detailed proposal on Wikidata, via its talk page.

Links

 * Jon Udell, blogpost Annotating to extract findings from scientific papers, 15 December 2015
 * TDM and Libraries, Virginia Tech report
 * Magnus Manske, The Whelming: Scaling up Wikidata editing
 * OCLC and Internet Archive collaborate to expand library access to digital collections, metadata and linking exchange
 * GLOW week in November: Wikidata workshops on politician info

Editor. Please leave feedback for him. If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Opted-out of message delivery to your user talk page. Newsletter delivered by MediaWiki message delivery MediaWiki message delivery (talk) 08:46, 17 October 2017 (UTC)
 * }

Template transclusion limit exceeded on Grade II* listed buildings in South Somerset
Nice to meet you in Oxford last week. We were talking about the template transclusion limit being exceeded (or similar term) on Grade II* listed buildings in South Somerset and I'm sorry I didn't have tome to understand what you were saying about lua (or similar). There is an old discussion at Talk:Grade II* listed buildings in South Somerset and I wondered if you had any more thoughts to add there about how to resolve the issue?&mdash; Rod talk 09:10, 22 October 2017 (UTC)
 * It was certainly a pleasure to meet you too, . I've left some explanations at Talk:Grade II* listed buildings in South Somerset – which will be more pertinent than here – and applied some sticking-plaster to the list article. It now displays everything, but probably not as nicely as you might want. Have a look and see what you think. --RexxS (talk) 16:52, 22 October 2017 (UTC)
 * didn't work because subst: is ignored inside ref tags. -- Red rose64 &#x1f339; (talk) 17:55, 22 October 2017 (UTC)
 * Yes, but once I'd remembered that, the effort of removing the ref tags, doing the subst and then replacing the ref tags seemed like too much work even with an external editor that does find & replace with regular expressions. So I just merely used it to disable the template expansion and see if that lowered the post-expansion size sufficiently to give a chance of a different solution. Which, fortunately, it did. --RexxS (talk) 18:47, 22 October 2017 (UTC)
 * Yes, but once I'd remembered that, the effort of removing the ref tags, doing the subst and then replacing the ref tags seemed like too much work even with an external editor that does find & replace with regular expressions. So I just merely used it to disable the template expansion and see if that lowered the post-expansion size sufficiently to give a chance of a different solution. Which, fortunately, it did. --RexxS (talk) 18:47, 22 October 2017 (UTC)