I approve this request on WMDE's end. Thank you

hi @Chuiimuii_ofc, thank you for the interest in our work. The task you've claimed is a part of the implementation of the functionality developed by Wikimedia Germany's team. To ensure effective work on the functionality involved, we'd like this task to be fulfilled by WMDE.
Happy to hear about your interest and needs from Wikibase GraphQL API, as those might inform our further development.

@Ifrahkhanyaree_WMDE the methods are available and not documented. Decision on whether it is beneficial to have those explicitly documented (in the Open API specification, the swagger "autodocs", or both) is still to be taken.

The api.postWithEditTokencall in line 26 of https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Wikibase/+/de96a53e5788a14194ec24bdda1f8351ba1bf719/repo/resources/wikibase.wbui2025/api/editEntity.js#26 would likely be replaced with something like

Tagging with Data-Engineering on that one as well: can we get some assistance in getting the related Gerrit changes merged. WMDE does not have +2 rights on operations/dumps repository. Thank you!

Tagging with Data-Engineering: can we get some assistance in getting the related Gerrit change merged. WMDE does not have +2 rights on operations/dumps repository. Thank you

I approve this request on WMDE's end. Thank you!

I approve this request on WMDE's behalf.
To my knowledge @ItamarWMDE has fulfilled most of formal requirements as they got access to analytics-privatedata-users. (NDA has been signed etc)
thank you

hello @BTracy-WMF @gmodena, how fixed you'd say you are about it being a date parameter and specifying the date the dump generated should be recorded for?
We've created (we = WMDE team responsible for Wikidata dumps) have created a subtask to only track our work on modifying the script T408800 and we have thought that from our limited understanding instead of passing the date that would used in a directory name for the output file we would see it more clear to have a way to specify the entire directory/path to store the resulting dump under. This would make the location of the resulting dump even more explicit and predictable (/someplace/wikibase/wikidatawiki/DATE - there's more than a date here)
But we thought there might be reasons to not make it so direct and explicit in the script input, e.g. maybe the airflow orchestrator does now the date it would be concerned with but does not know, or is not meant to know some other details like where exactly in file system the resulting dump file will be put. If you are convinced the date is the best way to solve the underlying issue we'll follow that, I'm not certain that current suggestion in T408800 is actually better.

what's the procedure of getting https://gerrit.wikimedia.org/r/1199078 applied to the train delivery branch? I.e. who's expected to cherry pick that to that branch?

Thanks @BTullis . I might have been clumsy with words as often.
To confirm we understand each other: Do I understand correctly that you're convinced that database queries used by wikidata dump scripts run, give or take, equally fast in both cases?

not that my opinion matters but I support @Dzahn's point

This specific type of request has become standard for WMDE staff afaict. A custom form for it would probably be helpful. So that it's clear for clinic duty and the new WMDE staff doesn't have to worry about the details.

But they are saying no ssh needed.. so we can safely assume they mean the lowest of the 3 levels.