Dear all,
A new Wikidata Query Service scaling update has been published. It
outlines the WDQS current state and summarizes the suggestions with
the most impact we’re exploring now, with a few in-progress.
You can read the full update here:
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_up…
We will also be hosting two office hour sessions on Jitsi
(https://meet.jit.si/WDQSOfficeHour) to directly address your comments
and questions with the team.
The first session will take place on *March 27, 2023, at 17:00 UTC*
(https://zonestamp.toolforge.org/1679936404). Additionally, to
accommodate those in the ESEAP area, we have scheduled a second office
hour on *March 28, 2023, at 8:00 AM UTC*
(https://zonestamp.toolforge.org/1679990419).
We hope you will be able to join us during one of these sessions to
discuss this important topic further.
Thanks!
--
Luca Martinelli [Sannita] (he/him)
Community Relations Specialist
Hello all,
As you may already know, the Wikimedia Hackathon 2023 will take place in
Technopolis, Athens, Greece, on May 19-21. This in-person event will gather
the global Wikimedia technical community to connect, hack, run technical
discussions, and explore new ideas.
*If you plan to join, please register as soon as possible.*
Registration for the Hackathon will be open until we reach the event's
maximum capacity [0]. If you plan to join, we encourage you to register as
soon as possible, as there are currently around ten slots left. We also
encourage you to book your travel and accommodation shortly. You will find
more information on the travel [1] and accommodation [2] pages. You are
also welcome to help us improve those pages by adding additional
information about Athens and how to travel there.
For people who already registered, remember to confirm your attendance by
filling out the additional field in the registration form (see the email
sent by hackathon(a)wikimedia.org on March 13). Please note that WMF's
scholarship process concluded in January, and aside from the 51 people who
got a scholarship confirmed, we cannot support people with funds or visa
documents. Therefore, most participants must organize their own travel to
stay in Athens.
This year's edition will focus on bringing together people who already
contribute to technical aspects of the Wikimedia projects, know how to find
their way around in the technical ecosystem, and can work or collaborate on
projects more autonomously. For people new to our technical environment,
there are other newcomers-friendly events you can join throughout the year
- feel free to improve the list. [3]
*You can organize a satellite event with your local community.*
For people new to the technical aspects of the Wikimedia projects or who
cannot attend the in-person event, a great option could be to organize an
autonomous, local satellite event to the Hackathon. These events can occur
before, during, or after the in-person event. If you are considering
running an event like this, contact your local community to get started! If
you need financial support, please note that the deadline to apply for the
current round of Rapid Funds is March 20 [4].
*Proposals for the in-person program are welcome until April 4.*
The Hackathon is organized as a participant-driven event and lives from the
active participation of its attendees. Because this year's edition is
focused on reconnecting with your technical community peers in person, most
of the program will take place onsite. You can propose a session by
creating a task on the Phabricator board. Find more information on the
Program page [5].
Similar to the satellite events, some online sessions, in parallel or ahead
of the event, may be organized autonomously by participants. In any case,
participants are free to work on their projects, whether in-person or
online, and connect to the technical community on the Hackathon channels
[6].
If you have any questions, feel free to use the Hackathon talk page or to
reach out to the organizers at hackathon(a)wikimedia.org.
Cheers,
Srishti
On behalf of the Hackathon organizing team
[0]
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Participate#Registr…
[1] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Travel
[2] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Accommodation
[3] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Documentation#Event…
[4] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Satellite_events
[5] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Program
[6] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Connect
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi all,
The next Research Showcase, focused on Gender and Equity on Wikipedia, will
be live-streamed Wednesday, March 15, at 9:30 AM PST / 16:30 UTC. Find your
local time here <https://zonestamp.toolforge.org/1678897840>.
YouTube stream: https://www.youtube.com/watch?v=lw4MzJgDIzo
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:
Men Are elected, women are marriedː events gender bias on Wikipedia
By *Jiao Sun, University of Southern California*Human activities can be
seen as sequences of events, which are crucial to understanding societies.
Disproportional event distribution for different demographic groups can
manifest and amplify social stereotypes, and potentially jeopardize the
ability of members in some groups to pursue certain goals. In this paper,
we present the first event-centric study of gender biases in a Wikipedia
corpus. To facilitate the study, we curate a corpus of career and personal
life descriptions with demographic information consisting of 7,854
fragments from 10,412 celebrities. Then we detect events with a
state-of-the-art event detection model, calibrate the results using
strategically generated templates, and extract events that have asymmetric
associations with genders. Our study discovers that the Wikipedia pages
tend to intermingle personal life events with professional events for
females but not for males, which calls for the awareness of the Wikipedia
community to formalize guidelines and train the editors to mind the
implicit biases that contributors carry. Our work also lays the foundation
for future works on quantifying and discovering event biases at the corpus
level.
- Paperː Sun, J. & Peng, N. (2021). Men Are Elected, Women Are Married:
Events Gender Bias on Wikipedia. Proceedings of the 59th Annual Meeting of
the Association for Computational Linguistics and the 11th International
Conference on Natural Language Processing, 350-360.
<https://aclanthology.org/2021.acl-short.45.pdf>
Twitter reacts to absence of women on Wikipediaː a mixed-methods analysis
of #VisibleWikiWomen campaignBy *Sneh Gupta, Guru Gobind Singh Indraprastha
University*Digital gender divide (DGD) is visible in access, participation,
representation, and biases against women embedded in Wikipedia, the largest
digital reservoir of co-created content. This article examined the content
of #VisibleWikiWomen, a global digital advocacy campaign aimed at
encouraging inclusion of women voices in the global technology conversation
and improving digital sustainability of feminist data on Wikipedia. In a
mixed-methods study, Sentiment Analysis followed by a Feminist Critical
Discourse Analysis of the campaign tweets reveals how digital gender divide
manifested in the public response. An overwhelming majority of tweets
expressed positive sentiment towards the objective of the campaign. An
inductive reading of the coded tweets (n = 1067) generated five themes:
Feminist Activism, Invisibility & Marginalization of Women, Technology for
Women Empowerment, Gendered Knowledge Inequity, and Power Dynamics in the
Digital Sphere. Twitter discourse presented many agitated digital users
calling out the epistemic injustice on Wikipedia that goes beyond the
invisibility of women. Their tweets reveal that they want an equal social
platform inclusive of women of color and varied identities currently absent
in the Wikipedia universe. Extracting ideas, values, and themes from new
media campaigns holds unparalleled potential in the diffusion of
interventions and messages on a larger scale.
- Paperː Gupta, S., & Trehan, K. (2022). Twitter reacts to absence of
women on Wikipedia: a mixed-methods analysis of #VisibleWikiWomen campaign.
Media Asia, 49(2), 130-154.
<https://www.researchgate.net/publication/356909618_Twitter_reacts_to_absenc…>
Warm regards,
Emily
--
Emily Lescak (she / her)
Senior Research Community Officer
The Wikimedia Foundation
Hello!
We will soon deploy some fixes for date parsing that especially affect
Czech and possibly other languages as well.
Wikidata’s parsing of dates in the Czech language has long been affected by
some issues (T221097 <https://phabricator.wikimedia.org/T221097>), where
some reasonable representations couldn’t be parsed (e.g. 01.02.2023), while
others were parsed incorrectly: for example, 11.12.2023 (11 December 2023)
was parsed as 12 November 2023, and 07.05.1997 (7 May 1997) bizarrely
became 30 June 1997.
Matěj Suchánek <https://www.wikidata.org/wiki/User:Mat%C4%9Bj_Such%C3%A1nek>
has investigated these errors and implemented a solution, which will be
deployed on February 15. As far as we can tell, all the changes it produces
are positive: that is, if the way a date is parsed changes, then the old
behavior was bad, and the change is an improvement. Nevertheless, it’s
possible that some users expected the old behavior, or that some external
programs might even be broken by the change. Users who add time data to
Wikidata should make sure that the date shown to them as a result of their
edit is correct. If you want to test the behavior changes, the new code is
already live on Beta Wikidata.
We are currently looking into other languages that may be affected as well.
If you have any questions or want to provide feedback please leave us a
comment on this ticket <https://phabricator.wikimedia.org/T221097>.
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.
Call for Participation at the First International Biochemical Knowledge
Extraction Challenge (BiKE2023)
ESWC 2023, May 28th to June 1st, 2023 in Hersonissos, Greece
https:// <https://project-hobbit.eu/challenges/qald2017/>aksw.github.io/bike
Most of the structured biochemical information available on the Web today
is manually curated, and it is practically impossible to keep pace with the
research being constantly published in scientific articles.
Within this challenge, we want to speed up and promote research on
automatic biochemical knowledge extraction mechanisms with the aim of
increasing the information available on natural products to promote the
development of environmental-friendly products while increasing awareness
of the biodiversity value.
We invite researchers to participate by re-using or designing new
innovative Biochemical Extraction methods. The participants will have the
opportunity to present, discuss and display their system at the BiKE
workshop.
The challenge consists of extracting relevant information matching a given
ontology.
#Pre-registration
Pre-registrations can be performed through the online form:
https://forms.gle/2sMUUondkULRwnE66
#Submission
Every competing approach should submit a 12 pages article describing the
method in the style of the Springer Publications format for Lecture Notes
in Computer Science (LNCS). For further instructions, you can check the
Springer Conference Proceeding templates at Springer submission guidelines (
https://www.springer.com/de/it-informatik/lncs/conference-proceedings-guide…
).
Papers should be submitted through the EasyChair system (
https://easychair.org/conferences/?conf=bike2023). Submissions will be
reviewed by members of the challenge program committee. Papers will be
evaluated according to their significance, originality, technical content,
style, clarity, and relevance to the challenge. The complete set of papers
will be published with the Tex2KG Workshop CEUR Proceedings (CEUR-WS.org),
listed by the DBLP.
#Awards
The first, second, and third best biochemical knowledge extraction methods
are going to be awarded as follows:
- First Place: EUR 1000
- Second Place: EUR 500
- Third Place: EUR 250
#Preliminary Schedule
- Release of training data and instructions: January 20th, 2023 PST
- Result submission deadline: April 27th, 2023 PST
- Release of test dataset & results: May 22th, 2023 PST
- Paper submission deadline: May 27th, 2023 PST
- Notification & Reviews: Jun 15th, 2023 PST
- Submission of camera-ready papers: Jun 27th, 2023 PST
#QA
Questions can be addressed directly in our QA Slack channel
https://chemnet.slack.com/archives/C04QZ77BS2K
Hi all,
I'm hoping to compare a local (my wikibase) property to its remote (wikidata) counterpart, as part of a quality control project. I'm struggling with what may be basic plumbing. Query below. I suspect my error is in the #commented out section. Can someone share a boilerplate wikidata SERVICE example?
Many thanks,
Michael Lindsey
UC Berkeley School of Law
PREFIX ira:<https://ir-authorities.wikibase.cloud/entity/>
PREFIX irp:<https://ir-authorities.wikibase.cloud/prop/direct/>
select ?person ?localLCN ?remoteLCN {
?person irp:P20 ira:Q174;
irp:P2 ?wikidataQNumber;
irp:P8 ?localLCN.
#SERVICE <http://query.wikidata.org/sparql> {
# wd:?wikidataQNumber wd:P244 ?remoteLCN.
#}
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
