User talk:Tagishsimon

From Wikidata
Jump to navigation Jump to search

Qs[edit]

Instead of typing [[Q20747326|Mary Mogg]], you can use {{Q|20747326}}. This renders as:

Mary Mogg (Q20747326)

and has the advantage of displaying the label in the reader's preferred language. Same goes for properties; {{P|496}} renders as:

ORCID iD (P496)

Cheers, Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:38, 27 September 2016 (UTC)

Thanks. I'm taking first steps, as you see. Related to the experimental w:User:Tagishsimon/test, a listing of ODNB women with no wikipedia article. --Tagishsimon (talk) 20:07, 27 September 2016 (UTC)

Beleidigungen[edit]

Mehr hast du nicht auf dem Kasten? --Succu (talk) 23:17, 2 November 2016 (UTC)

Grow up. --Tagishsimon (talk) 23:19, 2 November 2016 (UTC)
Soll ich größer oder erwachsener werden. Beides ist nicht mehr möglich. --Succu (talk) 23:22, 2 November 2016 (UTC)

Oh, Jeez (Q27824086)[edit]

Why did you tag a Southpark episode of being human and female? Multichill (talk) 15:23, 11 November 2016 (UTC)

By not noticing it in a large petscan listing. You need to be able to deal with a small number of errors in a large number of automated edits ... eventually a human will come along and fix it. --Tagishsimon (talk) 15:26, 11 November 2016 (UTC)

Items for women[edit]

I saw your comment about women wrongly tagged as male. A serious issue, but I suspect there are more with no gender at all; see the column in Wikidata:Database reports/Humans with missing claims, and please fix a few from time to time. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:57, 12 December 2016 (UTC)

Thanks. That's handy. --Tagishsimon (talk) 21:03, 12 December 2016 (UTC)

Kindly let me know what I Have to do in the below link and what is the cause of its creation[edit]

https://www.wikidata.org/wiki/Q28017188 yours sincerely, --Maaley (talk) 00:28, 16 December 2016 (UTC)

Item to be delete[edit]

In RFD there are one or more item proposed for the deletion created by you. If you do not agree you can participate in the debate --ValterVB (talk) 23:38, 3 March 2017 (UTC)

Romans[edit]

Hi Tagishisimon. Thanks for your help with adding name statements to people items. BTW, you might want to look into the convention for (some) Romans: Wikidata:WikiProject_Names/Help#Roman_names. Those with these wont have P735/P734.
--- Jura 07:33, 17 December 2017 (UTC)

Idem. --Romulanus (talk) 10:20, 17 December 2017 (UTC)
Thanks Jura & Romulanus. I'll roll my edits back in line with Wikidata:WikiProject_Names/Help#Roman_names. --Tagishsimon (talk) 11:04, 17 December 2017 (UTC)

named as (P1810) and described at URL (P973)[edit]

Not sure if I steered you in slightly the wrong direction, but you should watch out when using named as (P1810) and described at URL (P973): on an item like Given Lubinda (Q5565823) you have them the wrong way around at the moment: named as (P1810) should only be used as a qualifier, and described at URL (P973) should not be used as one. You can see the definition at the property constraint (P2302) section of each Property (or if you turn on the checkConstraints Gadget in your Preferences --Oravrattas (talk) 21:56, 22 December 2017 (UTC)

I'll be switching them around :) --Tagishsimon (talk) 23:34, 22 December 2017 (UTC)

Heads of State[edit]

Woot! The Heads of State Report is looking a lot better now. Thanks for filling in all those gaps! --Oravrattas (talk) 07:11, 31 December 2017 (UTC)

Creación de un nuevo actor de doblaje[edit]

Hola, gracias por tu respuesta!! Ya había leído ese artículo pero la verdad no se que hacer, no se como o donde he de dar de alta la información o si he de usar una plantilla ya diseñada o si he de partir de 0, me gustaría tener un formato similar al del actor Pepe Mediavilla. Gracias por tu ayuda. Javi.abengozar (talk) 08:32, 27 January 2018 (UTC)

@Javi.abengozar: comenzar en la página a la que me he vinculado - [1]. Agregue el nombre y la breve descripción, pulse Aceptar. En la siguiente página, presiona "Agregar declaración". En el campo Propiedad, comience a escribir "instancia de". Seleccione la "instancia de" que se ofrece como menú desplegable debajo del campo de propiedad. Ahora seleccione el valor, en este caso "ser humano". Presione el botón Publicar. En resumen, debe "Agregar declaración", seleccionar la propiedad que desea, luego agregar el valor de esa propiedad, por lo tanto, "sexo o género", "país de nacionalidad", etc. Tal vez vaya a una página existente y presione "editar" contra una propiedad existente para ver cómo se comporta la interfaz de usuario. Espero que ayude. Disculpas por google-translate español! --Tagishsimon (talk) 11:59, 27 January 2018 (UTC)

Chinese given name[edit]

Hello,

On December 17 you added a lot of given name (P735) to Chinese people like this [2]. But the Chinese people's first name is their family name, isn't it? For example, Mao Zedong (Q5816) is called "Mao", not "Zedong". Some of his children are called Mao too. What do you think? It seems that you corrected Roman people, why not Chinese ones? --El Caro (talk) 14:51, 26 March 2018 (UTC)

@El Caro: Agreed. Why? No-one pointed out the Chinese error, and it didn't occur to me. I've had a wander through my edits & removed some more. --Tagishsimon (talk) 18:00, 26 March 2018 (UTC)
This is where we are right now - at least for the current state of China; I'll add older incarnations of the state later. Added. --Tagishsimon (talk) 18:19, 26 March 2018 (UTC)
SELECT ?item ?itemLabel ?givenLabel
WHERE 
{
  {?item wdt:P27 wd:Q148 .}
  UNION
  {?item wdt:P27 ?state .
   ?state wdt:P31 wd:Q50068795 . }
  ?item wdt:P735 ?given .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
order by ?givenLabel
Try it!
Thank you! --El Caro (talk) 06:37, 27 March 2018 (UTC)
Thanks, El Caro. I've now been through the complete list & removed all probably incorrect given names; with luck, we're now good. --Tagishsimon (talk) 14:17, 27 March 2018 (UTC)

Share your experience and feedback as a Wikimedian in this global survey[edit]

WMF Surveys, 18:57, 29 March 2018 (UTC)

Please stop[edit]

Your current edits are very flawed, and also flooding the RC without a bot/flood flag. Please stop. Thanks. --Yair rand (talk) 04:03, 12 April 2018 (UTC)

What's the flaw? --Tagishsimon (talk) 04:07, 12 April 2018 (UTC)
Edits to items like Q4 and Q30 are importing nonsense. Among other edits, label imports are violating WD:L. Those are just the ones I noticed in a few seconds of looking. In any case, doing so many edits unflagged is itself problematic and against policy. --Yair rand (talk) 04:12, 12 April 2018 (UTC)
I grant you 4 & 30. They seem to be outliers. The rest? Better to have the en.wiki article title as a label, than no label. You're now doing more harm than good - [3] for instance? --Tagishsimon (talk) 04:16, 12 April 2018 (UTC)
You can't just copy the enwiki article title and assume it will be a valid label: Rules are different on capitalization, disambiguating bracketed text and text after commas in place names, and other issues. "Chengqu Subdistrict, Yuanshi County" is not the correct label, per WD:L. Making so many edits so fast makes it impossible to check for incorrect additions. --Yair rand (talk) 04:21, 12 April 2018 (UTC)
I don't assume it is the best label. I presume it is better than no label, and that if it can be improved, it will be. --Tagishsimon (talk) 04:25, 12 April 2018 (UTC)
Really? [4], [5] And the problems with these were? --Tagishsimon (talk) 04:27, 12 April 2018 (UTC)
The options are not "don't do it at all" or "do it with lots of flaws", they're "do it well" or "do it with thousands of mistakes, and then spend countless hours cleaning it up". I don't know how we're going to track down all the edits like this and this, but it's probably going to involve a whole lot more manual effort than went into making the problematic edits in the first place. While m:Cunningham's Law may apply to incorrect label capitalizations, it's not a fair way to get things fixed. Please don't make edits on a large scale that you're not willing to take responsibility for. (Sorry, I'm being a bit harsher than I intended, but I'm going to have to spend a lot of time looking through your edits because of this, which is formally always the bot operator's responsibility, but...) --Yair rand (talk) 04:42, 12 April 2018 (UTC)
I'm quite prepared to take responsibility for my edits. I'm not prepared to tolerate the best driving out the good. Are you /seriously/ telling me that you're reverting abouse you don't like capitalisation? I grant 4, 30 & 40 are egregious, as is the football. What about [6], [7]? --Tagishsimon (talk) 04:52, 12 April 2018 (UTC)
I had already added the label for Q9034636 with the correct capitalization before your prior post, but I don't intend to fix up all of them. It is generally easier to add the correct version than it is to fix a wrong one, as we generally want to avoid bots undoing the more correct work of a human editor. It's more efficient to rollback, since there are too many to easily fix up manually. Unless you're volunteering to go through the rest and fix up the capitalizations manually? --Yair rand (talk) 04:58, 12 April 2018 (UTC)
It would certainly seem to me that I could do it faster than you, having the original input information to hand. We disagree, however, that capitalisation necessitates rollback. --Tagishsimon (talk) 05:06, 12 April 2018 (UTC)
If you're willing to go through them and fix them, I don't need to rollback the edits. Are you willing to go through the edits and fix the various issues? --Yair rand (talk) 05:13, 12 April 2018 (UTC)
  • I think it's a good idea to attempt to do something about these items (with a sitelink in a language, but no label in the same). However, most of these were skipped by various bot operators on purpose. It might be worth opening a discussion on project chat on how to go about these.
    --- Jura 06:47, 12 April 2018 (UTC)

Reminder: Share your feedback in this Wikimedia survey[edit]

WMF Surveys, 01:40, 13 April 2018 (UTC)

Ping IP[edit]

I never saw a ping, seems not to work for IPs. Thanks for all your help!!! 77.180.35.91 17:01, 23 April 2018 (UTC)

So please, get an account. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:22, 5 May 2018 (UTC)

Wikidata:Requests for comment/Sort identifier statements on items that are instances of human[edit]

Since you work on human data, maybe you are interested in commenting. 77.180.110.58 16:49, 25 April 2018 (UTC)

sex or gender (P21) = Klim (Q581072)[edit]

Hello, please review edits like [8]. — Ivan A. Krestinin (talk) 09:12, 5 May 2018 (UTC)

@Ivan A. Krestinin: Yes, that's fairly poor. Another ten examples found & fixed; zero left. Thanks for letting me know. --Tagishsimon (talk) 11:40, 5 May 2018 (UTC)

Taking you up on your offer to help[edit]

Thanks for your help in connection with my project chat request about creating a list of Q values.

Before I asked my current question, I want to point out that your query led to some ancillary issues.

The way the table was originally created, it doesn't have a count of lines, and when I saw that your output had 351 entries when I was thinking there should be 349 lead me to realize that to additional items have been added so I have updated the count on that page.

The second issue is that the editor who helped create the templates is no longer active. While they were generally fine and have worked for the purposes for which they were intended, the fact that you had a number of failed hits revealed that the original editor used a canonical form of the article title. If you teams have a nonstandard title, and while the standard title always exists, in some cases it is a redirect. That's what caused your query to have a small number of failed items. I've gone to the template and replaced the redirects with a direct link so while I do not anticipate having to run the query again, if it were or if someone else were to run a similar query, they would not run into that problem.

While that wasn't your intention, thank you for highlighting a couple issues that have now been resolved.

On to my question.

I'm still unhappy (not with you) that the system requires a nonstandard way of identifying the main category. It's a pain, and one of the reasons I thought I'd look into quick statements.

However, I tried creating some quick statements to add the main category and failed miserably. I'm copying the statements below:

Q30325978 P910 "Category:Cal Poly Mustangs women's basketball"

Q30325977 P910 "Category:Cal State Fullerton Titans women's basketball"

Q30325901 P910 "Category:Cal State Northridge Matadors women's basketball"

Q5684359 P910 "Category:Hawaii Rainbow Wahine basketball"

Q21565045 P910 "Category:Long Beach State 49ers women's basketball"

Q30592518 P910 "Category:UC Davis Aggies women's basketball"

Q30325980 P910 "Category:UC Irvine Anteaters women's basketball"

Q30325939 P910 "Category:UC Riverside Highlanders women's basketball"

Q30325905 P910 "Category:UC Santa Barbara Gauchos women's basketball"

In my first attempt, I didn't have the quotes around the category and that failed so I thought that was the problem but after adding the quotes it still fails. Can you tell me what I'm missing?--Sphilbrick (talk) 21:41, 14 May 2018 (UTC)

@Sphilbrick: sorry, I'm stumped, too. I've tried all sorts of variations, but all yield "invalid snak data", which error message doesn't lead to any greater insight. Very odd. @Magnus Manske: - what are we missing? --Tagishsimon (talk) 22:20, 14 May 2018 (UTC)
Wow, going after the big guns! I guess I don't have to feel embarrassed that I missed something trivial.--Sphilbrick (talk) 23:34, 14 May 2018 (UTC)

Finding errors[edit]

One other question: I'm running some quick statements in batch mode. Several went fine but a recent batch 2601, says it has two errors. I don't know how to look and see the errors. link--Sphilbrick (talk) 14:04, 15 May 2018 (UTC)

@Sphilbrick: Sadly, the documentation says, of batch mode, "But there are also drawbacks: You can only see the total number of errors, not the statements that produced an error. Actually, you can not see any statement." :(
Equally, I can probably knock up a SPARQL query, if that'll help you track down the couple of records which didn't get actioned ... you'd need to tell me what the batch was doing. --Tagishsimon (talk) 23:26, 15 May 2018 (UTC)
That's OK, I just assumed it would be easy to track down. I have to look at many of these items manually for other reasons, so I may figure it out then, and if not, I don't think the world will end. Thanks for pointing me to the documentation, which also explains some other things.--Sphilbrick (talk) 01:41, 16 May 2018 (UTC)

--Sphilbrick (talk) 18:41, 25 May 2018 (UTC)== Checking my work ==

With your help, I've been working on adding data to articles about NCAA Division I women's basketball teams in the US.

I've reached the point where I'd like to do a couple things that I think are related. I'd like tolearn how to run a report to output the results, for example create a list of all nicknames. Before I do that, I'd like to double check my work by running a report to identify the elements I have added to see which ones I'm missing and/or made a mistake.

I'm not quite sure where to start. Do I create a report or a query are these the same things?

You may recall that you created a report for me to generate a Q values from the article titles (as an aside, that report had a small glitch arising from redirects which I believe I fixed).

I'm not sure whether I start with that report and ask for different output, whether I create a report that starts with the Q values (which I have in a spreadsheet somewhere) or do something else.

As a specific example, some of the teams have a description and in some cases it is blank. I want to fill in the blank ones with quick statements (which I know how to do), but I'd like to make a list of all the Q values with blank descriptions. However, rather than simply figure out how to do a report that lists only the blank descriptions I'd like a report that lists all descriptions so I can inspect the existing ones to see if there are any that need correcting, then sort the list to get all the blank ones and then extract the Q values and do quick statements.

Does this approach makes sense?

Then I like to rinse and repeat for home venues (I filled in most but I know there are a few that are missing), nicknames, and other properties.

Thanks in advance for all the help you've already provided — let me know if I should post this in the chat rather than directly to you.--Sphilbrick (talk) 14:43, 25 May 2018 (UTC)

If I'm reading correctly, this is outside your normal editing times, so I posted at Chat.--Sphilbrick (talk) 17:29, 25 May 2018 (UTC)
@Sphilbrick: The big first question is, whether there are some values which are found only on your records, such that we can find your set of records to interrogate further; or whether we have to work from the list of Q values. Right now, I'm working from the 339 Q values - the 11 or so that were astray are still astray ... you can add them. Or you can identify that a record with statements X = value Y and statement P = value Q will always be one of your teams, and we'll do a more conventional select.
With that preamble, here's a report showing a handful of values for each of your teams.
SELECT ?item ?itemLabel ?nickname ?head_coachLabel ?leagueLabel ?home_venueLabel
WHERE 
{
  VALUES ?item  {wd:Q4705232 wd:Q5461417 wd:Q5547760 wd:Q6365108 wd:Q6815890 wd:Q6868282 wd:Q7010204 wd:Q7056976 wd:Q7566589 wd:Q16201949 wd:Q16164975 wd:Q16202097 wd:Q16154463 wd:Q16147656 wd:Q16822493 wd:Q16823123 wd:Q17002222 wd:Q16972809 wd:Q17007074 wd:Q16969626 wd:Q19576850 wd:Q21531595 wd:Q21550167 wd:Q22096806 wd:Q25000663 wd:Q28444659 wd:Q28444662 wd:Q28868362 wd:Q29468792 wd:Q29468768 wd:Q29470713 wd:Q29469017 wd:Q29641529 wd:Q29791438 wd:Q29791447 wd:Q30325928 wd:Q30325823 wd:Q30326010 wd:Q30325964 wd:Q30325923 wd:Q30325998 wd:Q30325830 wd:Q30325941 wd:Q30325887 wd:Q30325898 wd:Q30325871 wd:Q30326014 wd:Q30325815 wd:Q30325986 wd:Q30325824 wd:Q30325889 wd:Q30325915 wd:Q30325875 wd:Q30325893 wd:Q30325831 wd:Q30325804 wd:Q30325973 wd:Q30325983 wd:Q30325988 wd:Q30325921 wd:Q30593141 wd:Q5547572 wd:Q6694561 wd:Q6837807 wd:Q6861792 wd:Q7598727 wd:Q7700100 wd:Q7707441 wd:Q7707839 wd:Q16154307 wd:Q16154256 wd:Q16154314 wd:Q16971255 wd:Q17507741 wd:Q19578136 wd:Q19864208 wd:Q20657621 wd:Q21546434 wd:Q28206758 wd:Q28444629 wd:Q29092785 wd:Q29094771 wd:Q29092793 wd:Q29468946 wd:Q29468780 wd:Q29641538 wd:Q30325908 wd:Q30325897 wd:Q30325822 wd:Q30325965 wd:Q30325917 wd:Q30325975 wd:Q30325882 wd:Q30325877 wd:Q30325968 wd:Q30325926 wd:Q30325914 wd:Q30325910 wd:Q30325873 wd:Q30325939 wd:Q19576965 wd:Q19577169 wd:Q19577277 wd:Q19578059 wd:Q22095719 wd:Q22096531 wd:Q23303100 wd:Q25005059 wd:Q29093013 wd:Q29092990 wd:Q29096404 wd:Q29468958 wd:Q29469127 wd:Q29470718 wd:Q29470716 wd:Q29791434 wd:Q30325932 wd:Q30325946 wd:Q30325978 wd:Q30325918 wd:Q30325909 wd:Q30325884 wd:Q30325907 wd:Q30325985 wd:Q30325806 wd:Q30326001 wd:Q30325913 wd:Q30326003 wd:Q30325996 wd:Q30325874 wd:Q30325929 wd:Q30325829 wd:Q30325872 wd:Q30325805 wd:Q30325809 wd:Q30632927 wd:Q30593394 wd:Q16154177 wd:Q52623210 wd:Q29092977 wd:Q29075948 wd:Q29468773 wd:Q29468769 wd:Q29469021 wd:Q29468791 wd:Q29468782 wd:Q29572582 wd:Q29791436 wd:Q29791431 wd:Q29791432 wd:Q30325896 wd:Q30325888 wd:Q30325999 wd:Q30325991 wd:Q30325883 wd:Q30325927 wd:Q30325930 wd:Q30325995 wd:Q30325919 wd:Q30325922 wd:Q30325879 wd:Q30325885 wd:Q30325989 wd:Q30325992 wd:Q30325905 wd:Q30325960 wd:Q30325808 wd:Q30325811 wd:Q30588386 wd:Q30591624 wd:Q30588521 wd:Q5161554 wd:Q5684359 wd:Q6064630 wd:Q6480880 wd:Q7058420 wd:Q7587318 wd:Q7895967 wd:Q16147605 wd:Q16201295 wd:Q16154116 wd:Q16154474 wd:Q16823182 wd:Q16961952 wd:Q16958990 wd:Q16982691 wd:Q16983723 wd:Q19577165 wd:Q19577174 wd:Q19577972 wd:Q20708371 wd:Q22096783 wd:Q28444648 wd:Q29095277 wd:Q29468771 wd:Q29468775 wd:Q29468778 wd:Q29470819 wd:Q29468781 wd:Q29470721 wd:Q29791430 wd:Q29791433 wd:Q29791435 wd:Q29791444 wd:Q30326011 wd:Q30325894 wd:Q30325816 wd:Q30325916 wd:Q30325827 wd:Q30325958 wd:Q30326008 wd:Q30325895 wd:Q30325943 wd:Q30325997 wd:Q30325812 wd:Q30325937 wd:Q30325947 wd:Q30325961 wd:Q30325906 wd:Q30325890 wd:Q30325972 wd:Q30325980 wd:Q30325931 wd:Q30325940 wd:Q30325900 wd:Q4951157 wd:Q5547840 wd:Q6984699 wd:Q7082333 wd:Q7569490 wd:Q7864012 wd:Q16151501 wd:Q16153415 wd:Q16201351 wd:Q16154193 wd:Q16205772 wd:Q16247862 wd:Q16969601 wd:Q16980215 wd:Q30325899 wd:Q30325902 wd:Q30325814 wd:Q30593139 wd:Q30593140 wd:Q30588227 wd:Q30592518 wd:Q4836897 wd:Q4947831 wd:Q5002584 wd:Q5020513 wd:Q5148748 wd:Q5330300 wd:Q5367124 wd:Q6365004 wd:Q6392430 wd:Q6460014 wd:Q7054636 wd:Q7080913 wd:Q7260974 wd:Q7566995 wd:Q7708113 wd:Q7863949 wd:Q7914438 wd:Q16154049 wd:Q16164964 wd:Q16970007 wd:Q16970019 wd:Q19577159 wd:Q19577406 wd:Q19577742 wd:Q19863871 wd:Q21565045 wd:Q22096156 wd:Q28449390 wd:Q28444660 wd:Q28805615 wd:Q28805614 wd:Q29092781 wd:Q29093805 wd:Q29092789 wd:Q29468783 wd:Q29470715 wd:Q29572324 wd:Q29641524 wd:Q29791446 wd:Q29791441 wd:Q30325977 wd:Q30325901 wd:Q30326007 wd:Q30325911 wd:Q30325810 wd:Q30325825 wd:Q30325821 wd:Q30325944 wd:Q30325876 wd:Q30325903 wd:Q30325924 wd:Q30325807 wd:Q30325880 wd:Q30325826 wd:Q30325828 wd:Q30325820 wd:Q30325813 wd:Q30325987 wd:Q30325962 wd:Q30325942 wd:Q30325886 wd:Q30591635 wd:Q30632926 wd:Q5131581 wd:Q5305591 wd:Q5547006 wd:Q5916456 wd:Q5999493 wd:Q6465106 wd:Q6781515 wd:Q6879755 wd:Q7163258 wd:Q7199343 wd:Q8027124 wd:Q16154459 wd:Q16954373 wd:Q16969737 wd:Q16971251 wd:Q18749589 wd:Q19867545 wd:Q20710750 wd:Q22097431 wd:Q22095802 wd:Q22095699 wd:Q22094777 wd:Q22073508 wd:Q23013781 wd:Q23302579 wd:Q24312890 wd:Q24765379 wd:Q28444649 wd:Q28444632 wd:Q28543867 } 
  optional {?item wdt:P1449 ?nickname .}
  optional {?item wdt:P286 ?head_coach .}
  optional {?item wdt:P118 ?league .}
  optional {?item wdt:P115 ?home_venue .}    
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!
It's fairly straightforward to adapt. There's a select statement, which I'll come back to - defines the columns in the report. There's a Values ?item {} statement, stuffed with the Qids of items you're interested in. This is where to add the missing 11.
Statements/claims we want to check for are found in lines like optional {?item wdt:P286 ?head_coach .} - this example finds the Qid in the head coach (P286) statement, and sticks it into a variable called ?head_coach. But notice the select at the top SELECT ?item ?itemLabel ?nickname ?head_coachLabel ?leagueLabel ?home_venueLabel. To get the actual name of the coach, I've added Label to the end of the variable name, so, ?head_coachLabel. By contrast, nickname is a string rather than a Qid, and so we can just find optional {?item wdt:P1449 ?nickname .} and not worry about the Label bit. (Although in fact you'll see the report actually asks for optional {?item wdt:P1449 ?nickname . FILTER(LANG(?nickname) = "en").} - the filter bit is making sure we get the EN.language nickname, rather than a nickname in another language. Probably over the top for this report, bit still).
Most of the statements have an optional {} wrapper, since we don't know if the item has the value. Without the optional, we would restrict ourselves to returning items that do have the value.
What else can I tell you? SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } is a thing which gets Labels for values.
More usefully. If you now want to find what's going on with another value, such as for official website (P856), then you would add a row in the report saying optional {?item wdt:P856 ?website .} and the ?website variable in the select statement, so SELECT ?item ?itemLabel ?nickname ?head_coachLabel ?leagueLabel ?home_venueLabel ?website ... it's not a QID and so it does not need Label appending to it. (It's not clickable in the results; we'd need to add another line to make it so - bind(IRI(?website) as ?clickable) and use ?clickable in the select rather than website ... probably best done as a job lot, so:
SELECT ?item ?itemLabel ?nickname ?head_coachLabel ?leagueLabel ?home_venueLabel ?clickable
WHERE 
{
  VALUES ?item  {wd:Q4705232 wd:Q5461417 wd:Q5547760 wd:Q6365108 wd:Q6815890 wd:Q6868282 wd:Q7010204 wd:Q7056976 wd:Q7566589 wd:Q16201949 wd:Q16164975 wd:Q16202097 wd:Q16154463 wd:Q16147656 wd:Q16822493 wd:Q16823123 wd:Q17002222 wd:Q16972809 wd:Q17007074 wd:Q16969626 wd:Q19576850 wd:Q21531595 wd:Q21550167 wd:Q22096806 wd:Q25000663 wd:Q28444659 wd:Q28444662 wd:Q28868362 wd:Q29468792 wd:Q29468768 wd:Q29470713 wd:Q29469017 wd:Q29641529 wd:Q29791438 wd:Q29791447 wd:Q30325928 wd:Q30325823 wd:Q30326010 wd:Q30325964 wd:Q30325923 wd:Q30325998 wd:Q30325830 wd:Q30325941 wd:Q30325887 wd:Q30325898 wd:Q30325871 wd:Q30326014 wd:Q30325815 wd:Q30325986 wd:Q30325824 wd:Q30325889 wd:Q30325915 wd:Q30325875 wd:Q30325893 wd:Q30325831 wd:Q30325804 wd:Q30325973 wd:Q30325983 wd:Q30325988 wd:Q30325921 wd:Q30593141 wd:Q5547572 wd:Q6694561 wd:Q6837807 wd:Q6861792 wd:Q7598727 wd:Q7700100 wd:Q7707441 wd:Q7707839 wd:Q16154307 wd:Q16154256 wd:Q16154314 wd:Q16971255 wd:Q17507741 wd:Q19578136 wd:Q19864208 wd:Q20657621 wd:Q21546434 wd:Q28206758 wd:Q28444629 wd:Q29092785 wd:Q29094771 wd:Q29092793 wd:Q29468946 wd:Q29468780 wd:Q29641538 wd:Q30325908 wd:Q30325897 wd:Q30325822 wd:Q30325965 wd:Q30325917 wd:Q30325975 wd:Q30325882 wd:Q30325877 wd:Q30325968 wd:Q30325926 wd:Q30325914 wd:Q30325910 wd:Q30325873 wd:Q30325939 wd:Q19576965 wd:Q19577169 wd:Q19577277 wd:Q19578059 wd:Q22095719 wd:Q22096531 wd:Q23303100 wd:Q25005059 wd:Q29093013 wd:Q29092990 wd:Q29096404 wd:Q29468958 wd:Q29469127 wd:Q29470718 wd:Q29470716 wd:Q29791434 wd:Q30325932 wd:Q30325946 wd:Q30325978 wd:Q30325918 wd:Q30325909 wd:Q30325884 wd:Q30325907 wd:Q30325985 wd:Q30325806 wd:Q30326001 wd:Q30325913 wd:Q30326003 wd:Q30325996 wd:Q30325874 wd:Q30325929 wd:Q30325829 wd:Q30325872 wd:Q30325805 wd:Q30325809 wd:Q30632927 wd:Q30593394 wd:Q16154177 wd:Q52623210 wd:Q29092977 wd:Q29075948 wd:Q29468773 wd:Q29468769 wd:Q29469021 wd:Q29468791 wd:Q29468782 wd:Q29572582 wd:Q29791436 wd:Q29791431 wd:Q29791432 wd:Q30325896 wd:Q30325888 wd:Q30325999 wd:Q30325991 wd:Q30325883 wd:Q30325927 wd:Q30325930 wd:Q30325995 wd:Q30325919 wd:Q30325922 wd:Q30325879 wd:Q30325885 wd:Q30325989 wd:Q30325992 wd:Q30325905 wd:Q30325960 wd:Q30325808 wd:Q30325811 wd:Q30588386 wd:Q30591624 wd:Q30588521 wd:Q5161554 wd:Q5684359 wd:Q6064630 wd:Q6480880 wd:Q7058420 wd:Q7587318 wd:Q7895967 wd:Q16147605 wd:Q16201295 wd:Q16154116 wd:Q16154474 wd:Q16823182 wd:Q16961952 wd:Q16958990 wd:Q16982691 wd:Q16983723 wd:Q19577165 wd:Q19577174 wd:Q19577972 wd:Q20708371 wd:Q22096783 wd:Q28444648 wd:Q29095277 wd:Q29468771 wd:Q29468775 wd:Q29468778 wd:Q29470819 wd:Q29468781 wd:Q29470721 wd:Q29791430 wd:Q29791433 wd:Q29791435 wd:Q29791444 wd:Q30326011 wd:Q30325894 wd:Q30325816 wd:Q30325916 wd:Q30325827 wd:Q30325958 wd:Q30326008 wd:Q30325895 wd:Q30325943 wd:Q30325997 wd:Q30325812 wd:Q30325937 wd:Q30325947 wd:Q30325961 wd:Q30325906 wd:Q30325890 wd:Q30325972 wd:Q30325980 wd:Q30325931 wd:Q30325940 wd:Q30325900 wd:Q4951157 wd:Q5547840 wd:Q6984699 wd:Q7082333 wd:Q7569490 wd:Q7864012 wd:Q16151501 wd:Q16153415 wd:Q16201351 wd:Q16154193 wd:Q16205772 wd:Q16247862 wd:Q16969601 wd:Q16980215 wd:Q30325899 wd:Q30325902 wd:Q30325814 wd:Q30593139 wd:Q30593140 wd:Q30588227 wd:Q30592518 wd:Q4836897 wd:Q4947831 wd:Q5002584 wd:Q5020513 wd:Q5148748 wd:Q5330300 wd:Q5367124 wd:Q6365004 wd:Q6392430 wd:Q6460014 wd:Q7054636 wd:Q7080913 wd:Q7260974 wd:Q7566995 wd:Q7708113 wd:Q7863949 wd:Q7914438 wd:Q16154049 wd:Q16164964 wd:Q16970007 wd:Q16970019 wd:Q19577159 wd:Q19577406 wd:Q19577742 wd:Q19863871 wd:Q21565045 wd:Q22096156 wd:Q28449390 wd:Q28444660 wd:Q28805615 wd:Q28805614 wd:Q29092781 wd:Q29093805 wd:Q29092789 wd:Q29468783 wd:Q29470715 wd:Q29572324 wd:Q29641524 wd:Q29791446 wd:Q29791441 wd:Q30325977 wd:Q30325901 wd:Q30326007 wd:Q30325911 wd:Q30325810 wd:Q30325825 wd:Q30325821 wd:Q30325944 wd:Q30325876 wd:Q30325903 wd:Q30325924 wd:Q30325807 wd:Q30325880 wd:Q30325826 wd:Q30325828 wd:Q30325820 wd:Q30325813 wd:Q30325987 wd:Q30325962 wd:Q30325942 wd:Q30325886 wd:Q30591635 wd:Q30632926 wd:Q5131581 wd:Q5305591 wd:Q5547006 wd:Q5916456 wd:Q5999493 wd:Q6465106 wd:Q6781515 wd:Q6879755 wd:Q7163258 wd:Q7199343 wd:Q8027124 wd:Q16154459 wd:Q16954373 wd:Q16969737 wd:Q16971251 wd:Q18749589 wd:Q19867545 wd:Q20710750 wd:Q22097431 wd:Q22095802 wd:Q22095699 wd:Q22094777 wd:Q22073508 wd:Q23013781 wd:Q23302579 wd:Q24312890 wd:Q24765379 wd:Q28444649 wd:Q28444632 wd:Q28543867 } 
  optional {?item wdt:P1449 ?nickname . FILTER(LANG(?nickname) = "en")}
  optional {?item wdt:P286 ?head_coach .}
  optional {?item wdt:P118 ?league .}
  optional {?item wdt:P115 ?home_venue .} 
  optional {?item wdt:P856 ?website . bind(IRI(?website) as ?clickable)}
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!
There are other tricks we can play. Want to see just those without a head coach? Add a line saying minus {?item wdt:P286 [] .} ... and much the same for any property you want to minus. Want to insist that a value be present? Add a line in the form ?item wdt:P286 ?head_coach . (or remove the optional {} from a line to get to the same place). Fullstops at the end of lines of code are important. Follow the pattern in the report and you'll be fine.
Happy to convene a SPARQL tutorial here - come back with questions. But 1) add the missing values to the Values list, or, 2) let me know whether there are values we can rely on to distinguish your teams, so we can dispense with the Values statements and 3) I found that the SPARQL reports service sometimes says "server error" when running my report ... ask it to run it again and it comes back with results. Don't know what's happeneing there. Indigestion, probably. --Tagishsimon (talk) 17:54, 25 May 2018 (UTC)
Looks great so far, let me try to absorb it.--Sphilbrick (talk) 18:41, 25 May 2018 (UTC)
Sucess! I manged to fill in all the blank descriptions, and correct some I had incorrectly capitalized. Now to try new things. Thanks!--Sphilbrick (talk) 00:26, 26 May 2018 (UTC)
@Sphilbrick: Good work. Excellent to see the thoroughness of your approach to this set of items. Kudos. By way of a thank-you, here's a basic query which returns 348 teams ... I'm guessing they're your set. If there are any missing, then the missing item will be missing one of the three values. Anyway: might allow you to dispense with the unsightly Values {} list ... you can build on this query per the queries above. If there are missing items, wrapping optional {} around all three triples, and then adding a minus {?item wdt:P31 wd:Q13393265 .} will reveal the one missing its Q13393265 (if there is one) ... and the same pattern will reveal the other two Qids ... what I'm trying to say is, do one minus statement at a time :) --Tagishsimon (talk) 00:47, 26 May 2018 (UTC)
SELECT distinct ?item ?itemLabel
WHERE 
{ ?item wdt:P31 wd:Q54190181 .       #instance of: NCAA Division I women's basketball team 
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } # get labels
}
Try it! --Tagishsimon (talk) 00:47, 26 May 2018 (UTC)


SELECT distinct ?item ?itemLabel ?leagueLabel
WHERE 
{ ?item wdt:P31 wd:Q54190181 .       #instance of: NCAA Division I women's basketball team 
  optional {?item wdt:P118 ?league .} #get the league, presuming the item has one
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } # get labels
} order by ?leagueLabel ?itemLabel
Try it! - College of Charleston Cougars women's basketball not in a league? --Tagishsimon (talk) 00:52, 26 May 2018 (UTC)
Heh, I was recently wondering if there was a cleaner way to identify all the subject entries and I knew that I had added competition class: women's basketball to, well, I thought all of them. However, given that I'm doing error checking it occurred to me that I might've missed some and I didn't want to perpetuate my errors. I do have a clean list of all 351 Q values. I'll search those for competition class and if I get lucky I'll find the three that are missing that entry, add them and then I can use the query you designed. Time to take a break for the evening but I'll try in the morning.--Sphilbrick (talk) 00:55, 26 May 2018 (UTC)
"College of Charleston Cougars women's basketball not in a league?" Yes they are. Which is exactly why I am doing the error checking. I added a lot of things manually and one can get into a zone which is both good and bad. I obviously miss that one. It's slightly odd because I was building quick statements to add leagues, I save the entries in a spreadsheet I'll have to check to see what I missed. They are the first item in the league in my list sorted by leak so I probably picked up one too few rows. Will fix in the morning.
@Sphilbrick: Not sure how many team's we're trying to get to. I found 3 that were missing the competition class property, and added it - Cal State Northridge Matadors (Q5018231), Quinnipiac Bobcats (Q7272308), Cal State Fullerton Titans (Q3529523) - and added the league to Charleston. However we seem to be at 352 results right now. Is that good or bad? - sorted below - we have 351.
I used the query below to find the three (and having fixed them, they're no longer in the report). But. There seem to be four other teams which you might or might not want to take a look at.
SELECT distinct ?item ?itemLabel
WHERE 
{ ?item wdt:P31 wd:Q13393265 .                  #instance of: basketball team
  ?item wdt:P31 wd:Q2367225 .                   #instance of: university and college sports club
  optional {?item wdt:P2094 wd:Q2887217 .}      #competition class: women's basketball 
  ?item wdt:P641 wd:Q5372 .                     #sport: basketball
  minus {?item wdt:P2094 [] .}                   #SHOW ONLY WHERE competition class: women's basketball IS MISSING 
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } # get labels
}
Try it! --Tagishsimon (talk) 01:15, 26 May 2018 (UTC)
@Sphilbrick: I've tracked down the 352 / 351 difference to Fordham Rams women's basketball (Q29468783) which appears twice in the report that has the league column, since there are two leagues associated with this team. It appears only once in the report without the league column. So, we have a handle, of a sort, on the 351. I kinda feel we're missing an item such as "NCAA Division I women's basketball team" ... if we had such an item (which would have the subclass of (P279) values of basketball team (Q13393265) and university and college sports club (Q2367225)), then each of the 351 teams could have a P31 of whatever is the Qid of "NCAA Division I women's basketball team" (and would not need the P31s they currently have); and we would then have an absolute handle on the teams. Right now it is possible that a team which is not part of the NCAA Division I women's could be given the three values we're using to distinguish the 351. Hope that makes sense? --Tagishsimon (talk) 01:34, 26 May 2018 (UTC)

Here's an uber report which selects for all of the properties I've found (and note the three that were 'found' this evening use represents (P1268) rather than part of (P361) to set out their link with the university). Right now I've commented (#) out some of the optionals, since if you fetch all values, the results switch from a grid to a list ... albeit you can export the list as CSV and it'll be back in grid format in your spreadsheet. Where an item has more than one value for a property, you will get one row per item/value, as we saw with Fordham Rams women's basketball (Q29468783). So, you can turn things on or off with this report by adding or removing the #.

Late news: I've implemented NCAA Division I women's basketball team (Q54190181). So now we can just search for ?item wdt:P31 wd:Q54190181 .

SELECT distinct ?item ?P361Label ?P571 ?P1449 ?P17Label ?P118Label ?P115Label ?P2094Label ?P641Label ?P856 ?P910Label ?P1268Label
WHERE 
{ ?item wdt:P31 wd:Q54190181 .       #instance of: NCAA Division I women's basketball team 
 optional {?item wdt:P361 ?P361 .}
 optional {?item wdt:P571 ?P571 .}
 optional {?item wdt:P1449 ?P1449 .}
 optional {?item wdt:P17 ?P17 .}
 optional {?item wdt:P118 ?P118 .}
 optional {?item wdt:P115 ?P115 .}
 optional {?item wdt:P2094 ?P2094 .}
 optional {?item wdt:P641 ?P641 .}
# optional {?item wdt:P856 ?P856 .}
# optional {?item wdt:P910 ?P910 .}
# optional {?item wdt:P1268 ?P1268 .}
 SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } # get labels
}

Try it! --Tagishsimon (talk) 01:56, 26 May 2018 (UTC)

We are on the same page! As I went to bed last evening, I wondered if this should be such a property. Thanks for creating it.
Regarding colleges Charleston — you may recall I ran a couple things in batch mode and a couple didn't work — my best guess is that this was one of them because I found the quick statement in my spreadsheet. I read it again and it seemed to work okay.--Sphilbrick (talk) 10:55, 26 May 2018 (UTC)
@Sphilbrick: Good that we're on the same page. I'll leave you to double-check the P279 properties assigned to NCAA Division I women's basketball team (Q54190181) ... one of them is college sports team (Q18558301) which only featured on two of the 351 team items. I've added some more statements to NCAA Division I women's basketball team (Q54190181) and am sitting here thinking that it feels perfectly right to have removed basketball team and university and college sports club from the 351 items, because they are represented in Q54190181 ... but it does not feel right to remove from the 351 the other statements I've added to Q54190181 - sport=basketball, competition class=women's basketball, country=USA. Anyway: it's all yours now. I have to go & paint something white. --Tagishsimon (talk) 11:11, 26 May 2018 (UTC)

This thread is too long section break[edit]

────────────────────────────────────────────────────────────────────────────────────────────────────The meta query is very helpful. I've already used it to identify and correct some errors; some still left to handle.

There is one issue that I want to run by you before making changes. A few queue values had their "instance of" change to the new NCAA Division I women's basketball team (Q54190181), But I think these should not have been changed.

I think it's as simple as reverting but before I do so I wanted to bring them to your attention to make sure that simple reversion was sufficient and so that you could also see if there's something else wrong with these entries that cause them to be picked up by your algorithm. There may be something else that's wrong with them.

Cal State Fullerton Titans These are sports other than women's basketball. http://www.wikidata.org/entity/Q3529523

Cal State Northridge Matadors Similarly, I suspect this is the entry for men's basketball and football http://www.wikidata.org/entity/Q5018231

There are two Quinnipiac Bobcat entries. My guess is the first of the two is the men's team. The history of show that I haven't had any edits to it. The second one I believe is the correct one that I'm interested in. https://www.wikidata.org/wiki/Q7272308

https://www.wikidata.org/wiki/Q3529523

Now I have to go plant some trees.--Sphilbrick (talk) 12:33, 26 May 2018 (UTC)

@Sphilbrick: Planting trees good. I envy you. Meanwhile:
and, by a miracle I do not understand, we still have 351 results from
SELECT distinct ?item ?itemLabel
WHERE 
{ ?item wdt:P31 wd:Q54190181 .       #instance of: NCAA Division I women's basketball team 
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } # get labels
}
Try it! and I shall once again go and paint things white. (I think there are things wrong with the three reverted items; they don't represent that which is described in their articles; but equally they're filed under 'someone else's problem' ... and I forget how I selected them before my quickstatements frenzy, so we'll let that slide.). Did you see the note on chat - Property NCAA sports team ID (P3692) exists, and possibly these teams have a P3692 value? --Tagishsimon (talk) 13:58, 26 May 2018 (UTC)

References - both in case the entry is needed, and in cases where the entry is present[edit]

I'm so close I can taste it but I'm still not quite there. (As an aside asked my question about URL references at chat rather than to you personally because I thought it might be of general interest to readers. Now that I sort of see how to do that, I want to add some entries but they are quite working correctly.)

Many basketball teams have a site typically called something like quick facts. This page typically a PDF, supports many of the Wikidata entries.

For example, here is the site for USC:

http://usctrojans.com/documents/2017/6/20/quick_facts.pdf

A page like that can be used to support the statement about:

  • NCAA Division I women's basketball team (Sometimes, not always)
  • Nickname
  • home venue
  • Inception (Sometimes, not always)
  • league
  • Competition class
  • sport
  • Twitter handle (Sometimes, not always)

My goal is to set up a spreadsheet, Where I can enter that you value for the team, add the nickname, the twitter handle, and generate quick statements to add all of the items.

This isn't working out as well as I had hoped.

For example, I tried the suggestion for Stanford and it seemed to work when I tried to create the exact same thing for USC it didn't seem to work.

I'd swear (but I must be wrong) I'd copy and paste an entry into quick statements and have it fail try again and have it work.

Let me mockup what I think would be the way to do this for USC and maybe you can help me figure out what I'm doing wrong. (I said USC but I'm using the Q value for the sandbox until I figure this out)

Q4115189 P31 Q54190181 S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"

Q4115189 P1449 "Trojans" S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"

Q4115189 P115 S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"


The first line works.

The second one fails.

The third one fails perhaps because I didn't provide an entry for home venue but the home venue is already filled and I simply want to add the reference.--Sphilbrick (talk) 14:43, 27 May 2018 (UTC)

@Sphilbrick: third one first: you need to add the value and the reference as a job lot. Cannot tack a reference onto a pre-existing value. (Think you probably have to, or are best to, delete the value, and then reinsert it with the ref. I'll look at 2 now. --Tagishsimon (talk) 14:58, 27 May 2018 (UTC)
@Sphilbrick: Second one is, you need to specify the language of the nickname, in the form en:"Trojans"
Q4115189 P1449 en:"Trojans" S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"
Let me know if that clears it all up. White paint is calling... --Tagishsimon (talk) 15:09, 27 May 2018 (UTC)
That's helpful. I sort of wondered about language, but didn't know how to cure it. BYW, I helped plant almost 100 trees yesterday. Good luck with the paint. --Sphilbrick (talk) 15:16, 27 May 2018 (UTC)
@Sphilbrick: couple of weeks before I get to commune with trees again. Well done. Meanwhile I wondered if the language thing was what was frustrating our attempt to use quickstatements to load categories, investigated, found it was not, but did find the answer. We were trying:
Q30325980 P910 "Category:UC Irvine Anteaters women's basketball"
when we should have been trying
Q30325980 P910 Q25025660
because P910 stores the Qid of the Category, not the string. Okay. Paint. Gone for a while. --Tagishsimon (talk) 15:36, 27 May 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I'm almost there. I handle home venue by creating a lookup table. (Same for league)

I think the last thing remaining is inception. It seems like 1969 is acceptable input when doing manual entry, but it doesn't like it as a quickstatement


e.g.

Q4115189 P571 1976 S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"

(Thanks for the answer re cat)--Sphilbrick (talk) 16:15, 27 May 2018 (UTC)

Good news! I figured it out myself:
Q4115189 P571 +1976-00-00T00:00:00Z/9 S854 "http://usctrojans.com/documents/2017/6/20/quick_facts.pdf"

"Maybe there's hope for me yet. :) --Sphilbrick (talk) 16:24, 27 May 2018 (UTC)

@Sphilbrick: That's the one. Nothing like having a task you want done, to force you to learn you some SPARQL & Quickstatements & excel tricks. It's ace when these textual incantations do what we want them to. And, excellent to see a corner of wikidata made very neat & complete. --Tagishsimon (talk) 18:00, 27 May 2018 (UTC)
@Sphilbrick: There's something going on with your commons categories. Connecticut Huskies women's basketball (Q5161554) points to
https://commons.wikimedia.org/wiki/Category:UConn_Huskies_women%27s_basketball
but the extant category is at
https://commons.wikimedia.org/wiki/Category:Connecticut_Huskies_women%27s_basketball
https://commons.wikimedia.org/wiki/Category:NCAA_women%27s_basketball_teams is, presumably, your friend. --Tagishsimon (talk) 18:13, 27 May 2018 (UTC)
I'm intrigued that you noticed that. I'm not sure how closely you are following my edits, but while I've made a lot of edits to women's basketball teams I don't believe I've made any edits involving categories. Well, a couple exceptions. One a few seconds ago, after seeing your note, and I got it wrong initially. I also tried a few days or maybe weeks ago when I first started working on this but I wasn't happy and I'm still unhappy at the irrational difference between the way entries are made for Wikipedia categories and Commons categories. As a consequence, I resolved not to work on categories. I know I could track down who added the wrong category to Q5161554, but it was someone else. I corrected it after a false start.
I'm making decent progress (thanks to your help) but have no intention of working on categories (at least not in the near term).--Sphilbrick (talk) 00:40, 29 May 2018 (UTC)
It's a very small corner, but I just now finished my pass through the 351 articles. Some wikidata entries not populated, but because the source material is deficient. Thanks for your help.--Sphilbrick (talk) 13:19, 6 June 2018 (UTC)

I finally went to the source[edit]

Topic:Ue2kyvfyb366sgqdNotARabbit (talk) 00:27, 30 May 2018 (UTC)

@NotARabbit: Good; I hope Magnus has the time to answer. Some sort of odd timeout, but hard to explain given the alactrity of the WQS report. I was seeing the same thing with the WiR redlist Soviet Union report - I updated Belarus, which worked, but if you look at the edit history of Soviet Union...sad. --Tagishsimon (talk) 00:42, 30 May 2018 (UTC)
@NotARabbit: So now we know. Plus it's working. Plus, presumably, Magnus has improved his code. Excellent job, NotARabbit & Magnus. --Tagishsimon (talk) 00:12, 1 June 2018 (UTC)

heritage designation (Q17504995)[edit]

Hi, whi did you change all the heritage designation (Q17504995) to listed in a community heritage register (Q18342392)? There is two level of protection in the municipalities of British Columbia. listed in a community heritage register (Q18342392) simply acknoledge that the building have a heritage value. heritage designation (Q17504995) mean that the property is protected by the municipality. It's explaned here. Can you change it back? --Fralambert (talk) 12:42, 27 June 2018 (UTC)

@Fralambert, Jmabel: See Wikidata:Project chat#Relation between these two topics. Get back to me when there's a consensus on the way forwards. thx --Tagishsimon (talk) 12:51, 27 June 2018 (UTC)

Labels for films[edit]

Hi Tagishsimon, I noticed that you added English titles to films. What are you using for these? Please bear in mind that the original title should use title statement (P1476) and the English label should be the English title of a movie.
--- Jura 05:36, 1 July 2018 (UTC)

@Jura1: I'm taking labels from non-En languages, that happen to be in English, where the En label is missing. I'm not doing any translations, but assuming that an English title found as a non-En label will do for the En label.
SELECT ?item ?Les 
WHERE 
{
  ?item wdt:P31/wdt:P279* wd:Q11424.
  filter not exists {?item rdfs:label ?Len. filter(lang(?Len)="en")}
  ?item rdfs:label ?Les. filter(lang(?Les)="es")
} order by ?Les
Try it! ... and then go thru the CSV by hand removing non-English labels. --Tagishsimon (talk) 09:28, 1 July 2018 (UTC)
Sounds good, even though the actual English title might be different. Spanish film labels are a bit of a mess.
I noticed you also did some Danish films (some consisting of a mere given name, which may not really be English).
I couldn't convince a Danish speaking film editor to set the original language of those films.
--- Jura 09:57, 1 July 2018 (UTC)
I took a view on whether given names were sufficiently familiar to the English ear. I grant, absolutely, the possibility that some of the films might have been released in the UK with a different title, but reckon that cost is outweighed by the value of the majority. I've been through #it #fr #es #de #da & #sv so far, which has yielded ~20k labels. --Tagishsimon (talk) 10:06, 1 July 2018 (UTC)
I should have thought of that earlier ;) Good work.
--- Jura 12:15, 1 July 2018 (UTC)

Data for instances of humans[edit]

Thanks for your help with data related to Baltisches Biographisches Lexikon digital and also with SPARQL requests related to that and to ISNI.

Maybe you are interested in Wikidata:Property proposal/Deutsche Biographie person ID, it could be a connector to a further source of data, to the de:Deutsche Biographie (DB). In the DB all (?) items in ADB and NDB that have their own article are supposed to get a GND and can be linked by that parameter. But it has to be the GND provided by the Deutsche Biographie, not the one from the authority file. Ideally both are the same, but there could be differences. The DB advises to use their GND ID not the SFZ. The de:Vorlage:Deutsche Biographie has just been switched from SFZ/GND mixed support to GND-only. 2.247.58.206 18:35, 8 July 2018 (UTC)

Hi Tagishsimon, this IP is a known troll, blocked multiple times on German Wikipedia (de:Vorlage Diskussion:Deutsche Biographie). Cheers --Kolja21 (talk) 18:52, 8 July 2018 (UTC)

Wrong labels[edit]

Hi, Tagishsimon. I deduce you're the one who added the English labels to some people in Ancient Rome. I'm afraid those labels are wrong. In Spanish, the names of the Romans are translated (in fact, there are a number of translation rules), but in English (as far as I know) the Latin original is maintained. I've already corrected this mistake I've seen. I'm just telling you so that you'll keep it in mind the next time you make a similar edition. Thanks.

Un saludo. --Romulanus (talk) 09:37, 9 July 2018 (UTC)

@Romulanus: Thank you; I was not aware of that naming rule. I am right now trying to improve EN label coverage by copying values from other languages into EN (and trying to improve EN descriptions by constructing these based on item properties). It's always a worry that I'll introduce systematic errors through lack of knowledge / competence. I'll take on board your advice on Romans, which will, I hope, cut off one avenue of error. This report shows that we have no people items where the EN and ES labels are the same ... predicated on the item having a country of citizenship (P27) of ancient Rome (Q1747689). So, hopefully, it shows that I have not made the error elsewhere, or that you've already corrected those I did make. Thank you for correcting those you found, and for letting me know. --Tagishsimon (talk) 16:23, 9 July 2018 (UTC)
Ok. In that case (for the Romans and as far as I know), you can use French, German (in fact, any Germanic language) when there is no label in English. Obviously, you can also use Latin. But never Spanish, Catalan, Galician, Italian.... unless you know the rules of translation of these languages.
Un saludo. --Romulanus (talk) 23:57, 9 July 2018 (UTC)

citizenship: qualify a start date?[edit]

Just a question re addition for UKI peoples. Was it considered whether there should be a start/finish date to qualify the item? Something to assist the distinguishing of consecutive citizenries changed, rather than co-joined.  — billinghurst sDrewth 04:46, 13 July 2018 (UTC)

@billinghurst: I'm not sure I understand the distinction you draw between consecutive and co-joined ... but I think you are right that we could and should use end and start dates for those people living during the transition between the Kingdom of England and the Kingdom of GB in 1707; or between the Kingdom of GB and Kingdom of GB+NI in 1927. I'll get around to doing that; but please let me know what I'm missing on consecutive vs co-joined. thanks --Tagishsimon (talk) 07:37, 13 July 2018 (UTC)
co-joined = dual nationality. I couldn't think of that term whilst typing earlier. One is nationality that changes due to processes not the person, the other is the person having choices/, decisions, etc. I can think that Brits have the former with GB -> UKI -> UK; there would also be Australians going from colonists -> Federation as British subjects -> Oz citizens (later legn.) Not that the latter has been well-decided in WD about that citizenry should b represented.  — billinghurst sDrewth 08:54, 13 July 2018 (UTC)
@billinghurst: Not that the latter has been well-decided in Australia, either - you're probably familiar with w:en:2017–18 Australian parliamentary eligibility crisis :). Thanks, distinction is clear now. And yes, not surprising that question of respresentation of the citizenship status of individuals from the former parts of the British Empire has not been settled (again: IRL imitates WD in w:en:Windrush scandal). I'll keep playing with UKians. Might not get around to Oz et al. --Tagishsimon (talk) 09:09, 13 July 2018 (UTC)
Illustrative only, conversation was just about qualifying what we know.  — billinghurst sDrewth 09:27, 13 July 2018 (UTC)

Weird dupes[edit]

I noticed your ping. You might want to keep an eye on the recent changes for other accounts or ip's. Multichill (talk) 15:35, 11 August 2018 (UTC)

Thanks; will do. I'm sure we've not seen the last. --Tagishsimon (talk) 15:48, 11 August 2018 (UTC)

Preffered rank[edit]

User:Xaris333/Test

Hello. Can you change the query to show only the preffered rank for population? Some items have a lot of values with population (P1082) but not a recent census. So for that items, will show nothing.

Cases:

  • If one value is in preffered rank -> show that value only
  • If all values are in normal rank -> show nothing because no value is in preffered rank (for example, must not show population for Arsos, Larnaca (Q4796610))
  • If one values is in normal rank and all the other is deprecated rank -> show nothing because no value is in preffered rank

Xaris333 (talk) 14:36, 14 August 2018 (UTC)

@Xaris333: We're talking User:Xaris333/Test, yes? I've not done the preferred rank thing ... I had a look at Arsos, Larnaca (Q4796610) ... all of the ranks look the same (and I'm a bit too tired right now to do any reading on how preferred rank actually works). So I took a different approach, which is to look for the most recent population statistic for each item. (And I threw in a population date column, which you may or may not want to keep). Let me know if that works for you. Is live on User:Xaris333/Test as of a moment or two ago.
I can & will come back to doing it by preferred rank maybe in the next 24 hours. Maybe in 5 minutes time. We'll see. --Tagishsimon (talk) 19:59, 14 August 2018 (UTC)
@Xaris333: Oh. THat was easier than I thought. This is the Preferred Rank version ... it is as I write this note the current version. This is the 'most recent population' version which I discussed above.
I am understanding your three cases, above to boil down to "show preferred rank only", or perhaps "show preferred rank only, but only if there is a single preferred rank". Right now I am doing the first of those - showing you the "show preferred rank only" without checking if more than 1 have a preferred rank. So, next, I'll look at that issue: can an item statement have 2 preferred ranks? If so, then yes, we can not show any values, or we can chose one of the preferred values, and/or we can produce a flag so you know which have 2 preferred values. --Tagishsimon (talk) 20:11, 14 August 2018 (UTC)
I learn that there can be two preferred rank values ... I'll come back later once I've worked out how to deal with that. --Tagishsimon (talk) 20:17, 14 August 2018 (UTC)
But have not found an effective way of not showing population when this happens, whilst still showing the item. More later. -Tagishsimon (talk) 20:50, 14 August 2018 (UTC)

@Xaris333: So maybe this is the version you want. To recap, as far as I remember:

Have a look at the results, especially for the either of the prefferred rank versions ... I'm not 100% sure, but I really am too tired this evening to do any more checking. --Tagishsimon (talk) 21:00, 14 August 2018 (UTC)

Many thanks for your time!! I didn't realize it was so difficult. The case "This is the Preferred Rank version which does not care how many preferred ranks" is what I wanted. Xaris333 (talk) 01:44, 15 August 2018 (UTC)

But is not working on wikipedia :( w:el:Επαρχία Λάρνακας#Πληθυσμός, έκταση και υψόμετρο ανά δήμο/κοινότητα. Άρσος must have no value. Xaris333 (talk) 01:49, 15 August 2018 (UTC)
@Xaris333: You used the second query, not the third. Now changed. Let me know if you spot problems - you know the data better than me, and I don't yet guarantee my work. Eventually we'll get there :). Oh, and note in particuar that the column line in the wikidata list needs to draw its population data from ?population and not from P1082. --Tagishsimon (talk) 01:57, 15 August 2018 (UTC)
Looks fine now! Many thanks!! Xaris333 (talk) 02:01, 15 August 2018 (UTC)

Duplicate movies[edit]

Hey there! You've posted in pt.wiki's Project Talk, but was reverted, regarding the duplicate movies "Unknown Caller (filme)" (Q25444931) and "Unknown Caller (2014)" (Q25445221), which were the same film. I've redirected the (2014) one to the (filme) one, so now you can merge the Wikidata items. Best regards! Guilhermebm (talk) 16:21, 27 August 2018 (UTC)

Many thanks, Guilhermebm, that's much appreciated. Wikidata merge now done. --Tagishsimon (talk) 16:41, 27 August 2018 (UTC)

Film directors[edit]

Any particular reason you're removing uses of director (P57) from lots of movie items? Some of the items I checked seemed like they had nothing wrong with the presence of that property. Mahir256 (talk) 21:05, 1 September 2018 (UTC)

@Mahir256: Other than the director linked to in the film item having predeceased the film by 25 - 1000 years. --Tagishsimon (talk) 21:08, 1 September 2018 (UTC)
Oh, I must have missed that. Carry on then, but perhaps adding back P57 with the real director is in order after your removals? Mahir256 (talk) 21:17, 1 September 2018 (UTC)
@Mahir256: Thanks. Yup, I'll be looking at that next. Right now, some I'm replacing by hand (based on comparison of the director's P106 values - lots of sportspeople are alleged by us to have a second line in film direction, with no supporting en.wikipedia corroboration); some I'm deleting (generally after date-wise comparisons). And whilst trying to avoid errors, inevitably I'll make some; there are instances of films being released decades after the death of a director; instances of cricketers turned film-maker. I suspect there are not yet items for many of those being deleted, but that's an issue for another week. --Tagishsimon (talk) 21:43, 1 September 2018 (UTC)

P921 tagging[edit]

Hi, I'm glad that you are interested in contributing annotations with main subject (P921) but think you should be a bit more circumspect in terms of how you do it. For instance, your batch 4333 on Malaria is being run over a set of articles that has already been tagged (example), while your batch 4334 on Tuberculosis is not distinguishing between tuberculosis (Q12204) and Mycobacterium tuberculosis (Q130971) and again ignoring existing annotations (example). I suggest you stop and revert both batches and critically review similar ones that you may have set up. Feel free to check out the kinds of queries I am using to generate my P921 batches. --Daniel Mietchen (talk) 02:43, 15 September 2018 (UTC)