[04:39:16] T [12:29:46] Hello, have a question and I was wondering if you could help me: I would like to add about 150 very similar items that share most of their statements. Is there a way to not type everything a 150 times, like duplicating an item or using a template or the like? [12:38:57] cephyr, yup! That sounds like something Quickstatements would be good for. https://quickstatements.toolforge.org [12:39:39] For generating the list of items you want to edit you can then use something like Petscan (or several other tools) https://petscan.wmflabs.org [12:40:25] interesting! [12:40:28] Then you can dump that into your preferred spreadsheet software, put in the appropriate Quickstatements commands for each item, then copy it into Quickstatements's web UI as tab separated info [12:44:41] Cool, thank! I'll look into this. [12:46:55] No problem. If you have any questions about it, you can ask here of course :) [13:09:12] indeed, I have one: I see the potential to create quite a mess if I don't operate quickstatements properly. Is there a way I can run the creation of objects and their properties in a sandbox, like in my user space? I can only find the general Wikidata sandbox, where I could not try creating new objects etc. [13:30:05] cephyr you can start with a small batch size (even just one object large if the query is very similar for each object). You then get a batch id which you can use to then "HECK UNDO UNDO UNDO" a bad query, or to discuss it on-wiki. [13:33:08] Oh, and you also get a pseudo-preview of what a batch is doing because you actually run it. [13:37:26] okay, thanks! [14:13:17] !admin@wikidata https://www.wikidata.org/w/index.php?title=Q858636&action=history needs protection [14:17:45] done [19:59:17] merryprog, I tried with quickstatements, and while it went well for two thirds of the batch, it didn't with the remaining third. It just tells me "error", rather unspecifially. To my eye, the data just looks the same as the one that went well. Is there a way I and see what exactly the error is? [20:11:50] cephyr, do you have a link to the batch? [20:12:40] Here you go: https://quickstatements.toolforge.org/#/batch/71544 [20:14:46] wow, yeah, that isn't too helpful [20:16:14] okay, so it isn't just me haha [20:16:50] solution: don't write batches that have errors [20:16:54] will have* [20:18:13] yeah, I'm all in [20:21:31] cephyr, my inclination is that the repeated "de/en" stuff that I see in the batch page looks odd, but I really don't know [20:21:49] Can you show what the commands looked like? Just a page is fine [20:21:53] s/page/item [20:22:20] qid,Len,Lde,Den,Dde,Aen,Ade,P31,P361,P17,P131 [20:22:20] ,Großsteingrab 111,Großsteingrab 111,The megalithic tomb No. 111,Das Großsteingrab 111 im Haldensleber Forst,,,Q10521078,Q1917052,Q183,Q689996 [20:23:25] hrm [20:28:05] Maybe the empty aliases [20:28:52] Ah, I think I know [20:28:53] yup [20:29:16] I just tried running it on the sandbox and the two alias commands were the ones that errored [20:32:09] Hmm, but then again, on most lines that prompted an error, there are no empty properties, like here: [20:32:10] ,Großsteingrab ALV 44,Großsteingrab ALV 44,The megalithic tomb ALV 44,Das Großsteingrab ALV 44 im Haldensleber Forst,Großsteingrab Bebertal I 41,Großsteingrab Bebertal I 41,Q10521078,Q1917052,Q183,Q689996 [20:33:33] hm, that runs fine on the sandbox [20:34:18] Use a separate batch with no Aen,Ade heading for items without aliases [20:34:32] ... and I can confirm that the sets that prompted no errors all had no empty aliases. But the other way around, aliases with a value do not seem to always do the trick. [20:34:38] cephyr, could also try just logging out and back in and running it again? [20:34:52] ah, alright [20:35:07] @markh: I will. Most of the errored lines though do have aliases. [20:35:16] might be the way it handles batch item creation or something and if one fails then everything explodes [20:35:45] being a diva you mean? Haha [20:35:55] I'll give that a try [21:00:30] merryprog, markh: That did the trick! [21:00:39] Thanks for your help :-) [21:00:50] Great! [21:04:10] :D [21:05:21] Just for reference, which change resolved it cephyr? [21:10:07] I left out the data sets with empty aliases, and the rest would run fine. Then, in a second, round, I removed the empty alias columns in those data sets that would not run before and ran them again. And voilá! [21:10:46] Nice [21:11:55] And for reference: If you annoy QuickStatements once, it will just not go on, even if the rest is fine. Prog with an attitude.