-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to write from [R] to wikidata via API #15
Comments
I'm checking how this can be done. The COVID-19 Wikidata item already exists (https://www.wikidata.org/wiki/Q84263196) and inside it you have different things. First, you have a series of 'statements' identified by a specific property numner (i.e. 'instance of' P31) and each of them lists a serires of other Wikidata items (i.e. 'disease' Q12136). Then we have 'identifiers', where we have again properties but that only list one ID (not a Wikidata item). And at the end we have all the pages on that item in all Wikimedia foundation projects. My question is: what do you want to be able to edit? Everything? Or just statements and identifiers? This is crucial as we need to think about a way to possibly structure the queries. |
Hmm, ideally everything, since being able to edit aliases and descriptions would be useful.
Backup option: outputting Quickstatments tables. Relevant issue link. |
The QS API and its token system are detailed here (if you are logged into QS) |
@magnusmanske, could you confirm what the relevant quickstatements API format is? |
I think I've found it: Will do some tests and then try to implement in [R] |
Successful first test (using token code as per my QS userpage)!
Resulting in this batch being correctly implemented. |
The new API almost works (now committed to wikiPackageTesting.R). I've also added a query about this at Wikidata Help_talk:QuickStatements. |
There s a current capability gap in the WikidataR package in that it can only read from, not write to wikidata. This will be a key and valuable feature. I've also added a note at that repo.
The text was updated successfully, but these errors were encountered: