User talk:MichaelSchoenitzer

From Wikidata
Jump to navigation Jump to search

You can find old discussions in the archive.

Little issue with quickpresets

[edit]

Hi! When you have time, could you have a look at this? Thank you very much! --Epìdosis 20:32, 6 May 2019 (UTC)[reply]

I couldn't use LexData - login issue

[edit]

I read the documentation of the tool, and it seems exactly what I need to add senses to the Hebrew lexemes I created. I managed to install and run the first two commands from example but when I tried the third command, repo = LexData.WikidataSession("MichaelSchoenitzer", "foobar") I got error. I replaced name and password with mine. Didn't help. The error I am getting: "API returned error: {'code': 'assertnameduserfailed', 'info': 'Assertion that the user is "Uziel302" failed.', '*': 'See https://www.wikidata.org/w/api.php for API usage."

Thanks, Uziel302 (talk) 20:35, 22 September 2019 (UTC)[reply]

@Uziel302: Sorry, the bug is fixed now. Just update to 0.1.6. -- MichaelSchoenitzer (talk) 21:08, 22 September 2019 (UTC)[reply]
When I tried to add senses without additional claims I got this error: self.__setClaims__(idSense, claims) so I had to add claims={}, for the script to work.Uziel302 (talk) 06:43, 24 September 2019 (UTC)[reply]
Thanks, fixed. Let me know whenever you have any issues like this (here, or better on github), so I can further improve it. -- MichaelSchoenitzer (talk) 21:32, 28 September 2019 (UTC)[reply]
L2.createForm("firsts", "Q146786")
I get: raise PermissionError("API returned error: " + str(DATA["error"]))
PermissionError: API returned error: {'code': 'bad-request', 'info': 'Field "grammaticalFeatures" in parameter "data" expected to be of type "array". Given: "string"', 'parameterName': 'data', 'fieldPath': ['grammaticalFeatures'], '*': 'See https://www.wikidata.org/w/api.php for API usage.Uziel302 (talk) 05:19, 5 October 2019 (UTC)[reply]
I changed to an array and it worked, you just need to change documentation.Uziel302 (talk) 05:51, 5 October 2019 (UTC)[reply]
There is also a bug when posting form without claims. Full error in note here Uziel302 (talk) 12:13, 5 October 2019 (UTC)[reply]
Fixed the documentation, the other bug was already fixed. -- MichaelSchoenitzer (talk) 11:40, 11 October 2019 (UTC)[reply]
I'm having issues with get or create lexemes, seems like it expects claims, Full error in note here. I had to remove line 580. Uzielbot (talk) 06:37, 19 October 2019 (UTC)[reply]
I get this error every few thousand edits: 'The wiki is currently in read-only mode.', 'readonlyreason': 'The database is read-only until replication lag decreases.', is it normal? And since create form isn't "get or create" I need to delete all the create commands that already done.Uziel302 (talk) 11:48, 21 October 2019 (UTC)[reply]

Structured Data - modeling data

[edit]

As you may have seen, there are community discussions underway on how to best model structured data on Commons.

Direct links to pages created so far:

Please visit and participate in topics you might be interested in when you get some time. Thanks. -- Keegan (WMF) (talk) 19:39, 2 October 2019 (UTC)[reply]

Structured Data - computer-aided tagging designs

[edit]

I've published a design consultation for the computer-aided tagging tool. Please look over the page and participate on the talk page. If you haven't read over the project page, it might be helpful to do so first. The tool will hopefully be ready by the end of this month (October 2019), so timely feedback is important. -- Keegan (WMF) (talk) 18:09, 9 October 2019 (UTC)[reply]

New page for catalogues

[edit]

Hi, I created a new page for collecting sites that could be added to Mix'n'match and I plan to expand it with the ones that already have scrapers by category. Feel free to expand, use for property creation. Best, --Adam Harangozó (talk) 12:03, 21 October 2019 (UTC)[reply]

Critical issue with LexData

[edit]

I am running the bot and I noticed something critical:

L2 = LexData.get_or_create_lexeme(repo, "הקדשה", he, "Q1084") L2.createForm("הקדשה", ['Q1084','Q1775415','Q110786'], claims={"P1343": ["Q6936841"]})

הקדשה doesn't exist, but instead of creating it, it updated a similar lexeme: הקדש, I had to revert it.

Since many Words can be both Lexeme and form of other Lexeme (e.g. wikt:movies) this behaviour is a critical issue and I guess I need to stop the bot until it is solved.Uziel302 (talk) 12:15, 25 October 2019 (UTC)[reply]

It only happens when the lexeme is missing, maybe there is some wrong fallback to search the string on other lexemes. Anyways, the workaround I will take is to make sure all the lexemes are there before uploading their forms.Uziel302 (talk) 13:34, 25 October 2019 (UTC)[reply]
I've fixed the behavior in 0.1.10. Sorry for the inconvenience. I started writing tests for the bot, so that we won't have that many bug in the future. -- MichaelSchoenitzer (talk) 19:47, 30 October 2019 (UTC)[reply]

Maxlag

[edit]

I mentioned before that every few thousands edits I get read-only mode and the script stops running. When it happens, I must edit the script, otherwise it will add the same forms once again (I didn't find get or create for forms, that may prevent double form creation). I think the solution to it should be adding maxlag. Pywikibot has default of maxlag 5 seconds. more about maxlag. Thanks. Uziel302 (talk) 09:06, 21 November 2019 (UTC)[reply]

syntaxfehler

[edit]

hallo michi, ich habe bdi meinen versuchen bereits mehrerre query-fehler begangen;

  1. https://www.wikidata.org/?curid=65288749#error01
  2. https://www.wikidata.org/?curid=65288749#error02

kannst du das bitte korrigieren? vielen dank im voraus
no bias — קיין אומוויסנדיקע פּרעפֿערענצן — keyn umvisndike preferentsn talk contribs 11:47, 21 November 2019 (UTC)[reply]

Is there a way to edit forms with LexData?

[edit]

I could find only abput creation of forms. Uziel302 (talk) 20:32, 1 December 2019 (UTC)[reply]

@Uziel302: what do you want to do? Adding claims is possible – but so far only in a hacky way. Will improve that. Changing the text of the form isn't possible (yet). -- MichaelSchoenitzer (talk) 01:12, 24 March 2020 (UTC) PS: Sorry for the late reply, I was busy writing my thesis. Will try to work on LexData in the next weeks more again.[reply]
I managedd to edit forms with wbeditentity. Uziel302 (talk) 16:54, 25 March 2020 (UTC)[reply]

"MachtSinn" shows the same items multiple times

[edit]

I used the tool now, very powerful. The most annoying issue is that it keeps showing the same offers over and over after I dismissed them (not by skip). Uziel302 (talk) 10:27, 20 December 2019 (UTC)[reply]

@Uziel302: Should be fixed now. -- MichaelSchoenitzer (talk) 14:52, 6 March 2020 (UTC)[reply]
I get 500 error on [1]. Uziel302
@Uziel302: Works for me – do you still get the error? Otherwise it was maybe just some glitch of toolforge. -- MichaelSchoenitzer (talk) 16:18, 24 March 2020 (UTC)[reply]
It keeps showing me the same items over and over. had to delete many duplicate senses. Uziel302 (talk) 20:53, 25 March 2020 (UTC)[reply]
I am very surprised that this can happen and don't know how this can be. But in installed a new version of LexData that fixes a few issues including one that I could see in the log files of today. Maybe that fixes this issue. (The version of LexData installed on the server was surprising old so maybe this was indeed an old bug). Let me know if there are still issues. -- MichaelSchoenitzer (talk) 21:42, 25 March 2020 (UTC)[reply]
I am still getting the same question multiple times, which results in duplicate senses: https://www.wikidata.org/w/index.php?title=Lexeme:L21978&oldid=prev&diff=1416727544 Menemenetekelufarsim (talk) 23:06, 7 May 2021 (UTC)[reply]

Ernie und Bert

[edit]

Was hat es mit Ernie (Q32859690), Bert (Q32859701) und Big Bird (Q32859678) auf sich?--Petermahlzahn (talk) 16:54, 15 May 2020 (UTC)[reply]

@Petermahlzahn: Das sind die bisher hochenergetischen Neutrinos die der Detektor IceCube Neutrino Observatory (Q1569514) bisher nachgewiesen hat. Es klingt absurd einem eizelnen Elementarteilchen einen Namen zu geben, aber die Nachweise diese höchstenergetischen Teilchen sind von großer wissenschaftlicher Bedeutung, weil es bisher keine plausible Erklärung gibt wie derart hochenergetische Neutrinos entstehen können. Es gibt auch bisher keine anderen bestätigte Fälle von Teilchen mit Energien in dieser Größenordnung. Daher haben die Wissenschaftler sie benannt um besser darüber streiten diskutieren zu können. -- MichaelSchoenitzer (talk) 17:44, 16 May 2020 (UTC)[reply]
[edit]

Greetings,

The Structured Data team is working on an alternative, image-focused prototype for media search on Commons. The prototype uses categories, structured data as well as wikitext from Commons, and Wikidata to find its results. The development team would like your feedback on the prototype, as they are looking to work to further enhance the search experience on Commons. If you have a moment, please look over the project page set up on Commons to find a link to the prototype and leave your feedback on the talk page. Thanks for your time, I'll be posting message similar to this one to other pages on Commons. The team is looking forward to reading what you think. Keegan (WMF) (talk) 20:47, 28 May 2020 (UTC)[reply]

Commons - Media Sarch, new feedback round

[edit]

Greetings,

I'm following up on a message from earlier in the year about the prototype development for Special:MediaSearch. Based on community feedback, the Structured Data team has developed some new features for Special:MediaSearch and are seeking another round of comments and discussions about the tool. Commons:Structured_data/Media_search is updated with details about the new features plus some other development information, and feedback is welcome on Commons talk:Structured_data/Media_search. Media Search works in any language, so the team would especially appreciate input around support for languages other than English. I look forward to reading about what you think. -- Keegan (WMF) (talk) 20:05, 23 September 2020 (UTC)[reply]

Commons - Media Sarch, new feedback round

[edit]

Greetings,

I'm following up on a message from earlier in the year about the prototype development for Special:MediaSearch. Based on community feedback, the Structured Data team has developed some new features for Special:MediaSearch and are seeking another round of comments and discussions about the tool. Commons:Structured_data/Media_search is updated with details about the new features plus some other development information, and feedback is welcome on Commons talk:Structured_data/Media_search. Media Search works in any language, so the team would especially appreciate input around support for languages other than English. I look forward to reading about what you think. -- Keegan (WMF) (talk) 00:07, 24 September 2020 (UTC)[reply]

Commons - Media Sarch, new feedback round

[edit]

Greetings,

I'm following up on a message from earlier in the year about the prototype development for Special:MediaSearch. Based on community feedback, the Structured Data team has developed some new features for Special:MediaSearch and are seeking another round of comments and discussions about the tool. Commons:Structured_data/Media_search is updated with details about the new features plus some other development information, and feedback is welcome on Commons talk:Structured_data/Media_search. Media Search works in any language, so the team would especially appreciate input around support for languages other than English. I look forward to reading about what you think. -- Keegan (WMF) (talk) 01:11, 24 September 2020 (UTC)[reply]

QuickPresets and Lexemes

[edit]

Hi,

I am a regular user of your Quickpresets tool, and I'm also a contributor to the Lexemes part of wikidata (Lxxxx) - but the Quickpresets I have on Lexemes are inadequate.

I would like either to "not display" the tool on Lexemes, or better, to use a specific configuration on Lexemes. But lexemes do not have P31, which is my principal trigger.

Could you please help me on this one... once you're over with your thesis - Thanks a lot --Hsarrazin (talk) 16:01, 7 March 2021 (UTC)[reply]

Q60168804

[edit]

Hi, kannst du mal bitte in die History des items schauen. Ich habe versucht, den Umzug vor 3 Jahren endlich umzusetzen. Inzwischen müssten die Infos stimmen. Aber eigentlich wäre es cool die alte Info mit einem Datum zu versehen, von wann bis wann sie gegolten hat, statt sie zu überschreiben. Ich kann das aber nicht. Könntest du für die Adresse in der Dachauer Straße die Dauer 1987 bis 2019 und für den Oskar-von-Miller-Ring seit 2019 eintragen? Ich würde mir das dann im Diff ansehen und hoffentlich was draus lernen. Grüße --H-stt (talk) 17:39, 11 May 2022 (UTC)[reply]

Improvements for the QuickPresets script

[edit]

I've created a fork of your quickpresets script to make a few QoL improvements to it: https://www.wikidata.org/wiki/User:Nicereddy/quickpresets.js

The main improvements are:

  • Adding a link to the config being used in the header of the fieldset.
  • Moving the confirmation messages below the fieldset so it doesn't jump around and cause misclicks when the confirmation messages appear (previously they appeared above, which moved the links down every time).
  • Slightly better usage of space (changing "Add X" to just "X" to allow more options to render without bleeding into the next line.

I use it a lot, so these improvements feel pretty significant for me given how many edits I've performed over the last year or two using your script. If you're interested in adopting any of them into your script, feel free :) Nicereddy (talk) 18:24, 24 September 2022 (UTC)[reply]

QuickPresets has the German work for "cross-platform"

[edit]

I couldn't work out why I was getting a single german word in my entry box""Add Os: Linux ∙ Windows ∙ macOS ∙ Plattformunabhäng ∙ unixoid" until I realised it was hard-coded in User:MichaelSchoenitzer/quickpresets defaultconf.js. It seems out of place as everything else there is either multi-lingual or English. Vicarage (talk) 17:53, 29 August 2023 (UTC)[reply]

String in quickpresets

[edit]

Hallo ich bin noch recht neu in WikiData ...

Wie kann ich beim quickpresets eine String Value (inkl. Sprache)für z.B. Inschrift (P1684) in Value-Array definieren?

Danke für eine Antwort ... bzw. auch Aufnahme in der default config bei der Installations-Anleitung

Gruss JochenCH JochenCH (talk) 19:37, 8 June 2024 (UTC)[reply]