Jump to content

Wikidata:Project chat

Shortcuts: WD:PC, WD:CHAT, WD:?
From Wikidata

Edit

(bidirectional?) links between disambiguation page and concrete items

What is current guideline for the topic in subject? Should they have relations? If so, which direction via which properties? Should such answers be found in Talk:Q4167410? Thanks

Examples : Trinomial coefficient (Q96152020) and trinomial coefficient (Q123472215) JuguangXiao (talk) 02:29, 28 May 2024 (UTC)[reply]

This has been asked a few times recently and I think the general consensus is no. Sjoerd de Bruin (talk) 08:12, 28 May 2024 (UTC)[reply]
I'd just have paired disambiguations between concrete items here, if they could be confused under our name/description system. WP disambiguation pages reflect the constraints of their no-duplicate name systems, and are of limited used as a second-level connection between items. Vicarage (talk) 08:16, 28 May 2024 (UTC)[reply]
In what way, do you pair them? JuguangXiao (talk) 12:53, 29 May 2024 (UTC)[reply]
different from (P1889) is sometimes okay if there's danger that someone in Wikipedia would try to merge sitelinks between the two. ChristianKl ❪✉❫ 08:37, 29 May 2024 (UTC)[reply]

P31 for firms and companies

For humans, we have a simple rule. P31 should always be human (Q5). This makes it very easy.

For organizations, the approach is much more complex. We can have a lot of values:

Is there any discussion about using one value for all organisations? I would propose to use organization (Q43229). PAC2 (talk) 20:18, 28 May 2024 (UTC)[reply]

There was some discussion on the WikiProject_Organizations talk page in December/January, off the back of Data Modelling Days 2023. I have no idea if discussion or work have progressed elsewhere on that front, though. M2Ys4U (talk) 21:38, 28 May 2024 (UTC)[reply]
See Wikidata:WikiProject_Companies/Properties. business (Q4830453) is preferred, enterprise (Q6881511) and organization (Q43229) are broader terms (but not wrong). --Jklamo (talk) 00:26, 31 May 2024 (UTC)[reply]

Wikidata Infobox image

Hi. At Category:Megan Compain over at Commons, the Wikidata Infobox image is showing as this image but the wikidata image for Megan Compain is this image. I can't figure out how to get the image to update. I have tried opening the page on multiple devices and browsers, so I don't believe it is cache and cookies related. Thanks in advance. DaHuzyBru (talk) 12:04, 29 May 2024 (UTC)[reply]

Try purging the page, it's a cache issue. Sjoerd de Bruin (talk) 13:22, 29 May 2024 (UTC)[reply]

Re: New EntitySchema data type is ready for testing on Test Wikidata

Hello,

You may recall our previous announcement inviting you to test a new EntitySchema datatype on Test Wikidata. Once fully implemented, this data type will allow editors to refer to existing EntitySchemas in statements to indicate what class of Items are governed by an EntitySchema for example. Many thanks to everyone who provided feedback during the initial testing phase.

Based on your input, we have reassessed the architecture of the datatype. It should now return as a ‘wikibase-entityid’ when accessed through the API. See phab:T339920 for more information on this.

In addition to this update, we have made the following improvements:

  • Improved Display: EntitySchemas linked in statements, Wikitext, edit summaries and Special Pages are now displayed by their labels instead of their IDs, making them more readable and easier to understand.
  • Language Support: We've added support for language fallback to ensure EntitySchemas are legible across different languages.

We invite you to test these changes once again and provide us with your feedback by June 6. Unless any major issues arise, we will enable the new datatype on Wikidata during the next train deployment. Once this is done, the open property proposal at Wikidata:Property_proposal/Pending#Shape_Expression_for_class can be created.

Please note when testing: the data type still needs to be registered with Wikibase Client to ensure full accessibility of Items with EntitySchema statements on client wikis. See phab:T363153 for more information on this.

If you encounter any issues, have questions or concerns, or want to provide feedback, please don’t hesitate to reach out to us on Wikidata talk:Schemas or leave a comment on this ticket (phab:T332157).

Cheers, -Mohammed Abdulai (WMDE) (talk) 13:32, 29 May 2024 (UTC)[reply]

1 year old vandalism not undone

https://www.wikidata.org/w/index.php?title=Q289058&diff=1896359096&oldid=1873684513 Rostworowski (talk) 14:38, 29 May 2024 (UTC)[reply]

https://www.wikidata.org/w/index.php?title=Wikidata%3ARequests_for_checkuser%2FCase%2FMrProperLawAndOrder&diff=2161755106&oldid=2029518263 . Multichill (talk) 16:34, 29 May 2024 (UTC)[reply]

Using Wikidata as an upstream for device information

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 storage 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 diskstorage capacity (P2928)128 GB and phone model Xhas part(s) (P527)RAMstorage capacity (P2928)8 GB. In practice, you find people saying storage capacity (P2928)128 GB{{{3}}} or storage 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]

Property label no longer displayed when adding a statement

Tracked in Phabricator
Task T366275
Tracked in Phabricator
Task T366236

When I add a statement, after saving, property PID are displayed instead of property label. I need to reload the page to have them correctly displayed. Are you facing the same issue? Ayack (talk) 07:42, 30 May 2024 (UTC)[reply]

Same as me.--S8321414 (talk) 12:42, 30 May 2024 (UTC)[reply]
+1. After reloading, the property label is displayed as usual. –Morneo06 (talk) 13:47, 30 May 2024 (UTC)[reply]
Ping @User:Lucas Werkmeister (WMDE), @User:Mohammed Abdulai (WMDE). Ayack (talk) 13:55, 30 May 2024 (UTC)[reply]
Thanks for reporting this issue. We're on it and already have a fix. However, the deployment will wait until early next week. -Mohammed Abdulai (WMDE) (talk) 14:08, 30 May 2024 (UTC)[reply]
Noted. Thanks @Mohammed Abdulai (WMDE). Ayack (talk) 14:24, 30 May 2024 (UTC)[reply]

br.wikipedia.org

Hello,

Could you validate and link between the breton language Wikipedia and others for the next two articles:

Thanks you,

MP (talk) 17:00, 30 May 2024 (UTC)[reply]

✓ Linked. --Wolverène (talk) 17:10, 30 May 2024 (UTC)[reply]

Items created using WikiShootMe

In a discussion on Discord, one user mentioned an item that he noticed, which seems to fail our notability guidelines: Q113319514 (it's just one of many power line pylons...). Looking at user:HighVoltage 5576 contributions, it seems that there are more such items. Is there any reason why these items exist in WD? Wostr (talk) 20:42, 30 May 2024 (UTC)[reply]

I thought wikishoot me was about images? but these items have no images? i'm confused. but yeah these items don't seem to be notable. BrokenSegue (talk) 23:49, 30 May 2024 (UTC)[reply]
I agree, no notability seen. Sjoerd de Bruin (talk) 09:26, 31 May 2024 (UTC)[reply]
@Magnus Manske: WikiShootMe seems to have a function to create a new Wikidata item for a Commons image (the blue circles). No mention at all about the notability policy. :-( Some sort of notification ought to be displayed the first time someone tries to use this functionality. Infrastruktur (talk) 09:44, 31 May 2024 (UTC)[reply]
Going to delete most of the power-line/pylon items. Not sure if the items for the electrical substations are worth keeping. Items for things like power stations should be notable. Infrastruktur (talk) 10:10, 31 May 2024 (UTC)[reply]
@Infrastruktur, Wostr, BrokenSegue, Sjoerddebruin, HighVoltage 5576: High-voltage pylons may be notable, dominant and distinctive, as well as other towers and masts. In areas that are thematically better covered, items are normally created and used for individual objects such as weirs, bridges, sculptures, bus or tram stops, railway crossings, houses, towers and masts, streets etc. A high-voltage pylon is certainly comparable in importance to them, especially when it has its own systematical identifier. This especially applies for pylons in a dominant position, but I don't think it's excessive to document main power lines pylon by pylon. The distance between such pylons is typically 300–500 meters – if it crosses a valley, it can be even a kilometer. As a rule, these are important orientation and landscape-forming structures. As a permanent registered structure of considerable size, such a pylon undoubtedly fulfills criterion 2 of Wikidata:Notability. In particular, if the pylon has it's photo here, it is advisable to identify it using its item to which the photograph is associated. However, a discussion can be held as to which types of power lines are so significant and which do not reach such significance to be elaborated in such detail. For my region, 400 kV and 220 kV (and some 110 kV) lines are the main long-distance lines. In some countries, also 750 kV lines are used. For local systems (35 kV, 22 kV, 15 kV, 10 kV, 6 kV), I would rather not consider individual masts to be significant - they are rather poles than pylons. But it can be open to debate whether it might make sense to import detailed street-furniture and infrastructure databases if they were available. --ŠJů (talk) 14:26, 2 June 2024 (UTC)[reply]
Reminds me about that time I asked if bus stops were considered notable, since they are after all semi-permanent infrastructure, although they don't form stable networks. Train networks don't have this problem. First things first, the items I deleted were technically not notable per WD:N since they lacked sitelinks, references or IDs, not even less "serious" ones. Nor were they interlinked. When I say that power stations are notable I mean there is significant precedence for those items, they are also of public interest.
I think section two of the notability policy is the only bad part of it. Often it is used as a poor excuse to keep items of dubious notability, it also does not lend itself to being easily assessed. What we should have accompanying that rule is granularity standards for what to include given no sitelinks. Example: Wikipedia sometimes have articles on a single house because it is interesting somehow, but I think you can agree it would be excessive to list houses in general. There are a lot of houses and very few of them are of public interest. You can also find official identifiers for houses, but none that implies notability.
Earlier I discovered that some dude had painstakingly documented the Australian power-grid. He did this down to the substation level. He did not document individual stretches of power-lines or pylons, he did however document the HV power-lines as a whole, which can be quite long. The granularity is reasonable here IMO. I would not consider intermediate voltage or consumer voltage lines notable. Infrastruktur (talk) 19:06, 2 June 2024 (UTC)[reply]
In Wikipedia, the question is often whether an item on it's own is of public interest. In Wikidata, we often have cases where a data set is of public interest even if the individual items on their own wouldn't be.
WD:N (2) says "It refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references." It technically says "can" and not "are". That said, unfortunately we don't have infinite space on Wikidata and storing more data comes with a cost as shown in the proposed split of the citation graph. ChristianKl ❪✉❫ 08:39, 3 June 2024 (UTC)[reply]
I don't have any particular opinion on documenting HV lines pylon-to-pylon, but doesn't that sound more suitable for OpenStreetMaps? Infrastruktur (talk) 19:39, 2 June 2024 (UTC)[reply]
@Infrastruktur: It is a question of whether Wikidata can go to the same level of detail as map projects for some topics and some types of objects. Anyway, Wikidata goes into greater detail than Wikipedia's ambitions are. Individual benches, trash bins, post boxes or street light poles would seem excessive to me for Wikidata. However, items for high-voltage pylons, transformer towers, bus stops, level crossings, bridges or weirs sometimes make sense. In localities that have some cultural and historical value, it may make sense to register all address points (buildings). The purpose of Wikidata is relatively open - originally it was created primarily as a support for an encyclopedia, but at the same time it also serves as a support for a photography project and can potentially also serve as a database and metadata repository for map projects. --ŠJů (talk) 12:02, 3 June 2024 (UTC)[reply]

Merged wrongly

I merged into the wrong phrase Absperrhahn into Absperrarmatur. It shouldve been the other way around. I even messed up trying to fix it, sry. LetztesSagen (talk) 05:10, 31 May 2024 (UTC)[reply]

Swedish military history

There is a "Wieriska lantmilisregemente" mentioned in a biography, but I do not see it listed in Wikidata. At one time all the Swedish historical regiments had entries. Perhaps it is misspelled, and ideas? See: Hans Christoffer von Rohr II (1684-1754) biography (Q109269711) RAN (talk) 13:31, 31 May 2024 (UTC)[reply]

Seem to refer to a infantry regiment stationed in Wierland county present day Estonia. Infrastruktur (talk) 14:08, 31 May 2024 (UTC)[reply]

What's going on wish qualifiers?

https://i.imgur.com/2cKg8oA.png Not being able to read them properly is really annoying Trade (talk) 16:19, 31 May 2024 (UTC)[reply]

See #Property label no longer displayed when adding a statement. Sjoerd de Bruin (talk) 16:32, 31 May 2024 (UTC)[reply]

Could someone please merge these?

https://www.wikidata.org/wiki/Q96000113 is a more recently-created duplicate of https://www.wikidata.org/wiki/Q28357688 .

I'm not a Wikidata geek, just someone who has created the en.wiki article on this Estonian-born singer (described in various sources as Russian or German).

I tried to merge them using Special:MergeItems: it said there was a conflict in the English descriptions, so I edited the newer one to remove all language descriptions. It then said there was a conflict in language "ast" description. At this point, I give up. Could someone who knows their way around Wikidata please combine the records? Thanks! PamD (talk) 07:39, 1 June 2024 (UTC)[reply]

On checking again, I removed the descriptors from the wrong version, so have reinstated them. PamD (talk) 07:42, 1 June 2024 (UTC)[reply]
Aaargh: a bot has created a third entry at https://www.wikidata.org/wiki/Q126227498 on the basis of my en.wiki article. PamD (talk) 07:45, 1 June 2024 (UTC)[reply]
I have removed the en.wiki link from Q126..., and added it to the oldest Wikidata record, Q283... . PamD (talk) 07:49, 1 June 2024 (UTC)[reply]
✓ Done (Please check that nothing has been lost. I am not familiar with the subject.) -- Cl3phact0 (talk) 07:56, 1 June 2024 (UTC)[reply]
@Cl3phact0 Looks good. Thanks. PamD (talk) 15:22, 1 June 2024 (UTC)[reply]

Invalid regex on P304

The regex for format constraint on page(s) (P304) is invalid. Could someone familiar with P304 fix it? Thanks DaxServer (talk) 11:17, 1 June 2024 (UTC)[reply]

If it's the error in regex101 "\x{10EAD} The character offset is too large" it's because the link to regex101 doesn't include the flags; the default is "/gm" but with "u" (for Unicode) added there are no errors. Adding "&flags=gmu" to the end of the regex101 URL also works. The bot that creates the constraint violations page can use the regex, although I don't know if that character (the Yezidi hyphenation mark) is recognised by the bot as I haven't found anywhere it is used. Peter James (talk) 15:45, 1 June 2024 (UTC)[reply]
Thanks @Peter James, I've made a comment to enable Unicode support in OpenRefine https://github.com/OpenRefine/OpenRefine/issues/1768 DaxServer (talk) 16:19, 1 June 2024 (UTC)[reply]

Proposals of transforming scripts into gadgets

Hi all! It has long been discussed, both here in Wikidata, on the Telegram group and in many events (lastly, as far as I remember, two months ago in the session "A few useful gadgets and scripts for Wikidata" in Wikidata:Events/Leveling Up Days 2024), that we have no standard procedure to promote CSS and Javascript scripts to gadgets. Sometimes proposals are made here in the Project chat, but it is difficult to follow them because in the Project chat many threads of every sort are opened frequently. As in the past I had created Wikidata:Tools/Proposals to collect proposals of new tools, I have just created also Wikidata:Tools/Potential gadgets in order to collect in a single place the proposals of transforming existing scripts into gadgets. Whilst I agree with the opinion expressed by many users that we don't need a formally structured process for a script to be approved as gadget (a certain number of users expressing their support, a minimum number of days for the discussion etc.), I think having a page to collect all these proposals would make it easier for interface administrators to follow these procedures and would probably encourage users in general to make such proposals. Of course feel free to propose improvements to the page (both the header and the title), here or in its talk page! --Epìdosis 17:05, 1 June 2024 (UTC)[reply]

It would be good to be also clear about how gadgets get updated/removed if we make the process more open. ChristianKl ❪✉❫ 09:41, 2 June 2024 (UTC)[reply]

Angelina Mango (Q118390992) and Angelina Mango discography (Q124661336)

Some identifiers have been duplicated. i.e. AllMusic artist ID (P1728), Discogs artist ID (P1953), Genius artist ID (P2373), MusicBrainz artist ID (P434), and YouTube channel ID (P2397).-- Carnby (talk) 07:06, 2 June 2024 (UTC)[reply]

So delete them. Sjoerd de Bruin (talk) 14:06, 2 June 2024 (UTC)[reply]
In which item?-- Carnby (talk) 19:55, 2 June 2024 (UTC)[reply]
The discography one. Sjoerd de Bruin (talk) 20:03, 2 June 2024 (UTC)[reply]

Hyphenated surname

Should a hyphenated surname (for example, in the name of Ulrike Janssen-Bienhold (Q87885011)) be treated as a single surname (which would created a new surname Q for Janssen-Bienhold) or as two surnames, Janssen and Bienhold? I think that a single surname is the correct answer, but I would like to be certain. Eastmain (talk) 08:01, 2 June 2024 (UTC)[reply]

@Eastmain: IMHO a hyphenated surname can mean one surname containing a hyphen, as well as two various surnames (or even two people can be joined with a hyphen – incorrectly, instead of a dash). The customs of the language, country and period must be taken into account. As for the combination of birth surname and acquired surname, I would think of it as two surnames. When it comes to hereditary double surnames (for example, in the case of merged or divided noble families), it would be possible to treat them also as one surname. --ŠJů (talk) 09:40, 2 June 2024 (UTC)[reply]
@ŠJů@Eastmain: at several places this topic has been discussed. My clear opinion is that double family / double given names should be banned in Wikidata. Otherwise we end like auto-generated categories in other Wikiprojects, e.g. Commons:Category:Amalie Louise of Courland. Some discussion here: https://www.wikidata.org/wiki/Topic:Wwm2h3w8gw02roi1 Estopedist1 (talk) 07:33, 3 June 2024 (UTC)[reply]

How to represent filter size on a camera lens?

See Canon EF 70-300mm F4-5.6 IS USM (Q126286127) for an example. Interchangeable camera lenses have a lens mount on one end, and a threaded attachment for a lens filter on the other. The lens mount is described using connector (P2935), and I've also included a value of "some value", qualifiers applies to part (P518) pointing to photographic filter (Q876650) and diameter (P2386) pointing to actual number, to describe the filter size.

I think I'm working around something; when I tried to add photographic filter (Q876650) as a value for connector (P2935), I got a constraint error, because the value isn't a subclass or instance of electrical connector (Q2119531), optical fiber connector (Q2296938), or lens mount (Q205722).

Should the constraint be expanded, or am I expressing this incorrectly, or both? Grendelkhan (talk) 18:00, 2 June 2024 (UTC)[reply]

Announcing the first Universal Code of Conduct Coordinating Committee

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Hello,

The scrutineers have finished reviewing the vote results. We are following up with the results of the first Universal Code of Conduct Coordinating Committee (U4C) election.

We are pleased to announce the following individuals as regional members of the U4C, who will fulfill a two-year term:

  • North America (USA and Canada)
    • –
  • Northern and Western Europe
  • Latin America and Caribbean
    • –
  • Central and East Europe (CEE)
    • —
  • Sub-Saharan Africa
    • –
  • Middle East and North Africa
  • East, South East Asia and Pacific (ESEAP)
  • South Asia
    • –

The following individuals are elected to be community-at-large members of the U4C, fulfilling a one-year term:

Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.

Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. Follow their work on Meta-wiki.

On behalf of the UCoC project team,

RamzyM (WMF) 08:14, 3 June 2024 (UTC)[reply]

Lexicodays, online event dedicated to Lexicographical Data, on June 28-30, 2024

- Indonesian version below -

Hello all,

Have you ever wondered how Wikidata stores and models words? How to create and improve Lexemes in your languages? Or even why it is useful and which projects could benefit from it?

The Lexicodays 2024 will answer these questions, and many more. During this online event, you will be able to learn more about Lexicographical Data on Wikidata, to discover how to model words in your languages, and to try out various tools that make it easier to work on Lexemes. It offers a space for editors involved in creating and maintaining Lexemes to discuss their ideas, challenges and best practices.

The online event will take place on June 28, 29 and 30, with sessions replicated in different languages and at different times across time zones. It is co-organized by Wikimedia Deutschland and the Software Collaboration Team in Indonesia, and we will focus on the languages of Indonesia and the Wikidata community in Indonesia. The event is open to everyone regardless of their knowledge of Lexemes. Most sessions will be recorded and published after the event.

On the main event page, you can discover the structure of the program, which will keep evolving in the upcoming weeks. We are also welcoming proposals for the program until June 20th - we are particularly interested in introductions to Lexicographical Data in different languages, and discussions run by community members on how to improve modelling and documentation in a specific language.

We will launch registration for the event in the upcoming days - if you’re interested, stay tuned by following the talk page or joining the Lexicographical Data Telegram group.

If you have any questions, feel free to write on the talk page of the event. See you soon, Léa (Lea Lacroix (WMDE)) and Raisha (Fexpr).

---

Halo, teman-teman!

Pernahkah Anda bertanya-tanya bagaimana Wikidata menyimpan dan memodelkan kata-kata? Bagaimana cara membuat dan meningkatkan Leksem dalam bahasa yang Anda tuturkan? Kenapa Leksem itu bermanfaat? Proyek-proyek apa yang akan terbantu dengan adanya Leksem ini?

Lexicodays 2024 akan menjawab pertanyaan-pertanyaan tersebut, dan masih banyak lagi. Selama acara daring ini, Anda akan dapat mempelajari lebih lanjut mengenai Data Leksikografis di Wikidata, menemukan cara memodelkan kata-kata dalam bahasa Anda, dan mencoba berbagai perkakas yang memudahkan Anda dalam menyunting Leksem. Acara ini membuka ruang bagi para penyunting yang terlibat dalam pembuatan dan pemeliharaan Leksem untuk saling berdiskusi mengenai ide, tantangan, maupun praktik-praktik terbaik.

Acara daring ini akan berlangsung pada tanggal 28, 29, dan 30 Juni, dengan waktu penyelenggaraan yang tersebar dalam beberapa zona waktu dan sesi-sesi serupa yang diantarkan dalam bahasa-bahasa yang berbeda. Acara ini diselenggarakan bersama oleh Wikimedia Deutschland dan Tim Kolaborasi Perangkat Lunak di Indonesia. Fokus dari acara ini adalah untuk bahasa-bahasa yang dituturkan di Indonesia dan komunitas Wikidata di Indonesia. Acara ini terbuka untuk siapa saja, terlepas dari seberapa akrab Anda dengan Leksem. Kami akan merekam sebagian besar sesi dan mempublikasikannya setelah acara selesai.

Anda dapat mengakses jadwal kegiatan pada halaman beranda acara, yang akan terus kami perbarui dalam beberapa pekan ke depan. Kami juga mengadakan panggilan terbuka untuk pengajuan proposal kegiatan hingga tanggal 20 Juni. Kami sangat tertarik dengan pengenalan Data Leksikografis dalam berbagai bahasa, dan diskusi yang dilakukan oleh anggota komunitas mengenai cara meningkatkan pemodelan dan dokumentasi dalam bahasa tertentu.

Kami akan membuka pendaftaran untuk acara ini dalam beberapa hari mendatang. Apabila Anda tertarik, silakan pantau terus laman pembicaraan ini atau bergabunglah dengan grup Telegram Data Leksikografis.

Jika Anda memiliki pertanyaan, jangan ragu untuk menulis di laman pembicaraan acara Lexicodays 2024. Sampai jumpa, Léa Lea Lacroix (WMDE) dan Raisha Fexpr. Lea Lacroix (WMDE) (talk) 08:58, 3 June 2024 (UTC)[reply]

Wikidata weekly summary #630

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-03. Please help Translate.

Discussions

  • Open request for adminship: The Squirrel Conspiracy - RfP scheduled to end after 9 June 2024 06:47 (UTC).
  • New requests for permissions/Bot: TongcyBot - Task: Linking the Chinese and English Wiktionary, specifically in categories using Template:auto cat, and pages in the Template, Module, Appendix, Reconstruction, and Rhymes namespaces.
  • Open request for permissions/Bot: IliasChoumaniBot - Task: Automatic updating of data from JSON files on German scientists.
  • Closed request for comments: IP Masking Engagement - The RfC was closed due to inactivity. Discussions are still welcomed on Meta.

Events

Press, articles, blog posts, videos

Tool of the week

  • WikiTwister - RoloWiki: Replace the interwiki links of a Wikipedia article with a pop-up card full of useful Wikidata, & Wikidata Quick Dip: Browse the Wikidata properties used by the pages in a category.

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

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

People falsely claiming Native American heritage

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]

Renaming the Community Wishlist Survey

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)

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]

Using illustrate_wikidata.py to get images from a commonscat ?

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]
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=2172394695"