*(apologies for cross-posting)*
Hello,
This is a significant change announcement relevant for some Wikibase API
users.
What's Changing?
Over the coming weeks, most Wikibase API modules will gain three new
parameters: returnto, returntoquery, and returntoanchor. Additionally,
these API modules may return tempusercreated and tempuserredirect fields in
their responses. These parameters are being added to support user
interaction flows related to IP Masking
<https://meta.wikimedia.org/wiki/IP_Editing:_Privacy_Enhancement_and_Abuse_M…>
.
Who’s Affected?
Only users who use the API to make anonymous edits are affected. If you
don’t use the API to make edits, or if you only make authenticated edits,
you can safely ignore these changes, and disregard the additional API
parameters and response data.
What You Need to Do
If you use the API to make anonymous edits, the response may contain a
tempusercreated string indicating the name of the temporary account that
was created, and a tempuserredirect nullable string. If the tempuserredirect
is not null, you should redirect the user to that URL to complete the setup
for the temporary account. Afterwards, the user will automatically be
returned to the current wiki; you can use the returnto, returntoquery,
and/or returntoanchor parameters in your original API request to control
the title, query, and anchor where the redirect returns to.
If you have any questions or concerns about this change, please don’t
hesitate to reach out to us in this ticket (T357024
<https://phabricator.wikimedia.org/T357024>).
Cheers,
--
Mohammed S. Abdulai
*Community Communications Manager, Wikidata*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
https://wikimedia.de
Grab a spot in my calendar for a chat: calendly.com/masssly.
A lot is happening around Wikidata - Keep up to date!
<https://www.wikidata.org/wiki/Wikidata:Status_updates> Current news and
exciting stories about Wikimedia, Wikipedia and Free Knowledge in our
newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>
.
Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us to achieve our vision!
https://spenden.wikimedia.de
Wikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Charlottenburg, VR 23855 B.
Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin,
Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine,
Dr. Christian Humborg
Dear Wikibase/Wikidata Community,
We are trying to understand which database technologies and strategies Wikibase/Wikidata uses for storing, updating, and querying the data (knowledge) it manipulates.
By looking at the documentation<https://wmde.github.io/wikidata-wikibase-architecture/assets/img/03-dataflo…> we understood that RDF is only used for the Wikidata Query Service, but we could not find out exactly how Wikibase/Wikidata stores the information that is translated to RDF during the data dump.
More specifically, we understood that a MySQL (or is it MariaDB?) relational database is used as the key persistence component for most of Wikibase/Wikidata services and that the information that is maintained in this database is periodically exported to multiple formats, including RDF.
In addition, looking at the relational database schema published in the documentation<https://www.mediawiki.org/wiki/Manual:Database_layout> we could not locate tables that are easily mappable to the Wikibase Data Model<https://www.mediawiki.org/wiki/Wikibase/DataModel>.
Thus, we hypothesize that there is some software component (Wikibase Common Data Access?) that dynamically translates the data contained in those tables to Statements, Entities, etc. Is that hypothesis, correct?
If yes, does this software component uses any intermediate storage mechanism for caching those Statements, Entities, ...? Or are those translations always performed at runtime on-the-fly (be it for querying, adding, or updating Statements, Entities, …)?
Finally, we would like to understand more about how Wikidata REST API<https://www.wikidata.org/wiki/Wikidata:REST_API> is implemented:
• In which database are the statements that added/retrieved through it stored? Is it being stored in the central MySQL database or in another database?
• Does it have any support for pagination of statements? For example, if an item has many statements associated with a property, does the API assumes that both the underlying database and the network will support the retrieval of all those statements?
• Are you currently considering implementing the support for more flexible querying of statements, or such requirement has been fully delegated to the Wikidata Query Service?
If there is an updated documentation that could help us answer those questions, could you kindly point us to it? Otherwise, would you be able to share this information with us?
Best Regards,
Elton F. de S. Soares
Advisory Software Engineer
Rio de Janeiro, RJ, Brazil
IBM Research
E-mail: eltons(a)ibm.com<mailto:eltons@ibm.com>
Dear Wikidata Community,
We are trying to understand which database technologies and strategies Wikidata uses for storing, updating, and querying the data (knowledge) it manipulates.
By looking at the documentation<https://wmde.github.io/wikidata-wikibase-architecture/assets/img/03-dataflo…> we understood that RDF is only used for the Wikidata Query Service, but we could not find out exactly how Wikidata stores the information that is translated to RDF during the data dump.
More specifically, we understood that a MySQL (or is it MariaDB?) relational database is used as the key persistence component for most of Wikidata services and that the information that is maintained in this database is periodically exported to multiple formats, including RDF.
In addition, looking at the relational database schema published in the documentation<https://www.mediawiki.org/wiki/Manual:Database_layout> we could not locate tables that are easily mappable to the Wikibase Data Model<https://www.mediawiki.org/wiki/Wikibase/DataModel>.
Thus, we hypothesize that there is some software component (Wikibase Common Data Access?) that dynamically translates the data contained in those tables to Statements, Entities, etc. Is that hypothesis, correct?
If yes, does this software component uses any intermediate storage mechanism for caching those Statements, Entities, ...? Or are those translations always performed at runtime on-the-fly (be it for querying, adding, or updating Statements, Entities, …)?
Finally, we would like to understand more about how Wikidata REST API<https://www.wikidata.org/wiki/Wikidata:REST_API> is implemented:
* In which database are the statements that added/retrieved through it stored? Is it being stored in the central MySQL database or in another database?
* Does it have any support for pagination of statements? For example, if an item has many statements associated with a property, does the API assumes that both the underlying database and the network will support the retrieval of all those statements?
* Are you currently considering implementing the support for more flexible querying of statements, or such requirement has been fully delegated to the Wikidata Query Service?
If there is an updated documentation that could help us answer those questions, could you kindly point us to it? Otherwise, would you be able to share this information with us?
Best Regards,
Elton F. de S. Soares
Advisory Software Engineer
Rio de Janeiro, RJ, Brazil
IBM Research
E-mail: eltons(a)ibm.com<mailto:eltons@ibm.com>
