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

Wikidata:Project chat

From Wikidata
Jump to navigation Jump to search

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

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

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

Wikidata weekly summary #634

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

Discussions

  • New requests for permissions/Bot:
    • DifoolBot 4 Task(s) - Split single references containing multiple reference URLs into multiple references.
    • Bot Bozze Task(s) - Add sitelinks to itwiki draft articles after they've been moved to the main namespace.
  • New request for comments: Spelling convention for labels and descriptions in English - RfC started 2024-06-25. This RfC requests feedback and input for finding consistency in spelling convention as English has multiple regional variations.

Events

  • Past: The Lexicodays 2024 was an online event designed to offer a discussion space for the Wikidata community about Lexicographical Data. An archive of some of the slides and session recordings are here c:Category:Lexicodays 2024. More will be added as they become available.
  • Upcoming:
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 10th July 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Talk to the Search Platform / Query Service Team—July 3, 2024
    • Botany-focused Wikidata online workshop online as part of the #IBC2024. Date: Tuesday 9th July at 9pm NZST (GMT+12) / 11 am central Europe. Register here!

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

  • The second iteration of the Wikidata:Open Online Course has begun. Class will continue until August 11. Whether you're a beginner taking your first steps, an individual in need of a refresher on Wikidata concepts, or a seasoned trainer looking to level up your skills - this course is right for you.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • EntitySchemas:
    • We worked around an issue where EntitySchema pages were no longer considered “content” and had become unsearchable (phab:T368010)
    • We prepared for the release of the new datatype on July 2nd.
  • mul language code: We are working on the last remaining blocker before rolling out the first stage to Wikidata (phab:T362917)
  • Wikibase REST API: We are continuing to rework API errors (phab:T366911, phab:T366239)

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

The wiki is now in read-only mode

[edit]

"Failed to save due to an error." and "The wiki is now in read-only mode." pop up. Why? Eurohunter (talk) 05:26, 2 July 2024 (UTC)[]

Apparently there were some brief spikes of replication lag around the time you posted that message; when this happens, the wiki may automatically put itself into read-only mode temporarily until the database has caught up again. Lucas Werkmeister (WMDE) (talk) 09:25, 2 July 2024 (UTC)[]

value-requires-statement constraint (Q21510864)

[edit]

Why If I add subclass of (P279) with for example history of Berlin (Q679741) then value-requires-statement constraint (Q21510864) pop up? For example, it pop up at history of trams in Berlin (Q1514212) while it not pop up in history of trams in Barcelona (Q11925955). Eurohunter (talk) 06:18, 2 July 2024 (UTC)[]

@Eurohunter You have to make sure there is a complete hierarchy of classes. In the example you have given, Q1514212 has class Q679741, but Q679741 needs to have some class too... I suggest Q122131 be added there as P279. Vojtěch Dostál (talk) 13:26, 2 July 2024 (UTC)[]
@Vojtěch Dostál: Thanks. Eurohunter (talk) 12:14, 6 July 2024 (UTC)[]

Implementing Orphanet Data into Wikipedia

[edit]

Orphanet is an important reference within wikipedia with over 1000 refs. Recently, they changed their data structure, thus the former Template:Orphaned does no longer work. I got a file with relevant changes I would like to be implemented. Zieger M (talk) 07:38, 2 July 2024 (UTC)[]

@Zieger M Hi, can you share the file publicly, so that I (or others) can have a look and decide if we're able to implement the change? Vojtěch Dostál (talk) 07:42, 2 July 2024 (UTC)[]
Yes, how can I share it? Zieger M (talk) 07:44, 2 July 2024 (UTC)[]
@Zieger M If it is a table file, maybe you can upload somewhere and share a link? Ideally, with properly labelled columns so that we understand what changes to what :-). Vojtěch Dostál (talk) 07:46, 2 July 2024 (UTC)[]
"upload somewhere"? Never done, don't know where to. Sorry Zieger M (talk) 07:51, 2 July 2024 (UTC)[]
https://www.mediafire.com/file/uimhjnvs9g4uf49/Linkliste+Orphanet_Original.xlsx/file Zieger M (talk) 12:01, 2 July 2024 (UTC)[]
@Zieger M Hi, I checked the file and I think I now better understand what you mean. In fact, the change does not have anything to do with Wikidata - you just want to properly format its links to Orphanet. I think that you only need to replace the URL string "https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=DE&data_id=" at de:Template:Orphanet with "https://www.orpha.net/en/disease/detail/". Isn't that right? You can do it locally in Dewiki. Vojtěch Dostál (talk) 13:16, 2 July 2024 (UTC)[]

Wikidata Question

[edit]

Hi Wikipedia, I have two concerns regarding data for Blic, daily newspaper from Serbia. I have tried entering publication interval and for some reason it does not let me publish it. Also, I have tried editing their social media information and it did not let me. For both of them, it does not let me publish changes. Can you tell me why ? Боки ✉ 18:21, 2 July 2024 (UTC)[]

What does it say? Ymblanter (talk) 18:42, 2 July 2024 (UTC)[]
@Ymblanter it doesnt say anything.
Basically, when I try and change it, publish button is blanked so I cant click on it. Боки ✉ 18:50, 2 July 2024 (UTC)[]
If you enter say "1 week" in the field for publication interval then the check-mark can't be clicked. Unit goes into a separate field. Infrastruktur (talk) 19:03, 2 July 2024 (UTC)[]
[edit]

I noticed that this item is linked not only as an antiseptic but also for many other medical topics. Its description only mentioned "antiseptic" and I've added the prevention and treatment of iodine deficiency, based on its page linked from WikiProjectMed. The mistake may arise from the fact that it's disambiguated in the English- (and several other) language Wikipedia(s) as "iodine (medical use)". I think all other medical uses (e.g. radioactive iodine therapy (Q13233408)) should link to either to iodine as an element (iodine (Q1103)), or to a new item created for this purpose, but the antiseptic (and possibly the deficiency-preventing) use shouldn't be conflated with the radioactive or other medical means of using it. Adam78 (talk) 21:08, 2 July 2024 (UTC)[]

@Adam78 Is iodine as antiseptic in any way chemically different from the iodine element? If not, all such links should point to iodine (Q1103) and Q28196266 should instead be facet of (P1269) of iodine (Q1103) or something of that sort. A similar example is calcium in biology (Q60097). Vojtěch Dostál (talk) 11:25, 4 July 2024 (UTC)[]

Railway junctions: Q24045957 vs Q336764

[edit]

I'd be grateful if anyone could help me distinguish railway junction (Q24045957) and junction (Q336764) -- both used specifically for railway junctions, and distinct from railroad switch (Q82818) and the more general junction (Q1777515).

There seem to be two different concepts here, at least in German, but I'm not entirely seeing how they should be named in English to express the difference, or whether articles in the various different language wikis are all connected to the correct item.

Which would be most appropriate for a location where one linear ELR railway line section (Q113990375) of track (perhaps 50 km long, double-track) meets another such section? Jheald (talk) 22:10, 2 July 2024 (UTC)[]

Multichill (talk) Thryduulf (talk) 21:38, 2 November 2013 (UTC) -revi (talk • contribs • logs)-- 01:13, 3 November 2013 (UTC) (was Hym411) User:JarrahTree (talk) 06:32, 3 November 2013 (UTC) A.Bernhard (talk) 08:28, 9 November 2013 (UTC) Micru (talk) 12:36, 9 November 2013 (UTC) Steenth (talk) YLSS (talk) 13:59, 25 November 2013 (UTC) Konggaru (talk) 12:31, 14 December 2013 (UTC) Elmarbu (talk) 21:48, 17 December 2013 (UTC) Nitrolinken (talk) 16:30, 14 February 2014 (UTC) George23820 Talk‎ 17:39, 17 August 2014 (UTC) Daniele.Brundu (talk) 21:34, 30 August 2015 (UTC) Dannebrog Spy (talk) 16:13, 9 December 2015 (UTC) Knoxhale 18:39, 26 June 2016 (UTC) happy5214 22:48, 8 July 2016 (UTC) Jklamo (talk) 07:32, 15 August 2016 (UTC) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits DarTar (talk) 16:36, 5 September 2016 (UTC) Pizza1016 (talk | contribs) 01:33, 10 November 2016 (UTC) Sascha GPD (talk) 23:00, 1 February 2017 (UTC) Liuxinyu970226 (talk) 09:09, 2 February 2017 (UTC) A1AA1A (talk) 18:17, 21 May 2017 (UTC) Mauricio V. Genta (talk) 13:56, 9 June 2017 (UTC) Sam Wilson 10:26, 18 June 2017 (UTC) Danielt998 (talk) 05:01, 28 August 2017 (UTC) Maxim75 (talk) 06:04, 22 September 2017 (UTC) Fabio Bettani (talk) 17:48, 3 June 2018 (UTC) Geogast (talk) 23:51, 13 July 2018 (UTC) Bodhisattwa (talk) 19:29, 17 December 2018 (UTC) Jinoytommanjaly (talk) 13:13, 21 May 2019 (UTC) OktaRama2010 (talk) 00:25, 1 May 2020 (UTC) PhiH (talk) 14:20, 26 July 2020 (UTC) Jcornelius (talk) 18:47, 30 July 2020 (UTC) Mackensen (talk) 15:21, 29 August 2020 (UTC) Michgrig (talk) 22:04, 20 December 2020 (UTC) Trockennasenaffe (talk) 16:27, 5 September 2021 (UTC) Secretlondon (talk) 07:46, 3 September 2022 (UTC) GALAXYライナー (talk) 05:17, 14 October 2022 (UTC) Yirba (talk) 09:49, 10 August 2023 (UTC) Zwantzig (talk) 09:08, 07 September 2023 (UTC) S4b1nuz ᴇ.656(SMS) 16:16, 21 November 2023 (UTC) Prefuture (talk) 07:02, 16 December 2023 (UTC) Cmelak770 (talk) 14:06, 15 May 2024 (UTC) DaxServer (talk) 14:41, 31 May 2024 (UTC)[]
Notified participants of WikiProject Railways. (I did ask on the talk page there a couple of years ago, but it didn't get any responses.) Jheald (talk) 22:14, 2 July 2024 (UTC) []
I can explain these from the Czech point of view, but the explanation is similar for all countries in the central Europe (Poland, Germany, Slovakia etc.). At thirst railway junction (Q24045957) is very big (hundreds of switches) and junction (Q336764) is very small (sometimes only one switch, but usually not more than four switches). railway junction (Q24045957) express connection of lot of railway lines usually in one town/city. E.g. železniční uzel Praha (Prague junction) consists of all railway station in Prague (Q1085), in which all railway lines leading to this big city are connected. junction (Q336764) is usually a place where one railway line splits into two railway lines and it is not railway station (Q55488), so if the railway lines are with one track, then one switch can be enough. In Czechia and Poland it is also a place on the double track line between two stations, where are 4 switches to go from the left to the right track and vice versa (the same place is Slovakia (till 2000 also in Czechia) is classified as passing loop (Q784159)). But I have no idea how to name these different places in English. When I translate it, I usually use "junction" for both, although they have completely different meanings. --Cmelak770 (talk) 06:54, 3 July 2024 (UTC)[]
In Germany we strongly distinguish between free track (Q1302250) which roughly means track which is not part of a railway station (Q55488) and tracks that are part of a railway station (Q55488). junction (Q336764) is a junction, that is not part of a railway station (Q55488). As far as I know, (most?) english speaking countries don't have this concept free track (Q1302250), so this may not be easy to translate. --Trockennasenaffe (talk) 06:09, 4 July 2024 (UTC)[]
Asked at en:Wikipedia_talk:WikiProject_UK_Railways whether anyone there can suggest better English-language labels / descriptions Jheald (talk) 12:56, 7 July 2024 (UTC) []

Ingest of SEC EDGAR data into Wikidata?

[edit]

I have recently noticed that many company infoboxes on Wikipedia are frequently out of date, even though they draw from Wikidata for many values like yearly results. All of this data is available online through the SEC's EDGAR system, at least for publicly traded companies in the US, so I was wondering whether it would be worthwhile to write a bot that would read SEC data and update Wikidata with it?

Botlord (talk) 19:18, 3 July 2024 (UTC)[]

Conventions for Knowledge Graph aligning

[edit]

Dear Wikidata Community,

We're looking to build a Aerospace Engineering Knowledge Graph, and linking (all) entries to wikidata. For some, like Q3319996, that's easy, for others like conceptual modelling not so much. Others, like CPACS, are not even in Wikidata yet, or Wikipedia for that matter. Given that context, I have the following cases and questions:

  1. If a perfect match exists, no questions.
  2. If a match exists that does look correct, but seems to be lacking relations, should we populate this entry as we see fit? (assumed answer: yes, see en:WP:BOLD)
  3. If a match exists that does look somewhat corect, but does not have the right type, should we split it into two different entities?
    1. e.g. Q377960 not being a Q3249551, but an Q166142 - should we create a new process instance with the same label?
    2. what about instances such as Q2623243, which specifically lists conceptual model (an object) and conceptual modelling (a process)? Does the existence of this entry mean differentiation is not desired?
  4. If no match exists, I assume we should create one. I've taken a look at Wikidata:Notability:
    1. "It refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references."
      1. All instances would fall under this category, since all are derived from a systematic literature review and we can link to the respective papers where they are discussed.
    2. All our instances would be instances of Q10843872, Q7397, Q235557 or similar. Examples: https://github.com/DLR-SC/tixi, https://dlr-sl.github.io/cpacs-website/

Furthermore, I have some SPARQL / Database questions, which I'll add to a separate topic to not overflow this one.

Thanks, TimBorgNetzWerk (talk) 11:00, 4 July 2024 (UTC)[]

API / Pyton / SPARQL access questions

[edit]

Hi everyone,

please see Wikidata:Project chat#Conventions for Knowledge Graph aligning for context.


TL;DR, we're looking to check if a wikidata instance exists for ~500 entries we have in our database. We also don't want to overburden the Wikidata API, hence:

What can we do to most efficiently query the wikidata database?


What currently do is: 

query = f"""
SELECT ?item ?itemLabel (GROUP_CONCAT(DISTINCT ?altLabel; separator = ", ") AS ?altLabels) 
(SAMPLE(?description) AS ?description) WHERE {{
{selection[select]}
OPTIONAL {{?item skos:altLabel ?altLabel FILTER(LANG(?altLabel) = "en")}}
OPTIONAL {{?item schema:description ?description FILTER(LANG(?description) = "en")}}
SERVICE wikibase:label {{bd:serviceParam wikibase:language "en".}}
}}
GROUP BY ?item ?itemLabel
LIMIT {limit}
"""

, wherin we limit the results to 20 at most, and select based on: 

selection = {
    'label' : f'?item rdfs:label "{label}"@en.',
    'altLabel' : f'?item skos:altLabel "{label}"@en.'
}

Then, per label, we check if:

  1. entries with that label are available (e.g. "STEP file" to Q3509055
  2. if these entries do not sum up to our limit (20), then we also check if entries with that label as altLabel exist (e.g. ".stp" to Q3509055),
  3. if these entries do not sum up to our limit (20) then we try 1. and 2. again with (if != label):
    1. label.lower(), so "STEP" -> "step",
    2. label.capitalize(), so "STEP" -> "Step",
    3. label.upper(), so "STEP" -> "STEP" -> not done, since == label


Then we store all queries and results so we run no query twice, and can just check our local "copy" for the result.


Given all this, our Question:

  1. Is there a better way?

Better as in "easier on wikidata / time" as well as "better results", since currently we have about 40% match rate. Likely, many ouf our instances do, in fact, have no match, but others (like Q2117885 "Systems Modeling Language" or "SysML") are currently just not catched. We have seen advise to run some preprocessing on the labels, to lower all wikidata labels in a filter, but that seemed unfathomably taxing on all parties involved.

There is also the general advice to use a data dump. We have checked Wikidata:Database download and https://dumps.wikimedia.org/wikidatawiki/entities/, and not found a dump that contains all labels AND is relatively small. The lexemes do not seem to contain all labels, presumably only Q111352 instances. All the aformentioned entries, e.g. .p21 and .stp, are not mentioned therein.


I really appreciate your help, and am open to suggestions, improvements, hints or anything, really :)


Best, TimBorgNetzWerk (talk) 11:30, 4 July 2024 (UTC)[]

Have you considered using a tool like OpenRefine to help reconcile your data with Wikidata's? M2Ys4U (talk) 16:26, 4 July 2024 (UTC)[]
Haven't heard about it yet (I think), will be looking into it, thanks! TimBorgNetzWerk (talk) 09:50, 5 July 2024 (UTC)[]
OpenRefine is nice if you intend to import data into Wikidata. Last time I checked the reconciliation it uses yielded less than ideal results. Is this a publicly available graph? If your graph had it's own identifier registered on Wikidata you could use Mix'n'match to do a preliminary matching of the dataset and then let you verify each match manually. Asking for a new identifier can be done at WD:PP.
In any case freetext search may be what WDQS is worst at. Unsurprisingly the built-in search does a much better job, see [1] for Wikidata specific functionality. You won't tax the API as long as you make calls sequentially and support maxlag. There are libraries available that makes this easier. Infrastruktur (talk) 16:36, 5 July 2024 (UTC)[]

Very widely used property no longer works

[edit]

See Property talk:P5380#No longer works BhamBoi (talk) 22:25, 4 July 2024 (UTC)[]

We need to put an end to this

[edit]

For months, items like

and likely more others have been target of constant edit warring, having English and Russian description changed back and forth by various IP addresses and few-edits-accounts. Could anyone have a look, say what is going on and suggest how administrators should deal with it? --Matěj Suchánek (talk) 08:57, 5 July 2024 (UTC)[]

Chechen-Ingush wars. All items should be protected at a random version. May be we should block the warriors as well. Ymblanter (talk) 19:41, 5 July 2024 (UTC)[]
Though may be things like this would help before protection, but then I need to go manually through the list. I can do it, but very slowly. Ymblanter (talk) 19:44, 5 July 2024 (UTC)[]
I see no good reason to protect them to be only edited by admins. Semiprotections should be good enough. ChristianKl ❪✉❫ 21:09, 6 July 2024 (UTC)[]

"agency" property?

[edit]

I'm getting "{{cite journal}}: |author= has generic name (help)" from:

  • CNN Newsource (24 February 2021). "Urban League of Greater Kansas City unveils social justice bus". KMIZ. Wikidata Q126365824.View profile on Scholia

in Wikipedia:Gwendolyn Grant (activist)#References.

In a section on "work with template:Cite Q?" on the talk page associated with Wikipedia:Template:Sfn, Wikipedia:User:ActivelyDisinterested said, "CNN News Source is not a valid author name ... . The correct field in this case would be |agency= but [that is not] supported by Wikidata / Cite Q." I've experimented with assigning "CNN Newsource" to different properties, so far without finding one that makes this complaint disappear.

Can someone help me find a property to which to assign "CNN Newsource" (Q5013147) so this complaint in Wikipedia disappears? Thanks, DavidMCEddy (talk) 00:15, 6 July 2024 (UTC)[]

constraint on instance or subclass of

[edit]

ISFDB award ID (P11395) has constraint 

subject type constraint:
class - type of award 
relation - instance or subclass of

So why is Ditmar Award (Q906455) which is a subclass of (P279) of science fiction award (Q107581015), an instance of (P31) of type of award (Q107467117) OK

While William Atheling Jr. Award (Q8004646) which is an instance of (P31) of literary award (Q378427), an instance of (P31) of type of award (Q107467117) reports a violation? Vicarage (talk) 14:07, 7 July 2024 (UTC)[]

Because William Atheling Jr. Award (Q8004646) is currently neither an instance nor a subclass of type of award (Q107467117) (instance of (P31) is not transitive and neither literary award (Q378427) nor Ditmar Award (Q906455) are subclasses of type of award (Q107467117)) while Ditmar Award (Q906455) is a direct instance of type of award (Q107467117). It seems to me that the subject type of ISFDB award ID (P11395) should be instance or subclass of science fiction award (Q107581015), not type of award (Q107467117). - Valentina.Anitnelav (talk) 09:00, 8 July 2024 (UTC)[]
Ah, I was expecting instance of (P31) to be transitive in this check. Changing ISFDB award ID (P11395) as you suggest solves my problem. Thanks. Vicarage (talk) 09:12, 8 July 2024 (UTC)[]

Removing unreferenced religions and ethnicities

[edit]

@Nikkimaria: Was a decision made to remove all unreferenced religions and ethnicities at some point? If so I missed that discussion. If the decision was made they should be deleted by a bot, not one-by-one by any individual. Doing it that way will lead to selection bias. I noticed some disappearing and traced the deletions to Special:Contributions/Nikkimaria RAN (talk) 16:21, 7 July 2024 (UTC)[]

These are mostly reverts of a particular problematic IP editor who pops up periodically in Special:AbuseFilter/95. If there is a preference to revert such edits by bot I have no objection. Nikkimaria (talk) 16:37, 7 July 2024 (UTC)[]
For ethinicities, removal was approved for unreferenced statements and deprecation for Wikipedia-referenced statements, see Wikidata:Bot_requests/Archive/2021/10#request_to_depreciated_ethnic_group_only_sourced_with_P143_(2021-10-23). At the time I think it was also notified or discussed on Project chat. Vojtěch Dostál (talk) 07:38, 8 July 2024 (UTC)[]

Voting to ratify the Wikimedia Movement Charter is ending soon

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

Hello everyone,

This is a kind reminder that the voting period to ratify the Wikimedia Movement Charter will be closed on July 9, 2024, at 23:59 UTC.

If you have not voted yet, please vote on SecurePoll.

On behalf of the Charter Electoral Commission,

RamzyM (WMF) 03:45, 8 July 2024 (UTC)[]

Is there something like a Wikidata WP:DOB?

[edit]

Specifically Q5364577, which seems to be ultimately sourced to imdb. Gråbergs Gråa Sång (talk) 06:43, 8 July 2024 (UTC)[]

Yes - see Wikidata:BLP. ArthurPSmith (talk) 17:35, 8 July 2024 (UTC)[]
Thankfully, Wikidata can structure these claims better than a textually-based Wikipedia project can.
For example, references can be attached directly to the DOB claim; these will unambiguously support that particular claim, and no others.
Also, multiple claims can be attached to one person's bio. Therefore if there is dispute, ambiguity, or competing claims for a DOB, all can be included!
Deprecation and preference values can be assigned. Therefore, if a DOB claim is found to be incorrect or invalid, it can be deprecated, colored red, and notations can be made about those reasons. Likewise, if a DOB is found to be valid above the others, it can be marked "preferred".
In this way we can better document any controversy, weak/strong sourcing issues, or disputes, not only about a date of birth but about any germane fact for a Wikidata item. It's a shame that enwiki still doesn't want to play nice and draw from Wikidata's growing pool of structured data such as this, because it's way easier to document and track such disputes here in one centralised location, than in parallel, on dozens or hundreds of language-specific wikis, with mazes of twisty little policies and guidelines, all different. Elizium23 (talk) 18:36, 8 July 2024 (UTC)[]

Wikidata weekly summary #635

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

Events

  • Upcoming:
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 10th July 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Registration for Wikimania 2024 is open! In-person participants: please register until 26 July, 11:59 p.m., UTC. Virtual participants can register anytime. If you received a scholarship from the Wikimedia Foundation, you will receive an email with a registration code and instructions.

Tool of the week

  • User:Teester/EntityShape.js - a userscript that adds an input box to a Wikidata page wherein you can enter an EntitySchema (such as E10). When you click "Check", checks whether each statement and property conforms to the schema. It then displays a summary at the top of the Item for each property indicating whether they conform or not. It also adds a badge to each statement and each property on the page indicating whether they conform or not.

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • EntitySchemas: The new datatype to link to EntitySchemas in statements has been released.
  • mul language code: We are preparing the release.

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

Showcase items discussion

[edit]

Editors are invited to join the discussion at Wikidata talk:Showcase items § Formalizing the process. Sdkb talk 19:31, 8 July 2024 (UTC)[]

Good practice on labels

[edit]

(pinging @Tm. continuing discussion from User talk:Tm#Edits on stores for Lojas com História. no harm to them.)

to the Wikidata community, I want to ask about Help:Label and what is the good practice in this situation. some Wikidata items, in this case buildings, are labeled simply as their street address with a prefix. take for example, Prédio na Rua Joaquim António de Aguiar, 45 (Q98962545) (literally, "building on Rua Joaquim António de Aguiar, 45") or Q90315021 (literally, "Loja Confeitaria Nacional, ground floor, including integrated movable heritage"). this is taken straight from the sourced external databases.

according to Help:Label: Labels begin with a lowercase letter except for when uppercase is normally required or expected [...] proper nouns such as the names of specific people, specific places, specific buildings, specific books, etc., should be capitalized. my question is, would this be counted as a proper name? the building itself has no name and these are simply descriptions of the given place. so then how would it be labeled? JnpoJuwan (talk) 00:13, 9 July 2024 (UTC)[]

These are proper names, as i said to you. They have their proper name by the portuguese cultural heritage, the former DGPC. If you had taken a few minutes you would see that, no ad hoc translation made with any sourced translated name is made, these are proper names named so in legislation and\or portuguese cultural heritage databases kept by the portugues estate organizations that have in their remit said cultural heritage. You said that :Prédio na Rua Joaquim António de Aguiar, 45 that "the building itself has no name and these are simply descriptions of the given place" yet you have the main DGPC database, other database of DGPC with the same name.
And Loja Confeitaria Nacional, piso térreo, incluindo o património móvel integrado] is the listed part of the shop Confeitaria Nacional, as the shop is not all listed cultural heritage in its totality. Again the name is the proper name, as stated in main DGPC database and legislation listing it, from Anúncio n.º 174/2017, going with Anúncio n.º 38/2020 and ending in Portaria n.º 613/2020. Tm (talk) 00:28, 9 July 2024 (UTC)[]
And these names are completly used in Wikidata, just as an example Iron Foundry (building Number 1/140) Iron Foundry (building Number 1/140) Including Railings And Bollards or Vulcan Block (Building Number 21) And Attached Bollards or Number 15 And Attached Agricultural Building or Factory Building Outbuilding Attached To Number 55 or Castle Farm Cottages Number 5 And Farm Building Attached, british listed cultural heritage monuments, among of hundreds silimars. Tm (talk) 00:48, 9 July 2024 (UTC)[]
I am also asking to a wider community to determine whether it is a good thing to continue doing as such. JnpoJuwan (talk) 00:50, 9 July 2024 (UTC)[]
Any search for listed buildings will show you that this is a common and long established pratice. Tm (talk) 01:07, 9 July 2024 (UTC)[]
Like, as an example of an US building New York Herald Building or the listed building in U.S. National Register of Historic Places Building at 73 Mansion Street and this last building uses same the name in its articles in english Wikipedia and german Wikipedia Tm (talk) 01:35, 9 July 2024 (UTC)[]
I have seen the descriptions given in these items, that I do not doubt. what I ask is: what is considered a proper name here, as the same databases list many other designations for the same item besides that, or for SIPA, do not list the original.
even if these are the legally recognised names, is it useful to list these names first as opposed to descriptive and importantly translatable names? JnpoJuwan (talk) 00:48, 9 July 2024 (UTC)[]
This are monuments are named so in legislation and the databases of the portuguese Património Cultural, IP (former DGPC), so these are proper names. The pratice in Wikidata is not not make ad hoc translation without proper sources that state that there is a commons translated name and you have the example of the british listed cultural heritage monuments to see what these are proper names and they are capitalized in Wikidata.
These are designations are other proper names to the same items, from the databases of portuguese Património Cultural, IP (former DGPC) from the main DGPC database (and legislation) for cultural heritage monuments. For complement, there are other databases from Património Cultural, IP (former DGPC) like the SIPA database and, for specific cases, other databases of works of specific routes or arquitects like the as the one linked as "other database of DGPC" and or archeological sites database. Tm (talk) 01:04, 9 July 2024 (UTC)[]
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=2199013076"