*(apologies for cross-posting)*
Hi everyone,
The Wikidata+Wikibase office hours
<https://www.wikidata.org/wiki/Wikidata:Events#Office_hours> for the next
quarter will be held on Wednesday, January 18th 2023 at 17:00 UTC (18:00
Berlin) in the Wikidata Telegram group
<https://t.me/joinchat/IeCRo0j5Uag1qR4Tk8Ftsg>.
*The Wikidata and Wikibase office hours are online events where the
development teampresents what we have been working on over the past
quarter, and the community is welcome to ask questions and discuss
important issues related to the development of Wikidata and Wikibase.*
We hope to see you there.
--
Mohammed Sadat
*Community Communications Manager, Wikidata*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
https://wikimedia.de
Keep up to date! 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 Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
*(apologies for cross posting)* Hello everyone,
As you may already know, we are developing a new REST API to improve
programmatic access to data from Wikidata and other Wikibase instances.
Many thanks to everyone who gave us the initial feedback on the proposed
implementation plan of the REST API and subsequently tested the
experimental phase of it on Beta Wikidata
<https://wikidata.beta.wmflabs.org>.
All the items listed in our previous communication
<https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/me…>
as still needing to be completed for the initial release have now been
completed and we are pleased to announce that the Wikibase REST API is
planned to go live on Wikidata about a week later.
What is the current state capable of doing?
-
Retrieve the data of an Item with ‘GET /entities/items/{item_id}’ and
filter what fields (i.e. type, labels, descriptions, aliases, statements,
sitelinks) are returned when reading the Item data
-
Retrieve all statements of an Item with ‘GET
/entities/items/{item_id}/statements’
-
Retrieve the data of a single statement of an Item with ‘GET
/entities/items/{item_id}/statements/{statement_id}’ or ‘GET
/statements/{statement_id}’
-
Conditionally request the data only if it has changed since the
specified revision/timestamp (using If-None-Match, If-Modified-Since
HTTP headers)
-
Create a statement on an Item with ‘POST
/entities/items/{item_id}/statements’
-
Authenticate and authorize as a Beta Wikidata user when making edits
using the API, as well as provide edit tags and edit comment, and mark an
edit as one made by a bot.
-
Replacing the statement on an Item with ‘PUT
/entities/items/{item_id}/statements/{statement_id}’ or ‘PUT
/statements/{statement_id}’
-
Removing the statement from an Item with ‘DELETE
/entities/items/{item_id}/statements/{statement_id}’ or ‘DELETE
/statements/{statement_id}’
-
Automated edit summaries
The following functionality is still awaiting a final security review of a
library <https://phabricator.wikimedia.org/T316523> and will be enabled
once that is finished:
-
Editing a statement on an Item with ‘PATCH
/entities/items/{item_id}/statements/{statement_id}’ or ‘PATCH
/statements/{statement_id}’
Please note that the following items previously listed under "The following
will likely not be available in the first version but follow later" have
not yet been finished and will not be available in this initial release:
-
Creating or deleting an Item
-
Getting a statement from an Item based on the Property ID in the
statement
-
Any operation (reading, adding, editing, removing) on sitelinks, labels,
descriptions and aliases
-
Any operation on entity types other than Items (i.e. Properties,
Lexemes, …)
-
Translated error messages
However, we will continue to work on these items in the future to provide a
more comprehensive REST API. In order to prioritize our next steps, we
would greatly appreciate feedback on which missing features you would find
most useful to add next.
If you have any questions or want to provide feedback please let us
know at Wikidata
talk:REST API feedback round
<https://www.wikidata.org/wiki/Wikidata_talk:REST_API_feedback_round#The_Wik…>.
As this new API is more tailored to the Wikibase data model than the Action
API, we have outlined the differences in the JSON data format between the
two
<https://doc.wikimedia.org/Wikibase/master/php/rest_data_format_differences.…>
for you for easy comparison.
Thank you for your patience and support as we continue to improve the
Wikibase REST API.
Cheers,
--
Mohammed Sadat
*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.
Keep up to date! 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 Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hello 👋🏽
I'm Benedict Nnaemeka Udeh from Nigeria, a recently hired Community
Relations Specialist (CRS
<https://meta.wikimedia.org/wiki/Community_Relations_Specialists>) for
Wikidata and Commons.
I'm a member of the Igbo Wikimedians User Group, the Founder of IG Wikidata
Hub, and the Founder of Wiki Mentor Africa, a mentorship program that seeks
to bring more African developers and technical writers into the technical
space of Wikimedia. I'm passionate about community growth and capacity
building. Like you, I'm incredibly spirited about the free knowledge
movement.
In my new position as CRS, I will focus on collaboration and communication
with you about Wikidata and Commons product development, the user-facing
changes and roll-outs, and sometimes on projects with special needs for
collaboration with Volunteers. In other words, I am here to serve you (the
editors, contributors, and readers of Commons and Wikidata projects) and
the working groups at the Foundation that support Commons and Wikidata.
I've already started sharing some updates; you can find them on the Product
and technical support for Commons Portal
<https://commons.wikimedia.org/wiki/Commons:Product_and_technical_support_fo…>.
Please feel free to use the discussion page
<https://commons.wikimedia.org/wiki/Commons_talk:Product_and_technical_suppo…>
to discuss these updates.
I look forward to working with and for you all and can't wait to see the
fantastic things we will do together.
Benedict Udeh
Community Relations Specialist
Hello everyone,
The next Research Showcase, focused on Editor Retention, will be
live-streamed Wednesday, January 18. Find your local time here
<https://zonestamp.toolforge.org/1674063059>.
YouTube stream: https://www.youtube.com/watch?v=gS8ELcVZ8Q4
You can join the conversation on IRC at #wikimedia-research. You can also
watch our past research showcases here:
https://www.mediawiki.org/wiki/Wikimedia_Research/Showcase
This month's presentations:
Vital Signsː Measuring Wikipedia Communities’ HealthBy *Cristian Consonni,
Eurecat - Centre Tecnològic de Catalunya, Barcelona*Community health in
Wikipedia is a complex topic that has been at the center of discussion for
Wikipedia and the scientific community for years. Researchers observed that
the number of active editors for the largest Wikipedias started declining
after an initial phase of exponential growth. Some media outlets picked
this fact as a death announcement for the project, but the news of
Wikipedia's death turned out to be greatly exaggerated. However, it remains
true that researchers and community activists need to understand how to
measure community health and describe it more accurately. In this
presentation, we would like to go beyond the traditional metrics used to
describe the status of the community. We propose the creation of 6 sets of
language-independent indicators that we call "Vital Signs." We borrow the
analogy from the medical field, as these indicators represent a first step
in defining the health status of a community; they can constitute a
valuable reference point to foresee and prevent future risks. We present
our analysis for several Wikipedia language editions, showing that
communities renew their productive force even with stagnating absolute
numbers; we observe a general need for renewal in positions related to
particular functions or administratorship. We created a dashboard to
visualize all the indicators we have computed and hope that the communities
will find it helpful for improving their health.
- Paperː Community Vital Signs: Measuring Wikipedia Communities’
Sustainable Growth and Renewal
<https://meta.wikimedia.org/wiki/File:Community_Vital_Signs_Research_Paper_-…>
Learning to Predict the Departure Dynamics of Wikidata EditorsBy *Guangyuan
Piao, Maynooth University*Wikidata as one of the largest open collaborative
knowledge bases has drawn much attention from researchers and practitioners
since its launch in 2012. As it is collaboratively developed and maintained
by a community of a great number of volunteer editors, understanding and
predicting the departure dynamics of those editors are crucial but have not
been studied extensively in previous works. In this paper, we investigate
the synergistic effect of two different types of features: statistical and
pattern-based ones with DeepFM as our classification model which has not
been explored in a similar context and problem for predicting whether a
Wikidata editor will stay or leave the platform. Our experimental results
show that using the two sets of features with DeepFM provides the best
performance regarding AUROC (0.9561) and F1 score (0.8843), and achieves
substantial improvement compared to using either of the sets of features
and over a wide range of baselines.
- Paperː Learning to Predict the Departure Dynamics of Wikidata Editors
<https://parklize.github.io/publications/ISWC2021.pdf>
--
Emily Lescak (she / her)
Senior Research Community Officer
The Wikimedia Foundation
Hello all!
The Search Platform Team usually holds an open meeting on the first
Wednesday of each month. Come talk to us about anything related to
Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query
Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, January 11, 2023
Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CET
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
Have fun and see you soon!
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>