I share the opinion of @Multichill, @LucasWerkmeister and others: I understand the rationale for authentication, and I think I can live with it as user ; but as a tool developer, I don’t want to have to implement OAuth2 in my tools (such as Tool-inteGraality) − I was planning to add WCQS to inteGraality (T294893) but frankly I’m unlikely to do so if I have to throw in oauth on top.

For lexemes a good grouping predicate would be wikibase:lexicalCategory and dct:language

@Addshore From a product perspective, would it make sense to ship integraality with wikibase / make it easy to add it to the setup (probably along the lines of a Docker image to add to the docker-compose setup) − is that smth that would be beneficial to users? I mean, it’s no QuickStatements, but it has proven valuable for many.

One year later, some more thoughts:

In T293543#7488987, @Reedy wrote:

In T293543#7488401, @JeanFred wrote:

As far as I can tell, there was no such outreach to Pattypan and Vicuna.

I filed https://github.com/yarl/vicuna/issues/154 back in July.

There was direct outreach to Commonist by @Reedy with https://github.com/ritschwumm/commonist/issues/25 − August 24th (7 days before the days before the deadline) − which the volunteer maintainer acknowledged on September 12th. As far as I can tell, there was no such outreach to Pattypan and Vicuna.

In T280806#7376680, @Multichill wrote:

The MediaWiki API developers and the Pywikibot framework maintainers had a bit of miscommunication causing deprecated code to still be in use. By forcing this change through you're effectively punishing the Pywikibot framework users for a mistake made by other people.

In T295215#7487428, @Aklapper wrote:

@JeanFred: Hi, what is supposed to happen with and in this very ticket? :)

Oh joy: tests fail with
AttributeError: <module 'pywikibot' from 'heritage/.tox/py37/lib/python3.5/site-packages/pywikibot/__init__.py'> does not have the attribute 'ImagePage'

integraality

• reads the configuration template {{Property dashboard}} to know the SPARQL bits and pieces to use to construct the SPARQL queries
• Throws these SPARQL queries into the SPARQL endpoint using pywikibot (via pywikibot.data.sparql)
• computes stuff
• writes the table as wikitext

Thanks @VIGNERON for fixing the dashboard! Also made the transposed one https://www.wikidata.org/wiki/User:Jean-Fr%C3%A9d%C3%A9ric/Integraality/Lexemes_bis

Sooo, smth like https://www.wikidata.org/wiki/User:Jean-Fr%C3%A9d%C3%A9ric/Integraality/Lexemes does return smth (no idea whether it makes any sense though ^^)

Probably resolved during the last fix sprint: https://www.wikidata.org/wiki/User:Jean-Fr%C3%A9d%C3%A9ric/T236960 is updated.

Actually, would https://www.wikidata.org/wiki/Wikidata:Tools/inteGraality#Using_two_properties_as_alternative_groupings just work there?

Probably good enough instrumentation for now.

So, I don’t know the first thing about the Lexemes data model, but some early thoughts:

Both the interactive and command-line updates are working! Yay! 🎉

@LucasWerkmeister on Telegram

I think you might need to upgrade to Pywikibot 6.6.1 or later? earlier versions used a deprecated method of getting API tokens, which was disabled at some point in Wikimedia (same error message at T291202)

And I still can’t reproduce locally. All updates done locally are working.

So what happened is:

I rollbacked all recent changes − no luck :-(

I must have broken something when deploying 0a8e7fb8...

With 30a2f2ba the offending SPARQL query should be always surfaced to the user. Closing as Resolved.

In T292931#7458851, @Ainali wrote:

Oops, that was a sloppy mistake. Thanks for pointing it out!

I went for option 2, “integraality throws an error when encountering any invalid syntax in columns and will not update the dashboard at all.”

See also T218057: Determine workflow to selectively purge potentially privacy-sensitive EXIF fields, such as geocoordinates, from a Wikimedia Commons file and T222675: Explore possibilities for users to remove/exclude geo data from EXIF on images

Cross-linking T284941: [S] Add note explaining that EXIF geolocation metadata may be uploaded with Commons images.

Basically, a SPARQL timeout error is not something we can solve on integraalit. The issue lies with the underlying queries − either it’s misconfigured or just more likely too expensive (try making a dashboard of all scientific articles… ;-þ)

Since T284183 you should get a proper error message: Unknown column syntax 9732. The issue is you entered 9732, not P9732.

Thanks for the report, and @Ashot1997 for the PR!

This is however more problem of us calling the field "country" rather than the more correct "dataset".

In T278918#7271066, @Lokal_Profil wrote:

@JeanFred Would you mind merging the patch?

In T286354#7271065, @Lokal_Profil wrote:

Aliases for parameters seem to be quite frequently used which I'm not sure the harvester supports (will dig into it unless @JeanFred remembers?)

I restarted the webserver, it seems to work now: https://wikiloves.toolforge.org/earth/2021/Portugal

Thanks for reporting!