User talk:Arlo Barnes/Archive 1

Talk here! Arlo Barnes (talk) 03:42, 30 January 2016 (UTC)

Open Humans Edit

Hi Arlo Barnes, Thanks for the Open Humans edit with a lower Q number for Madeleine Ball, but in that instance since the replaced Q was the same entity (see ORCID) a merge would have been a better fit so the second Q doesn't hang around for the same entity. I've made the merge in this case. Wolfgang8741 (talk) 06:01, 17 December 2018 (UTC)

Thanks for the heads-up and the merge! Actually, I just missed that there were two separate objects; I was trying to edit the qualifiers and only accidentally edited the Q number. Arlo Barnes (talk) 06:05, 17 December 2018 (UTC)

Personal Data WikiProject

Hi Arlo Barnes, I see you have expressed interest to work on the Personal Data WikiProject! I can certainly use the help ;-) Particularly, at this stage, around defining the scope and specifying it in a good way so others see it too. Pdehaye (talk) 12:54, 17 December 2018 (UTC)

title character of Q66048962

Hey, instead of writing the number in the description could you just use the name of the item instead? So instead of title character of Q66048962 you could write title character of Spooky's House of Jumpscares --Trade (talk) 19:16, 2 August 2019 (UTC)

Sure, I usually try to do the name and then the Q-number in parens, but I forgot that time.

I like to include the number because on the rare occasion that someone includes it, it has helped me when doing edits.

Thanks for the catch, though.

Arlo Barnes (talk) 21:53, 2 August 2019 (UTC)

Hmm, in my experience including a number doesn't make much of a difference in the difficulty of finding a description.

Do you have any examples where removing the number makes the item harder to find?

--Trade (talk) 10:29, 29 September 2019 (UTC)

It's more like an efficiency measure, since I can plop the number directly into the URL bar rather than using the search.

Also, it helps disambiguate items that have the same label; it is generally pretty clear which one is meant once their entries are opened, but again that requires an additional step.

Arlo Barnes (talk) 17:51, 29 September 2019 (UTC)

Community Insights Survey

Share your experience in this survey

Hi Arlo Barnes/Archive 1,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Wikidata and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 17:38, 10 September 2019 (UTC)

"novalue" items

Hi Arlo,

I've been cleaning up some odd values in date of death (P570) and noticed you added a few of them recently (eg). "no value" is really meant for cases where there is no meaningful value and won't ever be one - eg "spouse" for someone who was never married, "educated at" for someone with no formal education, or "number of children" for someone who never had any. As a result, it gets a bit conceptually weird to use it for dates/places of death, and the consensus has generally been to avoid it. (It also confuses a lot of database queries, which use "has any P570 statement" as a proxy for "is dead", on the assumption that novalue isn't used.)

We don't unfortunately have any clear way to record "is currently alive"; it's usually inferred by a recent birthdate + absence of a deathdate rather than an explicit statement. Andrew Gray (talk) 12:19, 21 September 2019 (UTC)

Ah, I see. I'll stick to only using it for the kinds of cases you mention, then. Thanks! Arlo Barnes (talk) 16:42, 21 September 2019 (UTC)

Lack of refs on Q63016981

Hi,

Reading Wikidata:Autobiography, I see that even if people edit their own item (like Q63016981 seems to be), they need a verificable source. It seems that most properties on that item are not properly sourced, so could you add them so people can verify the affirmations ? --Misc (talk) 19:30, 13 January 2020 (UTC)

Sure, let me know if there is a particular statement you think is lacking. Arlo Barnes (talk) 21:55, 13 January 2020 (UTC)

Q80439571

archive URL (P1065) should only be used when linking to archived versions of internet pages such as this. If you wanna link to files hosted by Internet Archive (Q461) you should use Internet Archive ID (P724) instead. Kh. --Trade (talk) 20:29, 27 January 2020 (UTC)

Profanity in American Sign Language (Q7247906)

Hey, I deleted your has part(s) (P527)-edits on Profanity in American Sign Language (Q7247906). The items you added may be part of the general item for Profanity, but they are not connected to the American Sign Language. --CENNOXX (talk) 14:37, 11 February 2020 (UTC)

Alright, fair enough; I think it's hard to separate the semantic from the lexical there. Perhaps I should learn more about lexeme editing...Arlo Barnes (talk) 14:54, 11 February 2020 (UTC)

Interview Invitation

Greetings,

I noticed your Wikidata editing stats on Wikiscan , which led me to look up your profile. Thank you for all the hard work!

I’m reaching out to you because I’m working on a research project about understanding what motivates editors like you to contribute to Wikidata. We’re also interested in learning about how you feel your contributions are being used outside of Wikidata. Since you are such an active community member, I thought you might also be interested in helping to build the broader community’s knowledge about Wikidata, and why it matters.

If you’re interested, let’s schedule a time to talk over Zoom, or whichever platform you prefer. You could leave a direct message or fill in a questionnaire. The conversation should take about 30 min.

Hope you have a great day,

Chuankaz (talk) 03:22, 11 June 2020 (UTC)

special:emailuserd. Arlo Barnes (talk) 04:34, 16 June 2020 (UTC)

Your edits of Big Ears: Listening for Gender in Jazz Studies (Q57233378)

Thanks for the edits of "Big Ears". I see you're adding the chapters as "also known as." I don't think that's appropriate. I think you can leave those out of the aka. See Big Ears: Listening for Gender in Jazz Studies (Q96360168). I'll add the rest of the chapters and connect them to the digital version. Trilotat (talk) 01:18, 18 June 2020 (UTC)

Thanks for both the attention to detail and your own efforts on the item; you are correct that it was not proper, but merely a stopgap measure. If you have a plan I will definitely follow your lead on that. Arlo Barnes (talk) 01:20, 18 June 2020 (UTC)

My pleasure. The work on Duke University publications I did was very early on in my wikidata education, so I don't claim it was all that good. I'm very happy to revisit and improve what I can. See Big Ears: Listening for Gender in Jazz Studies (Q96360168) with the addition of "has part". I am in no way familiar with the text, so I'm just going by what I find online. I also made that online version of the book a version of the one you were working on. I am not sure that's right, though. Trilotat (talk) 01:48, 18 June 2020 (UTC)

Wikidata for Firefox wishes?

Hi, I have noticed that you are using Wikidata for Firefox. I am writing to ask you if you have any wishes which external id properties should be supported for connecting to wikidata. So far I only support these. Let me know if you have other ideas or wishes for the extension--Shisma (talk) 14:31, 20 September 2020 (UTC)

(For my own reference: IMDb ID (P345), Trakt.tv ID (P8013), Twitter (X) username (P2002), MusicBrainz artist ID (P434), MusicBrainz release group ID (P436), Internet Archive ID (P724), Goodreads version/edition ID (P2969), Goodreads character ID (P6327), Goodreads series ID (P6947), Goodreads author ID (P2963), Goodreads work ID (P8383), YouTube video ID (P1651), Open Food Facts food category ID (P1821), Open Food Facts ingredient ID (P5930), YouTube channel ID (P2397), Google Play Music artist ID (former scheme) (P4198), YouTube playlist ID (P4300), fernsehserien.de ID (P5327), subreddit (P3984), Steam application ID (P1733), GOG application ID (P2725), Humble Store ID (P4477), MobyGames game ID (former scheme) (P1933), Duden lexeme ID (P8376), ISFDB title ID (P1274), ISFDB series ID (P1235), Internet Speculative Fiction Database author ID (P1233), AniDB anime ID (P5646), AniDB character ID (P5648), AniDB person ID (P5649), Internet Pinball Database ID (P6011), Spotify show ID (P5916), WhoSampled artist ID (P6517), New Georgia Encyclopedia ID (P4903), Television Academy Foundation interviewee ID (P5773), Television Academy Foundation show ID (P5829), IANA Root Zone Database ID (P5914), Playbill venue ID (P6113), Playbill person ID (P6132), Newseum newspaper front page ID (P6136), Disney+ movie ID (P7595), Disney+ series ID (P7596), Disney A to Z ID (P6181), Atlas Obscura ID (P7772), ToS;DR service ID (P8525))

I think I'll need to use the extension more to know better what I want from it; I've only just started. But quality-of-life improvements would not go amiss. In particular, exposing the constraints for a given property is useful and amounts to a major portion of the work of doing it by hand. That's somewhere an extension could really assist (and I noticed that WfF fills in refs already, which is great. Arlo Barnes (talk) 23:37, 20 September 2020 (UTC)

Q-IDs in Description

Hey Arlo,

I noticed a description you added that included Q-Ids for the items mentioned: "December 2013 book review of Guns, Germs, and Steel (Q279022) in Capitalism, Nature, Socialism (Q15757353)". I'm assuming you're using this practice because it makes sense in some step of your workflow. But these descriptions aren't intended for our (editors') convenience: they are supposed to give a description of an item in a form that makes sense for people that are decidedly less strange than we are, i. e. the general public. If you disagree with my reasoning (which somehow happens occasionally) I invite to consider that this practice is highly idiosyncratic. If it is beneficial, it would follow that it should become general practice. In that case, I would invite you to ask in, for example, Project chat for support to make it a recommended practice. Other than that: thank you for your work! Wikidata needs more of the kind of highly detailed handcrafted data you are adding. If there is some specific change in the interface that would make your work easier and obviate the need for the IDs in the description, it should probably receive some attention. Matthias Winkelmann (talk) 10:33, 10 January 2021 (UTC)

Hi Matthias. This seems to be the same appeal as #title character of Q66048962 so if you hadn't yet read the conversation Trade and I had, there it is. I'd disagree with your implication that being aware of Wikidata is somehow strange -- indeed, to be using a service that is using Wikidata but needing to be protected from knowing that it is using Wikidata is strange to me. Understanding the meaning of a Q-number is a websearch away (or simply looking to the left of the parentheses). Anyway, if a service is uptaking labels, descriptions, and aliases for semantic display rather than processing triples which seems more stable, then there's more irregularities than mine to deal with. I'd also disagree that all practices need to be evaluated in a universal context (even help:label isn't a guideline yet), but that's neither here nor there. I'll stop if you convince me that this practice should be considered harmful (Q840919), but currently I don't see it. If you'd like to start a discussion in WD:PC or help talk:description or elsewhere, I'll provide my perspective. In a nutshell, it's that the description field is for explication and disambiguation, which also comprise a lot of the activities of Wikidata as a whole. Having separate items for conceptually-separate entities is a good example of that. This structure is an intentional advantage that can be employed. I hope that provides some elucidation of my thoughts, and please don't take my listed disagreements above as unfriendliness; I really only want to do what is best for the project, and desire any feedback that can help me do that, so thank you. And happy New Year! Arlo Barnes (talk) 21:39, 10 January 2021 (UTC)

Publication date

For writings from the Ancient and Classical world, it isn't meaningful to talk about "publication dates", since none of the earliest copies survive, and since works were seldom "published" in any meaningful sense. For the Athenian plays, the date of first performance is meaningful, and publication dates are placed on the specific editions, including the editio princeps, which for Athenian drama usually dates from the Renaissance. But each of these editions will have its own data item with full publication details. --EncycloPetey (talk) 19:25, 23 January 2021 (UTC)

Alright, that makes sense. I think a publication that is lost is still considered published, but if the only form in which the public received it at that time was a performance, then of course you are right that the performing arts properties take precedence. Arlo Barnes (talk) 23:00, 23 January 2021 (UTC)

Wikisource & Wikidata

Hi Arlo, you created Wikidata:WikiProject Cooperation between Wikidata and Wikisource and I have question. Do you interested in this topic? I am user of Czech Wikisource and Wikidata/Tech programs coordinator as User:Michal_Josef_Špaček_(WMCZ) in Wikimedia Czech Republic. I am interested in cooperation between Wikidata and concrete project. So I am looking for other participants. e.g. I am creating SPARQL queries for Wikisource (examples). e.g. I am thinking about editathon about adding data about Wikisource items to Wikidata actually. Skim (talk) 13:53, 3 March 2021 (UTC)

Yes, I don't quite recall why I created that item despite it not being that long ago, but I do greatly value the intersection between WD and WS. I would take part in such an editathon. Arlo Barnes (talk) 20:21, 3 March 2021 (UTC)

Great :-) Skim (talk) 10:35, 5 March 2021 (UTC)

Jen-Hsun Huang Engineering

Your edit last year said that this building was located on the street of Via Crispi which is a kindergarten in Sapri in the province of Salerno? [1] [2] ??? Leijurv (talk) 03:54, 2 May 2021 (UTC)

And E-W Airlines, apparently. I don't want to imagine how tired I must have been at the time to make such blunders. Thanks for finding and correcting them; I have now restored the correct referents, Arlo Barnes (talk) 05:45, 2 May 2021 (UTC)

copyright license (P275) constraint edits

Not sure what you were trying to do with copyright license (P275), but it didn't work. You triggered millions of mandatory constraint violations on Wikimedia Commons. Please be a bit more careful with editing constraints. Please propose any changes to the constraints of copyright license (P275) on Property talk:P275 because it's used more than 55 million times. Multichill (talk) 13:42, 6 May 2021 (UTC)

Ah, apologies. I read that deprecating a constraint causes it to be ignored, so that the suggestion list will only be recommended, not required. Clearly that was a misinforming or misunderstanding. Arlo Barnes (talk) 20:35, 6 May 2021 (UTC)

I guess this edit caused the most constraint violations. Multichill (talk) 10:32, 8 May 2021 (UTC)

You did it again, now at collection (P195). You seem to be rather sloppy in your constraint edits. What I expect from you is to check for each constraint edit to check what the impact is before applying it. If you're unwilling to do that, you shouldn't be editing them. Multichill (talk) 20:48, 6 June 2021 (UTC)

Formatter URL (P1630) of format as a regular expression (P1793)

I saw that you added an ampersand to the regex101.com formatter url for the "format as a regular expression" property (edit). Did you do this on purpose? On my end it makes it add an extra space character at the end of the regular expression. Thank you, Lagewi (talk) 00:58, 15 May 2021 (UTC)

I did not have that intention, and the mistake has been emended. Arlo Barnes (talk) 14:52, 15 May 2021 (UTC)

Wikiproject Welcome to Night Vale

Would there be interest in such a Wikidata project? --Trade (talk) 11:20, 21 May 2021 (UTC)

Heck yeah I'd edit NV items. You don't think it would fit as a workgroup under an existing Wikiproject, though? I see you've been active at Wikidata_talk:WikiProject_Podcasts#Radio_show_vs_podcast... Arlo Barnes (talk) 20:52, 21 May 2021 (UTC)

@Trade: BTW are we still interested in following up on Wikidata:Property proposal/personality traits? Arlo Barnes (talk) 19:17, 2 June 2021 (UTC)

Call for participation in the interview study with Wikidata editors

Dear Arlo Barnes,

I hope you are doing good,

I am Kholoud, a researcher at King’s College London, and I work on a project as part of my PhD research that develops a personalized recommendation system to suggest Wikidata items for the editors based on their interests and preferences. I am collaborating on this project with Elena Simperl and Miaojing Shi.

I would love to talk with you to know about your current ways to choose the items you work on in Wikidata and understand the factors that might influence such a decision. Your cooperation will give us valuable insights into building a recommender system that can help improve your editing experience.

Participation is completely voluntary. You have the option to withdraw at any time. Your data will be processed under the terms of UK data protection law (including the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018). The information and data that you provide will remain confidential; it will only be stored on the password-protected computer of the researchers. We will use the results anonymized to provide insights into the practices of the editors in item selection processes for editing and publish the results of the study to a research venue. If you decide to take part, we will ask you to sign a consent form, and you will be given a copy of this consent form to keep.

If you’re interested in participating and have 15-20 minutes to chat (I promise to keep the time!), please either contact me at kholoudsaa@gmail.com or kholoud.alghamdi@kcl.ac.uk or use this form https://docs.google.com/forms/d/e/1FAIpQLSdmmFHaiB20nK14wrQJgfrA18PtmdagyeRib3xGtvzkdn3Lgw/viewform?usp=sf_link with your choice of the times that work for you.

I’ll follow up with you to figure out what method is the best way for us to connect.

Please contact me if you have any questions or require more information about this project.

Thank you for considering taking part in this research.

Regards

Kholoudsaa (talk) 00:01, 16 July 2021 (UTC)

jan (Q105816257)

I saw you created jan (Q105816257). I do not think "jan" really counts as a term of esteem or respect for a person, just like "ma" is not a term of respect for a territory. They are just words used before proper nouns. I think it makes more sense to model "jan" as part of the nickname, see nickname (P1449) at Sonja Lang (Q12854). Robin van der Vliet (talk) (contribs) 17:32, 18 October 2021 (UTC)

Your edits seem good to me. The reason I made the item was that I was working on Q105816235, not that I was trying to make bold claims about the language (about which I know little); I was probably confusing it in my head with the identical honorific from Pashto. I am curious why you removed the 'form of label' statements, since at those property pages it is suggested that languages that make no distinction should have the same statement for both, but I'll defer to your judgment on that. I see also an IP editor helpfully capitalised 'Toki Pona', I had mistakenly thought it was lowercased. Arlo Barnes (talk) 19:52, 18 October 2021 (UTC)

dummy (Q65088916)

I saw you made this a subclass of Wikibase reason for deprecated rank (Q27949697), and hence made it indirectly a subclass of Wikimedia internal item (Q17442446). I've contradicted the claim, as I wasn't sure what you intended by it. I'm not quite sure of the intended purpose of dummy (Q65088916) - indeed, its description says it's used for various purposes. But subclasses of dummy include for example toy weapon (Q356049) (a substitute nipple) and toy weapon (Q356049) (a dummy of a projectile weapon). These classes certainly shouldn't be subclasses of Wikimedia internal item. Should dummy perhaps be an instance rather than a subclass of reason for deprecation, in order to avoid these implications by transitivity? Dsp13 (talk) 21:55, 27 October 2021 (UTC)

Ah, that indeed seems problematic. At the root is that the item is overloaded, I guess. What I wanted to express was that a value wasn't a 'true' value, but rather stood in for one (in a given source, say) and therefore shouldn't be given a normal or preferred rank. So perhaps a 'Wikibase dummy' that merely points to the dummy item? Arlo Barnes (talk) 22:01, 27 October 2021 (UTC)

Not totally sure I understand your use case, but agree that a dedicated 'Wikidata dummy' item might be safest. That could be an instance of both dummy (Q65088916) and Wikibase reason for deprecated rank (Q27949697). I don't think it needs to be a class at all. Dsp13 (talk) 22:11, 27 October 2021 (UTC)

 Done Wikibase dummy (Q109290665) Arlo Barnes (talk) 22:32, 27 October 2021 (UTC)

Get a life

https://www.wikidata.org/w/index.php?title=Topic:Wpqfe4wfx7r9t9af&action=history

93.81.100.86 03:26, 10 February 2022 (UTC)

No, I don't think I will. Arlo Barnes (talk) 03:37, 10 February 2022 (UTC)

What about number of the beast (Q666)?

see title --Dr. Slow Decay (talk) 09:45, 15 February 2022 (UTC)

Added. However, I made that section before I knew about wikidata:humour, which is much more complete. Arlo Barnes (talk) 12:10, 15 February 2022 (UTC)

north wall (Q20871770)

north wall (Q20871770) is often used in architectual describtion as the descripton of any northern wall of a structure. It is a more generic term and not like in Western Wall (Q134821) a specific term. Nevertheless it would make sense to create equivalents for the south, the east and the west. But as you see in my example from Jerusalem you might run into disambiquities, because there are many western walls, but only one Western Wall. In Fürstenzug (Q513214) in the description of location (P276) I tried to show how this can be described alternatively. --Wuselig (talk) 13:53, 20 April 2022 (UTC)

bitext

I came across this edit and cannot see why you made it. The data item is for bitext, which is a document in which a text appears simultaneously in two different languages. For example, the Loeb Classics edition of Ovid's Metamorphoses, where the odd-numbered pages show the English translation, and the even-numbered pages show the same text in the original Latin. By contrast, a concordance is a list of all the words found in a text, with information about where each instance of the word was used. These are not the same thing, which is why I do not understand the change that you made. --EncycloPetey (talk) 01:21, 14 May 2022 (UTC)

I was making a few similar edits around that time, looks like I got my wires crossed in this case. I see you already took care of the mistake, for which I thank you. Arlo Barnes (talk) 02:20, 14 May 2022 (UTC)

former note

Note to other editors: My personal computer has malfunctioned, so I can now only edit Wikidata from library computers. As such I am taking something of an unplanned wikibreak. Regards, Arlo Barnes (talk) 17:49, 24 July 2021 (UTC)

Site 735 (Q57851885) for SCP-1176 (Q112046439)

This is a scholarly article...--Trade (talk) 15:25, 26 May 2022 (UTC)

Thanks for the heads-up, corrected. Arlo Barnes (talk) 17:46, 26 May 2022 (UTC)

Sugar Cone Emoji

Hello!

In regards to: https://www.wikidata.org/w/index.php?title=Q36940&diff=prev&oldid=1753863073

This should be for Unicode character (P487) instead. -wd-Ryan (Talk/Edits) 04:41, 1 November 2022 (UTC)

loose, half-fast, and fast stone (Q1867511)

Hi Arlo,

the classification has now become distinct items:

• fast stone (Q115130421)
• loose stone (Q115130400)
• half-fast stone (Q115130497)

The images may be removed now.-- Батальйон Нахтігаль (talk) 19:25, 8 November 2022 (UTC)

Thanks / Vielen Dank!--Батальйон Нахтігаль (talk) 20:20, 8 November 2022 (UTC)

Cheers :) Arlo Barnes (talk) 20:22, 8 November 2022 (UTC)

Generic properties?

Thanks for thanking me for my reply at Wikidata:Property proposal/Wikimedia Phabricator project. I am curious if you would prefer the generic modelling I suggested over the instance-specific property the proposal initially suggested? Because I think I agree that it makes sense to have more versatile properties but there for some reason does not appear to be too much support for them (see also my Wikidata:Property proposal/serves resource proposal).

--Push-f (talk) 05:13, 24 November 2022 (UTC)

Merging

Hi! Please, never merge synonyms as in Psephotus pulcherrimus (Q932059). Now we don't have item for Psephotellus pulcherrimus, but we have broken Psephotus pulcherrimus item with 2 taxon names. Can you undo your changes. Thanks. --Termininja (talk) 18:35, 28 December 2022 (UTC)

 Done Arlo Barnes (talk)

Suggestion constraint

Hi, back in October of 2021 you made suggestion constraint (Q62026391) a subclass of Wikibase reason for deprecated rank (Q27949697), and I just found some comments in your archive indicating you had done so to other items as well.

As I understand it, the proper way of defining a reason for deprecation is to declare it an instance of (P31) Wikibase reason for deprecated rank (Q27949697), not a subclass, although for technical reasons the latter has (sort of) worked as well.

However, the subclass method has significant undesirable side effects, as was pointed out in those comments a year and a half ago, such as there being over 9,000 technically valid reasons for deprecation, ranging from Magic in Ancient Egypt (Q21658950) to the Q41580588.

I'm therefore preparing a proposal to remove any subclasses from Wikibase reason for deprecated rank (Q27949697) and create a constraint aginst any new subclasses of that kind. I intend to bring it up in Wikidata:WikiProject property constraints, hoping to get a go-ahead, but first I want to ask you if you still have any use for suggestion constraint (Q62026391) as a reason for deprecation? Because I don't think it was ever meant to serve that purpose, but merely to indicate the status of a property constraint.

Is there anything you think I should know in this regard? SM5POR (talk) 17:14, 12 February 2023 (UTC)

Your plan sounds good to me, proceed as you will. Arlo Barnes (talk) 23:27, 12 February 2023 (UTC)

joke?

Old revision of Q21996814 -- eugrus (talk) 23:52, 11 May 2023 (UTC)

Perhaps you could call it that; its more that I want any variation on the name to lead back to the entity, which is what the aliases column is best at. Arlo Barnes (talk) 00:26, 12 May 2023 (UTC)

Thanks

Thanks for adding my items, Now the problem is how to add it I'm trying add one of them and it's not taking. Can you guide me how to add commons item ? Niccoale (talk) 09:01, 1 July 2023 (UTC)

Incorrect use of instance of (P31)

Hello –

This edit to "National Hispanic Cultural Center" (Q12062400) was in error. Because subclass of (P279) is transitive (for example, see this tree of parent classes), such errors lead to numerous false inferences. Before you use the properties instance of (P31) and subclass of (P279), please be familiar with Help:Basic membership properties, and look at the value item in your statement to be sure it's the one you intend. (In particular, note that all instances of a class must be of the same type.) There is often another property that can accurately express the relationship you had in mind; in this case, field of work (P101) works better. You can search through available properties here. Thanks! Swpb (talk) 18:09, 3 August 2023 (UTC)

Leveling Up Days: your feedback is needed!

Thanks for joining the Wikidata Leveling Up Days!

Hello there,

You receive this message because you added yourself on the participants list of the Wikidata Leveling Up Days. I hope you had a chance to attend the event!

If you didn't have a chance to attend, no worries: all the video materials are available in this Wikimedia Commons category. It includes captions in English and you can also contribute to adding translations in other languages.

If you attended at least one session or watched a video, we would love to have your feedback on the event! We kindly ask you to fill in this participants survey. It is anonymous and will take you 5-10min to answer.

We hope to see you around on Wikidata in the future. If you want to stay in touch with the community, feel free to join or subscribe to our communication channels!

Best, Lea Lacroix (WMDE)

team fortress

By the way, I have started to make items about TF2 weapons if you are interested Trade (talk) 22:11, 8 February 2024 (UTC)

Never played, but I'll check out what you have so far. Arlo Barnes (talk) 23:02, 8 February 2024 (UTC)

NDN Kars (Q124253591)

Is this supposed to be about a track, a song or a single? You are mixing items and properties for all three here Trade (talk) 11:43, 8 February 2024 (UTC)

I started with the Bandcamp track and then wasn't sure how the result should be split up. What do you suggest? Arlo Barnes (talk) 17:24, 8 February 2024 (UTC)

I recommend you use Multi-track Drafting when making songs/tracks in the future Trade (talk) 22:11, 8 February 2024 (UTC)

Excellent, worked like a charm at Boots Quest DX OST (Q124463936)! Thanks. Arlo Barnes (talk) 23:02, 8 February 2024 (UTC)

instance of (P31) item-requires-statement constraint

Deities are not appropriate for instance of (P31) - item of property constraint (P2305) Bamyers99 (talk) 19:58, 27 November 2023 (UTC)

Okay, why is that? Arlo Barnes (talk) 19:59, 27 November 2023 (UTC)

It's because the P31 property applies to instances of most everything, not just deities. :) 5.64.158.190 20:03, 27 November 2023 (UTC)

I see. Do you know if there is a way to specify a constraint such that an item with instance-of [special type of deity] will warn if there is no 'domain' statement? Arlo Barnes (talk) 20:09, 27 November 2023 (UTC)

Wikidata:Schemas provide for data structure model checking, although they are not at present tied into the automatic constraint checking. Bamyers99 (talk) 20:21, 27 November 2023 (UTC)

This SPARQL query can be used to find deities w/o domain. After clicking Try it, press the white arrow inside the blue box to run it. Replace deity (Q178885) with a subclass (ie. storm deity (Q115481069)) to restrict the results.

# deity and subclasses w/o domain
SELECT DISTINCT ?s ?sLabel WHERE {
  ?s wdt:P31/wdt:P279* wd:Q178885 .
  OPTIONAL {
    ?s wdt:P2925 ?domain
  }
  FILTER ( !bound(?domain) ) .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en" }
 }
ORDER BY ?sLabel

Try it!

--Bamyers99 (talk) 20:50, 27 November 2023 (UTC)

All the Tropes ID (P8895)

https://www.wikidata.org/wiki/Wikidata:Properties_for_deletion#Property:P6096

Could i get your input here? Trade (talk) 03:27, 9 October 2023 (UTC)

Unknown fictional character

Do you remember making Yūichi Jin (Q119123909)? I don't believe this character exists, so is it perhaps a conflation of two different things? Xezbeth (talk) 05:39, 6 October 2023 (UTC)

Yes, a conflation; got the series wrong. Corrected now. Arlo Barnes (talk) 15:24, 6 October 2023 (UTC)

JB Rietstap arms

on Q1370177 you recently added the arms image. Do you happen to remember what your source was for those being his arms, rather than just the arms of some (unspecified) family called Rietstap? The person who created the SVG image only provided the latter on the page, and they've quit being active on Wikimedia Commons. Pseudomonas (talk) 17:07, 5 September 2023 (UTC)

Ah I see, they quit due to having uploads deleted. I was just going off the filename, I'll deprecate the statement so that it is not used until we find a source. Arlo Barnes (talk) 17:11, 5 September 2023 (UTC)

Thanks! I've requested an image move to "Rietstap wapen.svg" which should be an uncontroversial name. Pseudomonas (talk) 17:14, 5 September 2023 (UTC)