Jump to content

User talk:MartinPoulter/Archive 30

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 25←Archive 28Archive 29Archive 30Archive 31Archive 32→Archive 35

Wikidata weekly summary #553

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, 17:00 UTC on Wednesday, 18th January 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they 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.
    • Ongoing
      • Weekly Lexemes Challenge #74, Urology
  • Tool of the week
    • OWL Map - a tool to help in linking Wikidata items with the matching object on OpenStreetMap.
  • Development
    • The development team took a break during the winter holidays and as a result, no development occurred.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

epistemology

Hi Martin, "How we know what we know" could become "How knowledge is verified" good change? Electricmic (talk) 13:06, 24 December 2022 (UTC)

@Electricmic: Please do not edit war. If it is so important to you to make a change, get consensus for it on the Talk page of the article. For Wikipedia's policy on first-person language, see WP:FIRSTPERSON. I think succinct is better. Epistemology is not purely defined by "how knowledge is verified" so that would be a factually incorrect statement to put in the article. I see that you're trying to give writing a lighter tone, and I agree that this is something Wikipedia needs in general, but the changes you are proposing for this particular sentence aren't improvements. MartinPoulter (talk) 13:20, 24 December 2022 (UTC)
Thanks for acknowledging my good faith, and for your specific critique of what you found unuseful about my edit and for your useful direction on how to proceed Electricmic (talk) 11:12, 4 January 2023 (UTC)

Your email - GA, FA etc

Hi Martin, I think my thoughts on this are unchanged, though I don't do as much FA reviewing as I used to, nor often look at GA noms. I imagine the waits there are as long as ever. Peer review often gets few comments, but at least you've asked. All the best for the NY (sorry for the delay, I've been away for NY). Johnbod (talk) 13:13, 9 January 2023 (UTC)

Wikidata weekly summary #554

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call January 10, 2023: Egon Willighagen will be introducing us to SARS-CoV-2 queries, a well-documented series of Wikidata queries around the SARS-CoV-2 virus and the pandemic. This work contributes to Wikiproject COVID-19 and documentation is currently available in Japanese, Dutch, Spanish, and Portuguese. Agenda
      • Talk to the Search Platform / Query Service Team—January 11, 2023. Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CET
      • The full version of View it! Tool is out! The new user script uses structured data to display related media in any Wikimedia content pages—including Wikidata items—in an on-wiki image panel or gallery view. Please join the public launch and demo of the full version of this new tool on Thursday, January 12th, 5:00 UTC via Zoom (Meeting ID: 160 454 5329) to learn more and discuss forthcoming editing features.
      • The next Wikidata+Wikibase office hours will take place on Wednesday, 17:00 UTC on Wednesday, 18th January 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they 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.
      • About 2 months left to register for the first digital@IANLS workshop: Learn the basics of Wikidata and how to use it in your Neo-Latin research. Event is online, free, and open to all. More info on event and registration.
    • Ongoing
      • Weekly Lexemes Challenge #75, Tools
  • Tool of the week
    • Web Hub allows users to navigate between origin and destination on the web using information from Wikidata, primarily on Wikimedia sites.
  • Development
    • REST API: Preparing the first release to test.wikidata.org on January 17th and to Wikidata on January 24th
    • Entity Schemas: Continuing to investigate and prototype technical approaches for version 2
    • Mismatch Finder: Working on giving mismatch providers access to the reviews of the mismatches they uploaded (phab:T304794)
    • Investigated how to best do language switching for the Query Builder and Mismatch Finder. So far they only support it by specifying the language via a URL parameter and not yet via the UI (phab:T324653)
    • Query Service:
      • Lexeme IDs now have tooltips so you can see the Lemma in the SPARQL code, similar as for Items and Properties (phab:T255245)
      • Fixed a bug where the y-axis label on a graph were misaligned and hard to read (phab:T325808)
    • Lexicographical data:
      • Statements linking to a Sense now also show the language of the Lexeme to make it easier to see for example which language a translation statement refers to (phab:T207392)
      • Fixed a bug in the language dropdown on Special:NewLexeme (phab:T324743)
      • The Lemma of a Lexeme is now shown in the title of the revision history of the Lexeme as well (phab:T312660)
    • Vector 2022 theme: worked on making the search on Wikidata work in this new theme. You can test it on test.wikidata.org now and next week on Wikidata. (phab:T316093)
    • mul language code:
      • Continued investigation around how to handle language fallbacks on mobile, which is a blocker for adding this language code (phab:T323098)
      • Preventing the addition of descriptions for mul (phab:T313027)
    • Constraint violations: Working on also showing them to non-logged in users (phab:T272132)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #555

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Vector 2020 skin: the search that works properly with Wikidata has been deployed
    • Entity Schemas: Making progress on the proof of concept that will help us figure out the technical way forward
    • REST API: getting ready to deploy the first version to test.wikidata.org on February 17th
    • Lexicographical data: When linking to a Sense in a statement the language of the Lexeme for that Sense is now also shown. This makes it easier to understand translation statements for example (phab:T207392)
    • Constraints: Constraint violations are now also shown to logged out users (phab:T272132)
    • Fixing a regression where Wikipedia and co are no longer notified about a disconnected sitelink when the Item that contains the sitelink is deleted (phab:T326082)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #556

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call January 24, 2023: We will be discussing plans for 2023, and requesting feedback and ideas for future programming. Based on a previous recommendation to host a discussion on advocacy for Wikidata within libraries, we will introduce and provide time to complete a short survey to foster conversation in a future Group Call. Please come ready to share your thoughts Agenda
      • Introductions to Wikidata, online meetings organized by Wikimedia Australia on January 25, 26 and 31
  • Development
    • Wikibase REST API: The new API is now available for testing on Test.Wikidata
    • Ontology issues: We finalized and published the survey to better understand which types of ontology issues are most problematic for reusers of our data.
    • Wikipedia and co: Fixing a regression where there is no entry in recent changes and watchlist when an Item is deleted that was connected to an article on that wiki (phab:T326082)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #557

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • A citation hunt program was organized for secondary school students at IIS School in Dubai as part of the 74th Republic Day celebration of India. 16 students participated, with different mother tongues and from different states of India living as expatriates in Dubai. The goal was to increase references for Wikidata statements based on research. The students were introduced to the importance of protecting India's history on the internet, and were taught how to edit Wikipedia and Wikidata. They were given a special event page on Wikidata with instructions and a list of Wikidata items to add citations to, and they searched for references in their textbooks and search engines to add to the Wikidata items.More details are given here.
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group Working Hour January 30, 2023: The #1Lib1Ref campaign is afoot, so we will be working on adding references to Wikidata statements. We'll have some data for you to work with, but you're welcome to bring your own. We'll be mainly working with adding webpages as sources, but if you want to get experience using books or articles as sources, we recommend bringing some to the session to use as references for Wikidata items you have identified. You are, as always, welcome to bring your own project to work on Event page
  • Tool of the week
    • theyrule.net is a website that helps to explore the boardroom connections of the largest US companies.
  • Development
    • Wikibase REST API: The first version of the new API is released on Wikidata now \o/ We'd love to hear your feedback on what to improve next in the API.
    • Property Suggester: We updated the data for the Property Suggester so suggestions for new statements to add to an Item should be more in line with current Property usage on other similar Items again.
    • Fixed an issue with Item deletions not showing up on Wikipedia and co if they affect an article on that wiki (phab:T326082)
    • Vector 2022: Made it possible to add a new sitelink on Wikipedia and co in the new Vector 2022 language selector (phab:T310259)
    • Lua: Working on two new Lua functions, getDescriptionByLang (phab:T230839) and getBadges (phab:T305378)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #558

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Let's Quiz is a game that generates random quizzes to test your knowledge & learn something new every day.
    • User:Nikki/AddTermboxLanguage.js - makes it easier to add/edit labels to an item in a language other than the ones shown by default.
  • Development
    • REST API: adding a new GET /entities/items/{item_id}/descriptions endpoint (phab:T327881)
    • Lua: added two Lua functions, getDescriptionByLang (phab:T230839) and getBadges (phab:T305378) that make it easier to get this data on Wikipedia and co
    • Lexicographical data: added documentation for the WikibaseLexeme JSON structure (phab:T201489)
    • Action API: fixed a bug that prevented the wblistentityusage API module from being used as a generator (phab:T254334)
    • Dates: working together with Matěj Suchánek to fix date parsing issues in Czech (phab:T221097)
    • Constraints: working on showing constraint clarification messages to make it easier to understand why a constraint violation is happening and how to fix it (phab:T219037)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #559

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • CJMbot (CJMbot lets users upload a CSV file in a certain format. The data inside this file is then validated and processed. New items wil be created based on the data in the CSV file and existing items wil updated by adding statements and references).
      • RPI2026F1Bot 5 Task/s: Import dependency and version data from PyPi
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikibase Working Hour February 13, 2023. The February Working Hour will feature a presentation by Steve Baskauf on using VanderBot with Wikibase: The Wikibase API provides a mechanism for programmatic control of uploads, and its behavior is consistent across instances (Wikidata, Structured Data in Commons, and those that are established privately). In this session, Steve will discuss basic interactions with the API and demonstrate using the VanderBot Python application to rapidly upload tabular data to a wikibase.cloud instance. After performing a mass deletion, Steve will conclude by describing how he's used the Wikibase API to facilitate addition of structured data to Commons. Registration link
      • Strategically Using Production Photos to Increase Your Online Discoverability, February 22 and 24, 2023. This two-part workshop presented by CAPACOA will explain how to upload performing arts production photos to Wikimedia Commons and how to document credits in Wikidata.
    • Ongoing
      • Weekly Lexemes Challenge #80, Work
  • Other Noteworthy Stuff
    • Wikidata Graph Builder released a major update, introducing new layouts and visualization ideas. You can read the full changelog here.
    • The new Service Level Objective for the Wikidata Query Service has been implemented: the current aim is to maintain a 95% uptime based on a 90 day rolling window. You can read the full announcement here.
    • Observablehq.com recently introduced a system of tags. Anyone authoring a notebook using data from Wikidata can add the #Wikidata tag: https://observablehq.com/tag/wikidata?filter=recent.
    • a.gup.pe provides group features for Mastodon. @wikidata@a.gup.pe is a group about Wikidata in general. @querywikidata@a.gup.pe is a group about Wikidata queries. Anyone can join those groups simply by following them in Mastodon. Anyone can share a message with all members of those groups by mentioning them in a publication in Mastodon or any other application of the Fediverse.
    • The hashtag #Wikidata can be used to tag all publications related to Wikidata in Mastodon. Anyone can find recent publications using this tag using the search feature: https://wikis.world/tags/Wikidata.
    • @wikidata@wikis.world is the official Mastodon account of the Wikidata project.
    • You can now vote for your favorite proposals on the Community Wishlist Survey 2023/Wikidata. The voting phase is open until February 24th.
  • Development
    • [Significant change] Heads-up: Upcoming fixes for date parsing - Thank you Matej for moving this forward!
    • REST API:
      • Went over the feedback on the first release and deciding on the next routes to add
      • Added a new endpoint for getting descriptions (phab:T327881)
      • Worked on throwing exceptions when something goes wrong (validation failed, Item not found, etc.) instead of returning an error response object (phab:T327527)
    • Entity Schemas: Finished the technical exploration that will unblock the next steps for actual development
    • Query Service: Changed URLs with URL-encoded characters to be shown un-encoded for better line-breaks and readability (phab:T327514)
      • Query Builder:
      • Adding support for a few additional datatypes (phab:T328528)
      • Adding a basic language selector to make it easier to switch the language of the page (phab:T328764)
    • Constraint checks: Working on showing constraint clarification messages to make it easier to understand how to fix a violation on a statement (phab:T219037)
    • Search: Exploring design options for how to make it easier to search for entities other than Items (phab:T327507)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #560

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • Cmtqwikibot 2 (Task/s: Add credits (cast and crew) for audiovisual work produced in Quebec based on the Cinémathèque québécoise's catalogue data. Adds reference. Deletes redundant, more general existing statements in certain circumstances.)
      • Gabrabot (Bulk upload Maltese lexeme data to wikidata from Gabra.)
      • MsynBot 12 (import missing GND ID (P227) identifier based on linked VIAF cluster)
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call February 21, 2023: Jim Hahn and John Mark Ockerbloom will be presenting on Penn Libraries' Linked Data Vision. They will discuss their framework for activities and goals around linked data, which includes both existing standards and new functionality. Additionally, they will share successes and areas where progress has not yet been made. The presentation will cover projects with Wikidata tie-ins, such as the Digital Scriptorium Wikibase project and the Deep Backfile copyright information project. The presenters also plan to have ample time for conversation with those interested in using linked data to bring new functionality to their libraries. Agenda
      • Wikidata and Wikibase - SEMIC workshop 2 physical hands-on workshop in Brussels on the 23rd of February (Register here)
      • If you are interested in organizing or joining the Wikimedia Hackathon 2023 satellite events, you can apply for funds by March 20 via the Rapid Grants maintained by the Wikimedia Foundation.
      • Call for papers for the 10th Wiki Workshop in 2023 is out. Submit your 2-page abstracts by March 23.
    • Ongoing
      • Weekly Lexemes Challenge #81, Eye
  • Development
    • REST API:
      • Finished work on endpoints for getting labels and descriptions (phab:T325647, phab:T327881)
      • Started work on makign it possible to get statements from an Item based on the Property ID instead of just the statement ID (phab:T309021)
    • Entity Schemas: finalized technical investigation and making plan for the next steps
    • Working on more validation for valid URIs for units, globes and calendar models (phab:T102840)
    • Query Builder:
      • Adding support for additional data types (phab:T328528)
      • Adding a language selector to make it possible to switch the UI language (phab:T329487)
    • Constraint: Putting finishing touches on showing the constraint clarification messages in the constraint violation popup (phab:T219037)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Your GA nomination of Mathematical Institute, University of Oxford

Hi there, I'm pleased to inform you that I've begun reviewing the article Mathematical Institute, University of Oxford you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by ChristieBot, on behalf of SyntheticSystems -- SyntheticSystems (talk) 21:23, 21 February 2023 (UTC)

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:MartinPoulter/Archive_30&oldid=1157507107"