Shortcuts: WD:PC, WD:CHAT, WD:?

Wikidata:Project chat

From Wikidata
(Redirected from Wikidata:Pc)
Jump to navigation Jump to search

Wikidata project chat
A place to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.

Please use {{Q}} or {{P}} the first time you mention an item or property, respectively.
Other places to find help

For realtime chat rooms about Wikidata, see Wikidata:IRC.
Start a new discussion
Edit
On this page, old discussions are archived after 7 days. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/06.

Using Wikidata as an upstream for device information

[edit]

As part of postmarketOS we track a significant amount of information about the specs of computer hardware, mostly tablets and phones (e.g. the OnePlus 6) . However, since this info is fixed, I've been thinking it probably makes more sense to find a more central datastore and put this info there and to pull from it instead. Found that some of our devices are already in Wikidata. We'd want to add some more fields probably, but a bunch would already be usable for us. Does this seem like a good use of Wikidata? 2A02:168:F912:0:0:0:0:1001 19:42, 29 May 2024 (UTC)[reply]

It could be a good use case. The main problem though is that we require information to have references (or at least be referenceable). I'm not clear on where your information is sourced to. Also it would depend on exactly how many new properties you would want made. You may want to consider using https://www.wikibase.cloud/ which I believe would let you federate somehow with wikidata while maintaining your own database separate from wikidata (which you could link bidirectionally to wikidata). If you went that route you wouldn't need to follow our rules about sources or notability. BrokenSegue (talk) 01:07, 30 May 2024 (UTC)[reply]
We don't have a rule that all information needs to have a reference. When it comes to specs there's going to be some official documentation that contains the information so it's going to be referencable. Our rules also don't forbid from using the existing postmarketos website as a source.
I would expect that the bigger issue is to think through the data model as when we create properties in Wikidata we create them not optimized for single use-cases like "I need a field in which to put X". ChristianKl ❪✉❫ 11:41, 30 May 2024 (UTC)[reply]
The postmarketOS wiki wouldn't be a reference in the scenario I'm proposing, it'd be downstream of Wikidata. My goal would be to put the specs we need in Wikidata so we can remove them from our wiki and instead reference them. However, there are sometimes other places that have this info (GSMArena or the manufacturer's pages, etc.). I think referencing things can be done in many cases.
Could you elaborate on the issue with properties? We mostly only log this info in our wiki so people can find devices that meet their specs, they aren't critical to our project. However, some are like the CPU and GPU. I've seen RAM (one of the properties we log) documented already in Wikidata, so that looks good. CPU and GPU looks good too. But some are missing, and maybe this is what you're talking about. Like I couldn't find a property for the amount of data storage on a device. Nor for things like the type of sensors that they have. If you look at the OnePlus 6 link in my OP you can see a table with the info I'm talking about. 85.195.207.54 15:53, 30 May 2024 (UTC)[reply]
The problem is that we don't really have a property for RAM. We have one for memory capacity (P2928) that can be used for both RAM and data storage. That wouldn't be that much of a problem if people would use it as intented and say phone model Xhas part(s) (P527)hard diskmemory capacity (P2928)128 GB and phone model Xhas part(s) (P527)RAMmemory capacity (P2928)8 GB. In practice, you find people saying memory capacity (P2928)128 GB{{{3}}} or memory capacity (P2928)8 GB{{{3}}} and the data we have is messy. This isn't an unsurmountable problem but it takes work to move forward.
When it comes to sensors, has part(s) (P527) would be the way to go. I'm unclear about what you mean with works/broken/partial. If that's a postmarketOS specific category it would likely need a new property. ChristianKl ❪✉❫ 13:12, 1 June 2024 (UTC)[reply]
I think everything I need is supported and then some! I created a new tablet. The only two missing properties I ran into were one for "sensor resolution" of the camera sensors and "diagonal" for the size of the display (since those are commonly referenced as diagonal inches). So in general everything looks good!
The RAM problem I solved by using has part(s) as you can see in the tablet item I made. I think it makes sense to break them out as parts with capacities under them. I'll want to engage more with others working in this area to see what might be the best route here.
https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada) shows the info we track on our wiki for reference. What we need is a way to pull all components of a device so that we can track how well it's supported on our end. I don't think that supported attribute should be in Wikidata, but we need a way to map from the components of a device in Wikidata to the way we track status in our system. I think it's possible with the way I've done organized the tablet I added.
I think the hardest part is integration, as it looks like there's no easy way to pull data into a Mediawiki I operate. However, we may move away from that towards a custom website given upstreaming this data to Wikidata removes a ton of the info we're tracking on our side! BasilicumTree (talk) 20:34, 1 June 2024 (UTC)[reply]
@BasilicumTree: To note, when adding references use reference URL (P854) rather than official website (P856). I've fixed that in your example item and cleaned up some other bits. I like how you've formatted it overall. — Huntster (t @ c) 21:18, 1 June 2024 (UTC)[reply]
https://m.mediawiki.org/wiki/Extension:External_Data works well for my mediawikis, though I do some external json mangling on a filesystem Vicarage (talk) 22:21, 1 June 2024 (UTC)[reply]
@Huntster - Thanks for adding more details and correcting some stuff! Glad we're on the right track here! Let me know if I shouldn't ask here, but what about storing manufacturer model numbers for devices? I couldn't find anything for that. I think I'll propose adding a "diagonal" dimension property, since that's so common for describing electronic displays. With that all the device metadata we need looks good!
@Vicarage - Awesome, thanks! I'll check that out.
We also track info on SoCs, for example the MSM8926, where mostly we want to track the status of components (just like with devices). So I created a Wikidata item for it and I think it covers everything. Thought most things are Parts, I didn't see a better way to do it right now. BasilicumTree (talk) 07:51, 2 June 2024 (UTC)[reply]
@BasilicumTree: for model number, catalog code (P528) possibly could be used in the form catalog code (P528)12345 applies to part (P518)product code (Q57446692), but it isn't ideal. Would be worth it to propose both model number and diagonal as new properties. — Huntster (t @ c) 12:42, 2 June 2024 (UTC)[reply]
Found https://www.wikidata.org/wiki/Wikidata:Property_proposal/part_number which discusses both part number (Q3879409) and product code (Q57446692), though I'm not certain how these are different in practice. Does it make sense to comment on this old thread about my new use case to revisit it? or is there a way to reopen an old property proposal?
I opened https://www.wikidata.org/wiki/Wikidata:Property_proposal/screen_size as well, but found there was already an old proposal closed previously. Figured I'd just leave it as the use case I'm proposing wasn't discussed much previously. BasilicumTree (talk) 10:41, 3 June 2024 (UTC)[reply]
@BasilicumTree: I see no reason the part number proposal couldn't be re-opened if you think you can make a stronger argument than the previous proposal. If you decide to, start a new proposal page and consider linking to the previous discussion. — Huntster (t @ c) 20:13, 4 June 2024 (UTC)[reply]
How should I start a new proposal page if I think the name of the previous proposal was a good one? Just append a 2 to the original URL for example? BasilicumTree (talk) 05:36, 6 June 2024 (UTC)[reply]
An alternative approach I came up with for the Android device codename and part number, is to use name (P2561) with applies to part (P518) and Android (Q94) and product code (Q57446692) respectively. Redmi Note 9 (Q85796390) was already using name (P2561) as well, so seems reasonable. WDYT? BasilicumTree (talk) 17:21, 9 June 2024 (UTC)[reply]
@BasilicumTree: My concern is the potential confusion about which product codes applies to which sub-model. Ideally, you'd have property "Product code" with a subproperty like object named as (P1932) providing a free-form field to specify the exact product name the code applies to, if there's multiple. But, if your alternative provides for your needs, then that's fine. As to your first question, yes, just append a "2", such as "/product code 2". — Huntster (t @ c) 23:24, 9 June 2024 (UTC)[reply]

People falsely claiming Native American heritage

[edit]

See for example: Iron Eyes Cody (Q587113) where he had social_classification=pretendian, it was removed because the term was considered a pejorative. What would be the best way to aggregate people that falsely claimed to have Native American heritage. The original list of about a dozen people came from reliable sources, such as a New York Times obituary. Should we create a new Wikidata entry called "falsely claiming Native American heritage" so it is worded neutrally? Should it be "social_classification=falsely claiming Native American heritage" or something else? Or should it be handled the way it was with Rachel Dolezal (Q20085770) and allow them to be called transracial? See also Sacheen Littlefeather (Q462050) where there is yet another way to model disputed ethnicity, where we add the false claim and deprecate it. I would like a single model where a single simple search term would find all the people. RAN (talk) 13:19, 4 June 2024 (UTC)[reply]

I would add statement ethnic group (P172)Native Americans in the United States (Q49297) with qualifier reason for deprecated rank (P2241)hoax (Q190084) and mark it as a deprecated claim. That model is not super easy to query if you want to find all persons with such statement but at least it is doable with existing items and properties. Samoasambia ✎ 13:41, 4 June 2024 (UTC)[reply]
More likely it was removed because it was incorrect use of properties. Some vigilantes like to add "occupation" claims on people accused or sentenced of certain crimes. Infrastruktur (talk) 15:08, 4 June 2024 (UTC)[reply]
  • They wrote that "pretendian" was a pejorative in a message to me. We also had difficulty with slave_owner and holocaust_victim, and how to model them. Social_classification=slave_owner was the final decision and significant_event=Holocaust_victim and subject_has_role=Holocaust_victim are still both in use, with significant_event givng an error message. --RAN (talk) 15:38, 4 June 2024 (UTC)[reply]
This can be closed, it is resolved "disputed Native American heritage" rather than the pejorative pretendian. --RAN (talk) 23:06, 6 June 2024 (UTC)[reply]

Renaming the Community Wishlist Survey

[edit]

Hello everyone,

Community engagement around the Wishlist's redesign is still in progress to help make decisions ahead of the relaunch of the survey in July 2024. The revised survey will need a new name that reflects its new direction. You are invited to help choose a name.

There are some early renaming ideas like Wikimedia Opportunities Registry, Wikimedia Collaboration Hub and ImagineWiki. These names may not resonate with you all, hence, please join the discussions and suggest your own name if need be.

Looking forward to hearing from you on the discussion page.

NB: In case you have missed previous discussions and announcements regarding the future of the Wishlist, please see them as bullets below:

On behalf of Community Tech, STei (WMF) (talk) 14:54, 4 June 2024 (UTC)[reply]

Are images transfers to WikiData working? (repost from help desk and village pump)

[edit]

I use Wiki Shoot Me to take photos for Wikipedia while I’m traveling. Typically you can identify articles that need photos by looking for yellow dots indicating Wikipedia articles and larger red circles near by indicating WikiData items without photos (as previously these seemed to sync). In two cases recently I noticed articles with CC-licensed images placed correctly in the lead and appropriately sized that did not have their photos synced with WikiData: National Hotel (Q65056276) and Wet Mountain Valley (Q7989973). I know the page image is being picked up because they display correctly on Special:Nearby using their coordinates: National Hotel and Wet Mountain Valley. It looks like they’re just not making it to WikiData. - Scarpy (talk) 17:15, 4 June 2024 (UTC)[reply]

You are free to add them, we do have some automated processes but editors tend sometimes to put non-relevant images as infobox images so we are a bit cautious. Sjoerd de Bruin (talk) 07:56, 5 June 2024 (UTC)[reply]
I’m okay doing that with my photos. For articles with existing photos where I can confirm their relevance, is there a tool I can use to import them so the author information is retained? - Scarpy (talk) 04:27, 6 June 2024 (UTC)[reply]
WDFIST might help. Sjoerd de Bruin (talk) 08:08, 6 June 2024 (UTC)[reply]

Using illustrate_wikidata.py to get images from a commonscat ?

[edit]

Hello, I managed to import images from articles to wikidata objects using

Is it possible to use illustrate_wikidata.py to get images from a commonscat, for example for every subcat of

and add the first (an mostly only one) image from the category to the wikidata objects connected to the commonscats? If yes, what would the parameters?

Thanks a lot! M2k~dewiki (talk) 17:16, 4 June 2024 (UTC)[reply]

@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -catr:"Cultural properties of local significance in Thun (East)"
returns:
>>> File:2023-06-01 Thun Bälliz Brunnen bei44.jpg <<<
commons:File:2023-06-01 Thun Bälliz Brunnen bei44.jpg doesn't have a Wikidata item.
@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -namespace:14 -catr:"Cultural properties of local significance in Thun (East)"
@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -namespace:14 -catr:"Category:Cultural properties of local significance in Thun (East)"
does not return anything M2k~dewiki (talk) 17:52, 4 June 2024 (UTC)[reply]

[PROPOSAL] Link labels, aliases and monolingual text with Lexemes

[edit]
Explanation about connection between labels and lexemes in Wikidata

I don't know if here is the right place to propose it. It would be nice to link item labels, item aliases and monolingual text from statements with a corresponding lexeme. This could be optional, either enter plain text or select a lexeme from the selector. I have no clue about how realistic or difficult to implement it could be. I created an image that I hope explains what I mean. 5628785a (talk) 17:42, 5 June 2024 (UTC)[reply]

User:Nikki/LinkLabelsToLexemes.js does that for labels/aliases (but not monolingual text). - Nikki (talk) 05:00, 6 June 2024 (UTC)[reply]
Nice work! But still, it would be nice to have it integrated in the Wikidata RDF data model, plus having the possibility of editing the links.--5628785a (talk) 13:37, 6 June 2024 (UTC)[reply]
@Danny_Benjafield_(WMDE): What steps do I need to take for the development team to consider this proposal?--5628785a (talk) 11:22, 9 June 2024 (UTC)[reply]
Hello @5628785a, thank you for ping'ing me. I would recommend leaving this message up for about a week to give others a chance to comment their thoughts, support and feedback on it.
  • In the meantime, I will take this to my PM to evaluate its feasibility.
  • If there are no objections, and the PM thinks it aligns with our development goals, I will create a Phabricator ticket for it and it will eventually get seen by one of our developers.
  • If it does not align with our development objectives, we will still keep a record of it for future updates to our development goals.
Thank you again, - Danny Benjafield (WMDE) (talk) 09:25, 10 June 2024 (UTC)[reply]

Can one do calculations with Wikidata?

[edit]

Hi,

I am brand new to Wikidata and am wondering whether one can use it for calculations. Here is the idea: we are seeking a way to derive party counts from government descriptions, in our case for European political parties represented in European institutions.

For instance, we would write that the German government has a coalition of the SPD, FDP and Greens. Separately, we would indicate that the SPD is a member of the European PES, that the FDP is a member of ALDE, and that the Greens are a member of the EGP.

Is there a way for this to lead to a counter which would show that the PES, ALDE, and the EGP each have 1 seat in government? This would apply to the Council of the European Union.

This idea is to then simply describe governments of European member states (and update them following elections) and to automatically populate counters in composition bars on pages relating to European political parties.

Thanks! 2A03:1B20:B:F011:0:0:0:A06D 10:24, 6 June 2024 (UTC)[reply]

I'm not exactly sure what you're asking. Maybe looking at https://query.wikidata.org/ would answer your question? The wikibase user interface itself won't do calculations but mediawiki instances that pull data from wikibase can. BrokenSegue (talk) 00:43, 7 June 2024 (UTC)[reply]

A book with different title on the cover and on the title page.

[edit]

I created an item for An Elegy on the Death and Burial of Cock Robin (Q126373391), which is a 1820 edition of the poem Cock Robin (Q4019610). On the cover, the book's title is "The Death and Burial of Cock Robin". On the title page, the book's title is "An Elegy on the Death and Burial of Cock Robin". I have put both values in the title (P1476) field for An Elegy on the Death and Burial of Cock Robin (Q126373391). However, when I try to add a qualifier to specify which one is associated with title page (Q1339862) and which one is associated with book cover (Q1125338), I keep running afoul of the property constraint (P2302) on title (P1476) for allowed qualifiers constraint (Q21510851) (not sure how to link it with templates, here's the direct link). What is the correct way to specify this information? Beleg Tâl (talk) 13:25, 6 June 2024 (UTC)[reply]

Long list of allowed qualifiers but I think qualifier applies to part (P518) is the best one for this case. –Samoasambia ✎ 23:39, 6 June 2024 (UTC)[reply]
Since most catalogs (e.g. WorldCat) seem to use the longer title ("An elegy of on..."), it might be good to set that as a preferred value for title (P1476). Covers of old books often have simpler titles which may omit subtitles, definite/indefinite articles (The, A, An) or other elements. Likewise, running headers at the tops of each page often use an abbreviated form. -Animalparty (talk) 01:20, 7 June 2024 (UTC)[reply]

Merge Q10267922 and Q113588564

[edit]

Please merge Q10267922 (pt:Dolo eventual) and Q113588564 (it:Dolo eventuale, et al.). Mathglot (talk) 06:16, 7 June 2024 (UTC)[reply]

Courtesy links: indirect intent (Q10267922), Q113588564 —Justin (koavf)❤T☮C☺M☯ 06:20, 7 June 2024 (UTC)[reply]

Can someone help me better model these events

[edit]

When I look at various annual shows, they are modeled slightly differently. I have 1914 Westminster Kennel Club Dog Show (Q107637781) and 1912 National Horse Show (Q126392669) to be improved. RAN (talk) 14:26, 7 June 2024 (UTC)[reply]

i took a stab at it BrokenSegue (talk) 15:27, 7 June 2024 (UTC)[reply]
This has been resolved. --RAN (talk) 16:29, 10 June 2024 (UTC)[reply]

Paul Rhoades

[edit]

the things who ever wrote about Paul Rhoades is not true. I am his sister. And before you talk about someone get your facts all the bullshit everyone writes is so far out of line. Maybe you shouldn't write about what you don't know. 2604:3DC0:1:AA0D:99AE:D311:6B4A:1862 21:50, 7 June 2024 (UTC)[reply]

If what you are saying is true and you are IRL related to Paul Ezra Rhoades (Q109860218) (??), you must've made it sure (before writing here) whether there is something in the Wikidata item besides what is known from the English Wikipedia or from publically available sources. Nothing special, let me guess so?.. We are ready to fix the inaccuracies if the item on very this site contains them and if you are going to point to them being more kindly than now. Have a great evening. --Wolverène (talk) 22:20, 7 June 2024 (UTC)[reply]
Probably something in the Wikipedia article or in Find a Grave, not Wikidata. Peter James (talk) 20:29, 8 June 2024 (UTC)[reply]

Occupation: neo-Nazi

[edit]

Can more people please watch Q30961105 Vita Zaverukha . Editor @Yarkovesh adds "Occupation: neo-Nazi" [1] providing a source which is not saying she works as "neo-Nazi" (anybody noticing absurd here?) Manyareasexpert (talk) 22:04, 7 June 2024 (UTC)[reply]

'Neo-Nazi' is not a kind of a job or a field of work. Also, she should not be persistently labeled as a Neo-Nazi activist, unless she or her closest allies admit(s) to such a definition. As we know, the propaganda in one of the countries located next to Ukraine claim as 'Neo-Nazi' everyone who fights for the UA Armed Forces, or just gives a helping hand to Ukraine. I mean, this way 'Neo-Nazi' means nothing relevant at all. I agree that that one is an incorrect value for the property. --Wolverène (talk) 22:42, 7 June 2024 (UTC)[reply]
Thanks! Manyareasexpert (talk) 22:54, 7 June 2024 (UTC)[reply]
Does your soul hurt so much for this girl that you can't leave her alone? Yarkovesh (talk) 15:08, 8 June 2024 (UTC)[reply]
Bellingcat says "reported neo-Nazi" in a caption, with a link to the Daily Mail, which is usually better than propaganda but not reliable. political ideology (P1142):neo-Nazism (Q151250) would be a valid statement but would require a better source. Peter James (talk) 20:00, 8 June 2024 (UTC)[reply]
We really ought to have a edit filter for these contentious statements Trade (talk) 00:16, 9 June 2024 (UTC)[reply]

Conflation

[edit]

Can someone help tease apart these two people conflated at Bernard Francfort (Q80651917)? RAN (talk) 18:21, 8 June 2024 (UTC)[reply]

I moved the subject of https://www.idref.fr/230217494 to Q126429057; it was only the date of birth and identifier that didn't belong to the original subject. This was probably caused by a conflation in IdRef - the 1904 works link to the author born in 1946. Peter James (talk) 19:17, 8 June 2024 (UTC)[reply]
This has been resolved. --RAN (talk) 16:29, 10 June 2024 (UTC)[reply]

Millon's Schizoid subtypes

[edit]

I wanted to make four items for the subtypes listed here but i could not figure what the correct modeling would be. Any suggestions? Trade (talk) 00:18, 9 June 2024 (UTC)[reply]


Question

[edit]

I have a table of around 1,800 Australian federal MPs in the below format containing their ID for Parliament of Australia MP ID (P10020). I want to link each to their corresponding wiki data item. Is there a quick way to do this?

Name P10020 ID number Date Of Birth Place Of Birth State Of Birth Country Of Birth Date Of Death Place Of Death State Of Death Gender Party State Electorate Senate State MP or Senator Service History: First Service History: Last Service History: Duration Age
ABBOTT, the Hon. Anthony (Tony) John AC EZ5 1957-11-04 London England Male Liberal Party of Australia New South Wales Warringah Member 1994-03-26 2019-05-18 25 years 2 month(s) and 1 days. 66.6

GMH Melbourne (talk) 05:44, 9 June 2024 (UTC)[reply]

I would recommend using OpenRefine. There you can reconcile the data based on the IDs. –Samoasambia ✎ 06:40, 9 June 2024 (UTC)[reply]

Merging two items regarding Ministry of Social Affairs (Indonesia)

[edit]

Is it possible to merge Ministry of Social Affairs (Q74529320) to Ministry of Social Affairs (Q11046702)? I think it is safe to assume that the scholary research organization is the ministry itself. Hans5958 (talk) 06:07, 9 June 2024 (UTC)[reply]

This doesn't sound logical to me, please don't merge different concepts. Sjoerd de Bruin (talk) 11:45, 9 June 2024 (UTC)[reply]
If you think these are different, then your edit Special:Diff/2174982241 was wrong. That belongs to Ministry of Social Affairs (Q11046702), and is already on that item (with slightly different capitalisation). - Nikki (talk) 01:52, 10 June 2024 (UTC)[reply]
You are correct, → ← Merged. Sorry, probably needed coffee yesterday! Sjoerd de Bruin (talk) 08:21, 10 June 2024 (UTC)[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Sjoerd de Bruin (talk) 15:33, 10 June 2024 (UTC)[reply]

Wikidata weekly summary #631

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-06-10. Please help Translate.

Discussions

  • Open request for adminship: Kadı - RfP scheduled to end after 14 June 2024 17:51 (UTC)
  • Closed request for adminship: The Squirrel Conspiracy - Closed as successful. Welcome back Squirrel!
  • New requests for permissions/Bot:

Events

  • Next Linked Data for Libraries LD4 Wikidata Affinity Group call June 11, 2024: We have our next LD4 Wikidata Affinity Group Call on Tuesday, 11 June, 2024 at 9am PT / 12pm ET / 17:00 UTC / 6pm CET (Time zone converter). Please join us for a community discussion on SMALL GLAM SLAM Pilot 1 with Ismael Olea. Link to agenda.
  • Celtic Knot Wikimedia Conference, September 25-27, 2024 in Waterford City, Ireland. This conference usually hosts Wikidata-related sessions. You can now propose your contributions to the program until July 14th, and apply for a scholarship until June 30th (full announcement and links)
  • WikiIndaba conference 2024, 4 - 6 October 2024 in Johannesburg, South Africa. This conference typically hosts Wikidata-related sessions. Program submissions 05 - 30 June 2024.

Press, articles, blog posts, videos

Tool of the week

  • Paulina: Data for the Public Domain - Explore the cultural heritage of humanity. Search Paulina by author and discover if they have freely accessible works in the Public Domain.

Other Noteworthy Stuff

  • Propose to transform an existing CSS or Javascript script (i.e. scripts that you can enable in your common.css and common.js pages) into a gadget: Wikidata:Tools/Potential gadgets

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • The UnpatrolledEdits gadget now shows a notice when there are older and multiple unpatrolled edits, previously it only showed the notice when the most recent edit was unpatrolled. Please help translate the messages here.
  • Query Service: We are fixing a bug where no examples are shown in the example dialog (phab:T366871)
  • EntitySchemas: We have enabled the new datatype for testing on test.wikidata.org and are preparing the rollout to Wikidata (phab:T365686)
  • Item UI: We fixed an issue where labels were not shown for badges or after making an edit (phab:T366236)
  • Wikibase REST API: We have continued the work on the route for modifying the data of an Item (phab:T342993)

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

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=2176175973"