Open Humans EditEdit
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)
Personal Data WikiProjectEdit
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 Q66048962Edit
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 SurveyEdit
RMaung (WMF) 17:38, 10 September 2019 (UTC)
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)
Lack of refs on Q63016981Edit
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)
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)
Hey, I deleted your has part (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)
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,
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?Edit
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 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 (P1933), Duden 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 identifier (P7772), ToS;DR service numerical identifier (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 DescriptionEdit
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)
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 & WikidataEdit
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)
Jen-Hsun Huang EngineeringEdit
copyright license (P275) constraint editsEdit
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)
- I guess this edit caused the most constraint violations. Multichill (talk) 10:32, 8 May 2021 (UTC)
Formatter URL (P1630) of format as a regular expression (P1793)Edit
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)
Wikiproject Welcome to Night ValeEdit
- 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)
Call for participation in the interview study with Wikidata editorsEdit
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 firstname.lastname@example.org or email@example.com 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.