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 or the Telegram groups.
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 2023/03.


Property:P7966 & Property:P7967[edit]

URLs used in Wikidata for P:P7966 and P:P7967 are dead

For NetBSD package (P7966), the formatter URL to use is https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/$1

Genium. 09:12, Feb 1, 2023 (UTC+01:00)

Transcluding lexemes[edit]

Hello. How is it possible (if at all) to transclude grammar forms of lexemes in Wikipedia? For example, I would like to use a genitive and sometimes a dative form of a noun (language: Slovene) in various templates. Can I insert them by calling them from Wikidata? Or should I go about this differently? --TadejM (talk) 02:21, 10 February 2023 (UTC)Reply[reply]

I guess this is not yet possible. I've filed a feature request (phab:T329344). --TadejM (talk) 03:08, 10 February 2023 (UTC)Reply[reply]
@TadejM: This little demonstration in the English Wikipedia might be of interest. ―BlaueBlüte (talk) 09:34, 10 February 2023 (UTC)Reply[reply]
BlaueBlüte, it seems great. I will check it out to see if it suits my needs. Thank you! --TadejM (talk) 09:36, 10 February 2023 (UTC)Reply[reply]
BlaueBlüte, it just works perfect. I've implemented it in sl:Predloga:Mesec kategorija. There are perhaps other things that need to be taken into account (vandalism, load etc.), but it does solve a major problem. Thank you again. --TadejM (talk) 10:29, 10 February 2023 (UTC)Reply[reply]
BlaueBlüte, what I don't see able to do is to call forms defined with two or more grammatical features; see e.g. L1013827. I guess these forms should always be defined with more than two grammatical features. The module's usability would be greatly expanded if it was possible to link directly to lexeme forms. Which I guess should be possible to implement.[1] --TadejM (talk) 14:28, 10 February 2023 (UTC)Reply[reply]
@TadejM: What I've generally done in this case--albeit somewhat inefficiently--is to iterate through the forms, concatenate the sorted QIDs of all features, and then check whether the result matches a particular ordered set I've previously defined. See bn:wikt:মডিউল:বাংলা_আভিধানিক_উপাত্ত for what I mean regarding concatenation (lines 235-238) and the particular ordered sets (lines 130-229). Mahir256 (talk) 14:45, 10 February 2023 (UTC)Reply[reply]
@TadejM: What would be the benefit of transcluding a specific lexeme form, say writing {{transcLexF|L1013827-F2}} in a page (invoking some fictitious lexeme-form-transcluding template Template:transcLexF), over just writing out the form in the page as meseca (cf. meseca (L1013827-F2))? ―BlaueBlüte (talk) 08:06, 17 February 2023 (UTC)Reply[reply]
Hello, BlaueBlüte. Transclusion would be mutually beneficial. On the one hand, it would possible to change the form in one place if required, provide additional information on the word/phrase, and reduce the number of spelling mistakes. On the other hand, Wikidata would put the forms to practical use and could also gather additional information on their use and the context where they are used. Finally, I guess it could be further upgraded, for example by creating sets of related forms that are displayed depending on the user preferences or something. It could also be used in various parser functions, such as {{#ifeq}}. Thank you. for the question. --TadejM (talk) 08:48, 17 February 2023 (UTC)Reply[reply]
BlaueBlüte, what I would in particular appreciate is to be able to define lists of various case forms for names of individual languages that may be reused at various places in various cases and without duplication. These are tiresome to translate again and again and variants easily occur if the name is not centralized as much as possible. It should be possible to translate them at one place, preferably in a central repository.
For example, in English the same word is used for lang-de to show a German term in the article text, to indicate a language name in the infobox or to name the category Articles with sources in German. In Slovene, one has to use the word nemško (adjective) for the article text, the word nemščina for the infobox and the word v nemščini (locative) for the category name. As said, the management of these forms should be centralized to avoid redundancy and variants.
The same applies for other such lists, e.g. of artistic media etc. --TadejM (talk) 19:51, 19 February 2023 (UTC)Reply[reply]
All those arguments and use-cases clearly make sense, but it would seem to me that any solution (maybe except for the grammatically simplest languages) has to go beyond what one might call ‘transcluding lexemes’—rather, a mechanism for dynamically selecting forms (or even lexemes) based on some feature (or even part-of-speech) requests seems necessary.
As to your example, which lexemes have the required Slovene forms
nemško
,
nemščina
, and
(v) nemščini
, repsectively (or the ones denoting any other language)? (If they aren’t in Wikidata yet, could you create them so we have an example to work from?) Also, is the preposition/particle
v
always the same with all language nouns? Or might it be a different preposition/particle like
po fantaščini
for some language nouns (making one up here)? BlaueBlüte (talk) 23:40, 19 February 2023 (UTC)Reply[reply]
Hello, BlaueBlüte. I would be very inclined to develop this option further when it is available in its basic form. Please note that the developer at the linked ticket in Phabricator said the transclusion should work via the form IDs, so I guess any selector should be implemented downstream via a module. I've created three lexemes for German yesterday with various forms that may be used to further illustrate the development: L1029357 (noun), L1029405 (adjective), and L1029479 (adverb). Yes, the locative and instrumental may use different prepositions, so I've omitted them in the forms. What I also found out was that a) the work was very tedious, b) the presentation of forms is non-transparent (they should be presented in a table instead), and c) many such forms are available on Wiktionary, so they could be reused. What's your opinion about how we should proceed? --TadejM (talk) 11:23, 20 February 2023 (UTC)Reply[reply]
@TadejM: Just briefly replying on one of your points, regarding nemščina (L1029357), nemški (L1029405), and nemško (L1029479): I added one sense each, and related those to German (Q188) via item for this sense (P5137). Could you have a look and check if those senses and statements are correct? Also, nemško (L1029479) currently has no forms. We need at least one form on any lexeme we want to transclude. Could you add one (even if the spelling might be exactly the same as in the lemma)? Thanks, BlaueBlüte (talk) 22:07, 22 February 2023 (UTC)Reply[reply]
@BlaueBlüte:, I have checked this and confirm that the meanings and senses are correct. I have also added a form for nemško (which may refer to German language, Germans or Germany). --TadejM (talk) 19:35, 28 February 2023 (UTC)Reply[reply]
Hi, Mahir256. Thank you for providing this. I'll try around a bit and see what works best. --TadejM (talk) 14:59, 10 February 2023 (UTC)Reply[reply]
One of the ideas of Wikifunctions is to provide an enviroment that can provide functions that do task like this. I don't think it would make much sense to invest into providing another API for this. ChristianKl ❪✉❫ 15:40, 10 February 2023 (UTC)Reply[reply]

Here is the code to call a form by its ID provided by a developer at Phabricator. If anyone will use it to construct a module, please link it here for others to reuse. --TadejM (talk) 03:04, 15 February 2023 (UTC)Reply[reply]

Accidentally made a lexeme instead of an item[edit]

invalid ID (L1037367) - I didn't know what "lexeme" meant in English (I'm not a native English speaker). --Μητσίκας (talk) 16:35, 25 February 2023 (UTC)Reply[reply]

✓ Deleted @Μητσίκας Estopedist1 (talk) 18:36, 25 February 2023 (UTC)Reply[reply]
It should not be necessary to know any English for this task. Does https://www.wikidata.org/wiki/Special:NewLexeme currently lack a Greek translation? ChristianKl ❪✉❫ 18:39, 25 February 2023 (UTC)Reply[reply]
@ChristianKl: It has a translation but it's "Δημιουργία νέου Lexeme". Sam Wilson 23:49, 25 February 2023 (UTC)Reply[reply]
I don't think the title is what matters. Special lexemes has the infobox that says "Lexemes don't contain general data (date of birth, opening date, author, country, coordinates, website, etc.) about the entity or concept to which they refer. If you want to submit general data, you need to create an Item instead". If someone doesn't know what a lexeme is (which is going to be most people who aren't linguists), that infobox has the job to tell them. If special lexemes does not the job of explaining what a lexeme is in the Greek version, that's an issue. I just did the job of actually checking and it seems like the infobox isn't translated. ChristianKl ❪✉❫ 10:47, 26 February 2023 (UTC)Reply[reply]
You may want to check that at https://www.wikidata.org/wiki/Special:NewLexeme?uselang=el GZWDer (talk) 17:22, 26 February 2023 (UTC)Reply[reply]
There are a bunch of messages (such as wikibaselexeme-newlexeme-info-panel-lexicographical-data) that are not translated yet. @Μητσίκας: If you wanted to, you could translate these on TranslateWiki.net (although it does sound like there's uncertainty about what 'lexeme' is in Greek!). Sam Wilson 02:01, 27 February 2023 (UTC)Reply[reply]
I don't know what a lexeme is and I am a native English speaker :) BrokenSegue (talk) 21:58, 25 February 2023 (UTC)Reply[reply]

I haven't used Wikidata for a while and nearly forgot how it works. And since I barely know what it means, it made thinks worse. Thanks guys.--Μητσίκας (talk) 15:06, 26 February 2023 (UTC)Reply[reply]

Link Wikidata item/Wikipedia articles to Commons category[edit]

There is a Wikidata item that links to articles on several Wikipedias, but doesn't have its own category on any Wikipedia. Is there some way to link this to the Commons category? Lights and freedom (talk) 00:44, 26 February 2023 (UTC)Reply[reply]

Commons category (P373) maybe? Would need to see an example. BrokenSegue (talk) 01:16, 26 February 2023 (UTC)Reply[reply]
Add a sitelink to the Commons category under "Multilingual sites". I put some notes at User:Mike Peel/Commons linking that you might find useful. Thanks. Mike Peel (talk) 08:09, 26 February 2023 (UTC)Reply[reply]

Help with relevant statements for a Film Festival[edit]

Hi, I'm working on filling out data for Human Rights Film Festival in Croatia, and I have relevant data about partners, financial donors and media supporters, but I am unsure which statements would be proper to use in this case?

I saw some Festivals used "partnership with" (P2652) for Festival partners, but I am still unsure if that would be the right call. And if it would be right for partners, what about donors and supporters?

Thanks! GrimmDominik (talk) 15:30, 26 February 2023 (UTC)Reply[reply]

Citing USA Federal District Court Case documents?[edit]

Hi there, I'd like to cite information from the documents of a specific US patent infringement court case on Wikidata:

  • Case Name: Caliper Life Sciences, Inc. v. Shimadzu Corporation et al
  • Date: 2009
  • Court: Texas Eastern District Court
  • Docket Number: 4:2009cv00034

But I can't figure out how to do. There isn't a publicly accessible URL for this court case so I can't just use reference URL. Alternatively, I guess I could put the court documents on Wikisource or something & cite those, since they are public domain(?), albeit not currently accessible from a public URL? Photocyte (talk) 19:52, 26 February 2023 (UTC)Reply[reply]

Using title (P1476), point in time (P585), court (P4884), and legal citation of this text (P1031) seems like a reasonable modelling. -- William Graham (talk) 03:16, 27 February 2023 (UTC)Reply[reply]

Confidence interval using OpenRefine[edit]

Hi, can anybody help me regarding OpenRefine: How can I set the confidence interval (lower and upper bound)? I would like to enter data like 40.2 +/- 2.7. Is this possible at all with OpenRefine? I already asked here. Thank you! Yellowcard (talk) 09:32, 27 February 2023 (UTC)Reply[reply]

Wikidata weekly summary #561[edit]

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
    • Closed requests for permissions/Bot:
      • Cmtqwikibot 2 (Task/s: Add credits (cast and crew) for audiovisual work produced in Quebec based on the Cinémathèque québécoise's catalogue data. Adds reference. Deletes redundant, more general existing statements in certain circumstances.)
      • MsynBot 12 (Task/s: import missing GND ID (P227) identifier based on linked VIAF cluster)
  • Press, articles, blog posts, videos
    • Videos
      • LIVE Wikidata editing #106 - YouTube
      • CALA Speaker Series "Describing Chinese Rare Books and Cultural Heritage Collections" Session 1 - YouTube
      • TWed Talk (21 Feb 2023): Sola Shirai on "Working with Wikidata" - YouTube
  • Tool of the week
    • AutosuggestSitelink is a gadget that suggests Wikidata items for possible linking with a Wikimedia site page, using interwiki linking.
  • Development
    • REST API:
      • We added a way to get all statements on an Item for a given Property ID via a filter (phab:T309021)
      • We made it possible to configure the server for the "Try it out" button on the OpenAPI spec (phab:T329606)
    • Query Builder:
    • Constraints: We added support for showing constraint clarifications in constraint violation pop-up (phab:T219037)
    • We finished restricting unit/calendar/globe URIs to sensible values (phab:T102840)

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.

Q7591807[edit]

At Q7591807, the name of this church is given as "St Swithun's", with "St Swithin's" listed as an "also known as" alternative. While both these spellings have apparently been used, the one actually used on their website, https://www.stswithin.co.uk/, is "St Swithin's", so I wonder if the spellings at Q7591807 should be switched round, so that "St Swithin's" is shown as the main one, and "St Swithun's" as an alternative. ITookSomePhotos (talk) 18:33, 27 February 2023 (UTC)Reply[reply]

It would be a reasonable change. U seems the more archaic of the two variants. Ditto the EN wiki article. --Tagishsimon (talk) 20:21, 27 February 2023 (UTC)Reply[reply]
OK, thanks. I don't know how to do this (rename an item), so if anyone else wants to do it, please go ahead. ITookSomePhotos (talk) 22:45, 28 February 2023 (UTC)Reply[reply]

question on 'also known as (aliases)'[edit]

Hi this Query finds a lot of architects together with their alias names. When looking at the results, I wonder about aliases containing the lastname only. While Michelangelo (Q5592) is primarily known by his first name, and the full name is mentioned as alias, I doubt that all these architects are known by their lastnames only. e.g. Rudolf Wondracek (Q2174150) Furthermore I feel that using the less unique lastnames as aliases will pollute the namespace. Search will find items by lastname only in any case. Is there a rule, when to put the bare lastname as an alias? And is it considered disruptive to remove such aliases? Help:Aliases says: you should include Surnames or nicknames of famous individuals ... Like Michelangelo or Shakespeare, but Wondracek? best --Herzi Pinki (talk) 20:07, 27 February 2023 (UTC)Reply[reply]

I would consider it disruptive. It cannot be beyond possible that a user might search for Wondracek with a view to finding the architect. I do not recognise the concept of "polluting the namespace"; search expresses its result as Rudolf Wondracek (Wondracek), which seems cromulent. I think as a general rule, seeking the removal of aliases added by other in, presumably, good faith, is going down the wrong track. --Tagishsimon (talk) 20:18, 27 February 2023 (UTC)Reply[reply]
I do wonder why the bot did it, but the operator doesn't seem to be around anymore to ask. Multichill (talk) 20:21, 27 February 2023 (UTC)Reply[reply]
@Multichill: I would say because of this. Redirects were commonly used to seed aliases, and the bot adding it right after creating the element seems to make sense with it. -- Nono314 (talk) 19:39, 28 February 2023 (UTC)Reply[reply]
removing the alias will not hinder searching for the surname, e.g. https://www.wikidata.org/w/index.php?search=Krawina for Josef Krawina (Q87563). --Herzi Pinki (talk) 21:28, 27 February 2023 (UTC)Reply[reply]
It will hinder search: the quicksearch would now not find it; it'd require a full search. It's a way of degrading WD for no obvious benefit. --Tagishsimon (talk) 21:32, 27 February 2023 (UTC)Reply[reply]
ok. So then the recommendation is to add the surname as an alias for all humans? To ease quicksearch? Help:Aliases then has to be fixed. Wouldn't it be an improvement, when quicksearch knows about this and implicitly does the expected thing? best --Herzi Pinki (talk) 22:51, 27 February 2023 (UTC)Reply[reply]
Currently, Help:Aliases says "you should include Surnames or nicknames of famous individuals" but not "you should include Surnames or nicknames of individuals that aren't famous". If we would add it as alias for all humans, that would likely result in humans showing up in a lot of quicksearches where the user is not searching for them.
When it comes to both labels and aliases it's worth noting that they exist for ease of use. If you do queries and care about how the name gets displayed, there's a good chance that refering to name (P2561) and it's subproperties give you better results. Those properties also have the advantage that they have sources while labels and aliases do not. ChristianKl ❪✉❫ 14:36, 28 February 2023 (UTC)Reply[reply]
To fix QuickSearch you could add:
  1. "Surname, Name"
  2. "Name Surname" for Japanese names
  3. "Surname XX" for people who publish papers with initials (this is needed for https://author-disambiguator.toolforge.org/ to work).
So a lot of options, not just adding the surname. Lockal (talk) 06:28, 1 March 2023 (UTC)Reply[reply]
I was asking for a rule to follow, not for (even contradicting) options. "Surname, Name" is discouraged by Help:Aliases (You should not include: ... Alternative word order for people names (first name followed by last name vs. last name, comma, first name)). --Herzi Pinki (talk) 08:32, 1 March 2023 (UTC)Reply[reply]

Your wiki will be in read only soon[edit]

Read this message in another language • Please help translate to your language

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

All traffic will switch on 1 March. The test will start at 14:00 UTC.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

  • You will not be able to edit for up to an hour on Wednesday 1 March 2023.
  • If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

  • Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
  • We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
  • GitLab will be unavailable for about 90 minutes.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

Trizek (WMF) (Discussion) 21:20, 27 February 2023 (UTC)Reply[reply]

Facilities count[edit]

I'm interested in specifying the number of buildings in a complex. Is there a property I could use for that? {{u|Sdkb}} talk 03:09, 28 February 2023 (UTC)Reply[reply]

@Sdkb: You could use has part(s) of the class (P2670) with "building" and the qualifier quantity (P1114). Amqui (talk) 16:13, 1 March 2023 (UTC)Reply[reply]
Hmm, that seems pretty clunky. Is a new property needed for this? {{u|Sdkb}} talk 17:23, 1 March 2023 (UTC)Reply[reply]
@Sdkb I'd say no, because we would then have hundreds of "number of..." properties. The proposed modelling seems just fine to me... Vojtěch Dostál (talk) 17:47, 1 March 2023 (UTC)Reply[reply]
I think logically it should be a qualifier so you know what the quantity applies to. — Martin (MSGJ · talk) 17:48, 1 March 2023 (UTC)Reply[reply]
@Sdkb I'd say no as well for the same reason mentioned by Vojtěch Dostál. Amqui (talk) 19:51, 1 March 2023 (UTC)Reply[reply]

documenta archiv ID[edit]

I've started Wikidata:Property proposal/documenta archiv ID. Unfortunately it's more complicated than I thought. If someone is interested in modern art, please fill in the missing information. Otherwise just delete the attempt. thanks 2A02:2454:986D:F700:D8E3:65B6:25FE:D6DA 06:30, 28 February 2023 (UTC)Reply[reply]

Use of 'participant in' for countries[edit]

United States of America (Q30) has about 20 arbitrary participant in (P1344) entries. Is is really appropriate to have these for such a multifaceted item when participant (P710) for the individual subjects seems a better approach. Could a constraint be applied to country (Q6256) or above to discourage this sort of thing? Vicarage (talk) 09:10, 1 March 2023 (UTC)Reply[reply]

Reminder: Office hours about updating the Wikimedia Terms of Use[edit]

Hello everyone,

This a reminder that the Wikimedia Foundation Legal Department is hosting office hours with community members about updating the Wikimedia Terms of Use.

The office hours will be held on March 2, at 17:00 UTC to 18:30 UTC. See for more details here on Meta.

Another office hours will be held on April 4.

We hereby kindly invite you to participate in the discussion. Please note that this meeting will be held in English language and led by the members of the Wikimedia Foundation Legal Team, who will take and answer your questions. Facilitators from the Movement Strategy and Governance Team will provide the necessary assistance and other meeting-related services.

On behalf of the Wikimedia Foundation Legal Team,

JPBeland-WMF (talk) 16:11, 1 March 2023 (UTC)Reply[reply]

Battles get warnings if given historic county locations[edit]

Battle of Hastings (Q83224) gets a warning for historic county (P7959) as its not a geographical location. I think historic county (P7959) constraints should be relaxed to allow either battle (Q178561) or even past occurrence (Q110227435), as occurrences often occur at places. Vicarage (talk) 17:11, 1 March 2023 (UTC)Reply[reply]

Languages[edit]

Until today, when I visited a Wikidata item, I was shown a description in four languages at the top left: in my case Dutch, English, French and German. That was fine with me. Today German had suddenly been replaced by 'American English'. Is there an American English Wikipedia nowadays? In any case: I never asked for this change and I need German much more than American English. How do I get my familiar German back? Sijtze Reurich (talk) 20:38, 1 March 2023 (UTC)Reply[reply]

If you create a bable box on your user page, Wikidata takes the lanugages of that page as the languages it shows you. ChristianKl ❪✉❫ 22:43, 1 March 2023 (UTC)Reply[reply]
I created bable boxes, but this does not help. But why do things like this happen at all? I never asked for American English, did I?

Agree wwith User Sijtze Reurich, this is really an unwanted action for all Wikidata users worldwide. If possible, somebody should find the reason for this unwanted major change and revert this. --Florentyna (talk) 06:18, 2 March 2023 (UTC)Reply[reply]

Strange. When I log out, US English is suddenly replaced by German. When I log in anew, German is replaced by US English again. Sijtze Reurich (talk) 07:55, 2 March 2023 (UTC)Reply[reply]
A colleague at the Dutch Wikipedia came up with a solution. The problem is not caused by Wikidata, but by Firefox! Hence, only Firefox users are affected. In Firefox go to "Settings", then to "Language" and delete "En-US". Sijtze Reurich (talk) 08:16, 2 March 2023 (UTC)Reply[reply]
The other solution would be to create https://www.wikidata.org/w/index.php?title=User:Sijtze_Reurich&action=edit&redlink=1 and to add a bable box. ChristianKl ❪✉❫ 18:45, 2 March 2023 (UTC)Reply[reply]

Add statement on the top of the page[edit]

Do we have any gadget to move "add statement" option and the consequent dialog to the top of the page? Juandev (talk) 08:04, 2 March 2023 (UTC)Reply[reply]

ISBN to Wikidata[edit]

Do we have a SourceMD-like tool that will generate Qucikstatemnts commands, given an ISBN? Or is Zotero still my best bet? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:38, 2 March 2023 (UTC)Reply[reply]

Full iso 639-3 support for title field[edit]

Is it possible to add additional languages as valid possibilities for the title field language? Many valid minority languages listed in (Property:P220) are not recognized. Nontoxicjon (talk) 17:52, 2 March 2023 (UTC)Reply[reply]

https://www.wikidata.org/wiki/Help:Monolingual_text_languages describes the process in which languages get added. ChristianKl ❪✉❫ 18:42, 2 March 2023 (UTC)Reply[reply]
Thanks for the reference! Nontoxicjon (talk) 21:28, 2 March 2023 (UTC)Reply[reply]

Geographic administrative entities with multiples statuses[edit]

How are we supposed to deal with entities with overlapping or changing statuses?

e.g. East Ham (Q5177614) has held status county borough (Q1137272), municipal borough (Q518343) and urban district of Great Britain and Ireland (Q374614). Should each be a separate item? MRSC (talk) 08:58, 3 March 2023 (UTC)Reply[reply]

The item already has start and end dates for its different roles. That seems fine to me. Multiple items would be a bad idea, even if there were minor boundary changes during its lifetime. Vicarage (talk) 09:39, 3 March 2023 (UTC)Reply[reply]

Data comemorativa[edit]

Criei uma data comemorativa que não encontrei em nenhum outro lugar, posso acrescenta-la no wiki? 2804:18:849:FC67:F372:B330:7F78:9868 20:21, 3 March 2023 (UTC)Reply[reply]

Google search engine[edit]

Dear community, could you please tell me why some Wikidata articles are not showing up in Google search engine? Is there a way to fix this? Thank you! 37.252.88.54 15:21, 4 March 2023 (UTC)Reply[reply]

what articles? BrokenSegue (talk) 15:50, 4 March 2023 (UTC)Reply[reply]

How to crowdsource specialized directories using Wikidata?[edit]

I believe it should be relatively easy to crowdsource the creation and maintenance of specialized directories using Wikidata. I have two examples in mind:

1. PeaceWorks Kansas City has a list of Peace, justice, environment, and human rights groups in the Kansas City Metro area on their website. Sadly, it has not been updated since 2018, because it's too much work for the limited staff of PeaceWorks. However, it seems to me that it should be fairly easy to train people in how to create and maintain Wikidata items for all the organizations on that list and update it automatically with a SPARQL query. Before I start, I feel a need to get help from someone who understands what Wikidata properties to use to make this happen.
2. People with Friends of Community Media and Community of Reason Kansas City want to create a directory of local news outlets in the Kansas City metropolitan area.

If I could figure out how to do one of these things, I think I could figure out how to do the other -- AND the same methodology would likely have many other applications. I'd want to document the methodology in a tutorial on Wikiversity and offer to make presentation(s) on it at a future Wikimedia:Wikimania.

Suggestions? Thanks, DavidMCEddy (talk) 18:51, 4 March 2023 (UTC)Reply[reply]

Please help me delete https://mix-n-match.toolforge.org/#/catalog/5789[edit]

I've messed up it by uploading a file not in UTF-8 encoding. I also find out mix-n-match can't pick up matches already on Wikidata if the ID contains a Chinese character, so it's difficult to sync it up. Midleading (talk) 02:52, 5 March 2023 (UTC)Reply[reply]

@Midleading: did you try doing an import again at https://mix-n-match.toolforge.org/#/import/5789 to overwrite the entries? Multichill (talk) 11:25, 5 March 2023 (UTC)Reply[reply]
Yes, I did it, and I just did it again now. But the garbled entries like https://mix-n-match.toolforge.org/#/entry/150037217 and https://mix-n-match.toolforge.org/#/entry/150037218 remain. Midleading (talk) 11:57, 5 March 2023 (UTC)Reply[reply]
IIRC the documentation is very lacking when it comes to updating catalogs, so much so that I've refrained from doing this in the past. If anyone who knows how this is done, can do something about that, that would be nice. Infrastruktur (talk) 11:57, 5 March 2023 (UTC)Reply[reply]

Interwiki[edit]

Hi, I'm asking for help interwiki budget (Q56410323) to budget (Q41263) Bung Badak (☕)(kontribusi) 03:41, 5 March 2023 (UTC) Badak Jawa (talk) 03:41, 5 March 2023 (UTC)Reply[reply]

→ ← Merged Estopedist1 (talk) 06:41, 5 March 2023 (UTC)Reply[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Matěj Suchánek (talk) 17:27, 5 March 2023 (UTC)Reply[reply]

Request for merge on Invidious.[edit]

Invidious (Q16868796) and Invidious(Q79343316) seem to describe the same thing, however I can't find the reason why both exist and why the former is defined as a "Wiktionary redirect", especially when it links to the English Wikipedia and not Wiktionary. I'd like to request a merge on both of these entries.

Money-lover-12345 (talk) 07:13, 5 March 2023 (UTC)Reply[reply]

Hi @Money-lover-12345, I agree with you. → ← Merged. Michgrig (talk) 13:48, 5 March 2023 (UTC)Reply[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Matěj Suchánek (talk) 17:27, 5 March 2023 (UTC)Reply[reply]

Disambiguation and different from[edit]

There are some 30 WD entries called Fort George (Q240678). I could add different from (P1889) with 29 entries for each, or I could point to the disambiguation page Fort George (Q240678) which listed the 30 sites. The former might be better for casual enquiry, the latter better in query land. But I'm not sure how WP disambiguation pages are handled across the different WPs, and confusion can easily be language dependant, as the names could be clearly different in certain languages. We don't seem to have a common way of linking disambiguation pages to items (or vice versa), so I'm uncertain as how to proceed. Vicarage (talk) 11:55, 5 March 2023 (UTC)Reply[reply]

I use different from mainly as a means to prevent similar items from being merged erroneously. It's not useful to label all things with the same label as different. But if two are especially prone to confusion and you are sure they are different it's good to mark them. BrokenSegue (talk) 20:39, 5 March 2023 (UTC)Reply[reply]

Belgian embassies and consulates[edit]

Hi, is there a way to export the data from this website to let's say openrefine? RVA2869 (talk) 14:03, 5 March 2023 (UTC)Reply[reply]

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