Wikidata

Shisma

Joined 30 October 2012

About this board

Previous discussion was archived at User talk:Shisma/Archive 1 on 2019-05-26.

Start a new topic
You are not logged in. To receive attribution with your name instead of your IP address, you can log in or create an account.

Wikidata weekly summary #653

One comment • 17:30, 11 November 2024 5 days ago
1
MediaWiki message delivery (talkcontribs)
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-11-11. Missed the previous one? See issue #652

Events

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

  • Starting ca. today (), tools or bots which use the wiki replicas (such as Quarry) will observe outdated data for up to 8-10 days, as a result of necessary database maintenance (T367856). Tools or bots which use the APIs will not be affected.
  • Job vacancy Product Manager: Wikibase Suite: Wikibase Suite allows institutions to create and host their own linked knowledge base with maximum customizability, this role will be responsible for the vision and strategy of this exciting product!

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Lua: We changed the Wikibase function getAllStatements logic to behave as getBestStatements. When invoked, it was returning mutable direct-values, now it will return a copy of those values (which are immutable). (phab:T270851)
  • Wikibase REST API:
  • Configuration: We removed 'mainpage' from $wgForceUIMsgAsContentMsg for Wikidata as requested so translations of the main page are available (phab:T184386)
  • mul language code: We moved it to the top of the termbox so labels and aliases in mul are visible first (phab:T371802)
  • Revision table size: We are investigating the current state of the revision table of Wikidata's database and what the next steps should be to address its issues.

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.

Weekly Tasks

· Previous issue · Mohammed Abdulai (WMDE) (talk) · MediaWiki message delivery (talk) 17:30, 11 November 2024 (UTC)
Reply 17:30, 11 November 2024 5 days ago
Reply to "Wikidata weekly summary #653"

Wikidata weekly summary #652

One comment • 18:31, 4 November 2024 12 days ago
1
MediaWiki message delivery (talkcontribs)
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-11-04. Missed the previous one? See issue #651

Discussions

Events

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

  • A small project on benchmarking query engine performance on useful Wikidata queries is asking for queries from the Wikidata user community to potentially be part of the benchmark. If you are a user of any Wikidata SPARQL service please send queries that you find useful to Peter F. Patel-Schneider. Say what you used the query for and whether you would like to be noted as the source of the query. Queries that take considerable time or time out are especially welcome, particularly if the query caused you to switch from the official Wikidata Query Service to some other service. More information about the project is available in Wikidata:Scaling_Wikidata/Benchmarking.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Mobile statement editing: We are making progress on the technical investigation for how to make it easier to edit statements on mobile. A lot more work to be done after that though.
  • We fixed the sidebar link to the main page in many languages (phab:T184386)
  • Codex: We are continuing with the migration of the Query Builder to Codex, the new design system. The migration of Special:NewLexeme is almost finished.
  • Query Service: We have updated the list of languages for the language selector in the UI (phab:T358572)
  • Vector 2022: We are continuing to adress issues of the Item UI in dark mode (phab:T369385)
  • Wikibase REST API:
    • We are moving from v0 to v1.
    • We have finished the work on the new endpoint for creating Properties.
  • Action API: We’re improving the way the wbformatvalue API handles invalid options (phab:T323778)

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.

Weekly Tasks

Reply 18:31, 4 November 2024 12 days ago
Reply to "Wikidata weekly summary #652"

Wikidata weekly summary #551

One comment • 16:28, 28 October 2024 19 days ago
1
MediaWiki message delivery (talkcontribs)
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-10-28. Missed the previous one? See issue #650

Discussions

Events

  • Wikidata's 12th Birthday is almost here! Let’s celebrate together and make it unforgettable! 🎂 Join in for events happening across the globe in October & November -- there's something for everyone! Here’s how you can be part of the fun.
    • Find a local event and connect with fellow Wikidata enthusiasts!
    • Give a birthday gift to the community -- whether it's a cool new tool or something fun!
    • Join our big online celebration on October 29th -- don’t miss out! Wikidata:Twelfth_Birthday
    • Join the special Wikidata Query-party tomorrow and win some branded Wikidata socks! 🎉
  • The LD4 Wikidata Affinity Group is taking a break from our new project series format this coming Tuesday, October 29, 2024 at 9am PT / 12pm ET / 16:00 UTC / 6pm CEST (Time zone converter) to celebrate Hallowe'en! We'll be celebrating Spooky Season with a WitchyData Working Hour! Following on Christa Strickler's recent project series, we will continue building proficiency with the Mix'n'match tool, but with a ghoulish twist. Join the fall fun by updating your Zoom background or even coming in costume. BYOC (bring your own candy). Event page: Wikidata:WikiProject LD4 Wikidata Affinity Group/Wikidata Working Hours/2024-October-29 Wikidata Working Hour

Press, articles, blog posts, videos

Tool of the week

  • Lexica – A mobile-friendly tool that simplifies micro contributions to lexicographical data on Wikidata, making various editing tasks accessible and intuitive for contributors of all experience levels. This tool is developed by the WMDE Wikidata Software Collaboration team in Indonesia. Try Lexica through this link: https://lexica-tool.toolforge.org/

Other Noteworthy Stuff

  • The Global Open Initiative Foundation is building an open-source web app for Supreme Court cases in Ghana. We are looking for volunteers in the following roles: Frontend Developers, Backend Developers, Wikidata/SPARQL Experts, UI/UX Designers, Quality Assurance (QA) Testers, and Legal Professionals. Join us by sendind your resume and a brief description of your expertise to globalopeninitiative@gmail.com

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Vector 2022: We are continuing to make Wikidata Items pages work in dark-mode (phab:T369385)
  • EntitySchemas: We are continuing to work on making it possible to search for an EntitySchema by its label or alias when making a statement linking to an EntitySchema
  • Wikibase REST API:
    • We discussed what will constitute breaking changes for the API (phab:T357775)
    • We are working on the endpoint for creating Properties (phab:T342992)

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.

Weekly Tasks

Reply 16:28, 28 October 2024 19 days ago
Reply to "Wikidata weekly summary #551"

Wikidata weekly summary #650

One comment • 16:43, 21 October 2024 26 days ago
1
MediaWiki message delivery (talkcontribs)
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-10-21. Missed the previous one? See issue #649

Discussions

  • Open request for adminship: Addshore (RfP scheduled to end after 23 October 2024 18:03 UTC)
  • New requests for permissions/Bot:
    • CarbonBot - (1) Add default mul labels to given and family names when the item has an existing default label with a mul language (2) Remove duplicated aliases matching the items mul label, when the item has a native label in with a mul language. As mul has not been fully adopted, a limited of aliases would be modified each day to ensure existing workflows are not disrupted. It is expected that these tasks will apply to roughly 800,000 given and family names.
    • So9qBot 10 - Add first line (P1922) with the first line of the paper to all scientific papers which has a full text link or where the abstract is available.

Events

  • Upcoming: We are getting ready for Wikidata:Twelfth Birthday on the 29th October. We already have 30 events scheduled on the list 😍. As a reminder, when your event is ready, don't forget to (1) create a wikipage with more information about the event, participants list, etc. (2) add your event to the global calendar and the map, following the instructions here: Wikidata:Twelfth Birthday/Run an event/Schedule
  • Past:

Press, articles, blog posts, videos

Tool of the week

  • User:Ainali/PreViewStats.js - is a Userscript that gives a quick glance at the pageviews in the header (and links to the full views). If you install it on your global.js on meta, it works on all projects).
  • Wikidata:ProVe - (Automated PROvenance VErification of Knowledge Graphs against Textual Sources) - is a tool for helping editors improve the references of Wikidata Items.

Other Noteworthy Stuff

  • Deepesha Burse joins WMDE as Developer Advocate for Wikibase Suite
  • Wikibase Suite: Patch releases as the first round of patch releases for all Wikibase Suite products, including all WBS Images as well as WBS Deploy
  • The CampaignEvents extension is now live on Wikidata! This means that if you are an event organizer, you can use several new tools to help manage your events more easily. By getting the Event Organizer right, you can:
    • Use simple on-wiki registration for your events.
    • Integrate Outreach Dashboard with your event registration page. (see demo)
    • Communicate more easily with your registered participants. (see demo)
    • Make your events more visible to other editors through the Special:AllEvents page.
    • Find potential participants for your next events. (see demo), and much more!
    • With this extension, you can also see all global events (past, present, and future) on the Special:AllEvents page, but only events using the event registration feature will appear there. If you are an organizer and want to use these new tools, follow the instructions on the Wikidata:Event_Organizers page to request the Event Organizer right.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Vector 2020: We’re working on improving Wikibase’s dark mode support somewhat (phab:T369385)
  • We polished the automatic undo/redo messages to make them more useful (phab:T194402)
  • Design system: We’re close to finishing migrating Special:NewLexeme to the Codex design system
  • EntitySchemas: We’re working on searching EntitySchema values by label and alias (phab:T375641)

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.

Weekly Tasks

Reply 16:43, 21 October 2024 26 days ago
Reply to "Wikidata weekly summary #650"

P854

8 comments • 12:20, 21 October 2024 26 days ago
8
Kirilloparma (talkcontribs)

When you want to add a reference to any statement, please avoid using reference URL (P854) property (as here) when there is an external identifier property in Wikidata. In this case, you should have used this property (as reference) instead of P854. I don't know who created the Wikidata for Firefox tool, but this should be fixed as soon as possible, as it is semantically incorrect. See for example how the UseAsRef tool works, this is exactly what is expected from Wikidata for Firefox. In a nutshell: when we have an external identifier property in Wikidata, it is that property that should be used in references, not P854.

Reply 01:54, 20 June 2024 4 months ago
Shisma (talkcontribs)
Reply 07:19, 20 June 2024 4 months ago
Shisma (talkcontribs)

Correct me if I'm wrong: It seems to me UseAsRef allows a human user, to use an external id statement as a source on a different statement that a human user has verified intrinsicly contain information to be referenced.

For example:

  1. title (P1476) → Quizzical
  2. ‎Playdate Catalog ID (P12125) → 318641

a human could assume that if statement 1. is true, a url that can be derived from statement 2. would contain a proof for it.

Is this the idea?

Reply Edited 10:07, 20 June 2024 4 months ago
Kirilloparma (talkcontribs)

Yes, that's the idea. A person who sees that a statement is true (let's say date of birth (P569)), then another property of the external identifier (let's say danskfodbold.com player ID (P12827)) can be a reference to confirm that statement, but instead of using the semantically incorrect and broad in scope property reference URL (P854), it should be exactly used (as in the example) danskfodbold.com player ID (P12827) property.

This is what it's supposed to look like:

Karim Zaza (Q945746)

date of birth
Normal rank 9 January 1975 edit
1 reference
danskfodbold.com player ID 10156
stated in danskfodbold.com
retrieved 21 June 2024
add reference


add value

And NOT like this as the Wikidata for Firefox tool suggests on a regular basis:

Karim Zaza (Q945746)

date of birth
Normal rank 9 January 1975 edit
1 reference
reference URL https://danskfodbold.com/spiller.php?spillerid=10156
title danskfodbold.com - DBU's Officielle Statistikere
retrieved 21 June 2024
add reference


add value

Regards

Reply Edited 01:50, 21 June 2024 4 months ago
Shisma (talkcontribs)

I think both reference types are alright. stated in works best in situations where a statement is derived from a database dump/extract, where the statement might not even be visible under a certain url. reference url is appropriate where a url holding the statement is known but the presence of an intrinsic connection to the database entry is uncertain. None of the two options are any better or worse: The difference is merely how the information was retrieved.

Wikidata for Web does not know database extracts: it only ever sees urls and can therefore only make reference statements for urls. Therefore I think reference url is a good default. However I could allow the user to choose which reference type is a better source for a particular statement. What do you think about this?

Reply 07:51, 21 June 2024 4 months ago
Kirilloparma (talkcontribs)

> I think both reference types are alright.

In this case yes, and in this case no. In the first case, you can use any tool you want, because we are referencing a news article and Wikidata does not have a separate property for news articles of this database. In the second case, Wikidata for Firefox is not suitable because we already have an external identifier property and it is that property that should be in the references, not P854, which is the crux of the problem.

> stated in works best in situations where a statement is derived from a database dump/extract, where the statement might not even be visible under a certain url. reference url is appropriate where a url holding the statement is known but the presence of an intrinsic connection to the database entry is uncertain. None of the two options are any better or worse: The difference is merely how the information was retrieved.

It has nothing to do with stated in (P248) in or reference URL (P854) for those cases where we are referring to a URL that does not contain any identifiers. In our case, I am talking about the URL that is used by the formatter URL (P1630) property. We don't need to use reference URL (P854) at all if we already have an external identifier property. stated in (P248) again has nothing to do with it, although it is the one that increases "what links here" and it is advantageous. I still suggest you avoid using the problematic Wikidata for Firefox for references, since we have UseAsRef which does a great job and doesn't use P854 for external identifiers that existing on Wikidata.

> Wikidata for Web does not know database extracts: it only ever sees urls and can therefore only make reference statements for urls

And that's the problem.

> Therefore I think reference url is a good default.

I don't think this is the right approach. By using reference URL (P854) we are only increasing its usability, and the external identifier property is essentially not used at all. What's the point of creating external identifier properties then if we don't even use them later and prefer P854? It's such a waste! Question: why did you propose this property that I created later? Let's say we're going to use this property and P854 in references (see ), okay, but what about the property itself? And here is the result, the property itself is used only 2 times in the references, that's the "waste" I'm talking about. Regards

Reply 02:30, 22 June 2024 4 months ago
Kirilloparma (talkcontribs)

Hi! Last time we discussed about this topic, I made it clear that this tool should not use P854 if the external identifier property exists, but I see that you are still using the first option. I would ask you to respect the choices of those who not only prefer, but also care about Wikidata external identifiers. Constantly using P854 instead of an existing created external identifier loses the whole point of Wikidata properties. Here's an example: this property mentions that its scope also includes the use of an external ID as a reference. But the question is: why is this indicated if P854 is going to be used instead of the external ID anyway? That's what I'm talking about, the whole point of using the property as a reference is lost here, its use will be useless if the P854 option is always applied. Regards

Reply 02:45, 21 October 2024 26 days ago
Shisma (talkcontribs)

I apologise for not answering earlier. I thought I did.

Question: why did you propose this property that I created later? Let's say we're going to use this property and P854 in references (see ), okay, but what about the property itself? And here is the result, the property itself is used only 2 times in the references, that's the "waste" I'm talking about.

When I proposed the property, I did not intend it to be used in references. I don't mind if anyone does though. It was meant as a main statement and I think i perfectly fulfils its function.

…not for experienced Wikidata editors, as no one in their right mind would use P854 in references.

Well, I'm sorry but I don't see that the use of reference URL (P854) is universally agreed to be a bad practice by the community.

Here's an example: this property mentions that its scope also includes the use of an external ID as a reference.

I think the constraint only implies that the property may be used in the reference scope, not that it has to be.

Reply 12:20, 21 October 2024 26 days ago
Reply to "P854"

The Chrome extension and big entities and regular expressions…

17 comments • 07:38, 19 October 2024 28 days ago
17
Trade (talkcontribs)

I dont know if you notice but the heavy amount of lag makes the extension very hard to use when matching entries to countries.

Any chance you could let us just not show the statements? Just show whether or not the entries is connected to an item along with description, label and P31

Reply 03:46, 13 October 2024 1 month ago
Shisma (talkcontribs)

Opening big items like say United States of America (Q30) is indeed very slow. I surely can make some optimisations for those cases. But from looking at your contributions I gather you are using the Chrome version which is unlikely to see such optimisations soon as it is currently unmaintained. 😕

Reply 08:20, 13 October 2024 1 month ago
Trade (talkcontribs)

What you got against Chrome /:

Reply 12:55, 13 October 2024 1 month ago
Shisma (talkcontribs)

Chrome is soon going to depricate the webRequest api in order to prevent adblockers from working. Unfortunately the same api is currently crucial for this extension to work. I'd still like to support chrome derivatives if possible but I'm not going to spend any time until the dust has around this has settled. I don't want to spend multiple weekends on something that could break the second I'm done.

I hope that puts things in perspective.

Reply Edited 16:05, 16 October 2024 1 month ago
Shisma (talkcontribs)

I don't have anything against chrome. Its just additional work and this is a project that I maintain in my spare time.

Reply 13:12, 13 October 2024 1 month ago
Trade (talkcontribs)

So which versions are actually maintained?

Reply 13:47, 13 October 2024 1 month ago
Shisma (talkcontribs)
Reply 13:52, 13 October 2024 1 month ago
Trade (talkcontribs)

I noticed that everytime i use the extension with Rate Your Music track ID (P13056), it adds an / at the end

Also it keeps trying to add the name of the artist and "Lyrics and ratings" as an alias to the tracks which is enabled by default

"Wenche Myhre - Ei snerten snelle - Lyrics and ratings" is not an alias you really want on Q130534993

Reply Edited 21:58, 15 October 2024 1 month ago
Shisma (talkcontribs)
Reply 07:00, 16 October 2024 1 month ago
Trade (talkcontribs)
Reply 17:02, 16 October 2024 1 month ago
Shisma (talkcontribs)

I don't understand. You want me to join ZI Jony's conversation, or you want ZI Joni to join this conversation? 😅

Reply 07:16, 17 October 2024 30 days ago
Trade (talkcontribs)

First

Reply 20:24, 17 October 2024 30 days ago
Trade (talkcontribs)

Oh and also add a URL match pattern and web page title extract pattern to Push Square series ID and VG247 series ID if you get time

Reply 20:28, 17 October 2024 30 days ago
Shisma (talkcontribs)

Yes, i’ll have a look at it later. How about i’ll write down a short guide on how to write a url regular expression? It’s pretty straightforward and you won’t depend on me.

Reply 05:58, 18 October 2024 29 days ago
Shisma (talkcontribs)

The general workflow looks like this:

  1. Click on the link om one of the examples that links to the external website and copy the URL.
  2. (when the url contains %) go to urldecoder.io paste the url into the top field and copy it from the bottom.
  3. Go to regex101.com
  4. Paste the URL into the field that says Test Sting.
  5. Now paste the same URL into the Regular expression field.

We will now fine tune the the Regular Expression so that the part of the Test string we want to extract is highlighted in green.

Things we need to change:

Some parts of the URL will be highlighted in the Regular Expression field:

Expression: https://www.pushsquare.com/games/browse?title=serie:overwatch

These characters have a specific meaning in the context of regular expression. At this stage, we don't want that. And we can convert them to regular characters by adding a \ in front of them.

Expression: https:\/\/www\.pushsquare\.com\/games\/browse\?title=series:overwatch

At this stage, the Test string should appear completely blue. This means, that the pattern will now match exactly this URL.

We now need to capture the actual id. We do that by wrapping the id in ( and )

Expression: https:\/\/www\.pushsquare\.com\/games\/browse\?title=series:(overwatch)

Test sting: https://www.pushsquare.com/games/browse?title=series:overwatch

The id should now be highlighted in green. This pattern will now only find the id overwatch. It won't match any other id. In order to change that we have to express the pattern of the id in the expression.

What is the pattern? It looks like the id only consists of one or more lowercase characters. You can just make a list of all possible characters and wrap it into [ and ]. Like [abcdefghijklmnopqrstuvwxyz] but you can shorten it down to [a-z]:

Expression: https:\/\/www\.pushsquare\.com\/games\/browse\?title=series:([a-z])

Test sting: https://www.pushsquare.com/games/browse?title=series:overwatch

This will now find only the first character of the id. In order to match one or more characters, you can just add a + after the group.

Expression: https:\/\/www\.pushsquare\.com\/games\/browse\?title=series:([a-z]+)

This pattern should now successfully highlight the id overwatch from

Test sting: https://www.pushsquare.com/games/browse?title=series:overwatch.

But what's that? It doesn't work with:

Test string: https://www.pushsquare.com/games/browse?title=series:assassin's-creed 😱

That's because we didn't expect characters like ' or - to appear in our ID.

In order to find them that we add these characters to the list of our possible characters, wrapped in [ and ]:

Expression: https:\/\/www\.pushsquare\.com\/games\/browse\?title=series:([a-z'-]+)

This pattern should now match all the provided examples.

There is a quick introduction on Youtube that should help with other scenarios you might come across. (the relevant part begins at minute 1)

Reply Edited 07:41, 18 October 2024 29 days ago
Shisma (talkcontribs)
Reply 12:32, 18 October 2024 29 days ago
Back ache (talkcontribs)

Looks pretty good :-) there are some "URL match pattern"'s out there that are that need a little maintence because of things like there now being a variation of URL they didn't expect or it initnally having been autogenerated from another property Back ache (talk) 07:38, 19 October 2024 (UTC)

Reply 07:38, 19 October 2024 28 days ago
Reply to "The Chrome extension and big entities and regular expressions…"

Wikidata weekly summary #649

One comment • 17:01, 14 October 2024 1 month ago
1
MediaWiki message delivery (talkcontribs)
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-10-14. Missed the previous one? See issue #648

Events

  • Upcoming:
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group session 15 October, 2024: We have our next LD4 Wikidata Affinity Group Session on Tuesday, 15 October, 2024 at 9am PT / 12pm ET / 16:00 UTC / 6pm CEST (Time zone converter). https://zonestamp.toolforge.org/1729008000 Christa Strickler will be our first Project Series lead with her joint project with the Wikidata Religion & Theology Community of Practice to contribute biographical data to Wikidata from the IRFA database https://irfa.paris/en/en-learn-about-a-missionary/ using the Mix’n’Match tool. We are excited to learn more about this project, provide a forum for discussion and shared learning, and lend a hand while building new skills. Event page:
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16th October 2024 at 18:00 CEST 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.
    • Wikidata:Twelfth Birthday: We already have 30 events scheduled on the list 😍. As a reminder, when your event is ready, don't forget to:

Press, articles, blog posts, videos

Tool of the week

  • Elemwala (এলেমওয়ালা) (https://elemwala.toolforge.org): is a proof-of-concept interface that allows you to input abstract content and get natural language text in a given output language. There may well be errors with particular inputs, and the text may not be quite as natural as you might expect, but that's where your improvements to your language's lexemes, other Wikidata items, and the tool's source code come in!
  • mlscores: Tool for calculating multilinguality score of Wikidata items (including properties). E.g. for Wikidata (Q2013), the scores are - en: 99.66%, fr: 89.49%, es: 84.07%, pt: 68.47%. For instance of (P31), the scores are - en: 99.86%, fr: 87.12%, es: 80.83%, pt: 61.37%.

Other Noteworthy Stuff

  • Launch of WikiProject Deprecate P642: The goal of this project is to prepare for deprecation, and eventual removal, of the property of (P642). Currently, of (P642) is labeled as "being deprecated", meaning its use is still allowed, but discouraged. From a peak of around 900,000 uses, the property now has around 700,000 uses (see status here). Our goal is to reduce that as much as possible in a systematic way, while ensuring that appropriate properties exist to replace all valid uses of of (P642). The latter is key to officially deprecating the property. Before removing the property, we want to get as close to zero uses as possible.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • EntitySchemas: We are continuing the work on making it possible to find an EntitySchema by its label or aliases when linking to an EntitySchema in a statement (phab:T375641)
  • Design system: We are continuing the work on migrating the Query Builder from Wikit to Codex
  • REST API: We finished the work on language fallback support in the REST API (phab:T371605)

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.

Weekly Tasks

Reply 17:01, 14 October 2024 1 month ago
Reply to "Wikidata weekly summary #649"

Wikidata weekly summary #648

One comment • 17:23, 7 October 2024 1 month ago
1
MediaWiki message delivery (talkcontribs)

Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-10-07. Please help Translate. Missed the previous one?
See issue #647

Events

  • Upcoming:
    • Wikidata Day 2024 at the Pratt Institute Manhattan Campus, New York - To celebrate Wikidata's 12th Birthday, a mini-conference with beginner workshops, lightning talks and keynote speeches will be held. October 26, 11am - 5pm EDT (UTC-4). More info, registration and full address on this Wikipedia event page.
    • The Wikidata Days 2024 in Bologna, Italy will take place on November 8th and 9th. Its program revolves around Wikidata for libraries and academia, and features a wide range of Wikidata-enthusiastic librarians and researchers from Italy. Registration is open until October 31st.
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16th October 2024 at 18:00 CEST 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.
    • Scholia hackathon on Oct 18-20, aimed at addressing changes related to the Wikidata graph split
    • Intangible Cultural Heritage on Wikidata - Hosted by Wikimedia Community Malta (WCM), November 8, 2024 18:00 - 19:00 CEST, Malta Fairs and Conference Centre (MFCC) in Ta’ Qali, Malta
    • Edit-A-Thon: 50 States of Comics - Ohio, take part in this virtual event held October 10, 10:00 - 16:00 EST (UTC-5).

Press, articles, blog posts, videos

Tool of the week

  • (fr) wikidata MultiSearch - search for a list of elements in Wikidata. A GPLv3 licenced tool built by Philippe Gambette allows you to search for a list of words in Wikidata and retrieve some associated Wikidata properties.

Other Noteworthy Stuff

  • Are you building applications or services with Wikidata's data? We'd love to hear from you to help us figure out the future of accessing Wikidata's data.
  • Wikidata: Event Organizers - If you are organizing or thinking about planning a Wikidata event, this new page listing the additional User rights the user-role 'event organizer' has will be a valuable resource. Including the process for applying for permission rights.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Data access:
  • Design system: We continued migrating the Query Builder and Special:NewLexeme from Wikit to Codex

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.

Weekly Tasks

Reply 17:23, 7 October 2024 1 month ago
Reply to "Wikidata weekly summary #648"

Duplicated "Star Trek: The Classic Episodes" editions

16 comments • 13:40, 7 October 2024 1 month ago
16
Maxlath (talkcontribs)

Hi! Back in 2018, it seems that you did a quickstatement import that resulted in creating 10 almost identical items, sharing the same ISBN as well as other identifiers. There seems to be some differences in format de distribution (P437) though:

Can those be merged? Was that intentional or a mistake?

Reply 18:05, 25 September 2024 1 month ago
Maxlath (talkcontribs)
Reply 18:10, 25 September 2024 1 month ago
Shisma (talkcontribs)

It sure looks like it. lets merge them

Reply 18:45, 25 September 2024 1 month ago
Maxlath (talkcontribs)
Reply 21:09, 25 September 2024 1 month ago
Shisma (talkcontribs)

It would seem that these three books – the only Star Trek Books published by Weltbild (Q883522) – actually all have the same ISBN. Is this possible?

They are definitely individual books.

Reply Edited 12:49, 27 September 2024 1 month ago
Maxlath (talkcontribs)
Reply Edited 21:37, 25 September 2024 1 month ago
Shisma (talkcontribs)

I'll work through it

Reply 14:59, 26 September 2024 1 month ago
Shisma (talkcontribs)

I think my script back then had issues with miscellanies. I'm sorry. thanks for making me aware

Reply 16:52, 3 October 2024 1 month ago
Maxlath (talkcontribs)
Reply Edited 13:26, 4 October 2024 1 month ago
Colin R Robinson (talkcontribs)

I made this SPARLQL query which gives all all items that have both a P212 violation and a P12204 ELMCIP ID.

SELECT ?item ?itemLabel ?p212_value ?elmcip_id WHERE {
  ?item wdt:P212 ?p212_value ;
        wdt:P12204 ?elmcip_id .
  FILTER(EXISTS {
    SELECT ?item (COUNT(?p212_value) AS ?count) WHERE {
      ?item wdt:P212 ?p212_value .
    } GROUP BY ?item HAVING(?count > 1)
  })
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!

There were 2 results, so I have quickly fixed them.

Reply Edited by Shisma 09:43, 4 October 2024 1 month ago
46.212.78.229 (talkcontribs)

Is there an easy way to see Unique Value Violations by ELMCIPBot? I will correct those immediately - User:Colin R Robinson

Reply Edited by Colin R Robinson 21:23, 3 October 2024 1 month ago
Maxlath (talkcontribs)
Reply 13:24, 4 October 2024 1 month ago
Maxlath (talkcontribs)
Reply 13:38, 7 October 2024 1 month ago
Richard Nevell (talkcontribs)

Indeed, if there's effectively a work list by user I'd like to fix the ones I'm responsible for.

Reply 23:27, 3 October 2024 1 month ago
Maxlath (talkcontribs)

I tried to find an effective way, and now have a list of users contributing to several items with the same ISBN; for you that gives this:

I'm going to post other users constraint violations on Property_talk:P212

Reply 14:16, 4 October 2024 1 month ago
Maxlath (talkcontribs)
Reply 13:40, 7 October 2024 1 month ago
Reply to "Duplicated "Star Trek: The Classic Episodes" editions"

Missing or faulty url match patterns

3 comments • 07:21, 7 October 2024 1 month ago
3
Summary by Shisma

Added new match patterns. Updated faulty ones

Trade (talkcontribs)

Could you make it work with MetalTabs.com musician ID (P13021)?

Reply 18:34, 1 October 2024 1 month ago
Shisma (talkcontribs)
Reply 18:45, 1 October 2024 1 month ago
Shisma (talkcontribs)
Reply 07:21, 7 October 2024 1 month ago
Reply to "Missing or faulty url match patterns"
Load more
Retrieved from "https://www.wikidata.org/wiki/User_talk:Shisma"