Jump to content

Template talk:COVID-19 pandemic data: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Line 219: Line 219:


US confirmed case figures and total confirmed case figure needs updating.[[Special:Contributions/119.74.163.85|119.74.163.85]] ([[User talk:119.74.163.85|talk]]) 16:05, 18 March 2020 (UTC)<ref>https://www.worldometers.info/coronavirus/</ref>
US confirmed case figures and total confirmed case figure needs updating.[[Special:Contributions/119.74.163.85|119.74.163.85]] ([[User talk:119.74.163.85|talk]]) 16:05, 18 March 2020 (UTC)<ref>https://www.worldometers.info/coronavirus/</ref>

== Reply to MarioGom ==

Switzerland figure is correct, there are already more than 3000 positive cases in that country right now.<ref>https://www.bag.admin.ch/bag/en/home/krankheiten/ausbrueche-epidemien-pandemien/aktuelle-ausbrueche-epidemien/novel-cov/situation-schweiz-und-international.html#-1199962081</ref>

Revision as of 16:09, 18 March 2020

Half collapsing this template

Am asking around

To see if any one has solutions to half collapsing or adding scrolling that would work... Doc James (talk · contribs · email) 01:13, 15 March 2020 (UTC)[reply]

Okay this works well on desktop, mobile, and in the app User:Bawolff/sandbox/covid One can swipe left and right to see the edges. Doc James (talk · contribs · email) 04:23, 15 March 2020 (UTC)[reply]
It works on desktop and tiny screen. But if we have scrollable, I suggest no default collapsed bits like notes. If you click on a note nothing happens if it is collapsed. Graeme Bartlett (talk) 04:43, 15 March 2020 (UTC)[reply]
Agree with that User:Graeme Bartlett. You want to make the change? I am unable to figure out how. By the way it opens for me on desktop. And I see it open by default on mobile. I also see it as open by default in the app. Doc James (talk · contribs · email) 04:48, 15 March 2020 (UTC)[reply]
While it seems to work well enough in the sandbox, on all of my Mac, Windows, and Android OS the entire left side of the box is cut off, icons and all scrolling left and right does not work. Perhaps looking to the past can provide a solution for today. During the 2009 flu pandemic the Template:2009 flu pandemic data was used and that template then provided the link to the data by country. Given the fluid nature of this event and the constant editing, perhaps a top 10 could be used in a condensed version, with the link provided to all the countries and territories a la the 2009 pandemic data box. Krazytea(talk) 05:14, 15 March 2020 (UTC)[reply]
User:Krazytea What browser are you on and can you provide screen shots? It works fine on a windows machine running chrome. And on an android phone (both mobile and app). Doc James (talk · contribs · email) 05:18, 15 March 2020 (UTC)[reply]
I am using Firefox and the Wikipedia App on Android. Krazytea(talk) 05:23, 15 March 2020 (UTC)[reply]
Okay try now User:Krazytea. I have now adjusted it and it works for me on Firefox. Doc James (talk · contribs · email) 05:24, 15 March 2020 (UTC)[reply]
Just FYI, for [1], the reason i had padding on the right, is that some browsers (in particular firefox desktop on linux) take out space for the scrollbar, and things get cut-off without some padding (I have no idea how much padding is appropriate though, the amount i chose was probably unideal). Bawolff (talk) 05:40, 15 March 2020 (UTC)[reply]
The sandbox works OK for me on Android - with firefox mobile, chrome mobile and chrome desktop (though here is is quite small, but zoomable). Graeme Bartlett (talk) 06:08, 15 March 2020 (UTC)[reply]
As pointed out by Krazytea above, Template:2009 flu pandemic data shows the perfect way to summarize the data in the pandemic main article. Cases by continents and economic regions and worldwide cases (grand totals), and maybe a few top countries, with a link to further information: Cases and deaths by country. Regardless, too much statistical data (e.g. excessively long tables to impede the readability of the main article) is against policy (WP:NOTSTATS). Being scrollable doesn't solve the problem because it hinders printability and has accessibility issues. Zarex (talk) 07:55, 15 March 2020 (UTC)[reply]
Support suggestion by Krazytea and Zarex. Bondegezou (talk) 11:27, 15 March 2020 (UTC)[reply]
I guess I do not. I quite prefer the current format, but I am proposing improvements too (see below). --Checco (talk) 11:34, 15 March 2020 (UTC)[reply]
I do not like the Flu layout either. People want to know what is happening in their country. I know that I want to know what is happening in my country. Lumping Canada, the US and Mexico together makes no sense.
With respect to accessibility / printibility. Can we have a button within the template that takes a person to the full version without scroll? Or has the scrollable version change to the full version? User:Bawolff Doc James (talk · contribs · email) 14:39, 15 March 2020 (UTC)[reply]
hmm. For printability, we could maybe use TemplateStyles so it doesnt scroll when printing. Bawolff (talk) 17:50, 15 March 2020 (UTC)[reply]
I made a new version that should print better, and has a button to expand all - User:Bawolff/sandbox/covid. Thoughts? Bawolff (talk) 21:24, 15 March 2020 (UTC)[reply]
@Bawolff: The button to expand is nice but in Firefox there is a horizontal scrollbar and the vertical borders in the second header row are missing (between Countries, Cases, Deaths, Recoveries and Refs). Zarex (talk) 22:22, 15 March 2020 (UTC)[reply]
@Zarex: I tried to add more padding so the vertical scrollbar doesn't show up, which worked in my testing but might not work everywhere (It seems like firefox requires the extra room, where chrome doesn't, and how much room a scrollbar takes up seems a bit unpredictable). I had trouble making the top border show up in both chrome and firefox. I found a way that works in chrome but not firefox, and a way that works in firefox but not chrome. Nonetheless, I think my new version is a lot better. Bawolff (talk) 23:45, 15 March 2020 (UTC)[reply]
This looks great. Exactly what I was looking for. Doc James (talk · contribs · email) 03:28, 16 March 2020 (UTC)[reply]

Another thing that might make sense, is word wrapping the country columns (But only if you are on a small screen). I tried to do that in my sandbox [2] (View on a small screen width). Honestly, it didn't really help as much as i thought it would. Bawolff (talk) 04:02, 16 March 2020 (UTC)[reply]

Further improvements

I quite like the scrollable box, but the header should be fixed. What do you guys think?
Secondly, what about reducing the first column's width, in order to make the table more readable also for smartphone users.
Many thanks, --Checco (talk) 11:08, 15 March 2020 (UTC)[reply]

How do you want to fix the header User:Checco?
Yes we should reduce the first column's width. Doc James (talk · contribs · email) 14:37, 15 March 2020 (UTC)[reply]
I guess we can keep the header stable, so that it is not scrolled down. --Checco (talk) 15:27, 15 March 2020 (UTC)[reply]
If we do have horizontal scrolling, maybe the flags should also be fixed - that would allow keeping track of what country well also not taking up a lot of room. Anyways, i did a version in my sandbox where the top headers (not the flags) are fixed, although it seems like some mobile browsers don't support it: User:Bawolff/sandbox/covid. Bawolff (talk) 21:41, 15 March 2020 (UTC)[reply]

Thanks for collapsing this table. Much too large otherwise. ---Another Believer (Talk) 16:09, 15 March 2020 (UTC)[reply]

Broken Again

For me, this is the last fully readable version: https://en.wikipedia.org/w/index.php?title=Template:2019%E2%80%9320_coronavirus_pandemic_data&oldid=945630678 edit notes describe the next as "fixed." 138.88.18.245 (talk) 20:09, 15 March 2020 (UTC)[reply]

For me, things get considerable worse with this version: https://en.wikipedia.org/w/index.php?title=Template:2019%E2%80%9320_coronavirus_pandemic_data&oldid=945711573 edit notes describe this as "At least make it so that you don't have to scroll horizontally" but it chops it off halfway through "cases" unless users find a way to scroll horizontally. And scrolling part of the window without the rest can trigger migraines. 138.88.18.245 (talk) 20:09, 15 March 2020 (UTC)[reply]

Revised template

Following a request from User:Doc James I have made a simpler to use template: it is at User:Rich Farmbrough/2019–20 coronavirus pandemic data

All the best: Rich Farmbrough (the apparently calm and reasonable) 22:32, 15 March 2020 (UTC).[reply]

Thanks User:Rich Farmbrough will review. Doc James (talk · contribs · email) 23:34, 15 March 2020 (UTC)[reply]
We will need a way to add references aswell. We change the references as we update the data. Doc James (talk · contribs · email) 03:44, 16 March 2020 (UTC)[reply]

"show all" expands. When expanded, could it be replaced by "show fewer" like "show"/"hide" ?

|-
! colspan="6" | <div class="covid-show-table">[[#covid19-container|[show all]]]</div>{{Navbar-collapsible|{{resize|85%|{{Nowrap|[[2019–20 coronavirus pandemic]] by [[2019–20 coronavirus pandemic by country and territory|country and territory]]}}}}|Template:2019–20 coronavirus pandemic data}}

T3g5JZ50GLq (talk) 14:05, 16 March 2020 (UTC)[reply]

User:T3g5JZ50GLq excellent idea. Have you tested it on desktop / mobile / chrome and firefox? Doc James (talk · contribs · email) 15:35, 16 March 2020 (UTC)[reply]
I think the biggest issue is what should the text say as the "hide" text. Hide doesn't seem right as its just making it scroll and not hide. Bawolff (talk) 18:54, 17 March 2020 (UTC)[reply]

Scrolling no longer working

User:Bawolff you able to fix? Doc James (talk · contribs · email) 22:24, 17 March 2020 (UTC)[reply]

The scrollbars got reverted at [3]. Bawolff (talk) 22:26, 17 March 2020 (UTC)[reply]

Scrolling

I saw that User:Koavf recently removed the scrollbars [4] out of WP:ACCESSIBLE concerns. However, the WP:ACCESSIBLE page simply states that "Wikipedia articles should be accessible to readers using browsers and devices that have limited or no support for JavaScript or Cascading Style Sheets". Browsers that don't support CSS would simply display the full table. Additionally there is a toggle button where people can disable the scrollbars if they don't want them. The scrollbars were also tested to work on the mobile site and app. There is also an accessibility cost to showing a very large table all at once. Anyways, i don't think the rationale behind WP:ACCESSIBLE applies here, and I don't think that the scrollbars in practice introduce any accessibility issues for anyone. I'd like to suggest the scroll bars be added back in. Bawolff (talk) 22:24, 17 March 2020 (UTC)[reply]

Thanks User:Bawolff. Have reverted them. Doc James (talk · contribs · email) 22:25, 17 March 2020 (UTC)[reply]
Doc James, Per MOS:SCROLL and Help:Scrolling list says to not use scrolling lists in article space. "This includes reference lists, tables and lists of article content, image galleries, and image captions." We cannot use scrolling lists in a table in the article namespace. ―Justin (koavf)TCM 22:28, 17 March 2020 (UTC)[reply]
We also have WP:IAR. Lots of people here are supportive of scrolling. Your first link does not work.
I assume you mean Wikipedia:Manual_of_Style#Scrolling_lists_and_collapsible_content Doc James (talk · contribs · email) 22:32, 17 March 2020 (UTC)[reply]
I'm having trouble finding the rationale behind that page or any sort of source for the accessibility claims, or what "devices" the concern is about. The closest i could find is Template:Scrollref TfD, where the concern was about printing, but that doesn't apply here as the full table is shown when printing due to a print stylesheet (You can test with print preview in browser). Bawolff (talk) 22:35, 17 March 2020 (UTC)[reply]
I did, thanks. IAR is not an acceptable excuse for making inaccessible content. I'm frankly shocked that a medical professional would make that argument. ―Justin (koavf)TCM 22:37, 17 March 2020 (UTC)[reply]
You have not described how this makes the content inaccessible. In fact not doing it makes the page less accessible. Doc James (talk · contribs · email) 22:39, 17 March 2020 (UTC)[reply]

So it says "When such features are used, take care that the content will still be accessible on devices that do not support JavaScript or CSS[5], and to the 45% (and climbing) of Wikipedia readers who use the mobile version of the site,[o] which has a limited set of features. Mobile ability to access the content in question is easy to test with the "Mobile view" link at the bottom of each page.[p]" Doc James (talk · contribs · email) 22:36, 17 March 2020 (UTC)[reply]

Doc James, "Scrolling lists should not used in article space. This includes reference lists, tables and lists of article content, image galleries, and image captions." is very explicit. I don't know why you are trying to argue around it. If it's a bad rule, then let's get rid of the rule. Nothing is special about this article. ―Justin (koavf)TCM 22:38, 17 March 2020 (UTC)[reply]
Also removing scrolling is interfering with solving https://phabricator.wikimedia.org/T247702 problem, by making an unstable target to work on. We have previously agreed on having scrolling, and have bypassed some of the negatives. So any bold changes here will need a consensus first. One point of the scrolloing is to make it more accessible. Graeme Bartlett (talk) 22:39, 17 March 2020 (UTC)[reply]
That is the Help:Scrolling list not the MOS on scrolling which makes no such claim. And yes their can be exceptions. Doc James (talk · contribs · email) 22:40, 17 March 2020 (UTC)[reply]

User:Koavf describe how this harms accessibility and we can work to address that. I would argue that it improves accessibility. Doc James (talk · contribs · email) 22:43, 17 March 2020 (UTC)[reply]

Doc James, For whom is accessibility improved, James? Internal scrolling is difficult for users with particular needs when it comes to interfacing with the content: e.g. if they have difficult controlling a mouse and so may use voice commands or a specialized browser that is not going to be able to scroll internal in a page. How could internal scrolling increase accessibility to anyone, particularly these users? ―Justin (koavf)TCM 22:46, 17 March 2020 (UTC)[reply]
Koavf so you are specifically looking at people who use screen readers and you want to make sure that this works for that group of individuals?
Or just those who use "voice commands or a specialized browser"? If so we should reach out to these individuals and see what they need. Doc James (talk · contribs · email) 22:50, 17 March 2020 (UTC)[reply]
Doc James, That is my understanding, based on my limited understanding of accessibility. I am not an expert, so I defer to what I know are the best practices. Rather than try to find everyone to post screenshots on Phabricator and hope that we aren't missing anyone (the sort of person who can't actually read this article is probably not going to be the sort of person who takes all of the extra effort to post why/how and tell everyone else how to fix it), I'm asking you as a fellow Wikimedian who has provided a lot of value to this site for years, an admin who is trusted to have best judgement about how to enforce the norms of this community, and a medical professional whom I am sure wants nothing better than the best outcomes for everyone to please revert yourself for the benefit of those persons who will be impacted by your decision to ignore the best practices about internal scrolling. Additionally, I have asked you questions that you ignored and I would appreciate you answering them. ―Justin (koavf)TCM 22:58, 17 March 2020 (UTC)[reply]
Additionally, I just realized that there is pre-collapsed content and a button to "show all". As MOS:SCROLL points out, this is the exact opposite of what should happen: the content should be rendered and then have the option to collapse it. ―Justin (koavf)TCM 23:00, 17 March 2020 (UTC)[reply]
Koavf if you are not an expert who do you suggest we reach out to? User:RexxS does a lot of work around accessibility. Rexx you have thoughts? As User:Graeme Bartlett states not having scrolling is also an accessibility issue. We really want this to work for everyone. We currently have technical support helping to solve any issues with respect to this. Doc James (talk · contribs · email) 23:01, 17 March 2020 (UTC)[reply]
The show-all button just gets rid of the scroll bars. Nothing is "collapsed". Bawolff (talk) 23:03, 17 March 2020 (UTC)[reply]
Your question was "how does scrolling improve accessibility for anyone"? Well with the table at nearly 200 rows it creates a great deal of white space on a narrow screen pushing content lower in the article and thus making it harder to get too. Doc James (talk · contribs · email) 23:01, 17 March 2020 (UTC)[reply]
Doc James, That may be a usability issue but I'm not seeing an accessibility dimension here to there being white space. It's an annoyance and not aesthetically pleasing but it doesn't prohibit access to anyone based on a different cognitive ability, etc. ―Justin (koavf)TCM 23:40, 17 March 2020 (UTC)[reply]
Doc James, Thank you for asking and for seeking some feedback: I respect that you're putting in effort into this. I don't collaborate with anyone on accessibility here and in fact, I frequently have to fight solo over and over again to get basic accessibility into articles and templates (e.g. table captions). It seems like Wikipedia:WikiProject Accessibility is a good place to go shopping. ―Justin (koavf)TCM 23:39, 17 March 2020 (UTC)[reply]
User:Koavf okay I will ask there. Doc James (talk · contribs · email) 23:46, 17 March 2020 (UTC)[reply]

Note, from googling, the internet seems to say, scrollable things are ok, as long as they have tabindex=0 (so they are focusable and scrollable with keyboard) and label-aria. Which User:Volker E. (WMF) (indirectly via editrequest) got added to the template. Edit: The tabindex doesn't work due to MW banning that attribute (phab:T247910). However firefox still considers it a focusable element, so its all ok in firefox at least. Bawolff (talk) 23:10, 17 March 2020 (UTC)[reply]

User:Koavf my request of you is to help us solve the accessibility issues of scrolling so that they are no longer an issue. Would you not agree that this would be win win? Doc James (talk · contribs · email) 23:14, 17 March 2020 (UTC)[reply]
Okay I have reached out to people on FB for someone who uses voice commands. Doc James (talk · contribs · email) 23:39, 17 March 2020 (UTC)[reply]
Doc James, I don't know that there can be internal scrolling that is accessible. I do think that a broader best practice should be considered but that's not on the level of this one single template but the level of the MOS and help page mentioned above: that way, it's applicable to the whole encyclopedia. ―Justin (koavf)TCM 23:41, 17 March 2020 (UTC)[reply]
I think we should give the tech folks a chance to work on it. Doc James (talk · contribs · email) 23:46, 17 March 2020 (UTC)[reply]

First of all, can I request that we don't go back-and-forth editing the CSS in and out while this is under discussion, please? It would be helpful if we can see the template with scroll bars just for the purposes of checking whether we are creating accessibility problems by adding them.

The way I would usually tackle accessibility concerns is to try to simulate the experience of a possible disadvantaged user:

  • I can confirm that none of the screen readers I use to check have any problems with the table, which is expected, as they generally take no notice of CSS and the table is properly marked up with column and row headers and scopes. We could be more certain if we asked Graham87 to have a look at Template:2019–20 coronavirus pandemic data and make sure that he can read the entire table and the accompanying notes.
  • I can confirm that on Chrome and Firefox, I am able to focus the links in the table using just the keyboard, and so am able to read the entire table and notes without the use of a mouse.
  • I can confirm that on my mobile phone (a fairly generic Android device), I see the entire table without scroll bars, so there is no issue for me there.

That leads me to suggest that there probably isn't any class of disadvantaged user that those scroll bars cause problems for. I'm coming round to the view that our guidance at MOS:SCROLL is being taken rather too mechanically at Help:Scrolling list. MOS:SCROLL requires us to "take care that the content will still be accessible on devices that do not support JavaScript or CSS, and to the 45% (and climbing) of Wikipedia readers who use the mobile version of the site". It looks to me like the template developers have done their due diligence in this case, and I believe that we don't need to invoke IAR to show that this template is a reasonable exception to the general injunction not to use scrolling lists in article space. Of course, that's just my opinion, and someone may yet find a group of users that I hadn't considered, who are disadvantaged by the scroll bars, so perhaps we should keep the issue under review for a while, and await any reports of readers finding problems with the template before coming to a final decision. Cheers --RexxS (talk) 23:54, 17 March 2020 (UTC)[reply]

RexxS: Just to confirm, are you talking about the mobile site or mobile app? There should be scrolling on mobile website [6], but not the mobile app [7]. Bawolff (talk) 23:59, 17 March 2020 (UTC)[reply]
Voice readers don't work here.....and mobile view is not readable.--Moxy 🍁 00:12, 18 March 2020 (UTC)[reply]
User:Moxy what issues are you seeing with mobile view? I am able to scroll right an left on my android phone. With respect to voice readers are you talking about the ones built into your phone? Doc James (talk · contribs · email) 00:31, 18 March 2020 (UTC)[reply]
I use NVDA.....as for scrolling in mobile view both horizontal and vertical are there. This template is not abnormal in this type of function. Don't see a solution....just pointing out a fact that very few of us deal with.--Moxy 🍁 00:48, 18 March 2020 (UTC)[reply]
User:Moxy you say "mobile view is not readable"? You means that screen readers do not work on this table when on mobile? Does it work for this table without scrolling? Doc James (talk · contribs · email) 01:59, 18 March 2020 (UTC)[reply]
Screen reader cant begin in the right place because vertical and horizontal side-scrolling is in effect thus the template is mostly hidden from the reader. File:Screen shot of pandemic template.jpg. But again this is a normal problem and why we recommend prose text.--Moxy 🍁 02:09, 18 March 2020 (UTC)[reply]
User:Moxy so this reads fine with a screen reader? Template:2019–20 coronavirus pandemic data(nonescroll). What about it you hit the "show all" button to turn off the scroll does it work than? Doc James (talk · contribs · email) 03:39, 18 March 2020 (UTC)[reply]
(edit conflict) @Bawolff: Unfortunately, using mobile view on a desktop machine often does not accurately reflect what is seen when viewing a Wikipedia page on a mobile device. I agree that viewing https://en.m.wikipedia.org/wiki/Template:2019%E2%80%9320_coronavirus_pandemic_data using Chrome on my desktop machine shows scroll bars. However, actually viewing that page on my Android phone using 'Chrome for mobile' shows no scroll bars as they are particularly pointless on mobile phones. --RexxS (talk) 00:18, 18 March 2020 (UTC)[reply]
Interesting. For me, chrome version 80 on my android phone - area is scrollable. Scrollbars only show up during dragging (Seems to be generally how the ui works on my phone. Bawolff (talk) 01:04, 18 March 2020 (UTC)[reply]
Yeah, there's no screen reader problem with scrolling. The mobile view doesn't work at all well with desktop screen readers. Graham87 03:46, 18 March 2020 (UTC)[reply]
User:Graham87 thank you. So would you say this is sufficiently accessible than? With respect to mobile does it work when there is no scrolling? Or does it not work regardless of whether there is scrolling or not? Doc James (talk · contribs · email) 04:24, 18 March 2020 (UTC)[reply]
Error in Template:Reply to: Input contains forbidden characters. Yes, it's accessible enough. Re mobile, I'm not very familiar with that environment at all, but I'd say it wouldn't make any difference re scrolling. Graham87 06:14, 18 March 2020 (UTC)[reply]
Such a problem for editing we have a script Wikipedia:Editing on mobile devices#Scrolling....that should be implemented all over.Wikipedia:Manual of Style/Accessibility/Data tables tutorial.--Moxy 🍁 06:35, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 17 March 2020

Change 41 to 50 cases in Costa Rica Source: Costa Rican Ministry of Health Official Website https://www.ministeriodesalud.go.cr/index.php/centro-de-prensa/noticias/741-noticias-2020/1573-casos-confirmados-covid-19-llegan-a-los-50 Edacunav (talk) 22:52, 17 March 2020 (UTC)[reply]

 Done. Thanks for the source! RayDeeUx (talk) 23:02, 17 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Panama has 86 confirmed cases. Change 69 to 86. Source: https://www.tvn-2.com/nacionales/Panama-registra-confirmados-coronavirus-sancionado_0_5535196515.html 190.219.162.190 (talk) 00:20, 18 March 2020 (UTC)[reply]

Updated, thank you. Graeme Bartlett (talk) 02:18, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Sweden has eight deaths as of 4.30 am CET March 18, current number in the template is 7. Source: https://www.svt.se/datajournalistik/the-spread-of-the-coronavirus/ Eliste96 (talk) 03:31, 18 March 2020 (UTC)[reply]

 Not done: I just checked the source you provided and it says 7 deaths in Sweden. WorldOMeter is showing 8 deaths in Sweden. In this case I favor the source from SVT over WorldOMeter. Alucard 16❯❯❯ chat? 07:35, 18 March 2020 (UTC)[reply]
"In total, eight people have now died due to the virus in Sweden" it says under the headline "Currently in Sweden" on the SVT source and also it was widely reported here yesterday of the eighth death. For example, here https://omni.se/nytt-svenskt-dodsfall-aldre-patient-har-dott-i-sormland/a/pLkjxR (in Swedish but the third sentence says 'it's the eighth death in Sweden") — Preceding unsigned comment added by Eliste96 (talkcontribs) 10:29, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Mexico confirmed cases: 93

https://www.eluniversal.com.mx/nacion/coronavirus-mexico-17-de-marzo-registran-11-casos-mas-suman-93 Lpgomar (talk) 04:32, 18 March 2020 (UTC)[reply]

 Partly done: The numbers were updated but the secondary source was not. So I went ahead and updated the source Lpgomar Alucard 16❯❯❯ chat? 07:44, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Change Serbia cases from 72 to 83 (as of 8am CET today; same source) Matija (talk) 10:10, 18 March 2020 (UTC)[reply]

 Done. Thank you. --MarioGom (talk) 10:18, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Numbers on Spain: affected 13,716, 558 deaths and 1,081 recovered. Updated today. Source: https://www.elmundo.es/ciencia-y-salud/salud/2020/03/18/5e71c29f21efa0f84a8b4590.html Thedannysawyer (talk) 10:52, 18 March 2020 (UTC)[reply]

It got updated, but we had 598 deaths. Graeme Bartlett (talk) 11:33, 18 March 2020 (UTC)[reply]

Extended-confirmed-protected edit request on 18 March 2020

Please update San Marino cases counts as follows: confirmed: 119, recovered: 4, deaths: 11. Press message from the official source: http://www.iss.sm/on-line/home/articolo49014129.html Garyczek (talk) 10:58, 18 March 2020 (UTC)[reply]

Thanks for the alert, I have updated. Graeme Bartlett (talk) 11:37, 18 March 2020 (UTC)[reply]

RfC: Explanation for Netherlands: added, removed, added, removed, etc.

I have understood that - de facto - the figures presented for Netherlands are an aggregate for the Kingdom of the Netherlands, consisting of the a) country of the Netherlands, b) Aruba, c) Curaçao, and d) Sint Maarten. Since, however, the sole name Netherlands is ambiguous, I plead for at least adding - and keeping added - as a note that Netherlands as mentioned in the table is to be understood the whole kingdom consisting of the four countries each with their own responsible authority. I think this is essential for a good understanding of the nature of the figures. This is a matter of both geography (one country lies in Europe, one in the southeastern Caribbean, two in the northeastern Caribbean) and politics (since it concerns the political division of one kingdom into four countries). Notes to this end have been added and removed several times. Why and by whom they have been removed, I cannot seem to retrace in the edit history, either because the rate of edits is rather high or because no comment was added from which I succeeded to understand that it concerned a change with respect to Netherlands. Those who like to have such a note removed, please provide arguments.Redav (talk) 14:24, 18 March 2020 (UTC)[reply]

Redav: what is your exact proposal and options being discussed? --MarioGom (talk) 15:40, 18 March 2020 (UTC)[reply]

Switzerland updates and sources reliability

There is a pending update for Switzerland, I'm not sure what are the right numbers. Multiple sources are supposedly up-to-date but with different numbers: [8], [9]. What is the figure we're looking for? "Tested positive"? "Confirmed"? --MarioGom (talk) 14:49, 18 March 2020 (UTC)[reply]

Request amendment for Germany and Switzerland

Germany figure has increased sharply to 11302 and Switzerland to 3070 respectively119.74.163.85 (talk) 15:29, 18 March 2020 (UTC)[1] [2][reply]

 Done. Updated Switzerland according to worldometers.info, although I still have doubts about the correct number, see the above thread. --MarioGom (talk) 15:39, 18 March 2020 (UTC)[reply]

Request edit for Vietnam

Confirmed 76 cases. https://tuoitre.vn/bo-y-te-thong-bao-ghi-nhan-benh-nhan-covid-19-thu-76-ca-thu-10-trong-ngay-20200318223050473.htm 2601:204:E37F:FFF1:40D8:4F58:9294:BFF6 (talk) 15:54, 18 March 2020 (UTC)[reply]

 Done. --MarioGom (talk) 16:02, 18 March 2020 (UTC)[reply]

United States figures and total confirmed case figure

US confirmed case figures and total confirmed case figure needs updating.119.74.163.85 (talk) 16:05, 18 March 2020 (UTC)[3][reply]

Reply to MarioGom

Switzerland figure is correct, there are already more than 3000 positive cases in that country right now.[4]