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

Wikidata:Project chat

From Wikidata
(Redirected from Wikidata:Help desk)
Jump to navigation Jump to search

Edit

Class instances of physical object (Q223557)

[edit]

There are several classes in Wikidata where it seems clear from their description that their instances cannot be classes. The most obvious of these is physical object (Q223557), but there is also concrete object (Q4406616). These classes are also instances of first-order class (Q104086571), the class of all classes whose instances are not classes, or subclasses of its instances giving further evidence that their instances cannot be classes. Of course, if the instances of these classes cannot be classes then so also for their subclasses, including, for example, physical tool (Q39546).

However, in Wikidata there are currently many instances of these classes for which there is evidence in Wikidata that they themselves classes, either having instances themselves or having superclasses or subclasses. For example, there were recently 1,821,357 instances of physical object (Q223557) that fit one or more of these criteria, out of 21,154,884 instances of physical object (Q223557), an error rate of 8.6 per cent. (These numbers come from the QLever Wikidata query service, as the WDQS times out on the queries.) This is very likely an undercount of class instances of physical object (Q223557), as there are items in Wikidata that are classes but that have neither instances, superclasses, or subclasses in Wikidata, such as R3 device (Q7274706).

I propose trying to fix these problems. It is not necessary to make nearly two million corrections to Wikidata as in many cases a single change to Wikidata can fix the problem for many of these class instances. For example, there are at least 764,424 items related to protein (Q8054) involved so determining what to do with protein (Q8054) may fix a large part of the problem.

In many cases fixing these problems requires making a decision between several different ways forward. For example, airbag (Q99905) could be determined to be a class of physical objects, and thus stay a subclass of physical object (Q223557) but would have to have its class instance changed to a subclass. Alternatively, airbag (Q99905) could be determined to be a metaclass, and thus would need to be removed from the subclasses of physical object (Q223557) and probably be stated to be is metaclass for (P8225) physical object (Q223557). It would be useful to have a consistent treatment of involved classes like this one.

So who is interested in trying to address this large number of errors in Wikidata? This effort is likely to take some time and could have a larger discussion than is common here so I have created a page in the Wikidata Ontology Project for the effort. If you are interested please sign up on that page. Peter F. Patel-Schneider (talk) 14:03, 13 September 2024 (UTC)[reply]

I think as a very general rule instance of (P31) is overused and subclass of (P279) underused in Wikidata, and where things are ambiguous the right choice is to replace a instance of (P31) statement with subclass of (P279). The vast majority of items in wikidata are concepts, designs, etc., not physical objects. Yes there are lots of individual people or geographical or astronomical objects, but it is rare to have notable actual instances of most concepts. ArthurPSmith (talk) 19:36, 13 September 2024 (UTC)[reply]
Agreed. But it does not appear to be reasonable to just replace all instance of (P31) under physical object (Q223557) with subclass of (P279) as there are actual physical objects there, for example items in museum collections. And it is not sufficient to just do this only for those items for which there is evidence in Wikidata that they are classes because there are items in Wikidata that are classes in the real world but there is no information in Wikidata signalling this. Peter F. Patel-Schneider (talk) 13:38, 16 September 2024 (UTC)[reply]

How to replace a statement to another

[edit]

Hi, editing Amagasaki Domain (dissolved in 1871), I found its statement "located in the administrative territorial entity" Property:P131 should be rather "located in the present-day administrative territorial entity" Property:P3842. OTOH I already added some elements to this statement and don't want to waste them. So I tried to edit the source of that page but found no way.

In addition, I'm afraid other * Domain entities might share the same problem, but have no time to dig it up deeper, now that 1:49 at my local time. There were around 300 Domains in Japan at that period (from 1600 till 1871).

Can anyone kindly suggest me what's the best to manage that?

Cheers. --Aphaia (talk) 16:52, 13 September 2024 (UTC)[reply]

The Move Claim gadget will do this for you. - PKM (talk) 01:59, 15 September 2024 (UTC)[reply]
@PKM How does one install this gadget? Peter F. Patel-Schneider (talk) 20:49, 17 September 2024 (UTC)[reply]
@Peter F. Patel-Schneider: Go to Special:Preferences#mw-prefsection-gadgets and tick the box next to moveClaim. Dexxor (talk) 08:44, 18 September 2024 (UTC)[reply]

deidetected.com, a self-published source potentially used for harassment

[edit]

This website launched and run by the creator of the "Sweet Baby Inc detected" Steam curator would fall under the definition of a self-published source on Wikipedia. The Steam curator has been linked to the harassment campaign against Sweet Baby Inc. by reputable sources like PC Gamer, The Verge, and multiple others.

Wikidata has a page for the website, with the website linked via the described at URL property, by User:Kirilloparma on more than one if not every occasion. Even within the scope of that source, it is done in a very targeted way in that the website seems to be added to the Wikidata pages only when the game is recommended against at deidetected.com (e.g. The First Descendant, Abathor, Valfaris: Mecha Therion recommended as "DEI FREE" by deidetected do not have the property set). Based on that, its goal of harassment or POV pushing appears to be evident.

Does Wikidata have any guidelines that would explicitly allow or disallow this behavior or the coverage of deidetected.com at all? Daisy Blue (talk) 09:45, 14 September 2024 (UTC)[reply]

There is no policy on WD for blacklisting websites for other than malicious cases such as spam or malware Trade (talk) 11:59, 14 September 2024 (UTC)[reply]
Now from having read the property description for described at URL on its talk page, which explains that it's for "reliable external resources", I'm convinced the website has no place on Wikidata, as it's not a reliable source (at least not per the guidelines of Wikipedia (WP:RSSELF)). What is the best place to initiate its removal without having to start a potential edit war? A bot would also do a more efficient job at removing it from all the pages. Daisy Blue (talk) 12:03, 14 September 2024 (UTC)[reply]
You might have more luck if you stopped bringing up Wikipedia guidelines and used the Wikidata ones instead Trade (talk) 00:09, 15 September 2024 (UTC)[reply]
Wikidata itself cites the Wikipedia guidelines on self-published sources (and on original research). Daisy Blue (talk) 05:04, 15 September 2024 (UTC)[reply]
English Wikipedia policy is im many cases useful to decide what should be done in Wikidata (e.g. which sources are reliable), but should never be considered normative and have no more authoritativeness than policies in any other project. GZWDer (talk) 06:37, 15 September 2024 (UTC)[reply]

This could be used to mass undo 18 of the edits that introduced the links, but it's not progressing for me when trying. Daisy Blue (talk) 11:14, 15 September 2024 (UTC)[reply]

Seems like a low-quality, private website that doesn't seem to add anything of value to our items. There are countless websites out there, but we generally don't add every single site via described at URL (P973) just for simply existing. IIRC, there were various cases in the past where users added unreliable websites to lots of items, that were then considered spam and deleted accordingly. And if the site's primary purpose is indeed purely malicious and causing harassment, there's really no point in keeping it. Best to simply put it on the spam blacklist and keep the whole culture war nonsense out of serious projects like Wikidata. Additionally, DEIDetected (Q126365310) currently has zero sources indicating a clear lack of notability. --2A02:810B:5C0:1F84:45A2:7410:158A:615B 13:50, 15 September 2024 (UTC)[reply]

I've already nominated that and Sweet Baby Inc detected for deletion citing the same reason, though specifically for the curator, one could stretch point 2 of Wikidata:Notability to argue against it, but I'm not sure what value it would bring to the project apart from enabling harassment and its use to justify any other related additions. Daisy Blue (talk) 16:06, 15 September 2024 (UTC)[reply]
Just add this website to the spam blacklist, no one will be able to add links to this website on Wikimedia projects anymore. Midleading (talk) 17:18, 16 September 2024 (UTC)[reply]
What's the proper venue for proposing that? Also, seeing how you have a bot, could you suggest a quick way to mass remove the remaining instances from Wikidata? I've already undone a number by hand but it's not the greatest experience. Having the knowledge may also help in the future. Daisy Blue (talk) 18:24, 16 September 2024 (UTC)[reply]
On the home page of Meta-Wiki, click Spam blacklist, and follow instructions there.
To clean up links to this website, I recommend External links search. A WDQS search is likely to time out. I also recommend reviewing each case manually, sometimes the item should be nominated for deletion, but tools can't do that. Midleading (talk) 01:27, 17 September 2024 (UTC)[reply]
Thanks. I'll remove the rest by hand then. As for the Wikimedia spam blacklist, it says that "Spam that only affects a single project should go to that project's local blacklist". I'm not sure if there have been any attempts to cite deidetected on Wikipedia or elsewhere. We can search for the live references (there are none) but not through the potential reverted edits, I don't think. Daisy Blue (talk) 07:33, 17 September 2024 (UTC)[reply]
Well, you may request this website be banned on Wikipedia first, then you may find some users who agree with you. Midleading (talk) 08:45, 18 September 2024 (UTC)[reply]
I believe Wikipedia has the same policy in that if it hasn't been abused (and I wouldn't know if it has been specifically on Wikipedia), then there is no reason to block it. On Wikidata, as it stands now, the additions come from one user, Kirilloparma, who pushed back on my removals here but hasn't reverted. Unless it becomes a sustained effort by multiple users, it will come down to whether Kirilloparma concedes that described at URL is for reliable sources and the website is not a reliable source. Daisy Blue (talk) 12:14, 18 September 2024 (UTC)[reply]
For some reason Kirilloparma keeps making points on the subject on the Requests for deletions page rather than here (despite having been informed), now arguing that the short property description takes precedence over the property documentation on the talk page, which is dismissed as "outdated". Daisy Blue (talk) 09:29, 20 September 2024 (UTC)[reply]

Basic instructions are lacking

[edit]

Editors with experience editing English Wikipedia who find ourselves here in Wikidata need a lot more handholding than is currently provided. I was editing the Wikipedia article en:User:Stitchbird2/sandbox, which includes a reference in this Wikidata space, Sinopsis de las especies austroamericanas del género Ourisia (Scrophulariaceae) ... which, when I came, did not have the genus name Ourisia in italics. I came to this page and tried to italicize the genus name, and I assumed that, like Wikipedia, surrounding something with two apostrophes, before and after, causes italics. Did I do it right? If so, why does the User sandbox article show the genus name with two apostrophes before and after, instead of treating the two apostrophes before and after as italic markup? Please, Wikidata needs instructions for this sort of thing. If they exist, tell me where and make them easier to find. If they don't exist, they need to be created. Signing off with four tildes, does that work? I guess I'll find out. Anomalocaris (talk) 03:46, 15 September 2024 (UTC)[reply]

For more information on item labels you can read Help:Label. The section "Fonts and characters" has a good explanation. William Graham (talk) 05:21, 15 September 2024 (UTC)[reply]
All right, I reverted my changes to the item mentioned above. Anomalocaris (talk) 07:33, 15 September 2024 (UTC)[reply]
@Anomalocaris: You may also find title in HTML (P6833) and/or title in LaTeX (P6835) useful, though I have no idea if either of them are used by the English Wikipedia templates used in your article. (You can try it out on Wikidata Sandbox (Q4115189) if you like.) Lucas Werkmeister (talk) 10:13, 16 September 2024 (UTC)[reply]

Wikidata weekly summary #645

[edit]
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2024-09-16. Please help Translate. Missed the previous one?
See issue #644

Discussions

  • New requests for permissions/Bot: Framabot 5 - Task: update a typography error in the French description of homonym pages, seen on 1.
  • New request for comments: Additional rights for bureaucrats - The proposal suggests allowing Wikidata bureaucrats to remove admin rights, which they currently cannot do, to streamline processes, reduce reliance on stewards, and align with practices of other wikis.
  • Proposal: Mul labels - proposal of massive addition - The proposal suggests massively adding "mul" labels to Wikidata items for given and family names, using a bot to streamline the process and reduce redundant labels.

Events

  • Next Linked Data for Libraries LD4 Wikidata Affinity Group session 17 September, 2024: We have our next LD4 Wikidata Affinity Group Session on Tuesday, 17 September, 2024 at 9am PT / 12pm ET / 17:00 UTC / 6pm CET (Time zone converter). 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 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: Session 2 (September 17) - Working session using Mix‘n’Match to add Wikidata items
  • Wikidata Day 2024 (Seattle) - Agenda: Wikidata Twelfth Birthday, Training and Edit-a-thon. When: Saturday, October 26, from 12:30–4:30pm PDT

Press, articles, blog posts, videos

Tool of the week

  • User:Lagewi/references.js - "Sometimes, the data on Wikidata does not answer all your questions. Some types of information are difficult to encode in statements, or simply has not been encoded on Wikidata yet. In such cases, it might be useful to go through the references attached to claims of the entity, for additional information. To simplify this process, this user script lists all unique references based on stated in (P248) and reference URL (P854). The references are listed in a collapsible list below the table of labels and descriptions, collapsed by default to not be obtrusive." To enable it, include the following line in your common.js: mw.loader.load('//www.wikidata.org/w/index.php?title=User:Lagewi/references.js&oldid=2039248554&action=raw&ctype=text/javascript');

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • The development team attended the annual WMDE Software Department retreat, so there wasn't much development activity this week.

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

Petscan not returning full results list?

[edit]

Hi everyone! Over the weekend I used Petscan to add a bunch of P27 statements to items based on "Japanese people by occupation" categories. My hope was to reduce the number of results in this query that contains items with a link to jawiki that only have P31:Q5, since I usually fill in each item by hand. However, I was really disappointed to find that the number of results in the query didn't change at all. There's simply no way that there isn't a single actor, musician, or politician in all 4,400+ results! Most of the results in that query are newer, and were imported from jawiki sometime in 2023 or 2024.

I usually use the SPARQL query below in Petscan to filter out items that already have P27, but whether the SPARQL query is present or not I don't get results with Q numbers that are more than 8 digits long (not including Q). A good category to test with is "日本の銀行家‎ ", which returned 42 results for me, with the most recent being Q65291794.

SELECT ?item WHERE { ?item wdt:P31 wd:Q5 . OPTIONAL { ?item wdt:P27 ?dummy0 } FILTER(!bound(?dummy0)) }

I've read the manual over and over and I can't figure out why Petscan won't return items with newer, 9-digit long QIDs. What am I doing wrong? Thanks in advance! Mcampany (talk) 00:13, 17 September 2024 (UTC)[reply]

Replying to say that I'd ask on the Petscan discussion page, but it seems really quiet there. I don't think this is worth opening an issue in Github because I'm pretty sure this is user error. If someone knows of a better place to ask than here, I'd appreciate if you'd let me know! Mcampany (talk) 00:23, 17 September 2024 (UTC)[reply]
Hello Mcampany, in PetScan there is a Wikidata tabulator, where you could put the value P27 (citizenship) or P106 (occupation) or any other property ID in the field Uses items/props, plus the checkbox None, to find all items without the P27 or P106 property related to the selected subcategory.
M2k~dewiki (talk) 16:23, 17 September 2024 (UTC)[reply]
Hi @M2k~dewiki! Thanks, using the "Uses items/props" field brought back 500+ results, which is what I expected to see. Unfortunately, if I don't have a SPARQL query in Petscan, or am not using create mode, all the checkboxes and the option to use Quickstatements disappear. A list is really nice, but I'd rather not have to export and open up Quickstatements in another tab to make the edits. I really like how seamless having the checkboxes and Quickstatements box there is. Do you have any idea why the Quickstatements box in Petscan keeps disappearing? Mcampany (talk) 17:32, 17 September 2024 (UTC)[reply]
Sometimes it happens with PetScan that checkboxes disappear, I havent found out in which cases, yet. Could you post your PetScan-Short-URL? M2k~dewiki (talk) 17:35, 17 September 2024 (UTC)[reply]
For example, something like https://petscan.wmcloud.org/?psid=29304610&al_commands=P31%3AQ847017 M2k~dewiki (talk) 17:36, 17 September 2024 (UTC)[reply]
Sure! It's https://petscan.wmcloud.org/?psid=29304637 Mcampany (talk) 17:38, 17 September 2024 (UTC)[reply]
You have to switch on Other sources from Automatic to Wikidata:
https://petscan.wmcloud.org/?psid=29304729 M2k~dewiki (talk) 17:48, 17 September 2024 (UTC)[reply]
Amazing! Thank you so much, @M2k~dewiki. You're the best.
 Resolved Mcampany (talk) 17:54, 17 September 2024 (UTC)[reply]

Updates in Wikidata item not reflecting in Commons..

[edit]

Once after connecting a Commons-category to Wikidata (not by adding QID at first, but by adding category name in Wikidata), the data is visible in Commons. Then after adding some updates to the Wikidata item, no matter what is done, the updates are not visible in the Commons page, until unless the QID is added in Commons category. Similarly again, any updates in Wikidata-item are not visible in Commons-category until-unless some changes are made in the connection to Wikidata in Commons, such as removing QID.
The updates are not visible at all (like forever) even if cache memory is removed from the computer. Why this happens and does anybody know any solution? Gpkp (talk) 09:13, 17 September 2024 (UTC)[reply]

Hello Gpkp, please see
regaring (purging) server side caches. M2k~dewiki (talk) 15:48, 17 September 2024 (UTC)[reply]
User:M2k~dewiki, Thank you very much. --Gpkp (talk) 14:59, 18 September 2024 (UTC)[reply]

Captions and colour of images of personalities scanned from books

[edit]

There are many drawings of Czech personalities used here in Wikidata which look like e. g. File:Adolf Heyduk – Jan Vilímek – České album.jpg or File:Karel Jaromír Erben – Jan Vilímek – České album.jpg. Sometimes there may be another version of the same image of similar quality in Commons (often uploaded by me) such as File:Karel Jaromír Erben (cut).jpg, which

  1. is without the caption present directly in the image,
  2. is more cut with less space around the portrait
  3. has the colour of the book paper removed.

Until now I did not have any problems with such replacements in Wikidata although I've been doing this occasionally for years, but now I have met with disagreement by User:Skot. Because my arguments did not convince him, and because I would like to prevent any edit-warring, I would like to ask other people for their opinions.

While I admit that the pictures with captions can be useful for somebody and so it is good to have them in Commons, I also believe that pictures without them like File:Karel Jaromír Erben (cut).jpg are better for Wikidata, because WD has a different tool to include captions if they are needed–the qualifier "media legend". Images from Wikidata are also being taken over by other projects, which also use different tools for captions, and the result then is that the caption is being doubled, as has happened e. g. in s:Author:Adolf Heyduk.

Cutting off the extra space around the portrait leads to better display in infoboxes, where the portrait looks larger, while taking the same infobox space.

I also think that the yellow-brown colour of the book paper is a noise contaminating the picture and worsening its contrast, and that it is not the colour of the picture but the colour of the medium from which the picture was taken. While it is absolutely possible to use such coloured pictures in Wikidata when there is no choice, if there is a possibility to choose between two alternatives, users should not be prevented to replace the coloured version by the de-coloured one in these cases.

Any opinions whether such replacements in Wikidata are possible are really appreciated. -- Jan Kameníček (talk) 20:58, 17 September 2024 (UTC)[reply]

@Jan.Kamenicek: I totally agree with you, a cropped and clean version is obviously better (especially as the coloration is a degradation of the paper that was not originally present nor intended ; but also the white space or the caption inside the image doesn't bring anything really useful for Wikidata). AFAIK, most people are doing the same (and for years, it was done also on other projects before Wikidata). I'm curious of hearing Skot arguments and reasoning. Cheers, VIGNERON (talk) 11:21, 21 September 2024 (UTC)[reply]
@VIGNERON The question is not whether to adjust the color of the images, we adjust them both, the question is the degree of adjustment. You can compare the original file: https://ndk.cz/uuid/uuid:8ea19fd0-cb83-11e6-ac1c-001018b5eb5c
For me personally, the degree of colour editing (it is simply automatic contrast) from a colleague is beyond the edge of losing image information, so I will not do it this way. At the same time, I have no intention of replacing his images as long as he uploads them in full resolution from the original source. The core of the problem is determining whether one of the color versions is significantly better than the other, justifying systematic replacement of each other's images within Wikimedia projects.
Regarding uploading images without captions, there i feel quite consensus within the community, so there is no problem uploading both the version with a caption and the one without directly to Commons. Skot (talk) 12:05, 21 September 2024 (UTC)[reply]

"position held" vs. "member of"

[edit]

Hello, I am looking for advice on when to use "position held" or "member of" on Amy Brown Lyman. She was president of the Relief Society (the women's organization in the Church of Jesus Christ of Latter-day Saints). That seems clearly like a "position held." She was also part of the Relief Society General Board. I'm not sure which way to model that (I did both ways I could think of). Rachel Helps (BYU) (talk) 21:06, 17 September 2024 (UTC)[reply]

I think "member of" is better for the board membership, but "position held" is right for being a president of something. ArthurPSmith (talk) 18:00, 19 September 2024 (UTC)[reply]

Daniel Levy: Two items for one person

[edit]

Q76245151 and Q3014345 are for the same person, each item lists biographies in two different Wikipedia language versions. Could someone who knows what they are doing, like User:M2k~dewiki, please merge them? Thank you! --Andreas JN466 08:31, 18 September 2024 (UTC)[reply]

Hello Jayen466, the two objects have been merged: Help:Merge M2k~dewiki (talk) 11:45, 18 September 2024 (UTC)[reply]

Dict: protocol

[edit]

Do we have a server for the dict: protocol, as described in this blog post and at DICT?

Curiously, if I type dict:cheese in the search bar here, I am taken to https://www.wikidata.org/wiki/Special:GoToInterwiki/dict:cheese (and similar if I do so on en.Wikipedia, etc.*), which displays:

Leaving Wikidata

You are about to leave Wikidata to visit dict:cheese, which is a separate website.

Continue to https://www.dict.org/bin/Dict?Database=*&Form=Dict1&Strategy=*&Query=cheese}}

and not to a Wikidata entry (nor a Wiktionary page**). Can we get that changed?

[* doing so on fr.Wikipedia still takes me to an English definition; does it do so for people whose browsers use other languages?]

[** Also raised at wikt:Wiktionary:Grease pit/2024/September#Dict: protocol]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:15, 18 September 2024 (UTC)[reply]

See phab:T31229.--GZWDer (talk) 16:02, 18 September 2024 (UTC)[reply]
It's kind of retro-sexy but also incredibly niche. Since the WMF offers servers to useful projects you could set up a server that offers wikidata or wikipedia over gopher, telnet (BBS-style or non-interactive) or dict. I didn't intend to register a developer account, but for something fun like this I might change my mind. I can hardly think of a better way of procrastinating. Be warned though, I might be compelled to do the implementation in D (language designed by walter bright and andrei alexandrescu, both C++ heavyweights) just because I want more experience with it. I recon a single docker instance will do which doesn't require much formality, so this this could be up and running without too much delay. Main thing would be agreeing on how the protocols should be queried. Infrastruktur (talk) 17:39, 19 September 2024 (UTC)[reply]

Map of Holocaust memorials

[edit]

I was just looking for images of Holocaust memorials, and made the below query. I never expect wiki info to be complete, but I was surprised how incomplete this map was compared to, say English Wikipedia. Even Commons has photos of memorials which don't seem to be on this map. I don't have time to work on this much myself but I hope it's okay to flag it up here as something that people may want to improve, mainly by adding commemorates (P547) The Holocaust (Q2763) to the relevant items. Holocaust education is a hot topic here in the UK as the new government is suggesting making it compulsory in all schools.

The following query uses these:

Features: map (Q24515275)  View with Reasonator View with SQID

#defaultView:Map{"hide":"?coords"}
SELECT ?item ?itemLabel ?coords ?image WHERE {
  ?item wdt:P547 wd:Q2763; wdt:P625 ?coords
      OPTIONAL {?item wdt:P18 ?image}
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],mul,en". }
}
Try it!

MartinPoulter (talk) 12:43, 18 September 2024 (UTC)[reply]

Here's a Petscan query for articles in en:Category:Holocaust commemoration without property commemorates (P547): [1]. If you or someone else wants to add statements to them, go through the list, select suitable items, add "P547:2763" to the command list and press Start QS. Samoasambia ✎ 13:09, 18 September 2024 (UTC)[reply]

aircraft engine (Q743004) and models (also many classes similar to aircraft engine (Q743004))

[edit]

The class aircraft engine (Q743004) has problems in Wikidata. aircraft engine (Q743004) is a subclass of physical object (Q223557), which means that its instances are physical objects. But almost all the instances of aircraft engine (Q743004) are not physical objects, instead mostly being aircraft engine models like Poinsard (Q7207885).

What should be done to fix this problem? The simplest fix would be to just make aircraft engine (Q743004) no longer be a subclass of physical object (Q223557) and other classes that cause similar problems, perhaps by replacing aircraft engine (Q743004)subclass of (P279)aircraft component (Q16693356) with aircraft engine (Q743004)is metaclass for (P8225)aircraft component (Q16693356). But that would leave all the labels and descriptions for aircraft engine (Q743004) as is, and not corresponding to the actual intent of the class. Changing just the English label and descriptions would be possible but would cause a difference in the meaning of the labels in different languages. Adding an English value for Wikidata usage instructions (P2559) would help a bit not would not solve the mismatch. Changing all the descriptions doesn't seem immediately possible.

A variation of the first option would be to add a new class for aircraft engines, transfer all the labels and descriptions and aliases to the new class, correctly place the new class in the Wikidata ontology, give the new class appropriate label and description and aliases, and make the model instances also be subclasses of the new class.

Another option would be to make all the aircraft engine models that are currently instances of aircraft engine (Q743004) subclasses of it instead, perhaps in conjunction making the models instances of some suitable metaclass like engine model (Q15057021). This option probably requires many more statment changes than the previous approaches. If this is done, adding an appropriate English value for Wikidata usage instructions (P2559) on aircraft engine (Q743004) seems indicated.

Given what I have seen in related classes, I expect that there are many classes that have the same problem so perhaps the best way forward is to consider the problem in general and come up with a general solution.

Does anyone have preferences between these approaches? Does anyone have a different approach to fix this problem? Does anyone know what is the best way to gather a community that could come up with a consensus decision? Peter F. Patel-Schneider (talk) 15:32, 18 September 2024 (UTC)[reply]

the standard solution would be to create a new item "aircraft engine model" as a metaclass for aircraft engine. Fgnievinski (talk) 23:50, 19 September 2024 (UTC)[reply]
We'd save a lot of work generating a parallel *_model hierarchy if something could be a instance of (P31) of product model (Q10929058) and a subclass of (P279) (or some other property) of its functional class. Vicarage (talk) 00:17, 20 September 2024 (UTC)[reply]
Care to exemplify Fgnievinski (talk) 02:03, 20 September 2024 (UTC)[reply]
Peter and I are working on a RfC. Vicarage (talk) 20:51, 21 September 2024 (UTC)[reply]
Sadly I think the first thing you need to do is make sure aircraft engine (Q743004) is used as a subclass of (P279), not the 237 times its currently used as a instance of (P31). Once that's done, I don't see why you can't leave the subclass of (P279) aircraft component (Q16693356) alone, and work up the chain to find a point where a design idea erroneously becomes a physical thing. Naively it seems to me you can have design all the way down to a final instance of (P31) for a single object. But you know a lot more about ontology than me. Really it should be called "aircraft_engine_model", like we have for weapon model (Q15142894) but I don't like the idea of doubling up adding _model to every concept, to have 2 parallel trees. I see we have engine model (Q15057021), so perhaps as we do with weapons, we make the 237 aircraft engines use that, and keep looking for generic terms at the level above a specific design.

Vicarage (talk) 16:31, 19 September 2024 (UTC)[reply]

Yes, I'm coming around to this approach of moving lots of items from instance to subclass of aircraft engine (Q743004), except that there might be a few instances that are actual physical objects (like aircraft engines in museum collections). That's probably the most actual changes but probably has the least changes to the Wikidata ontology. Peter F. Patel-Schneider (talk) 16:52, 19 September 2024 (UTC)[reply]
Those actual objects should either at a pinch have P31 of physical_object directly, or for museum items, item of collection or exhibition (Q18593264). I expect we can come up with useful reasons why we care about a physical instance of a manufactured design. Vicarage (talk) 16:58, 19 September 2024 (UTC)[reply]

Uploading photos on WikiLovesMonuments.org having problem with no category for .....

[edit]

In County Sligo, Ireland there's a historic site which I believe is incorrectly named "Carrowmore Passage Tomb". There is no 'no Wikimedia Commons category'. It has a Wikidata entry # Q33093088. I've uploaded a set of images on the site but have just disappeared.

⁨I understand correct name to be Carrowmore Megalithic Cemetery⁩, ⁨Carrowmore⁩, ⁨Co. Sligo⁩, ⁨Ireland⁩


Any help appreciated.

Gillfoto (talk) 23:10, 18 September 2024 (UTC)[reply]

I moved the Wiki Loves Monuments ID to Carrowmore (Q260398) (Carrowmore Megalithic Cemetery). It's possible that Carrowmore Megalithic Cemetery W-M 9a (Q33093088) was intended to be "Carrowmore Passage Tomb Cemetery", but the "Cemetery" was missing, and it was unclear whether it referred to the cemetery or one of the tombs. Peter James (talk) 20:44, 19 September 2024 (UTC)[reply]

Uploading Logo on NCWiki

[edit]

I could use some help to add the logo from Wikimedia Commons to WIkidata the logo is uploaded as Logo_NCWiki.png. Kroeppi (talk) 09:19, 19 September 2024 (UTC) [reply]

Enabling the CampaignEvents Extention on Wikidata

[edit]

The Campaigns Product team at the Wikimedia Foundation is proposing to enable the CampaignEvents extension on Wikidata by the second week of October.

This extension is designed to make it easier for organizers to manage community events and projects on the wikis, and it makes it easier for all contributors to discover and join events and projects on the wikis. Once it's enabled on Wikidata, you will have access to features that will help with planning, organizing, and promoting events/projects on Wikidata.

These features include:

  • Event Registration: A tool that helps organizers and participants manage event registration directly on the wiki.
  • Event List: A simple event calendar that shows all events happening on the wiki, particularly those using the Event namespace. It will also be expanded soon to have an additional tab to discover WikiProjects on a wiki.
  • Invitation Lists: A feature that helps organizers identify editors who might be interested in their events, based on their editor history.

Please note that some of these features, like Event Registration and the Invitation List, require users to have the Event Organizer right. When the extension is enabled on Wikidata, the Wikidata admins will be responsible for managing the Event Organizer right on Wikidata. This includes granting or removing the right, as well as establishing related policies and criteria, similar to how it’s done on Meta.


We invite you to help develop the criteria/policy for granting and managing this right on Wikidata. As a starting point for the discussion, we suggest the following criteria:

  1. No active blocks on the wiki.
  2. A minimum of 300 edits on Wikidata.
  3. Active on Wikidata for at least 6 months.


Additional criteria could include:

  1. The user has  received a Wikimedia grant for an event.
  2. The user plans to organize a Wikidata event.


We would appreciate your input on two things:

  1. Please share your thoughts and any concerns you may have about the proposal to enable the CampaignEvents extension on Wikidata.
  2. Review the starting criteria listed above and suggest any changes or additions you think would be helpful.

Looking forward to your contributions - Udehb-WMF (talk) 16:00, 19 September 2024 (UTC)[reply]

300 edits may be too low; Wikidata edits are generally very granular, so it's easy to make a lot of them. Maybe set the minimum at 1000? ArthurPSmith (talk) 18:04, 19 September 2024 (UTC)[reply]
I think 300 or 1000 matters little. The rights also don't give much room to mess up, so it is okay to have a low bar. From the additional criteria, I think a grant is way too restrictive, but the plan to organize is a must. Why else would the rights be needed? Ainali (talk) 18:22, 19 September 2024 (UTC)[reply]
I think the proposed criteria are reasonable. It is really hard to judge someone by the amount of edits because of the tools we are using on Wikidata. Perhaps we want to use a trial period for granting the rights (at least for less experienced users). We could grant it temporary for one year and renew it if it is still needed. --Ameisenigel (talk) 19:35, 19 September 2024 (UTC)[reply]
Hello! As a staff from an affiliate, I'd suggest to add a criteria that bypasses the number of edits for staff that belongs to an affiliate. In the case of Wikidata it's always useful if they know the platform before running an event, but it could be among the responsibilities of a new member of an affiliate staff to organize an event. Other than that, the criteria seems to follow what other wikis are currently discussing or implementing. Scann (WDU) (talk) 12:48, 20 September 2024 (UTC)[reply]
That's an interesting point that makes me question why we need an extra limit at all. Couldn't this right just be added to what autoconfirmed users can do? If someone misbehaves, it wouldn't be too much hassle to notice it and block, and the harm they can do wouldn't be any worse than being able to create items or pages in the Wikidata namespace. Ainali (talk) 13:38, 20 September 2024 (UTC)[reply]

fusion

[edit]

Georges Meyer (Q19629082)

Georges Meyer (Q107279424)

seem to be the same one, not sure how to do it Io Herodotus (talk) 07:52, 20 September 2024 (UTC)[reply]

@Io Herodotus Well, they're not the same... so they shouldn't be merged. RVA2869 (talk) 08:27, 20 September 2024 (UTC)[reply]
Sorry wrong item.
Georges Meyer (Q107279424)
Georges Meyer (Q125422040)
--Io Herodotus (talk) 08:36, 20 September 2024 (UTC)[reply]
For more info: Help:Merge RVA2869 (talk) 09:05, 20 September 2024 (UTC)[reply]

Rewriting Blazegraph syntax to pure SPARQL 1.1

[edit]

Hi All,

@Andrawaag and I have been working on extracting all SPARQL templates in wikidata at the latest Biohackathon Japan DBCLS BioHackathon (Q109379755). So that we can automatically rewrite them to be SPARQL 1.1. The tool we use is something developed for the SIB Swiss Institute of Bioinformatics (Q3152521) sparql examples project [2]. That now has support for crawling wikibase. We still have issues open [3] and we hope that the community can find some more. We have aimed to be gentle with crawling and encourage to test the java code with the "--use-cached" flag so that you don't use more server resources than needed.

For example still missing is the nice static webpages due to an issue with Jekyll. Also the extraction of "comments" is still being worked on by @Andrawaag.

Please let us know if you like/dislike this and what you would like to see added.

Regards, Andra and Jerven (talk) 16:20, 20 September 2024 (UTC)[reply]

Automotive

[edit]

Imperial cars are called Chrysler Imperials. Imperial has not been a model of Chrysler since 1954. In 1955 Imperial became a separate car brand like Lincoln is from Ford or Cadillac is from Buick. Since 1954 there has not been a Chrysler Imperial. 2600:1700:E770:7680:54D0:3A6B:2947:91BA 20:32, 20 September 2024 (UTC)[reply]

There was a Chrysler Imperial between 1989 and 1993 (https://www.nytimes.com/1989/11/08/business/chrysler-imperial-joins-cutthroat-car-market.html https://www.macsmotorcitygarage.com/the-royal-prerogative-chryslers-very-last-imperial-1990-93/). Chrysler Imperial (Q1088705) is for the Chrysler model series, Chrysler Imperial (Q97373892) is the 1989-1993 Chrysler model, and Imperial (Q668822) is for the brand. The models have "brand: Chrysler", which links to Chrysler (Q29610); the brand only has "founded by" and and "owned by" linking to the Chrysler company Stellantis North America (Q181114). This seems to be correct, at least for the time the cars were produced (although this may need changing if the Stellantis North America (Q181114) item is split). The items could probably be improved with the addition of start and end of production or sale - Imperial (Q668822) has inception (P571) and dissolved, abolished or demolished date (P576), but I'm not sure they are suitable properties for a product. Peter James (talk) 00:20, 21 September 2024 (UTC)[reply]
I found the properties date of commercialization (P5204) and discontinued date (P2669) and added them. There was also the Chrysler Imperial Concept (Q50396854) from 2006 but that is probably not relevant as it was only a concept car. Peter James (talk) 00:50, 21 September 2024 (UTC)[reply]

Description

[edit]

Hi, could you explain the easiest way to add the same description to all articles within a specific category on Wikipedia? I'm looking to do this for settlements in the municipalities of Serbia, based on the categories in the Serbian-language Wikipedia. I'm aware of QuickStatements but haven't used it before. Thank you! — Sadko (words are wind) 01:48, 21 September 2024 (UTC)[reply]

Deletion of Userpage

[edit]

Hello,

I unknowingly created my user page in this wiki. Later realized that global user pages at MetaWiki exist. Now I am confused where do I list my userpage for Speedy deletion. Any help would be greatly appreciated regarding this issue. Thanks in advance! Bunnypranav (talk) 12:36, 21 September 2024 (UTC)[reply]

Hi Bunnypranav, just add {{Delete}} template to your user page. Samoasambia ✎ 13:13, 21 September 2024 (UTC)[reply]
Thanks for the clarification, I thought this template cannot be used for user nominated speedy deletions. Bunnypranav (talk) 13:15, 21 September 2024 (UTC)[reply]

Merging needed of two items

[edit]
situation in 1981

I accidentaly created Q130340447 while Q5649310 already existed. Some things are not correct. It not out of use but rebuild for another purpose. (no trains but used as a greenhouse).Smiley.toerist (talk) 21:24, 21 September 2024 (UTC)[reply]

Expelled because endorsement.

[edit]

How to say that a person was excluded from a political party because he endorsed an another political party how can i represent that in Wikidata using the Property end cause (P1534)?

For instance most political parties have in their charter URL (P6378) that if you endorse or are elected on another political party ticket than you get expelled from your political party. Johshh (talk) 23:01, 21 September 2024 (UTC)[reply]

I'd likely just use the P1534 but then add additional qualifier property statements to say when/where/how/why ? There are a few "expulsion" concepts you could link the qualifiers to, there's also this one removal from office (Q106677579) I found, but maybe that one is too narrow for your use case and you might have to search for others, or create one called "removal by policy" or something suiting the exact case like "removal from political party". Thadguidry (talk) 05:55, 22 September 2024 (UTC)[reply]

How do I replace a citation? How do I get coords displayed in decimal degrees?

[edit]

First question. There are many Queensland place names which have been imported from something called the Geographic Names Server. I don't know what that is, but it is not an authoritative source for Queensland place names and the information is often wrong, and then it creeps into Wikipedia and Commons infecting them with its misinformation. My immediate problem is Alligator Creek (Q21922742). Although I managed to change the coords and I eventually managed to delete the Geographic Names Server, I cannot see how to add a citation to a reliable source, the Queensland Places names database, entry 391. So how do I do this? There is a cite template on Wikipedia for the purpose (cite QPN). How do I use it here or get set up something equivalent set up on Wikidata?

To illustrate the problem, see this Wikidata-generated infobox on Commons

https://commons.wikimedia.org/wiki/Category:Alligator_Creek_(creek,_City_of_Townsville)

See how the point is the middle of dry land because it is incorrect. The creek mouth is further west.

Second question. Most of the Queensland resources use decimal degree format. Although I entered my coords in the decimal degree format, they are displaying as DMS. How do I get them to display (in general or just for me) as decimal degrees so I can check what's in Wikidata without having to manually convert all the DMS each and every time.

Thanks, Kerry Kerry Raymond (talk) 02:56, 22 September 2024 (UTC)[reply]

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