Wikidata February 2021

wikidata@lists.wikimedia.org

40 participants
37 discussions

Guidelines for entering label in various languages, e.g. Chinese
by j s 21 Feb '21

21 Feb '21

Hi, I was alerted that there are many properties without a label in zh-Hant <https://www.wikidata.org/w/index.php?search=-haslabel%3Azh-hant&title=Speci…>. When I reviewed the search result, I was surprised to see Chinese traditional (zh-Hant) and simplified scripts (zh-Hans) were both recorded under the lable Chinese (zh). Does anyone know if there are guidelines for entering data under different language tags, subtags for script and region? Thank you for your help. --- Jackie Shieh Descriptive Data Management Discovery Services Division LibrariesArchives.si.edu library.si.edu

2 1

Identifiers for WDQS queries
by James Heald 19 Feb '21

19 Feb '21

Dear wikidata list, One of the key things we do as Wikidata people is go round the internet, hassling people to create nice identifiers for their things, with URIs and landing-pages that we can link to. It brought me up quite short to realise that actually applies to *us* too -- there is an important thing of ours that haven't got a linkable identifier for, that it would be useful if there was a short linkable url for, and that is WDQS queries. So here's the use-case: [[User:PKM]] and I have been working with a new external project who want to build a "Gazetteer of Early Modern England and Wales" (EMEW) -- basically a historical GIS for 15th & 16th century England and Wales, able to plot things on this map: https://viaeregiae.org/index.php/map/?layers=l9001l0007 There's huge scope for collaboration with Wikidata, with deep linking both ways, as we both try to improve our coverage of C16-C17 England and Wales (expect WikiProject [[:d:WD:EMEW]] just as soon as we can get the pages made) Something that we realise we want to be able to do, from the EMEW site, is for a user to be able to give it the URL for a WDQS sparql query, for the site to send that to WDQS, get back a file of EMEW ids, and show the results on the EMEW map. Now of course that *can* be done with full WDQS query URLs. But they are horribly long and awkward. What would be much nicer would be if each time WDQS ran a query it hadn't seen before, it generated a new short identifier, that the UI would display, and which could then be used to refer to the query. So on the EMEW site, one would just put in the short identifier, that would send it to WDQS with some appropriate URL-start to show it was a request for data rather than for a link, back would come the results -- and all the user would have had to copy in was a short identifier. Of course to some extent the URL-shortener does this, but there are some issues: 1) The maintainers point-blank refuse to let it allow URLs of more than 2000 characters. ( https://phabricator.wikimedia.org/T220703 ) Gnarly WDQS queries can often be longer than this, sometimes a lot longer. 2) The short URL could be for anything on any wiki site -- the EMEW site can't be sure that it corresponds to a SPARQL query 3) The short URL needs to be adjusted, to turn it from a WDQS url that's a link to the query in the GUI into a WDQS url that's an external request for query results. This is not straightforward. A short identifier for a WDQS query would get round all these things. It also might be one step forwards towards creating a place like Quarry (https://quarry.wmflabs.org/) where users could save their queries, share them, document them, see other people's shared queries, and come back to them later. But that's another ticket (https://phabricator.wikimedia.org/T104762 open since July 2015). All I am suggesting, first, is an identifier. One objection that I thought of might be that if identifiers were automatically assigned, without having to actually request them, then people might be able to "spy" on what other queries people happened to be writing at any one time. I don't know how serious an objection this is - it doesn't seem to be a problem for Quarry - but could largely be avoided if the query-number was hashed to make the sequence less predictable. (Or alternatively, query-numbers could just be issued on request). Anyway, just putting this out here, for thoughts. Best wishes to everybody, James.

8 8

WDQS updater outage: 16 feb, 21:45 —
by Mike Pham 17 Feb '21

17 Feb '21

Hi all, As of roughly 21:45 UTC on Tues, 16 Feb 2021, Wikidata Query Service’s updater is currently experiencing an outage due to application server overload. We are currently addressing the issue, but Wikidata workflows will potentially be affected in the meantime. We will send out another message with major updates on resolution of this issue. Thanks for your patience while we get things back up and running. — Mike Pham (he/him) Sr Product Manager, Search Platform Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

Weekly Summary #455
by Mohammed Sadat Abdulai 15 Feb '21

15 Feb '21

*Here's your quick overview of what has been happening around Wikidata over the last week.* Discussions - Other: Tool ideas/ImproveWikidata <https://www.wikidata.org/wiki/User:So9q/Tool_ideas/ImproveWikidata> Events <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Events> - Past: Linked Open Storytelling - Winter School 2021 - Fellow-Programm Freies Wissen (in German) (reply on YouTube <https://www.youtube.com/watch?v=7JuqzW_zOBc&feature=youtu.be>) - Upcoming: SPARQL queries <https://www.twitch.tv/belett> live on Twitch and in French by Vigneron, February 16 at 18:00 CET - Upcoming: Bug triage hour about Lexemes <https://www.wikidata.org/wiki/Wikidata:Events#Wikidata_bug_triage_hour>, February 16 - Upcoming video: LIVE Wikidata editing #32 - YouTube <https://www.youtube.com/watch?v=BlxsQQPfrqU>, Facebook <https://www.facebook.com/groups/WikidataCommunity/permalink/289217304440118…>, February 20 - Upcoming: Online Wikidata meetup in Swedish #50 <https://www.wikidata.org/wiki/Wikidata:Events/Swedish_online_editathon#Träf…>, February 21 Press, articles, blog posts, videos <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Press_coverage> - Blog post: The promise of Wikidata: How journalists can use the crowdsourced open knowledge base as a data source <https://datajournalism.com/read/longreads/the-promise-of-wikidata>, by Monika Sengul-Jones <https://en.wikipedia.org/wiki/User:Shameran81> - Blog post: Data donation to Wikidata, part 2: country/subject dossiers of the 20th Century Press Archives <https://zbw.eu/labs/en/blog/data-donation-to-wikidata-part-2-country-subjec…> (by Joachim Neubert <https://www.wikidata.org/wiki/User:Jneubert>, ZBW Labs) - Blog post: Bibliography and Citations of Hausa Folklore <https://diff.wikimedia.org/2021/02/09/bibliography-and-citations-of-hausa-f…> by Anasskoko <https://www.wikidata.org/wiki/User:Anasskoko> - Video: Querying Linked (Wiki)data with SPARQL ✨ <https://www.youtube.com/watch?v=m50voG57yac> (presentation by Lucas Werkmeister <https://www.wikidata.org/wiki/User:Lucas_Werkmeister> at rC3, 90 minutes) - Video: Wikidata editing #31 Free Software Day - YouTube <https://www.youtube.com/watch?v=IkAirxHj-Ps>, Facebook <https://www.facebook.com/groups/WikidataCommunity/permalink/288760838819098…> - Video: Knowledge Graphs for AI: Wikidata and beyond - YouTube <https://www.youtube.com/watch?v=mTz0zSNSKEY> Tool of the week - UseAsRef script allows you to add references to statements using one external ID as source (see User:Bargioni/UseAsRef <https://www.wikidata.org/wiki/User:Bargioni/UseAsRef> and this YouTube video <https://www.youtube.com/watch?v=-3nkeqKnfTg> for more information) Other Noteworthy Stuff - Abstract Wikipedia presents prototypes of two tools that could help people to visualize, exemplify, and better guide our understanding of the coverage of lexicographic data in Wikidata <https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2021-02-10>. - Public Domain Tool <https://pro.europeana.eu/post/public-domain-tool-automating-the-calculation…>, developed by the Flemish Institute for Archives automates the process of determining whether their collection items could be in the public domain. - Sizes of country items (like "Portugal" (Q45) <https://www.wikidata.org/wiki/Q45>) were recently reduced by 30% to 50% by moving a few economics properties to "economy of"-items (sample: "economy of Portugal" (Q1649355) <https://www.wikidata.org/wiki/Q1649355>). The item "economy of Portugal" is currently larger than "Portugal". This can simplify uses of country items that previously timed-out. Infoboxes can still access the properties with the link through "economy of topic" (P8744) <https://www.wikidata.org/wiki/Property:P8744>. - Later this week, the development team will enable a rate limit for assigning new item IDs. Bots and users who successfully create items should notice no change, since the rate limit is equal to the existing limit on all edits. However, bots that often *fail* to create items may start to see different error messages than usual. This will hopefully reduce the problem of skipped item IDs. - Guidelines and compensation for UX research lead by Wikimedia Germany <https://www.mediawiki.org/wiki/WMDE_Engineering/Participate_in_UX_Activities> (announcement <https://lists.wikimedia.org/pipermail/wikidata/2021-February/014516.html> ) Did you know? - Newest properties <https://www.wikidata.org/wiki/Special:ListProperties>: - General datatypes: service status information URL <https://www.wikidata.org/wiki/Property:P9138>, first family name in Portuguese name <https://www.wikidata.org/wiki/Property:P9139>, time played <https://www.wikidata.org/wiki/Property:P9140>, coordinates of depicted place <https://www.wikidata.org/wiki/Property:P9149> - External identifiers: CompositionToday composers showcase ID <https://www.wikidata.org/wiki/Property:P9130>, Royal Museums Greenwich artwork ID <https://www.wikidata.org/wiki/Property:P9131>, Saint Louis Art Museum artwork ID <https://www.wikidata.org/wiki/Property:P9132>, AZLyrics.com song ID <https://www.wikidata.org/wiki/Property:P9133>, Studio di Fonologia Musicale RAI person ID <https://www.wikidata.org/wiki/Property:P9134>, WreckSite ID <https://www.wikidata.org/wiki/Property:P9135>, SOUNZ contributor ID <https://www.wikidata.org/wiki/Property:P9136>, Doktori.hu ID <https://www.wikidata.org/wiki/Property:P9137>, Portal da Literatura ID <https://www.wikidata.org/wiki/Property:P9141>, IPHAE ID <https://www.wikidata.org/wiki/Property:P9142>, Play:Right ID <https://www.wikidata.org/wiki/Property:P9143>, National Portrait Gallery (London) artwork ID <https://www.wikidata.org/wiki/Property:P9144>, Xinjiang Data Project identifier <https://www.wikidata.org/wiki/Property:P9145>, CITWF title ID <https://www.wikidata.org/wiki/Property:P9146>, Union Catalog of Armenian Continuing Resources ID <https://www.wikidata.org/wiki/Property:P9147>, Saxony-Anhalt cultural heritage object ID <https://www.wikidata.org/wiki/Property:P9148>, FloGrappling ID <https://www.wikidata.org/wiki/Property:P9150>, Can I use feature ID <https://www.wikidata.org/wiki/Property:P9151> - New property proposals <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Property_proposal> to review: - General datatypes: National Gallery of Art Library Bibliographic ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/National_Gallery_o…>, letterer <https://www.wikidata.org/wiki/Wikidata:Property_proposal/letterer>, set during recurring event <https://www.wikidata.org/wiki/Wikidata:Property_proposal/set_during_recurri…>, number of references <https://www.wikidata.org/wiki/Wikidata:Property_proposal/number_of_referenc…>, sensors <https://www.wikidata.org/wiki/Wikidata:Property_proposal/sensors>, Applying institution <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Applying_instituti…> - External identifiers: Lexikon Literatur in Tirol <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Lexikon_Literatur_…>, Danmarks Adresseregister named street ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Danmarks_Adressere…>, Baidu Baike ID (2) <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Baidu_Baike_ID_(2)>, Kickstarter username <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Kickstarter_userna…>, Protagonisti della storia delle scienze della mente ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Protagonisti_della…>, Curling.fi player ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Curling.fi_player_…>, RILM ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/RILM_ID>, Swiss vote ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Swiss_vote_ID>, svoyak.info player ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/svoyak.info_player…>, Germanistenverzeichnis <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Germanistenverzeic…>, Svenska Institutet i Rom ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Svenska_Institutet…>, CinemaRx title ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/CinemaRx_title_ID>, Sinemalar title ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Sinemalar_title_ID>, English Placenames MADS ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/English_Placenames…>, Armenian Book ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Armenian_Book_ID>, identifiant inventaire Occitanie <https://www.wikidata.org/wiki/Wikidata:Property_proposal/identifiant_invent…>, AaRC title ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/AaRC_title_ID>, Biblioteca Iglesia Nacional Española en Roma ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Biblioteca_Iglesia…>, BFS ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/BFS_ID>, Dizionario biografico online degli anarchici italiani ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Dizionario_biograf…>, JedeSchule.de ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/JedeSchule.de_ID>, bashenc.online ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/bashenc.online_ID>, Svoya Igra television player ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Svoya_Igra_televis…>, Wisconsin Architecture and History Inventory ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Wisconsin_Architec…> - Query examples: - Spanish Wikipedia articles about women astronauts <https://w.wiki/yQR> (Source <https://twitter.com/editatona/status/1359980994636488705>) - Websites related to works in the Women's & Gender History DH list <https://w.wiki/Com> (Source <https://twitter.com/dta_cthomas/status/1360198435715100672>) - List of states with more than one official language <https://w.wiki/ykR> (Source <https://twitter.com/belett/status/1359533946959245317>) - Location of the organizations in the Name Assigning Authority Number (NAAN) registry <https://w.wiki/yVm> (Source <https://twitter.com/BertrandCaron/status/1359094070409322496>) - List of locations named after the planned language Esperanto or its founder, L. L. Zamenhof <https://w.wiki/y$C> - Use the MediaWiki API to get the content of a Wikipedia category into a query <https://w.wiki/yAR> - Number of scholarly articles sharing their datasets <https://w.wiki/zAD> (Source <https://twitter.com/jsamwrites/status/1360556323448971271>) - Most specific taxon that includes two given species <https://w.wiki/zPN> (Source <https://twitter.com/danbri/status/1361065883280506888>) Development - Work on the Simple Query Builder continues. We finished connecting query conditions via OR (phab:T272694 <https://phabricator.wikimedia.org/T272694>). Next we will work on adding the UI for sharing the visual query via a link (phab:T272887 <https://phabricator.wikimedia.org/T272887>) - Improved the deployment process for the Query Service UI to make it easier to deploy - Fixed language code "dag" for Dagbani not working for Lemmas for Lexemes (phab:T272242 <https://phabricator.wikimedia.org/T272242>) - Fixing the bug where the Property selector is not falling back from language variant to major language for Property labels (phab:T272712 <https://phabricator.wikimedia.org/T272712>) - Adding a rate limit for creating Item IDs to avoid skipping so many due to misbehaving bots (phab:T272032 <https://phabricator.wikimedia.org/T272032>) - Fixed the case where no error was shown when trying to save a lemma with an invalid language code (phab:T265783 <https://phabricator.wikimedia.org/T265783>) - Fixed a but where merging two Lexemes fails if the source Lexeme has links to its own Senses (phab:T273830 <https://phabricator.wikimedia.org/T273830>) - Increasing the rate of edits that trigger a check by the constraint checker to 50%. This will increase the number of constraints violations that you can query in the Query Service. (phab:T204031 <https://phabricator.wikimedia.org/T204031>) - Making it possible to add interwiki links to/from Multilingual Wikisource (phab:T138332 <https://phabricator.wikimedia.org/T138332>) You can see all open tickets related to Wikidata here <https://phabricator.wikimedia.org/maniphest/query/4RotIcw5oINo/#R>. If you want to help, you can also have a look at the tasks needing a volunteer <https://phabricator.wikimedia.org/project/board/71/query/zfiRgTnZF7zu/?filt…>. Monthly Tasks - Add labels, in your own language(s), for the new properties listed above. - Comment on property proposals: all open proposals <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Overview> - Contribute to a Showcase item <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Showcase_items> . - Help translate <https://www.wikidata.org/wiki/Special:LanguageStats> or proofread the interface and documentation pages, in your own language! - Help merge identical items <https://www.wikidata.org/wiki/User:Pasleim/projectmerge> across Wikimedia projects. - Help write the next summary! <https://www.wikidata.org/wiki/Wikidata:Status_updates/Next> -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de

1 0

Guidelines and compensation for UX research lead by Wikimedia Germany
by Léa Lacroix 15 Feb '21

15 Feb '21

Hello all, As you may know, the User Experience team in Wikimedia Germany’s software department regularly conducts user research, surveys and interviews for the projects we develop: not only Wikidata’s software and infrastructure, but also the German Wikipedia’s Technical Wishes project. Starting in February 2021, we will be making some improvements in our UX research processes; we’ve documented the details on this page <https://www.mediawiki.org/wiki/WMDE_Engineering/Participate_in_UX_Activities>. This includes the details and conditions for the how and why of participating in UX research, our technical and language requirements, and of the nominal compensation we provide to people who participate in research that requires significant time and involvement from its participants. By offering compensation, common practice in the UX research field, we hope to achieve more diversity among participants and to open participation to people who cannot easily dedicate time in addition to their volunteer activities. Compensation will be optional, in the form of a gift card whose value of which will vary depending on the participant’s country. It applies only to specific types of activity (long interviews and surveys organized by our UX researchers) and does not include informal discussions online or offline nor giving feedback on mockups and new features. You can read more details about how we plan to implement this compensation here <https://www.mediawiki.org/wiki/WMDE_Engineering/Participate_in_UX_Activitie…>. We have tried to be as transparent as possible, while retaining some flexibility if you have any questions, or if you find something unclear, feel free to reach out to us on this talk page <https://www.mediawiki.org/wiki/Talk:WMDE_Engineering/Participate_in_UX_Acti…> . Cheers, -- Léa Lacroix Community Engagement Coordinator Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

Gregorian/Julian dates QuickStatements
by Olaf Simons 15 Feb '21

15 Feb '21

Dear Wikidata people, I am trying to find out whether QuickStatements has found a way to define Julian/Gregorian markers on dates. We have massive lists of dates for German and English territories after 1582 that are on the Julian calendar since they come from Protestant or Eastern Orthodox calendars that switch to Gregorian far later. Is there a way to mark the proper calendar on a QuickStatement input - which we could easily do with a look at our varius sources. Best wishes, Olaf Dr. Olaf Simons Forschungszentrum Gotha der Universität Erfurt Am Schlossberg 2 99867 Gotha Büro: +49-361-737-1722 Mobil: +49-179-5196880 Privat: Hauptmarkt 17b/ 99867 Gotha

4 4

Universal Code of Conduct - a survey to hear your voice
by Sannita WMF 11 Feb '21

11 Feb '21

Hi all, Again a brief update about the ongoing consultation about the Universal Code of Conduct. Firstly, the third round of questions is on: https://www.wikidata.org/wiki/Wikidata_talk:Universal_Code_of_Conduct_consu… Again the topic will be reporting, but this time from other (and conflicting) points of view, such as the potential violation of the UCoC from somebody "with authority" inside the project, or the potential slandering of innocent users by someone who falsely accuses them of an alleged violation. Secondly, there is now also an online survey! You can find it here: https://forms.gle/FhP1E9RFKBm7eRCAA The survey will go on until the end of this consultation (meaning, until the end of the month), but please consider taking some of your time now to answer it. The survey is completely anonymous, in order to help you write, ehr, speak up your mind more freely. :) As always, I'm here for any clarification needed or for any idea, feedback, whatever comes to your mind, also privately. Cheers, Luca "Sannita" Martinelli Universal Code of Conduct facilitator for Wikidata

1 0

Fwd: [Abstract-wikipedia] Newsletter #18: Two prototype tools to visualize lexicographic coverage in Wikidata
by Lydia Pintscher 11 Feb '21

11 Feb '21

Hi everyone :) Forwarding this message from Denny as this is very relevant for our work on lexicographical data in Wikidata and helping us understand where the gabs are and how to fill them best. Cheers Lydia ---------- Forwarded message --------- From: Denny Vrandečić <dvrandecic(a)wikimedia.org> Date: Wed, Feb 10, 2021 at 11:38 PM Subject: [Abstract-wikipedia] Newsletter #18: Two prototype tools to visualize lexicographic coverage in Wikidata To: Abstract Wikipedia list <abstract-wikipedia(a)lists.wikimedia.org> The on-wiki version of this newsletter is here: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Updates/2021-02-10 The goal of Abstract Wikipedia is to generate natural language texts from an abstract representation of the content to be represented. In order to do so, we will use lexicographic data from Wikidata. And although we are quite far from being able to generate texts, one thing that we want to encourage everyone’s help with is the coverage and completeness of the lexicographic data in Wikidata. Today we want to present prototypes of two tools that could help people to visualize, exemplify, and better guide our understanding of the coverage of lexicographic data in Wikidata. Annotation interface The first prototype is an annotation interface that allows users to annotate sentences in any language, associating each word or expression with a Lexeme from Wikidata, including picking its Form and Sense. You can see an example in the screenshot below. Each ‘word’ of the sentence here is annotated with a Lexeme (the Lexeme ID L31818 <https://www.wikidata.org/wiki/Lexeme:L31818> is given just under the word), followed by the lemma, the language, and the part of speech. Then comes, if selected, the specific Form that is being used in context - for example, on ‘dignity’ we see the Form ID L31818#F1, which is the singular Form of the Lexeme. Lastly, comes the Sense, which is assigned Sense ID L31818#S1 and defined by a gloss. At any time, you can remove any of the annotations, or add new annotations. Some of the options will take you directly to Wikidata. For example, if you want to add a Sense to a given Lexeme, because it has no Senses or is missing the one you need, it will take you to Wikidata and let you do that there in the normal fashion. Once added there, you can come back and select the newly added Sense. The user interface of the prototype is a bit slow, so please give it a few seconds when you initiate an action. It should work out of the box in different languages. The Universal Language Selector is available (at the top of the page), which you can use to change the language. Note that glosses of Senses are frequently only available in the language of the Lexeme, and the UI doesn’t yet do language fallback, so if you look at English sentences with a German UI you might often find missing glosses. Technologically, this is a prototype entirely implemented in JavaScript and CSS on top of a vanilla MediaWiki installation. This is likely not the best possible technical solution for such a system, but should help to determine if there is any user-interest in the tool, for a potential reimplementation. Also, it would be a fascinating task to agree on an API which can be implemented by other groups to provide the selection of Lexemes, Senses, and Forms for input sentences. The current baseline here is extremely simple, and would not be good enough for an automated tagging system. Having this available for many sentences in many languages could provide a great corpus for training natural language understanding systems. There is a lot that could be built upon that. The goal of this prototype is to make more tangible the Wikidata community's progress regarding the coverage of the lexicographical data. You can take a sentence in any written language, put it into this system, and find out how complete you can get with your annotations. It's a way to showcase and create anecdotal experience of the lexicographic data in Wikidata. The prototype annotation interface is at: http://annotation.wmcloud.org/ You can discuss it here: https://annotation.wmcloud.org/wiki/Discussion (You will need to create a new account - if you have time to set this up with SUL, drop me a line) Corpus coverage dashboard The second prototype tool is a dashboard that shows the coverage of the data compared to a corpus in each of forty languages. Last year, whilst in my previous position at Google Research, I co-authored a publication where we built and published language models out of the cleaned-up text of about forty Wikipedia language editions [1]. Besides the language models, we also published the raw data: this text has been cleaned up by the pre-processing system that Google uses on Wikipedia text in order to integrate the text in several of its features. So while this dataset consists of relatively clean natural language text; certainly, compared to the raw wiki text — it still contains plenty of artefacts. If you know of better large scale encyclopedic text corpora we can use, maybe better cleaned-up versions of Wikipedia, or ones covering more languages, please let us know <https://phabricator.wikimedia.org/T273221>. We extracted these texts from the TensorFlow models <https://www.tensorflow.org/datasets/catalog/wiki40b>. We provide the extracted texts for download <https://drive.google.com/drive/folders/1HfL138UCqr69w0XfAhlAEUh6VVOnzwBE> (a task <https://phabricator.wikimedia.org/T274208> to move it to Wikimedia servers is underway). We split the text into tokens and count the occurrences of words, and compared how many of these tokens appear in the Forms on Lexemes of the given language in Wikidata’s lexicographic data. If this proves useful, we could move the cleaned-up text to a more permanent home. A screenshot of the current state for English is given here: we see how many Forms for this language are available in Wikidata, and we see how many different Forms are attested in Wikipedia (i.e., how many different words, or word types, are in the Wikipedia of the given language). The number of tokens is the total number of words in the given language corpus. Covered forms says how many of the forms in the corpus are also in Wikidata's Lexeme set, and covered tokens tells us how many of the occurrences that covers (so, if the word ‘time’ appears 100 times in English Wikipedia, it would be counted as one covered form, but 100 covered tokens). The two pie charts visualize the coverage of forms and tokens respectively. Finally, there is a link to the thousand most frequent forms that are not yet in Wikidata. This can help communities prioritise ramping up coverage quickly. Note though, the progress report is manual and does not automatically update. I plan to run an update from time to time for now. The prototype corpus coverage dashboard is at: https://www.wikidata.org/wiki/Wikidata:Lexicographical_coverage You can discuss it here: https://www.wikidata.org/wiki/Wikidata_talk:Lexicographical_coverage Help wanted Both prototype tools are exactly that: prototypes, not real products. We have not committed to supporting and developing these prototypes further. At the same time, all of the code and data is of course open sourced. If anyone would like to pick up the development or maintenance of these prototypes, you would be more than welcome – please let us know (on my talk page <https://meta.wikimedia.org/wiki/User_talk:DVrandecic_(WMF)>, or via e-mail, or on the Tool ideas page <https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Ideas_of_tools> ). Also, if someone likes the idea but thinks that a different implementation would be better, please move ahead with that – I am happy to support and talk with you. There is much to improve here, but we hope that these two prototypes will lead to more development of content and tools <https://www.wikidata.org/wiki/Wikidata:Tools/Lexicographical_data> in the space of lexicographic data. [1] Mandy Guo, Zihang Dai, Denny Vrandečić, Rami Al-Rfou: Wiki-40B: Multilingual Language Model Dataset, LREC 2020, https://www.aclweb.org/anthology/2020.lrec-1.297/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

Invitation to apply to Outreachy and Google Summer of Code program with Wikimedia!
by Gopa Vasanth 11 Feb '21

11 Feb '21

(feel free to forward the message as is to your friends, family members & colleagues) Hello folks, We would like to invite you to apply to the Outreachy and Google Summer of Code program with the Wikimedia Foundation (a non-profit organization behind Wikipedia)! About the Outreachy program Wikimedia will be mentoring ~3 projects in the Outreachy program in the May to August 2021 round. The initial applications are due February 22nd at 4 pm UTC. Apply today: https://www.outreachy.org/apply/ [1] Outreachy offers three-month internships to work remotely in Free and Open Source Software (FOSS) projects with experienced mentors. The internships may include programming, user experience, documentation, illustration, and graphic design, or data science. Outreachy internships run twice a year – from May to August and December to March. Interns are paid a stipend of $5,500 USD for the three months of work. They also have a $500 USD stipend to travel to conferences and events. Interns often find employment after their internship with Outreachy sponsors or in jobs that use the skills they learned during their internship. Outreachy is open to both students and non-students. Outreachy expressly invites the following people to apply: - Women (both cis and trans), trans men, and genderqueer people. - Anyone who faces under-representation, systematic bias, or discrimination in the technology industry in their country of residence is invited to apply. - Residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. About the Google Summer of Code program Wikimedia is planning to mentor 8-10 projects in 2021’s Google Summer of Code (GSoC) program. Beginning March 9th, pending Wikimedia’s acceptance as a mentoring organization, applicants can begin discussing ideas with the mentors! The student application will be due on April 13, 2021: https://summerofcode.withgoogle.com/ [2] Google Summer of Code, now in its 17th year, is Google's summer program for candidates participating in any academic programs who want to get involved in open-source software. Over 6,626 students from 121 countries have already participated in the last year’s round i.e 2020 < https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis…> [3]. Google Summer of Code is a unique program that pairs students with mentors who introduce them to the open-source community and provide guidance while they work on real-world open-source projects during their summer break from university. This year there are some new breaking changes in the GSoC program, including: - Smaller project size ~175 hr project (previously 350 hr) - Shortened coding period ~10 weeks long (previously 3 months) - Eligibility criteria redefined; the program is now open to candidates participating in a variety of academic programs (previously accredited university programs only) Projects cover a wide range of fields including Cloud, Operating Systems, Graphics, Medicine, Programming Languages, Robotics, Science, Security and many more. It's a highly competitive program (and this year is expected to be even bigger than last year), so don't wait until the last minute to prepare! About the Wikimedia Foundation The Wikimedia Foundation is the nonprofit organization that hosts and operates Wikipedia and the other Wikimedia free knowledge projects. Our vision is a world in which every single human can freely share in the sum of all knowledge. We believe that everyone has the potential to contribute something to our shared knowledge and that everyone should be able to access that knowledge, free of interference. We host the Wikimedia projects, build software experiences for reading, contributing, and sharing Wikimedia content, support the volunteer communities and partners who make Wikimedia possible, and advocate for policies that enable Wikimedia and free knowledge to thrive. Resources * Browse through the participants’ guides, to learn more about the application process steps: <https://www.mediawiki.org/wiki/Outreachy/Participants> [4] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants> [5] * All the projects will be showcased here: <https://www.outreachy.org/communities/cfp/wikimedia/> [6] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021> [7] We hope you will help us spread the word about Wikimedia’s participation in these programs (by sharing this email) Looking forward to your participation! Cheers, Gopa, Srishti, Pavithra, Ankit & Mahveotm (Wikimedia organization administrators for GSoC & Outreachy) [1] https://www.outreachy.org/apply/ [2] https://summerofcode.withgoogle.com/ [3] https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis… [4] https://www.mediawiki.org/wiki/Outreachy/Participants [5] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants [6] https://www.outreachy.org/communities/cfp/wikimedia/ [7] https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021 -- Regards Gopa Vasanth <https://www.mediawiki.org/wiki/User:Gopavasanth> Amrita Vishwa Vidyapeetham <http://www.amrita.edu/> | Blog <https://gopavasanth.wordpress.com/> amFOSS <https://amfoss.in/@gopavasanth> | GitHub <https://github.com/gopavasanth> | Gerrit <https://gerrit.wikimedia.org/r/#/q/gopavasanth> “Yesterday is not ours to recover, but tomorrow is ours to win or lose.”

1 0

Open Call for Project Grants Jan 11 - Feb 10, 2021
by Rupika Sharma 10 Feb '21

10 Feb '21

Hello everyone, Hope this email finds you well. Crossposting this notification from Wikimedia L. This is a gentle reminder about the Project Grants Program open call that started on January 11, with the submission deadline of February 10, 2021. <https://meta.wikimedia.org/wiki/Grants:Project>. This first open call will be focussed on Community Organizing proposals. A second open call focused on research and software proposals is scheduled from February 15 with a submission deadline of March 16, 2021. For the Round 1 open call, we invite you to propose grant applications that fall under community development and organizing (offline and online) categories. Project Grant funds are available to support individuals, groups, and organizations to implement new experiments and proven ideas, from organizing a better process on your wiki, coordinating a campaign or editathon series to providing other support for community building. We offer the following resources to help you plan your project and complete a grant proposal: Weekly proposals clinics via Hangouts during the Open Call Join us for real-time discussions with Program Officers and select thematic experts and get live feedback about your Project Grants proposal. We’ll answer questions and help you make your proposal better. < https://meta.wikimedia.org/wiki/Grants:Project#Upcoming_Proposal_Clinics <https://meet.google.com/linkredirect?authuser=6&dest=https%3A%2F%2Fmeta.wik…> > You can join the different proposal clinics on the following dates: General Proposal Clinics - Monday, February 8, 2021 at 5:00 PM UTC - Videoconference link <https://wikimedia.zoom.us/j/2195984855> - Wednesday, February 10, 2021 at 3:00 PM UTC - Videoconference link <https://wikimedia.zoom.us/j/2195984855> GLAM-themed Proposal Clinics - Monday, January 25, 2021 at 4:30 PM UTC - Videoconference link <https://wikimedia.zoom.us/j/99588568064> - Tuesday, January 26, 2021 at 9:30 AM UTC - Videoconference link <https://wikimedia.zoom.us/j/91745569202> Campaign-themed Proposal Clinics - Tuesday, January 26, 3:00 PM UTC - Videoconference link <https://wikimedia.zoom.us/j/99588568064> - Thursday, February 4, 8:30 PM UTC - Videoconference link <https://wikimedia.zoom.us/j/99588568064> We also offer these support pages to help you build your proposal: * Video tutorials for writing a strong application: <https://meta.wikimedia.org/wiki/Grants:Project/Tutorial> * General planning page for Project Grants: < https://meta.wikimedia.org/wiki/Grants:Project/Plan> * Program guidelines and criteria: <https://meta.wikimedia.org/wiki/Grants:Project/Learn> Program officers are also available to offer individualized proposal support upon request. Contact us at projectgrants(a)wikimedia.org if you would like feedback or more information. We are excited to see your grant ideas that will support our community and make an impact on the future of Wikimedia projects. Put your idea into motion, and submit your proposal by February 10, 2021! < https://meta.wikimedia.org/wiki/Grants:Project/Apply> Please feel free to get in touch with questions about getting started with your grant application, or about serving on the Project Grants Committee. Contact us at projectgrants(a)wikimedia.org. Please check more about the changes introduced in the Project Grants program in the forwarded email below. Best regards, Rupika *Rupika Sharma* Junior Program Officer Wikimedia Foundation Grants Wikimedia Foundation <https://wikimediafoundation.org/> [1] https://meta.wikimedia.org/wiki/Grants:Project [2] https://meta.wikimedia.org/wiki/Grants:Project#Upcoming_events [3] https://meta.wikimedia.org/wiki/Grants:Project/Tutorial [4] https://meta.wikimedia.org/wiki/Grants:Project/Plan [5] https://meta.wikimedia.org/wiki/Grants:Project/Learn > > On Wed, 23 Dec 2020 at 09:54, Marti Johnson <mjohnson(a)wikimedia.org> >> wrote: >> >> Hello Wikimedians, >> >> I’m writing to announce the next opportunity for funding through the >> Project Grants program, and to share changes in how review will happen in >> the coming year and beyond. >> >> Background context: >> >> Over the past few months, the Wikimedia Foundation has begun work on a >> new strategy for how we will structure our grants programs in the future, >> with the goal of aligning more closely with the Wikimedia Movement’s 2030 >> Strategic Direction [1]. We’ve been having conversations with many >> stakeholders in the Wikimedia community and we’re in the process of >> brainstorming about possible frameworks to improve how we make grants. This >> coming year, 2021, will be an experimental year in which we will pilot some >> smaller changes as we move toward a larger redesign process later in the >> year and beyond. >> >> How do I learn more about applying for project funding through Project >> Grants? >> >> - >> >> You can learn more about the guidelines for the Project Grants >> program here: https://meta.wikimedia.org/wiki/Grants:Project/Learn >> - >> >> You can learn more about how to plan for a project proposal here: >> https://meta.wikimedia.org/wiki/Grants:Project/Plan >> - >> >> You can learn about how to apply here: >> https://meta.wikimedia.org/wiki/Grants:Project/Apply >> >> >> What will change in the grant review process for Project Grants in 2021? >> >> - >> >> In previous rounds, all Project Grant proposals have been reviewed in >> one round, inclusive of proposals related to four themes: research, >> software, and online and offline community organizing. In 2021, we will >> experiment with offering two separate and dedicated rounds. One will be >> focused on online and offline community organizing. A second round will >> focus on review of research and software grant proposals. >> - >> >> By offering separate, dedicated rounds, we hope to offer more >> tailored support for applicants, with better integration with staff in the >> Wikimedia Foundation who have relevant expertise, and with more focused >> Committee recruitment to improve the quality of proposal review. We also >> hope it will reduce the burden on volunteer committee reviewers in any >> given round. >> >> >> When will community organizing grant proposals be accepted? >> >> - >> >> The open call will launch January 11, and the submission deadline is >> February 10, 2021. >> - >> >> The full schedule is posted here: >> https://meta.wikimedia.org/wiki/Grants:Project >> >> >> When will software and research grant proposals be accepted in 2021? >> >> - >> >> The open call will launch February 15, and the submission deadline is >> March 16, 2021. >> - >> >> The full schedule is posted here: >> https://meta.wikimedia.org/wiki/Grants:Project >> >> >> How will this affect currently funded Project Grants? >> >> - >> >> Our intention is to make sure that current projects will not be >> interrupted by this change, both with regard to current or planned work. >> >> >> Will there be other changes coming in the future? >> >> - >> >> After these rounds, we expect bigger changes for Project Grants. >> - >> >> We are currently in a strategic design process and have been actively >> engaging many stakeholders from around the world to help us think about >> what these changes should look like. >> - >> >> Once we have draft frameworks ready, there will be opportunities for >> feedback from Wikimedia community members before any decisions are >> finalized. We will keep you updated! >> >> >> Please let us know if you have any questions about these changes or if >> you would like to learn more about how to get involved in the strategic >> redesign process for Project Grants. >> >> Warm regards, >> >> Marti >> >> [1] <https://meta.wikimedia.org/wiki/Wikimedia_2030> >> >> *Marti Johnson* >> >> *Pronouns: she/her/hersProgram Officer* >> *Individual Grants* >> *Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>* >> *1 Montgomery, Ste. 1600* >> *San Francisco, CA 94104* >> +1 415-839-6885 >> Skype: Mjohnson_WMF >> >> Imagine a world in which every single human being can freely share in the >> sum of all knowledge. Help us make it a reality! >> Support Wikimedia >> <https://donate.wikimedia.org/> >> _______________________________________________ >> Wikimedia-l mailing list, guidelines at: >> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and >> https://meta.wikimedia.org/wiki/Wikimedia-l >> New messages to: Wikimedia-l(a)lists.wikimedia.org >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, >> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> >> >

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata February 2021