Help talk:QuickStatements/Archive 2

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

How to refer to the last created element?

I’m trying to create an element for the last name of a person. My statements look like this:

CREATE
LAST	P31	Q101352
LAST	P282	Q8229
LAST	Den	"family name"
LAST	P1705	en:"The Last Name"
Q68574956	P734	LAST

However the last line doesn’t work: I want to create the lastname then add the newly-created item as P734 on an existing item, but LAST doesn’t seem to work outside of CREATE. Any idea? -- Okhjon (talk) 13:02, 29 September 2019 (UTC)

@Okhjon: It works in version 1: https://tools.wmflabs.org/wikidata-todo/quick_statements.php --- Jura 13:06, 29 September 2019 (UTC)

Server down?

GUI does not react, does not show batches. Can someone help? --SCIdude (talk) 09:44, 30 September 2019 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. SCIdude (talk) 13:04, 30 September 2019 (UTC)

anti-abuse causes errors?

Wondering why I get >30% errors for simple changes (batches #19700, 19702) I noticed that during runs I often get "could not save / anti-abuse" with manual edits. If indeed the QS batch errors are from anti-abuse throttling then, why not simply reduce the speed of batches instead of risking errors? Please fix. --SCIdude (talk) 16:14, 4 October 2019 (UTC) Well and trying to send this was not possible either the first time... what's the matter? --SCIdude (talk) 16:14, 4 October 2019 (UTC)

And today I get 100% errors with setting descriptions. Someone out there? --SCIdude (talk) 07:28, 5 October 2019 (UTC)

No success flag set in API result is the error message.[1] Don't know what it means. Does Magnus? --Matěj Suchánek (talk) 08:45, 5 October 2019 (UTC)

I think one bad command crept in with that batch. Just tested a small batch without it, still no go. --SCIdude (talk) 13:07, 5 October 2019 (UTC)

(somewhat) resolved by noticing that "hypothetical protein" in the label prevents descriptions starting with "protein..." which is facetous because why then "instance of"-->"protein" and not "hypothetical protein"? Moreover, if such obscured rules exist, where can I inspect them? --SCIdude (talk) 13:58, 6 October 2019 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. SCIdude (talk) 07:50, 22 October 2019 (UTC)

500 - Internal Server Error (7 Oct 2019)

Is this down temporarily or should we expect otherwise? Trilotat (talk) 16:09, 7 October 2019 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Trilotat (talk) 21:13, 19 October 2019 (UTC)

Commons

How can I use QuickStatements for Structured Commons and where is it defined how the Syntax for this looks like. -- Hogü-456 (talk) 22:29, 8 November 2019 (UTC)

In "New batch", you will choose "Create new command batch for Commons [batch mode only!]". See phab:T181062#5518968. The syntax should be same otherwise. --Matěj Suchánek (talk) 09:13, 9 November 2019 (UTC)

Thank you for the link to Phabricator. It helped me. Has someone added File Captions already with QuickStatements. I added the following Commands and it did not work. How is the right way of the command for adding File Captions.

Mid,Lde

M6874507,"Leere Seite in der Übersicht über die Reichsgesetzblätter 1879"

-- Hogü-456 (talk) 14:33, 9 November 2019 (UTC)

Internally, captions are equivalent to Wikidata labels. So it should be like M6874507,Lde,"Leere ...". Unlike me, QS cannot guess which language you mean. --Matěj Suchánek (talk) 16:37, 9 November 2019 (UTC)

It does not work. The first line in my example Lde means that I want to add a German Label. I usually add this in the first row and not in every row and until now it worked. It were great if QuickStatements for StructuredCommons is not in a betaphase that the Syntax for it is described at a help page. -- Hogü-456 (talk) 20:26, 9 November 2019 (UTC)

Sorry for confusion, my bad. For CSV (there is no Mid, just qid):

qid,Lde

M6874507,"Leere Seite in der Übersicht über die Reichsgesetzblätter 1879"

For tabs:

M6874507 Lde "Leere Seite in der Übersicht über die Reichsgesetzblätter 1879"

--Matěj Suchánek (talk) 10:08, 10 November 2019 (UTC)

Can you try it please if it works. By me it does not work. I dont know what I am doing wrong. What does the batch mode only in brackets mean, when I choose Commons as the Wiki for adding the captions.-- Hogü-456 (talk) 18:48, 11 November 2019 (UTC)

It does. You just have to use "Run in background". --Matěj Suchánek (talk) 11:32, 16 November 2019 (UTC)

Thank you for the Answer it does work and it really helps me. -- Hogü-456 (talk) 12:23, 16 November 2019 (UTC)

I was going to ask one finds the M-number on Commons, but then I found the Minefield tool that does this nicely. John P. Sadowski (NIOSH) (talk) 09:10, 10 December 2019 (UTC)

Merging two pages, does not work

Hello, I would like to merge Leratiomyces ceres (Q15651408) and Leratiomyces ceres (Q1544892) but I can not seem to because English is used for both? (I get this warning: Failed to merge Items, please resolve any conflicts first. Error: Conflicting descriptions for language en. I have no clue how to fix this.Garnhami (talk) 22:04, 17 November 2019 (UTC)

“You can't create a new batch, because you are blocked on Wikidata”

Tracked in Phabricator
Task T240316

I get this error message even though I have (to my knowledge) never been blocked. What to do? --Emu (talk) 22:37, 9 December 2019 (UTC)

@Magnus Manske: I got the same error message, despite confirming that I have not in fact been blocked. John P. Sadowski (NIOSH) (talk) 01:21, 10 December 2019 (UTC)

Hey @Magnus Manske: I got the same error message. is this an issue? Please help! --Douglasfugazi (talk) 04:37, 10 December 2019 (UTC)

@Magnus Manske: same here. --SCIdude (talk) 07:45, 10 December 2019 (UTC)

+1 --Loominade (talk) 11:18, 10 December 2019 (UTC)

+1 Florentyna (talk) 11:58, 10 December 2019 (UTC)

Bug fix is working in progress: https://phabricator.wikimedia.org/T240316 --Douglasfugazi (talk) 15:48, 10 December 2019 (UTC)

Fixed. QuickStatements is working now :) Thanks a lot! --Douglasfugazi (talk) 18:01, 10 December 2019 (UTC)

Looks indeed fixed at least for me. Thanks ! Bouzinac (talk) 20:32, 10 December 2019 (UTC)

Works now for me too. Thanks for the quick fix! John P. Sadowski (NIOSH) (talk) 22:28, 10 December 2019 (UTC)

removing aliases impossible

Tracked in Phabricator
Task T241530

From the help this should work:

-Q14861555|Aen|"proteinase"

But the parser swallows the string and running it fails. In the v1 interface it is correctly parsed but still fails. The suggestion

Q14861555|Aen|""

does not work either (it works with labels/descriptions). Can someone help? I need to remove >26k non-synonyms that were carelessly added. --SCIdude (talk) 14:09, 11 December 2019 (UTC)

This is now reported as https://phabricator.wikimedia.org/T241530. --SCIdude (talk) 08:36, 29 December 2019 (UTC)

merge seriously borken

Tracked in Phabricator
Task T241890

These items should all be merged into one, so I created the commands:

MERGE|Q62199016|Q62199000
MERGE|Q62198978|Q62199000
MERGE|Q62198991|Q62199000
MERGE|Q62199004|Q62199000
MERGE|Q62198983|Q62199000
MERGE|Q62198995|Q62199000
MERGE|Q62198974|Q62199000
MERGE|Q62199008|Q62199000
MERGE|Q62198987|Q62199000
MERGE|Q62199012|Q62199000

Giving this to the parser results in this mess:

screenshot used to demonstrate the merge bug in QuickStatements

Note that at input all of the commands have Q62199000 as target item. After parsing most of the Q62199000 appear to the left. So, merging is unusable. --SCIdude (talk) 17:17, 4 January 2020 (UTC)

Now also reported at https://phabricator.wikimedia.org/T241890 --SCIdude (talk) 17:27, 4 January 2020 (UTC)

Wikisource

Can we attach wikisource link by QuickStatement? VardanMn (talk) 19:03, 19 January 2020 (UTC)

Q123|Sxxwikisource|"Link". --Matěj Suchánek (talk) 11:07, 2 February 2020 (UTC)

Numeric qualifier

Adding numeric qualifier (exactly similar to an example) through csv doesn't work:

qid,P179,qal1545
Q85719908,Q4483653,1

QS breaks at adding a qualifier saying "invalid snak data". What am I doing wrong? --Infovarius (talk) 21:57, 20 February 2020 (UTC)

@Infovarius: If I am not mistaken, series ordinal (P1545) is a string type, and so the '1' will need to be in double quotes. I ran across this while adding page numbers in references using page(s) (P304). Josh Baumgartner (talk) 23:07, 28 April 2021 (UTC)

Removing qualifiers via QuickStatements?

I mistakenly added a number of exauthors (P697) as authors (405) of taxon-names (P225). I don't wish to delete these by hand (too many) but would like to remove them via quick statements, but cannot see how to do this. MargaretRDonald (talk) 07:49, 10 March 2020 (UTC)

@MargaretRDonald: unfortunately you have to remove the whole statement and add it afterwards without the false qualifiers. --Mfchris84 (talk) 08:39, 10 March 2020 (UTC)

Thanks @Mfchris84:. MargaretRDonald (talk) 11:50, 10 March 2020 (UTC)

@MargaretRDonald: However, this approach causes severe data loss unless you add all references to the new statements. --Matěj Suchánek (talk) 13:05, 11 March 2020 (UTC)

Thankks for that, @Matěj Suchánek: For the ex authors I have (re)edited I was careful to add the authors, year of publication and reference again. MargaretRDonald (talk) 20:49, 11 March 2020 (UTC)

Correct wrong statements

On Help:QuickStatements#Using_QuickStatements_version_2 there is written how run QS. What if you discover a mistake and want to correct it? Is there something like a Quit or Back button so that I can edit the arguments again? --D-Kuru (talk) 20:06, 12 March 2020 (UTC)

BTW: If there is an error, is there any way to see where QS had troubles?

Eg. something like this. In the end I figured out that it value needed a language code, but if QS told me that in line X there is an error and why it fails it would have saved me like 30 minutes of testing. Which was also related to the first problem where I didn't see any option to return to the edit page

--D-Kuru (talk) 20:47, 12 March 2020 (UTC)

If you see a mistake, you can just stop the batch, fix errors and correct the rest and upload it again (so you should keep your text files). Buttons for editing data were in the first rewrite. --Matěj Suchánek (talk) 16:28, 13 March 2020 (UTC)

@Matěj Suchánek: The problem rather is that the full section is rejected in total if it starts with CREATE. It does not fill in all the other sections and tell you that it couldn't process line X, but it just tell you that it failed entirely. This is incredibly boring to work with if you search for an error and have no idea where it is hiding. --D-Kuru (talk) 16:28, 14 March 2020 (UTC)

It looks like error messages are currently broken, see WD:PC#Cannot save wikilinks. --Matěj Suchánek (talk) 10:02, 15 March 2020 (UTC)

Adding Link to Wikimedia Commons

How can I do this with QS? What did not work so far:

• Q87491810|commons|"Category:Soldatenfriedhof Neufeld an der Leitha (Zweiter Weltkrieg, russisch)"
• Q87608772|commonswiki|"Category:Soldatenfriedhof Neufeld an der Leitha (Zweiter Weltkrieg, russisch)"
• Q87608772|wikicommons|"Category:Soldatenfriedhof Neufeld an der Leitha (Zweiter Weltkrieg, russisch)"
• Q87608772|wikimediacommons|"Category:Soldatenfriedhof Neufeld an der Leitha (Zweiter Weltkrieg, russisch)"
• Q87608772|comwiki|"Category:Soldatenfriedhof Neufeld an der Leitha (Zweiter Weltkrieg, russisch)"

Any ideas? --D-Kuru (talk) 23:30, 12 March 2020 (UTC)

Scommonswiki (Help:QuickStatements#Adding labels, aliases, descriptions and sitelinks). --Matěj Suchánek (talk) 08:57, 13 March 2020 (UTC)

@D-Kuru: a comment made a difference for me.

• Q...|Scommonswiki|"Category:value" worked, while
• Q...|Scommonswiki|"Category:value"|#comment didn't

--Herzi Pinki (talk) 01:28, 24 February 2021 (UTC)

@Herzi Pinki: You can add comments using /* COMMENT */ at the end --D-Kuru (talk) 20:53, 24 February 2021 (UTC)

Removing statements is failing

Currently it's not possible for me to remove statements. Example syntax:

-STATEMENT	Q3753632-D2FA0EEF-542B-4B30-9256-94B192B2E96D
-STATEMENT	Q504061-71DDD6C9-90E3-452B-B0F0-1741BA7C247F
-STATEMENT	Q504061-B36380E7-013F-4646-BB78-12BB1ED49CF9

Nonetheless for some reasons it's not working out: https://tools.wmflabs.org/quickstatements/#/batch/27441 Any ideas what I might be doing wrong? --Tomukas (talk) 16:00, 29 March 2020 (UTC)

Found it out myself. The statement id consists of the object id and the statement id. In quickstatements both need to be concatenated with a "$" and not - as I did with a "-". query.wikidata.org unfortunately shows statement ids as such. So, the upper example should have been:

-STATEMENT	Q3753632$D2FA0EEF-542B-4B30-9256-94B192B2E96D
-STATEMENT	Q504061$71DDD6C9-90E3-452B-B0F0-1741BA7C247F
-STATEMENT	Q504061$B36380E7-013F-4646-BB78-12BB1ED49CF9

Thanks anyway! --Tomukas (talk) 18:54, 29 March 2020 (UTC)

Error by importing date statement with Quickstatements

Question on my talk page by @AntoineLogean::

I have a new problem: I would like to add statistic about the number of deaths caused by the covid-19. To do so I use quickstatments. As input I enter the following:

Q88938850 P1120 1 P58 +2020-02-27T00:00:00Z/11 P854 "https://gd.zh.ch/internet/gesundheitsdirektion/de/themen/coronavirus.html#title-content-internet-gesundheitsdirektion-de-themen-coronavirus-jcr-content-contentPar-textimage_7"

I get always an error by the date. Do you know what is wrong?

I leave it here as I currently don't have time to look into it in detail. --- Jura 12:59, 30 March 2020 (UTC)

Different results from same submission via API or website.

There seem to currently be some problems with qualifiers submitted via the API (more info here). When the exact same submission is made via the API it returns errors, whereas submitted as a table via the website it runs fine:

• Submitted via API request
• Submitted via QS website

Any insights or ideas as to the difference and possible fix? T.Shafee(evo&evo) (talk) 00:42, 5 April 2020 (UTC)

Text moved from Help:QuickStatements#Commas_and_double-quotes

The double quotes for string values seem to interfere with CSV syntax. Empirically four double quotes before and one after the string have been found to work. Sometimes three double quotes before and three double quotes after work instead.

For example

qid,P473
Q304652,"""62"""
Q582223,"""34"""

---

• Not sure if the above is of much use. I removed it from the help page. The new wording by GZWDer seems much more helpful. --- Jura 10:53, 10 April 2020 (UTC)

Can't log in

Experiencing issues logging in - was fine this morning, but then kept kicking me out, and now I can't get logged in at all. 2 x other users in different parts of the country also experiencing issues. Any ideas? We're using the tool over a weekend hack event, so kinda frustrating :) Lirazelf (talk) 14:38, 11 April 2020 (UTC)

The fact that other users are experiencing the same is worrying. Sorry about that. You can try disabling the tool's grant in Special:OAuthManageMyGrants, log out, clear cookies (at least those for Wikimedia sites), restart browser, re-login and try QS again. --Matěj Suchánek (talk) 15:54, 11 April 2020 (UTC)

Thanks, will try that. There's a Phabricator task here that I've been pointed to, have also added a comment there. Currently getting this error message: "Error retrieving token: mwoauthdatastore-request-token-not-found" Lirazelf (talk) 08:54, 12 April 2020 (UTC)

I also had problems logging in (around same time and earlier when you reported here) and even got a timeout error once when waiting redirect to oauth login page. Stryn (talk) 16:24, 11 April 2020 (UTC)

Soooo, got this working on the second day after a few bumps, in firefox. Used the same procedure - disabling the tool's grant, and then logging back in - which hadn't worked the first time, but magically did the second time. Hurrah :) Thanks for the help & comments! Lirazelf (talk) 12:24, 14 April 2020 (UTC)

Move a batch a values (+qualifiers+references) from a property to another

Hi, I would like to move a value from a property to another :
From :

  ITEM         PROPERTY       VALUE
  Q390055      P179          Q1357619

To this :

  ITEM         PROPERTY       VALUE
  Q390055      P279           Q1357619

Problems :

• I have a list of about 400 ITEM/PROPERTY/VALUE in the same case (automobile models in which a car classification is a value of a P179 instead of a P279).
• For some values, there might be some associated qualifiers and/or references that must be moved as well.
  

Is there a way to do this automatically? Thanks. Sovxx (talk) 12:44, 15 April 2020 (UTC)

Create Properties and set labels and descriptions on existing Properties

I am asking this with a look at new Wikibase installations (like FactGrid.

• Is it possible to create Properties with QuickStatements (nice for instance if you want to create a complex environment with a structture you already have)
• What is the Syntax to put labels and descriptions in a new language on existing Properties?

I get an error message "Revision with ID not found" if I try

P367      Les      "Identificación de la BnF"

but I can state

P367      P2      Q7

--Olaf Simons (talk) 21:01, 4 May 2020 (UTC)

duplicated items created

Batch #33824 shows 3062 edits have been done. However, EditGroup shows that there are 4545 edits. Some duplicated items are created.--Njzjz (talk) 09:40, 10 May 2020 (UTC)

Also see https://phabricator.wikimedia.org/T234162

Tracked in Phabricator
Task T234162

--M2k~dewiki (talk) 17:39, 24 May 2020 (UTC)

Confirmed users

It seems that manually confirmed users are not able to edit through QuickStatements because they are not autoconfirmed. Vicimediorum (talk) 16:31, 17 May 2020 (UTC)

How to debug

I was trying to run QuickStements as part of docker-wikibase, while everything seems to work, Quick Statements does not create new item phab:T252832. I am asking myself, what could possibly be wrong? Has anywone experience with debugging QuickStatements in docker-wikibase? --Physikerwelt (talk) 11:23, 18 May 2020 (UTC)

Feature request: negative Qids

I proposed to allow using negative Qids (idea comes from OpenStreetMap). When a negative Qid is used a new item is created automatically. For example:

Q-1<TAB>P22<TAB>Q-2
Q-2<TAB>P40<TAB>Q-1

This will create two items linking each other.--GZWDer (talk) 07:11, 27 May 2020 (UTC)

I wonder how the first one could work. Both items would need to be created simultaneously (I doubt this is possible) or the P22 edit for it stored and done afterwards. Obviously, fans of follows/followedby statements will love. --- Jura 15:20, 28 May 2020 (UTC)

Feature suggestions: CSV format enhancements

• allow "_" nistead of "," in first line (also mentioned at Topic:Vklj7ag5qazmn130)
• allow "REMOVE" instead of "-" in first line
• make final c/r optional (also mentioned at Topic:Vklj7ag5qazmn130)

As Magnus isn't so active these days, I mention these here. --- Jura 15:20, 28 May 2020 (UTC)

Fatal Error

When I attempt to run a QuickStatements batch (like I've done so many times), I appear to have to login. I click on login, and I get this unpleasant message. I cannot figure out how to get past it.

Fatal error: Uncaught Exception: Error retrieving token1: {"error":"mwoauth-callback-not-oob-or-prefix","message":"oauth_callback must be set, and must be set to \"oob\" (case-sensitive), or the configured callback must be a prefix of the supplied callback."} in /data/project/magnustools/public_html/php/oauth.php:282

Suggestions? Thanks. Trilotat (talk) 13:03, 1 June 2020 (UTC)

Try what I suggest in #Can't log in (ie. re-authenticate). --Matěj Suchánek (talk) 10:22, 2 June 2020 (UTC)

@Matěj Suchánek: I re-authenticated, but it continues. Now I have this:

Fatal error:  Uncaught Exception: Error retrieving token1: {"error":"mwoauth-callback-not-oob-or-prefix","message":"oauth_callback must be set, and must be set to \"oob\" (case-sensitive), or the configured callback must be a prefix of the supplied callback.","callback":"api.php"} in /data/project/magnustools/public_html/php/oauth.php:283
Stack trace:
#0 /data/project/quickstatements/public_html/api.php(101): MW_OAuth->doAuthorizationRedirect('api.php')
#1 {main}
thrown in /data/project/magnustools/public_html/php/oauth.php on line 283

Note the on line 283 bit in the line above. I have no idea what any of it means. Trilotat (talk) 13:45, 2 June 2020 (UTC)

Resolved. Thanks. Trilotat (talk) 18:47, 2 June 2020 (UTC)

Old interface stopped working

Looks like the old interface has stopped working after the domain change to toolforge.org. All I see is a white page with the text "your token:". - Premeditated (talk) 07:52, 4 June 2020 (UTC)

• See Topic:Vnjbti7ei8peth5d --- Jura 08:15, 4 June 2020 (UTC)

You can't create a new batch, because you are not autoconfirmed

How should I solve this problem in order to create a new batch? Many thanks in advance.  – The preceding unsigned comment was added by Robertaleotta2020 (talk • contribs) at 11. 6. 2020, 20:52 (UTC).

By becoming autoconfirmed user. Basically, you need to be active on Wikidata for a longer time. --Matěj Suchánek (talk) 09:14, 12 June 2020 (UTC)

Batch #37458

Can anyone please tell me why it's giving me error? -- CptViraj (talk) 11:25, 9 July 2020 (UTC)

@CptViraj: A link, please. —Eihel (talk) 11:27, 9 July 2020 (UTC)

@Eihel: https://quickstatements.toolforge.org/#/batch/37458 -- CptViraj (talk) 13:12, 9 July 2020 (UTC)

Did you include quotes, i.e. Q83265 P8333 "4577". --Matěj Suchánek (talk) 14:25, 9 July 2020 (UTC)

@Matěj Suchánek: Nope. -- CptViraj (talk) 15:23, 9 July 2020 (UTC)

@CptViraj: The error referenced is "No success flag set in API result". You can see it here. The second line is useless. If I understood correctly, it's an error, but I'm sure of nothing. Could you copy-paste here, the order batch you entered, please? —Eihel (talk) 16:13, 9 July 2020 (UTC)

@Eihel:

Q83265 P8333 4577 S248 Q63386904

-- CptViraj (talk) 16:20, 9 July 2020 (UTC)

@CptViraj: Strings (including… external-ID property values) must be in "double quotes". and P248 is really useless. Cordially. —Eihel (talk) 16:26, 9 July 2020 (UTC)

Gotcha! Tried with double quotes and it worked. Apologize, Thanks! -- CptViraj (talk) 16:31, 9 July 2020 (UTC)

RUN takes a long time, not completed, due to syntax issue?

I am wondering what caused QS to take a long time to complete the task? Both V1 and CSV took a long time. Still not completed after an hour. Please advise, thank you. jshieh (talk) 13:58, 16 July 2020 (UTC)

Quickstatements upload

@ShiehJ: I think you need to double quote all string types (external identifiers and URLs). —Dexxor (talk) 06:31, 17 July 2020 (UTC)

@Dexxor: Thanks for the pointer. For the next one, I put text in double quotes

QS read in the content, when I pressed <Run>, still hanging... When I tried CSV, clicked <Import CSV commands>, the wheel on upper right just turned and turned, nothing happened. Still puzzled as what to do next. Thanks in advance for additional help! jshieh (talk) 12:59, 17 July 2020 (UTC)

@ShiehJ: 2009 is a date, it should be in the same format you used for the "retrieved" date: +2009-00-00T00:00:00Z/9 —Dexxor (talk) 13:14, 17 July 2020 (UTC)

@Dexxor: Thanks for the tip! Getting closer. Though still hanging, after changing the pub date using the date code as instructed. jshieh (talk) 13:33, 17 July 2020 (UTC)

Generally, the "quoting policy" is different for CSV and V1. You can find some workarounds on Help:QuickStatements#CSV file syntax. Still, I find V1 more reliable. The following worked for me (loaded without hanging, did not test the result):

qid,Len,Den,P31,P31,P50,P577,P243,P7851,P212,P957,P136,P136,P123,S854,s813
,"A Fool's Errand: Creating the National Museum of African American History and Culture in the Age of Bush, Obama, and Trump","Washington, DC : Smithsonian Books",Q571,Q732577,Q12053846,+2019-01-01T00:00:00Z/11,"""1089275852""","""siris_sil_1113245""","""9781588346681""","""1588346684""",Q36279,Q4184,Q131626,"""https://www.smithsonianbooks.com/store/recent-releases/a-fools-errand/""",+2020-07-16T00:00:00Z/11

Also note using s813 instead of S813. --Matěj Suchánek (talk) 14:28, 17 July 2020 (UTC)

@Matěj Suchánek: Thanks so much!!

I remained baffled as the reason that the two new items failed to be accepted by V1 commands in QS!

CREATE
LAST	Len	"Morris Blackburn"
LAST	P31	Q5
LAST	P21	Q6581097
LAST	P27	Q30
LAST	P569	+1902-00-00T00:00:00Z/9
LAST	P570	+1979-00-00T00:00:00Z/9
LAST	P106	Q1028181
CREATE
LAST	Len	"Berthold Schmutzhart"
LAST	P31	Q5
LAST	P21	Q6581097
LAST	P27	Q30
LAST	P106	Q1028181

See screenshots showing system's response after pressing <Import V1 commands>

--jshieh (talk) 19:17, 28 July 2020 (UTC)

How to add alias?

When I use

qid,ALTzh
Q753,"Cu, 銅"

to add the alias "銅", it fails. How to add alias? --The Master (talk) 03:52, 19 July 2020 (UTC)

See CSV file syntax: qid,Azh. --Matěj Suchánek (talk) 10:15, 19 July 2020 (UTC)

Thanks! --The Master (talk) 13:56, 19 July 2020 (UTC)

error with Template:Artwork autocomplete on Commons

Prior to a few months ago, fields in Template:Artwork could be automatically populated to Wikidata by clicking the QuickStatements arrow icon. At present, I just get taken to a mostly empty screen that says only "Your token:" Try it on File:Brooklyn Museum - William Allen - John Wollaston - overall.jpg. Please look into this. In the meantime, is there a simple workaround? Thanks. -Animalparty (talk) 19:12, 24 July 2020 (UTC)

Duplicates

Hello, it seems that my QS creates duplicates... is there a bug ? https://quickstatements.toolforge.org/#/batch/39340 Bouzinac (talk) 11:44, 6 August 2020 (UTC)

Property with multiple values

Hello, I am wondering whether Quickstatements allows you to import a statement with a property which has multiple values? i.e. if you want to batch upload an item and that says someone had several children, or that someone spoke multiple languages, how would you do that?

e.g. how would you write the following in quickstatements (i.e. sandbox spoke Latin and Hebrew)?

qid,P1412
Q4115189, Q397 Q9288

I apologise if I missed this in the documentation somewhere already Valeriummaximum (talk) 22:31, 13 August 2020 (UTC)

Technically, a property with multiple values is made of multiple statements. You can simply write:

qid,P1412
Q4115189, Q397
Q4115189, Q9288

—Dexxor (talk) 07:23, 14 August 2020 (UTC)

@Dexxor: I'm wondering if there might be another way to express this? If you had a large csv file, would you need to create new rows every time a property had multiple values for each relevant property?Valeriummaximum (talk) 11:32, 14 August 2020 (UTC)

@Valeriummaximum: I'm trying to solve the same problem. The solution given by Dexxor works well when the item is already created, but it doesn't work in the case of a newly created item (the first statement creates the item, but the second statement can't have the QID). --Deansfa (talk) 15:10, 26 December 2020 (UTC)

@Deansfa: I ended up using Pywikibot with Pandas to read data from a spreadsheet into wikidata. I'd be curious to see any developments with quickstatements though!Valeriummaximum (talk) 21:41, 29 December 2020 (UTC)

No success flag set in API result

I have started multiple background batches in the last days and always see "No success flag set in API result" errors for some edits. This is very annoying as I have to submit the batch later again. I assume that the edits fail because of anti spam or rate limiting. QuickStatements should probably work slower then or offer an option to retry failed edits (in batch). --Pyfisch (talk) 18:41, 24 August 2020 (UTC)

After the batch is completed a button appears to retry those edits with errors. :-) --Pyfisch (talk) 20:10, 24 August 2020 (UTC)

It's annoying but we don't know why it happens. My guess is that it's caused by server being unhappy about QuickStatements (or anybody else) editing too fast and sending "please wait a while" responses. --Matěj Suchánek (talk) 09:59, 25 August 2020 (UTC)

Code to add area to all SSSIs in Wales

I'd like to add area to all SSSIs in Wales and need qualifier = Hectare. What's the property for Unit (optional) please? This is what I have at the moment: Q14995340|P2046|3.15|P?|Q35852 Thanks! Llywelyn2000 (talk) 08:38, 5 September 2020 (UTC)

Units are not qualifiers. Per Help:QuickStatements#Add simple statement:

Quantity in the form of amount~toleranceUxx (amount[lower,upper]Uxx in QuickStatements version 1), with amount, tolerance, lower and upper being a rational number and Uxx being the item number of a unit (Qxx).

... it should be Q14995340|P2046|3.15U35852. --Matěj Suchánek (talk) 09:43, 5 September 2020 (UTC)

That did the trick! I didn't think of looking under 'simple' ! And the u=unit is new for me. Thanks again! BOT-Twm Crys (talk) 10:06, 5 September 2020 (UTC)

Batch Upload with Null Values

Hello! I am working with a large dataset that has a number of null values i.e. objects that sometimes have height and width listed and sometimes not (along with other properties that are sometimes present, sometimes not). It seems that Quickstatements does not like null statements except when creating an item (at least it wouldn't work when I tried) but I am wondering if there is a workaround because it would be useful to be able to ingest a large dataset into wikidata without having to manually upload each item with a null cell. Valeriummaximum (talk) 17:43, 6 September 2020 (UTC)

Hello Valeriummaximum, An example:

• work the data on a spreadsheet
• sort the columns where there are blanks (by selecting all the data, so as not to disorganize them)
• save as many csv files as there are columns to add (be sure to remove the statement or the header of the column where the blanks are)
• incorporate as many batches in QS as there are files (several batches can be launched simultaneously). Cordially. —Eihel (talk) 01:02, 8 September 2020 (UTC)

Thank you Eihel I feared that might be the case. It seems a little inefficient--I'm wondering if OpenRefine has this issue when importing to QuickStatements. Will investigate. Valeriummaximum (talk) 12:36, 8 September 2020 (UTC)

Update--OpenRefine can support this and upload to Quickstatements.Valeriummaximum (talk) 23:23, 12 September 2020 (UTC)

Creating a set of new streets from Petscan

Hello. I've created quite a few buildings and streets in Denmark using Petscan/QuickStatements allready. Now i want to create wikidata items from commons:Category:Streets in Haderslev, using the commoands "P31:Q79007,P17:Q35,P131:Q21143,P276:Q29868". A QuickStatements batch, which looks OK, is created, but when I try to run it, all I get is error shown in red with no indication what the error might be. Anything I can do?  – The preceding unsigned comment was added by Hjart (talk • contribs) at 09:39, 9 September 2020 (UTC).

Hi Hjart, a derivated question from your own question do you know if there is street identifier in denmark likewise FANTOIR code (P3182) or Unique Street Reference Number (P8447) ? Bouzinac ^{💬●✒️●💛} 12:14, 11 September 2020 (UTC)

@Bouzinac: We do indeed have street identifiers in denmark. I'll see if I can find them. --Hjart (talk) 12:21, 11 September 2020 (UTC)

@Hjart: Could you write here precisely the commands you entered (or the first few lines, csv or not), please? —Eihel (talk) 12:47, 11 September 2020 (UTC)

@Eihel: P31:Q79007 P17:Q35 P131:Q21143 P276:Q29868(4 lines) is what I entered into the Petscan wikidata creation box. Clicking the green "Start QS" button below the box now produces a ready to run QuickStatements page. Do you need more? --Hjart (talk) 13:34, 11 September 2020 (UTC)

Use of <somevalue> in Quickstatements

Hello, I am trying to think how to model situations where an object is described as "made between 165 and 256". In that case, I would use inception (P571) for the inception date and use earliest date (P1319) and latest date (P1326) to express the lower and upper limits of the date range expression, but obviously these can only be used as qualifiers. Someone on the wikidata telegram community suggested using somevalue for the date and then using earliest date and latest as qualifiers.

I can do this manually on wikidata but am having some trouble using Quickstatements. For reference I tried,

qid,P571,qal1319,qal1326
Q4115189,somevalue,+0165-00-00T00:00:00Z/9,+0256-00-00T00:00:00Z/9

When I import the CSV commands, the Quickstatements interface correctly parses the statements to mean that P571 has "somevalue" and this statement has two qualifiers, and it correctly parses the dates to 0165 and 0256, but when I run the commands, it comes up with an error with the two qualifiers.

Is it that Quickstatements does not like qualifiers applied to somevalue or am I confused about some syntax here? or is there some issue with my date expression?

Thank you!Valeriummaximum (talk) 12:45, 13 September 2020 (UTC)

@Valeriummaximum: somevalue can be used without qualifier, otherwise P571 must receive value (+0165-00-00T00:00:00Z/7) so that qal1319,qal1326 are not errors. —Eihel (talk) 17:30, 13 September 2020 (UTC)

@Eihel: So just to be absolutely clear, you are saying that I would need to say "inception is 165CE" with a qualifier "latest date is 256CE"? I'm just wondering if that is a logical way to parse out an expression like inception 165-256CE  – The preceding unsigned comment was added by Valeriummaximum (talk • contribs) at 18:22,‎ 13 September 2020 (UTC).

@Valeriummaximum: Please sign your messages. +0165-00-00T00:00:00Z/7 gives 2nd century. You can also add sourcing circumstances (P1480) circa (Q5727902) if you want. But this is only a suggestion for you to use QS for your dates. —Eihel (talk) 19:29, 13 September 2020 (UTC)

My apologies for forgetting to sign, @Eihel:. I'm not sure if you answered my question though. You seemed to be suggesting earlier that Quickstatements cannot add qualifiers to <novalue> and that if you want to indicate a date range 165-256, you should use 165 with inception (P571) and add 256 as qualifier with latest date (P1326), is that right? I'm not sure how adding sourcing circumstances or changing the date precision would be helpful here (while 165 is second-century, 265 is not). Or are you saying that the date precision has to be changed? So that it would say something like "date is second century", "earliest date is 165" and "latest date is 256" (even if the range exceeds the second century)? Valeriummaximum (talk) 01:16, 14 September 2020 (UTC)

@Valeriummaximum: The only thing I say for QS2: somevalue seems to work only without qualifiers. If you put a value for P571, you can add qualifiers, without committing a constraint violation as in date of birth of Jesus (Q3016939). Of course, setting the Somevalue value by adding qualifiers remains valid on the interface, but not with QS2 as you have seen. (Unknown values and no values are added to statements by clicking on the icon beside the value field that looks like this .) Another tool may be suitable. Even adding unknown (Q24238356) as a value causes an error on QS2. For the rest, Where do I suggest new features? You can ask at tool's Bitbucket page or at User:Magnus Manske/quick statements2, but be aware that we keep Magnus busy! By explaining that a property with the value Somevalue should be able to have qualifiers, just like greater than (Q47035128) and less than (Q52834024). Cordially. —Eihel (talk) 03:32, 14 September 2020 (UTC)

@Eihel: Thank you! This is very clarifying!Valeriummaximum (talk) 11:14, 14 September 2020 (UTC)

Julian vs. Gregorian calendar

Hello, I am trying to upload a series of statements to Wikidata involving pre-Gregorian dates. My understanding was that Wikidata would by default parse a date before 1600 as Julian calendar (Q11184) but all my uploads (with date expressions like +0245-00-00T00:00:00Z/9) gave the marker "Gregorian". Is there a way to specify Julian date? Many thanks (as always!) for any assistance! Valeriummaximum (talk) 19:43, 21 September 2020 (UTC)

I see now that the documentation says that specifying calendar is currently a limitation for Quickstatements. I'm just curious why Wikidata defaults to Gregorian here. Valeriummaximum (talk) 20:51, 22 September 2020 (UTC)

submission via URL using LAST

The following URL submission isn't working: https://quickstatements.toolforge.org/#/v1=CREATE%7C%7CLAST%7CLen%7C%22Digital%20media%20use%20and%20mental%20health%22%7C%7CLAST%7CDen%7C%22Scholarly%20article%22%7C%7CLAST%7CP31%7CQ580922%7C%7CLAST%7CP7347%7C%22https:%2F%2Fen.wikiversity.org%2Fwiki%2FTalk:WikiJournal_Preprints%2FDigital_media_use_and_mental_health%22%7C%7CLAST%7CP793%7CQ76903164%7CP585%7C2019-06-08T00:00:00Z%2F11

However, each aspect of it works alone if I just create a new item and add a single statement (=CREATE%7C%7CLAST%7C[statement]). Is there something obvious I'm doing wrong? I've merged the items into Q99557809, but I'm making a template that auto-formats up these submission URLs so I really want to get it working (see further example here). T.Shafee(evo&evo) (talk) 03:44, 24 September 2020 (UTC)

@Magnus_Manske, Marsupium, Ederporto, ValterVB: Any ideas on this one? I'm sure there's some simple error I'm missing, but I just can't get it running. T.Shafee(evo&evo) (talk) 03:43, 28 September 2020 (UTC)

@Evolution and evolvability: For your example, you're missing "+" in the date. For your further example, "enwikiv" is not a valid sitelink, I think maybe it would be "enwikiversity"? Good contributions, Ederporto (talk) 06:01, 28 September 2020 (UTC)

T.Shafee(evo&evo), The submission via URL described at Help:QuickStatements#Running_QuickStatements_through_URL never worked for me for new interface to version 2, so I was rather surprised that above link actually worked. Was this new URL syntax documented somewhere? --Jarekt (talk) 16:00, 28 September 2020 (UTC)

I guess it is documented at https://quickstatements.toolforge.org/#/batch . But why the ending "%2F11"? --Jarekt (talk) 16:10, 28 September 2020 (UTC)

@Jarekt: The date needs precision, in this case 11 (day). Good contributions, Ederporto (talk) 19:49, 28 September 2020 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ @Ederporto, Jarekt: Thank you! The updated further example now worked (of course, the same example URL won't work a second time since the WV page is already linked, but included for reference). It's allowed my to get a {{PAGEQID}} template working. I had worked entirely from the Help:QuickStatements#Running_QuickStatements_through_URL information, but wasn't sure whether it was up to date. T.Shafee(evo&evo) (talk) 02:27, 29 September 2020 (UTC)

4 wrong lots in QuickStatements

I made 4 wrong "lots" in QuickStatements, the last 4 made by me. Is it possible someone reverse these 4 lots, or I must undo all the items, one by one? I tried in QuickStatments the cancellation of these 4 lotes but not managed. (I made this same request at "Wikidata:Bot requests"). I am sorry. Thank you, GualdimG (talk) 11:52, 29 September 2020 (UTC)

: Already done manually by the editor Tm. Thank you. GualdimG (talk) 13:15, 29 September 2020 (UTC)

Watchlist addition of QS edits

Tracked in Phabricator
Task T217144

@Lucas_Werkmeister (WMDE), Lydia_Pintscher (WMDE):

Some change these days lead to edits with QS being watchlisted .. I don't find that terribly useful .. is there a way to opt out of it? --- Jura 05:04, 2 October 2020 (UTC)

Ultimately, each tool should give users ability to control the watchlist. --Matěj Suchánek (talk) 08:58, 2 October 2020 (UTC)

Removing a date via QS

Can QS remove date statements? I've tried a few different variants of the command below, but all result in errors. Variants tried include using a different /n precision, truncating the date to only the year, omiting the + symbol, and including quote marks.

-Q98853409	P571	+2020-01-01T00:00:00Z/9

Any ideas? T.Shafee(evo&evo) (talk) 23:43, 7 October 2020 (UTC)

Try +2020-00-00T00:00:00Z/9 –LiberatorG (talk) 23:59, 7 October 2020 (UTC)

@Evolution and evolvability: Unfortunately it seems that some date values with precision=9 (year) or less use month-date of 00-00 and some use 01-01, and QuickStatements requires you to match what is in the database, even though the user interface and the query service do not report this information. It is possible to see what is in the database with wbgetclaims. –LiberatorG (talk) 00:29, 8 October 2020 (UTC)

@LiberatorG: Aha, thanks! Definitely wouldn't have guessed that one! I've updated the removals section with the bodge workaround. T.Shafee(evo&evo) (talk) 00:57, 8 October 2020 (UTC)

Running_QuickStatements_through_URL on Commons?

I just updated Help:QuickStatements#Running_QuickStatements_through_URL. I wonder if anybody figured out a way to create URL which adds QS to Structured data on Commons? --Jarekt (talk) 02:06, 9 October 2020 (UTC)

Yes, there is one valid option and a suggested option:

1. Use the API:

1. Make a GET req. https://quickstatements.toolforge.org/api.php

?action=import

&data=M85873074|P180|Q146

&format=v1

&temporary=1

&compress=1

2. Returns a JSON obj. Collect the value in 'data'.

3. Make the following URL: https://quickstatements.toolforge.org/#/batch/?tempfile=qs_8EZIdb&site=commons

OR

2. If Magnus merge the following file [2] to the master.

1. This will allow https://quickstatements.toolforge.org/#/v1=M85873074%7CP180%7CQ146?site=commons or with csv.

--Premeditated (talk) 11:52, 15 October 2020 (UTC)

@Premeditated: Thanks for reply the first approach did not work for me (the data was still being added to Wikidata. But the second approach sounds like a great solution. @Magnus Manske: any chance "?site=commons" flag can be added? That would be a perfect solution. --Jarekt (talk) 03:05, 16 October 2020 (UTC)

@Jarekt: Hi, that is because I wrote '?', instead of '&'. Works now. - Premeditated (talk) 09:25, 16 October 2020 (UTC)

Updating current statements

Hello, it's currently difficult to update multiple identical statements which differ only by qualifiers (to add another qualifier, for instance). Would it make sense to support a syntax which allows you to update a statement based on its id? Something like:

STATEMENT TAB Q1$00000000-0000-0000-0000-000000000000+1600-00-00T00:00:00Z/7 TAB P1319 TAB +1586-00-00T00:00:00Z/9

Gettinwikiwidit (talk) 22:51, 14 October 2020 (UTC)

I made a mistake

Hello, I think I made a mess. Earlier I tried to run this on Quickstatements v2:

CREATE

LAST	P356	"10.1002/CPA.3160160407"

LAST	P31	Q13442814

LAST	P1476	en:"Exponential Decay of Solutions of the Wave Equation in the Exterior of a Star-Shaped Obstacle"

LAST	Len	"Exponential Decay of Solutions of the Wave Equation in the Exterior of a Star-Shaped Obstacle"

LAST	P433	"4"

LAST	P304	"477-486"

LAST	P1104	"10"

LAST	P478	"16"

LAST	P577	+1963-11-00T00:00:00Z/10

LAST	P921	Q193846

LAST	P1433	Q5154224

LAST	P50	Q323331	P1545	"1"	P1932	"P. D. Lax"

LAST	P50	Q450331	P1545	"2"	P1932	"C. S. Morawetz"

LAST	P50	Q1299250	P1545	"3"	P1932	"R. S. Phillips"

LAST	P894	"0161.08001"

Then I tried this on the Quickstatements v1 window, but instead I created a massive mess of new items: from Q101210127 to Q101210180

I'm seeking help here, because I'm not sure where to seek help on this. Xenmorpha (talk) 23:44, 5 November 2020 (UTC)

EDIT: I made a request for bulk deletion on my newly created pages, but I would appreciate help on why my quickstatements v2 as above errors when I try it out Xenmorpha (talk) 23:56, 5 November 2020 (UTC)

Submitting QuickStatements using templates

In case it's useful, I've been experimenting with making adding items to wikidata easier in-wiki with this pair of templates over at Wikiversity:

• v:Template:Quickstatements link
• v:Template:QS

They're pretty simple really, I think it makes it easier to write the URLs for submitting statements to wikidata. Any improvements welcomed through! T.Shafee(evo&evo) (talk) 07:16, 1 December 2020 (UTC)

Submitting QuickStatements using [R]

I'm a fan of the programming language programming language R. I've therefore been working for a while on making it possible to submit statements to wikidata using the R package:

• WikidataR

If it's of interest, go check it out and let me know if you come across any issues! T.Shafee(evo&evo) (talk) 07:19, 1 December 2020 (UTC)

how do I modify Label by quickstatement

For items that have already been created，how do I batch modify labels through QuickStatements. In the wikibase I built myself, there are a large number of items that need to be modified

you simply create a csv list like this:

qid,L(your preferred language code)

Qxxxx1,New label 1

Qxxxx2,New label 2

and click "import csv commands" on the QuickStatements page. Good luck. --Hjart (talk) 12:55, 15 December 2020 (UTC)

Invalid snak data

Hi, I am trying my first quickstatements. Preprocessing looks fine, but when I hit run, all entries show errors. First "Invalid snak data" and then "Base statement not found". Here is what I used:

qid,P7842,qal1810,#
Q1755186,36283,"""Alfred Ebenhoch""",Export from Vienna History Wiki 20210120110126

@Dajasj, Mfchris84, CanadianCodhead:, ID's that look like numbers need to be triple-quoted:

qid,Vienna History Wiki ID (P7842),qalsubject named as (P1810),#
Alfred Ebenhoch (Q1755186),"""36283""","""Alfred Ebenhoch""",Export from Vienna History Wiki 20210120110126

--Hjart (talk) 09:30, 11 May 2021 (UTC)

@Krabina: adding statements with qualifier i had the same issues running QS in CSV- and/or batch mode. If you try to add the statement with the qualifier in "V1-mode" (TSV) and non-batch mode everything works fine.

Q1755186	P7842	"36283"	P1810	"Alfred Ebenhoch"

--Mfchris84 (talk) 12:30, 20 January 2021 (UTC)

I have the same issue, but only for P1545. For example:

qid,P3602,qal1545,qal1268,qal1111,S248,s813
Q57792,Q16061881,1,Q239333,1760117,Q104635841,+2020-12-28T00:00:00Z/11

What am I doing wrong? Dajasj (talk) 16:32, 26 February 2021 (UTC)

same error for P1618

CanadianCodhead (talk) 16:35, 1 April 2021 (UTC)

I just encounterd the smae problem, I beleave I found the solution:"Invalid snak data" means that there is an error with whe value you want to add. In my case it needed a qualifier of language, and in an other case it neded to be a Wikidata item insted of a string. For me it helped to try and add it by hand on wikidata.org to trubulshoot. --Daanvr (talk) 13:48, 7 May 2021 (UTC)

Special:MyLanguage missing

Special:MyLanguage is missing on the "Help" button in this tool. --Sabelöga (talk) 16:33, 6 May 2021 (UTC)

Running down?

Is there pb with the QS service ?Bouzinac ^{💬●✒️●💛} 21:02, 9 May 2021 (UTC)

My batches the last 4 days didn't run.--Hjart (talk) 09:11, 10 May 2021 (UTC)

Temporary batches still works, but the background stuff appears stuck. --Hjart (talk) 14:49, 10 May 2021 (UTC)

Empty fields in CSV

Is there a way to avoid errors with empty fields inside the csv. In my case I have a lot of statements and sources. All sources have a URL, but only some of them I have a page number. At the moment QuickStatements stops working with incomplete data sets. --Newt713 (talk) 22:06, 10 May 2021 (UTC)

I would like this functionality as well! Justin0x2004 (talk) 17:28, 3 October 2021 (UTC)

csv file with some missing fields

Hoping t o get some help on csv formatting. I encounter problems with missing data. some rows do not have a value for every column. this results in either errors or halting the progress (getting stuck). This happens for example because some rows have several "instance of" and some have any one. exemple:

Qid,Len,Den,P17,P17,P17...
Q123456,"""some name""","""Some description""",Q12345,,...
Q654321,"""some name""","""Some description""",Q12345,Q12345,...

Before executing QS identifies it as: 'instance of [P31]:{ "type": "unknown", "text": "" }' When executing QS does not succeed in running thees commands.

Any tips?

Cutting up the import in many different csv’s is undesirable because of the number of possible combinations. --Daanvr (talk) 08:00, 17 May 2021 (UTC)

The best solution I found for now is using the triple quote’s like this:

Qid,Len,Den,P17,P17,P17...
Q123456,"""some name""","""Some description""",Q12345,"""""",""""""...
Q654321,"""some name""","""Some description""",Q12345,Q12345,""""""...

resulting in either "invalid snak data" or "Must be at least one character long" --Daanvr (talk) 10:15, 17 May 2021 (UTC)

Does that mean the batch will stop or continue to run when it reaches the blank value? — Martin (MSGJ · talk) 10:11, 23 June 2021 (UTC)