|
Василиса▶ Я жду вашего обращения. Что Вы хотите узнать?
|
|
|
|
|
|
Wikidata project chat
|
|
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 2021/03 . |
|
SpBot
archives
all sections tagged with
{{
Section resolved
|1=~~~~}}
after 1 day and sections whose oldest comment is older than 7 days.
|
Hello,
How can I document subsidies (capacity payments) to power stations please. I know there is feed-in tariff (P6826) but these subsidies are a bit different as they are not just per MWh but also include payments for MW installed capacity. – The preceding unsigned comment was added by Chidgk1 ( talk • contribs ).
@ Chidgk1 : This sort of data tends to be tabular, and would typically differ from year to year. Such data are often unsuitable for the data model Wikidata use, and I'd consider using tabular data on Commons . @ Vojtěch Dostál : That's right it differs from year to year: but if we look at an example: on Çatalağzı power station (Q6099668) there is annual energy output (P4131) for which I can add a different quantity each year. So I was wondering if there is something similar or if not I could request a new property which could be qualified by point in time (P585) each year, such as "payment", "subsidy" or "capacity payment"? As I am using wikidata for the rest of the data if I used tabular data on commons for that one item I think it would be more complex to add the whole lot into a Wikipedia table - like I do at tr:Türkiye'deki kömür yakıtlı enerji santralleri listesi Estacion Espacial Internacional[ edit ]In spanish version of Estacion Espacial Internacional (International Space Station) thera are some mistakes in "Especificaciones Tecnicas" and "Parametros orbitales". It has several numers 3 like cubic kilometers in Altitud de Perigeo. It must be just kilometres. The same mistake there are with several "3 " number in different measures
Interpreting "described at URL" (P973)[ edit ]I have some questions about the proper use of described at URL (P973) . As I interpret this property, it should be used to point to a web page or document that is about the Q item. On items for subjects, e.g. data-driven modeling (Q102047184) and safari industry (Q105347324) , I have added P973 and linked out to some articles about these topics that didn't have Wikidata items themselves. Jura1 has been removing these statements and creating new items for the articles, and in those items he is using P973 to give the URL that provides the actual full text of the article. I wrote to him saying that this didn't make sense to me, because the article isn't describing the article. Instead, I think that full work available at URL (P953) is the correct property to use for a URL that provides the full text of an article. As an example, I changed P973 to P953 on Safari tourism (Q105534089) . Jura1 said to me that "it isn't consistent with the purpose of described at URL (P973)." Am I misunderstanding the purpose of described at URL (P973) ? UWashPrincipalCataloger ( talk ) 00:37, 17 February 2021 (UTC)
I use and have used described at URL (P973) the same way you use it. To me it's a top level property that is roughly analogous to a reference URL or further reading URL you'd see on English Wikipedia. If he's going to move them to a new item, I would recommend adding described by source (P1343) with a value of the newly created item. William Graham ( talk ) 01:13, 17 February 2021 (UTC) That's a very good suggestion. But on the new item, shouldn't P973 just be P953? UWashPrincipalCataloger ( talk ) 01:21, 17 February 2021 (UTC) I forgot to ping @ Jura1 : as is good etiquette. William Graham ( talk ) 01:25, 17 February 2021 (UTC)I use “described at URL” the same way you do. - PKM ( talk ) 01:30, 17 February 2021 (UTC)Odd, if everybody uses it that way, I suppose we can delete the autofixes on Property talk:P973 and maybe create another property for its original purpose per its proposal: Wikidata:Property_proposal/Archive/15#P973 . --- Jura 06:10, 17 February 2021 (UTC)Isn't this exact match (P2888) ? Ghouston ( talk ) 06:24, 17 February 2021 (UTC) I think art catalogues and databases mostly used P973, before people started creating properties for every catalogue. --- Jura 06:34, 17 February 2021 (UTC)@ Ghouston : So should we sort out exact matches on mainly use for Springer papers as in the sample by UWash ? --- Jura 09:56, 19 February 2021 (UTC) Multichill
Notified
participants of WikiProject sum of all paintings
(given the uses for paintings)
@
Jarekt
: (given the use on Commons). ---
Jura
09:56, 19 February 2021 (UTC)
Hi everyone,
As you may know, you can include Sitelinks (also known as interwiki links or interlanguage links) that go from individual Items in Wikidata to pages on other Wikimedia sites including Wikisource . Until now, it was not possible to manage the interwiki links to/from multilingual Wikisource on Wikidata. This was due to the unusual technical setup of multilingual Wikisource as well as the fact that we can only link to one page for a topic on any given wiki (multilingual Wikisource can theoretically have several pages covering the same topic in different languages though this is very rare).
We resolved the technical constraint and starting today you can connect pages on multilingual Wikisource with the other language-specific versions of Wikisource so these interwiki links don't have to be maintained in the wikitext anymore. After adding a sitelink, the sitelink appears on the Item page (in the Sitelinks section) with language code
mul
. The restriction of only being able to link to one page on multilingual Wikisource per Item stays in place and was considered acceptable based on feedback by the Wikisource community.
This feature was requested by users from the Wikisource community. We hope that it can give them more access to Wikidata and the freedom to add multiple links to different Items.
If you encounter any issues or want to provide feedback, feel free to use this Phabricator ticket .
Cheers,
- Mohammed Sadat (WMDE) ( talk ) 16:26, 23 February 2021 (UTC)
There is an ongoing discussion about the way to identify the language of such pages and about the default language code ("en", "mul" or "und") at Wikidata:Contact_the_development_team#language_of_https://wikisource.org/_:_currently_"en"_(_phab:T138332) . So the actual details of the implementation might be slightly adjusted. --- Jura 11:20, 24 February 2021 (UTC)For phab:T275500 @ DCausse (WMF) : would need to add "wikisource.org" to [1] as currently only *.wikisource.org is possible. At least, it seems that https://wikisource.org/ isn't "mul.wikisource.org" or "old.wikisource.org" --- Jura 21:30, 24 February 2021 (UTC)@ Mohammed Sadat (WMDE) : And when for the Incubator? -- Liuxinyu970226 ( talk ) 02:00, 25 February 2021 (UTC)Support for the wiki seems somewhat limited in PetScan as well. --- Jura 19:22, 25 February 2021 (UTC)Here is a query to find most languages of Sourceswiki and their main elements: https://w.wiki/32ba : main page (sample: Main Page/Aragonés for Aragonese (Q8765) ) and category (sample: Category:Aragonés ). A few parts still need adding. --- Jura 19:22, 25 February 2021 (UTC)Another point to sort out is mentioned below, but it isn't specific to Wikisource. --- Jura 10:11, 26 February 2021 (UTC)Ticket for missing interlanguage links is phab:T275958 . --- Jura 12:01, 27 February 2021 (UTC)Announcement on Sourceswiki is in their Scriptorium . --- Jura 12:01, 27 February 2021 (UTC)Query for a few items without P31 or P279 (some created months ago): https://w.wiki/3349 --- Jura 10:09, 28 February 2021 (UTC)Media legends don't appear on wikipedia pages with infoboxes[ edit ]Many wikipedia pages use infoboxes which, in turn, refer to the wikidata records. Very often, e.g. for settlements, a picture is also used that is referred to in wikidata. I seem to remember that - at least some months ago - the media legend was also copied from wikidata if it existed in the language of the wikipedia page. This does not seem to be the case any more. Is it the fault of the infobox templates (of which several are affected, and in different languages), or has something been done to prevent the forwarding of media legend to the wikipedia pages? -- Schlosser67 ( talk ) 09:24, 25 February 2021 (UTC)
No. Many pictures don't have legends in Wikidata as one can be found on Commons and should eventually be available directly from there.If there is a legend in Wikidata and it's not displayed in a given language version of Wikipedia, this is something to check there: either in the article or its infobox settings.With a sample, we can try to help you figure it out.Given that Commons is working on image legends, in general, it's preferable to contribute them directly there going forward. --- Jura 10:28, 25 February 2021 (UTC) It is somehow inconsistent. I have just added a photo for "Samtgemeinde Sickte" on wikidata with German and French media legends, and it shows up all right on the French wikipedia, complete with legend. On the other hand, the legend for the view of Elze is not displayed on fr:Elze (Basse-Saxe) . Is this perhaps because of the different infoboxes? The article for Elze uses "Commune d'Allemagne" while fr:Samtgemeinde Sickte uses "Localité". I don't know much about the programming of infoboxes. -- Schlosser67 ( talk ) 07:32, 26 February 2021 (UTC) Indeed fr:Modèle:Infobox Commune d'Allemagne used on fr:Elze (Basse-Saxe) doesn't use the legend from Wikidata at all. It seems that initial Wikidata support was added to the infobox only last year. Maybe @ Pelanch3 :, who edited it, can help you. --- Jura 11:52, 27 February 2021 (UTC)Description capitalisation[ edit ]Hello,
I was just curious as to why the rules of capitalisation for descriptions are the way they are. Why do they start in lower case – unless there's a proper noun etc.?
Cheers, Ritenerek ( talk ) 00:27, 26 February 2021 (UTC)
Probably because they aren't complete sentences. -Animalparty ( talk ) 00:30, 26 February 2021 (UTC) And so they can easily be quoted within sentences. Similarly why labels for items for generic things are lower-case. Jheald ( talk ) 11:00, 28 February 2021 (UTC)Error with JSON dump[ edit ]
Hey, I'm working with the latest JSON dump today (
https://dumps.wikimedia.org/wikidatawiki/entities/latest-all.json.bz2
, downloaded February 25, 2021), and I notice that at least one, and possibly more, of the entries have invalid JSON. The item with ID Q105653764, for example, is missing a lot of close quotes. The first few bytes look like
{"type:"item,"id:"Q105653764,"labels:{"en:
, when they should look like
{"type":"item","id:"Q105653764","labels":{"en":
. I'm not sure what happened here, but I figured you might like to know about it.
--
50.35.70.129
04:11, 26 February 2021 (UTC)
I've been using "20. century" for approximate dates, under the impression that "20. century" means "20th century". This appears not to be the case, as a constraint clash shows it apparently starts after 1977. Can anyone tell me what it actually means? Is it the years 2000-2099? Or 2001-2100? Or something else? Either way, this seems very confusing to me. -- The Anome ( talk ) 06:49, 26 February 2021 (UTC)
Looking at, for example Andrea Bergamasco (Q61472634) the date of birth "20. century" is stored as 1 January 2000. I viewed the value using a SPARQL DESCRIBEDESCRIBEwd:Q61472634 Try it! PiecesofukTry it! Piecesofuk ( talk ) 07:31, 26 February 2021 (UTC)
@ The Anome : There is a precise date, to the day, stored with any date value on Wikidata, along with a precision. Something showed as « 20th century » can have any precise date like « 3rd of may 1949 » or « 4th of july 1960 », with a « century » precision. The « problem » is that it’s difficult to take the precision into account in every computation, and in a lot of one only the precise date is used, for sorting.For example, imagine you want to sort people by age … you have one person with century precision on the date of birth, and one other with the precise date 1 january 1950. Is the first older than the other ? It’s impossible to know …if you naively sort by value, it’s easier to use only the precise date. One solution could be to take advantage of the fact that the year is not significant to make an educated guess about the precise date of birth of the person : if you don’t know the year of birth, or even the decade, you can set the precision to « century », but setting the year as 1910 if you guess it’s probably around this period and 1960 if you guess the person is probably born in the second half of the century. That way you get a more plausible sorting using the (non significant) year/month/date of the precise value. author TomT0m / talk page 08:42, 26 February 2021 (UTC)a constraint clash shows it apparently starts after 1977 - this is a bug in specific implementation of constraint checker. There are multiple implementations - naïve sparql-based, element-based ( mw:Extension:Wikibase Quality Extensions ), dump-based analysis by KrBot, complex constraints - some of them suffer from precision issues. -- Lockal ( talk ) 08:56, 26 February 2021 (UTC) Perhaps we should force the default for "20th century" to be 1950, "19th century" to be 1850, etc, and mass-convert all "nth century" dates with sorting-values of eg n00 or (n+1)00 to be n50 ? It could be done as a very big bot job. (Obviously if there were qualifiers like earliest date (P1319) or refine date (P4241) they could be taken into account too)? Jheald ( talk ) 11:09, 28 February 2021 (UTC) Quite pointless and misleading, IMO. According to this logic, year precision should store value not on the 1st of January, but on July 2. Just exclude low-precision values when doing comparisons, like here . It is expected from well-written clients to know about precision anyway. Even more, your suggestion may not be possible due to specification with Wikidata:Stable Interface Policy . -- Lockal ( talk ) 19:30, 1 March 2021 (UTC) Well, as somebody who runs queries that often run close to the 60-second limit, with little time for any extra clauses, I would find it useful.Also, it would be good if the WDQS output UI automatically indicated precision for dates (it's there in the downloads, but not on the screen) -- it's embarrassing when a query is full of 1 January dates being presented as if they had full position. But I guess, on your terms, WDQS UI is just "not a well written client". Jheald ( talk ) 19:58, 1 March 2021 (UTC)Geodata for Bookburnings by the nationalsocialists in Germany 1933[ edit ]Hi,
i'm working for an Organisation which is running an remembrance and information project about the bookburnings by the nationalsocialists in germany in 1933. We collected over 140 Places where bookburnings took place. We have geodata, date, short description for it as well as the source of the information. We would like to offer at least the geodata and date information to the wikidata community. With this link it would be possible to have list of Places where and when bookburnings took place and connect that to other data. We our self have interesting questions in mind what to do with this data. For example.
1. Make a list of the Place sorted by size of the city.
2. Connect it to Information of authors of which the books were burned.
The data is accessible via an georss and geojson API. I would like to hear your Opinions about that. Thanks a lot.
JanSchenckJanSchenck ( talk ) 16:25, 26 February 2021 (UTC)
I think it would make sense for each instance of a "bookburning" to be a Wikidata item - so that would be 140 new items. You can then attach data to these items such as location, lists of books or authors, etc. - I would hope existing properties can handle this, but not sure exactly which ones to recommend. ArthurPSmith ( talk ) 18:27, 26 February 2021 (UTC)Merge request[ edit ]I think Q2740581 should be merged into Q1068611 . See, for example, ru:Salpidae (from Q1068611 ) redirects to ru:Сальпиды (from Q2740581 ). -- Gryllida 01:13, 27 February 2021 (UTC)
The difference is in taxonomic rank. It happens rarely that two different taxa have the same name, in those cases you always have different rank. Also in general, if you see two items that appear the same and both have lots of statements and wikilinks, then there is probably a reason they weren't already merged. -- SCIdude ( talk ) 10:12, 27 February 2021 (UTC)Help needed: Floor cloth ( Q46146955 ) vs. Floorcloth ( Q1409430 )[ edit ]I would very much appreciate any guidance that can be provided. I have been working on the Floorcloth article in Wikipedia. When I started, it was defined as per Q1409430 and had one sentence reflecting that use of the term (for cleaning floors), but the bulk of the entry reflected Q46146955 (a floor covering). I have added to the article in the sense of Q46146955, floor covering. The sources I have been using primarily spell it as used for a floor covering as one word. Therefore, I am concerned about a couple of things: the Wikidata item linked to the developing Floorcloth article, and the definition of the term as a single word. How might this confusion be resolved? Thank you. -- TrudiJ ( talk ) 12:05, 27 February 2021 (UTC)
@ TrudiJ : The sitelink should be moved from Q1409430 to Q46146955 reflecting the new scope of the Wikipedia article.|
How to move sitelinks?
|
|---|
|
There is a gadget in your
preferences
called
Move
that gives users the ability to move sitelinks quickly. Once the gadget is enabled, go to the obsolete item, click the icon next to the sitelink you wish to move, then input the Q#### of the recipient item.
(source: Help:Merge ) |
All entries seem to be read-only for me as of a couple of minutes ago. Is there a reason why? I just merged a second entry into Q77581 and mistakenly added his wife a second time. When I wanted to undo that I was unable to edit anymore.-- 176.199.18.119 16:08, 27 February 2021 (UTC)
I removed the duplicaed wife from Fritz Wepper (Q77581) , the item is not semiprotect. Joao4669 ( talk ) 14:21, 28 February 2021 (UTC)Scientist[ edit ]The item scientist (Q901) is used very broadly, with subclasses like brazier , byzantinist , church historian , collector of folk music , ironmaster , law theorist , land surveyor , management engineer , mathemagician , mental calculator , mythologist , sport historian , special educator , script kiddie and utopian ( full list ).
The demarcation between science and other fields is fuzzy, but it would be helpful to come up with some guidelines about what should be included. The guidelines could consider research vs. application to help determine the applicability of chemist vs. chemical engineer or animal scientist vs. farrier . It may also be helpful to create three subclasses for scientists in the natural, the social and the formal sciences. (But right now, natural scientist (Q55002844) is a fictional operatic character.) -- Ariutta ( talk ) 19:22, 27 February 2021 (UTC)
You can easily create several items for "scientist" each with its definition and references. --- Jura 22:34, 27 February 2021 (UTC) Since most entries are using scientist (Q901) , I'm hesitant to make a major disruptive change, and I want to get some consensus before making any change, because the boundaries can be fuzzy. The most minimal change would be adding some guidelines for the item, so we don't end up with results like scientist as a superclass of theologian ( theologian -> religious studies scholar -> social scientist -> scientist ). A more major change would be adding three subclasses for scientists in the natural, the social and the formal sciences. While this would be useful for me, I don't have the bandwidth to create and maintain those items myself right now.-- Ariutta ( talk ) 23:59, 1 March 2021 (UTC) You don't need to change that item to create items for other definitions. --- Jura 00:45, 2 March 2021 (UTC)Seems to me that it's mostly a "downstream" thing. At one point a subclass-of link is applied a little abusively (e.g. land surveyor as a subclass of geodesist (Q11699606) ). Circeus ( talk ) 18:10, 3 March 2021 (UTC)How to add a reference multiple times, without creating seperate item for it[ edit ]Hello, I am trying to update information for Dutch politicians. For this I use sources that support multiple claims I'm trying to make (such as this curriculum vitae of Mark Rutte ). I do not believe this webpage qualifies for being a seperate item. However, I find it quite cumbersome to add all the reference info (archive url, date, retrieved date, url, author etc.) to every claim I make based on this url. Often I take the shortcut of only placing the url, which is problematic ofcourse. Is there a way to re-use a reference (e.g. copying?) for multiple claims, or should I perhaps create a seperate claim? Thanks in advance! Dajasj ( talk ) 13:17, 28 February 2021 (UTC)
Sounds like you need the "DuplicateReferences" gadget from Special:Preferences#mw-prefsection-gadgets . — MisterSynergy ( talk ) 14:03, 28 February 2021 (UTC) That's exactly what I needed! Thank you :) Dajasj ( talk ) 14:11, 28 February 2021 (UTC) I find that often the page has to be reloaded for this gadget to work. -- SCIdude ( talk ) 15:52, 28 February 2021 (UTC)easy SPARQL wrapper[ edit ]While current efforts for making access to SPARQL easier are highly appreciated and anticipated, would it not be easy to place an input field on every property page that takes a value and starts a SPARQL query for items with that property and that value? Many of my personal queries are of such type, and the implementation seems a no-brainer. -- SCIdude ( talk ) 16:18, 28 February 2021 (UTC)
That's not a million miles away from what Preferences / Gadgets / EasyQuery gives you. -- Tagishsimon ( talk ) 16:52, 28 February 2021 (UTC) Maybe it should be activated by default. --- Jura 22:32, 28 February 2021 (UTC) Probably. It produces execrable SPARQL: SELECT?item?label?_imageWHERE{?itemwdt:P31wd:Q39614.SERVICEwikibase:label{bd:serviceParamwikibase:language"en".?itemrdfs:label?label}OPTIONAL{?itemwdt:P18?_image.}}LIMIT100 Try it! -- Tagishsimon ( talk ) 01:13, 1 March 2021 (UTC)Would prefer (and maybe without the ?image, which serves only to cause items duplicated across rows; add ?itemDescription instead): SELECT?item?itemLabel?imageWHERE{?itemwdt:P31wd:Q39614.SERVICEwikibase:label{bd:serviceParamwikibase:language"[AUTO_LANGUAGE],en".}OPTIONAL{?itemwdt:P18?image.}}LIMIT100 Try it! -- Tagishsimon ( talk ) 01:13, 1 March 2021 (UTC) The version I use includes "?itemDescription". --- Jura 12:49, 1 March 2021 (UTC)and no image; no embedding/autorun and opens in a separate tab. I think it's based on an older version of the script, but I still prefer that.Anyways, I think either would be a plus for users. --- Jura 13:14, 1 March 2021 (UTC)I left an edit request at MediaWiki_talk:Gadget-EasyQuery.js . --- Jura 13:27, 1 March 2021 (UTC)Colonial Mayor of New Brunswick or Mayor of Colonial New Brunswick[ edit ]At Talk:Q6797896 for example, the numbering system for politicians of localities begins with independence. Should we call the earlier politicians "position=Colonial Mayor of New Brunswick" or "position=Mayor of Colonial New Brunswick". I tried to find examples as a guide, any help would be appreciated if you can find some examples, or input which is more widely used. In the end they will be synonyms, but the right name earlier is best. -- RAN ( talk ) 22:42, 28 February 2021 (UTC)
@ Richard Arthur Norton (1958- ) : Looking at the Wikipedia article, New Brunswick was incorporated, chartered, reincorporated, and rechartered several times. But in my best estimation, New Brunswick was the same municipality, but reauthorized under newer laws. I guess if you really wanted to distinguish those periods it would be "Mayor of the Town of New Brunswick" and "Mayor of the City of New Brunswick". At that point you'd be going down the road to split up the Wikidata and Wikipedia articles into "Town of New Brunswick" and "City of New Brunswick". I don't think that is necessary and would just stick with treating the mayoralty as the same continuity throughout all the incarnations of New Brunswick. William Graham ( talk ) 00:42, 1 March 2021 (UTC) The numbering system of the canonical list starts with independence. The list does not restart with each change of government style. -- RAN ( talk ) 01:22, 1 March 2021 (UTC) Which, or whose, canon are we talking about? -- Tagishsimon ( talk ) 01:30, 1 March 2021 (UTC)You can search the New York Times archive for a phrase like "3rd mayor" or "2nd governor", "1st president", or "100th pope" or visit the website for that entity and recognize that there is a canonical numbering system, no matter who started it, or who decided it is canonical. I don't think we have to worry about integrating antimayors to mirror antipopes, or pretender mayors. See " he was sworn in as the 21st Mayor of Montclair. ", all you need is the current filler of office and their number to work out the sequence. -- RAN ( talk ) 13:37, 1 March 2021 (UTC)Are you actually able to point to a canonical list for the Mayor of New Brunswick, RAN, or are you just blowing smoke? Can you point to a NYT search for, e.g. 3rd Mayor of NB? You say "I don't think we have to worry about integrating antimayors to mirror antipopes, or pretender mayors", but I'm old enough to remember that it was you who raised this whole question of how we cater for colonial-era Mayors of New Brunswick. It seems to me that you have decided such colonial-era Mayors of New Brunswick are holders of an office distinct from post-independence Mayors of NB, and are perhaps unhappy that others think that the Mayor of NB is the mayor of NB, irrespective of the situation with the national government. -- Tagishsimon ( talk ) 01:54, 2 March 2021 (UTC)@ Tagishsimon : I agree there are many different ways of thinking about the history of a named populated place. It feels like a corollary to the "Ship of Theseus" question. I generally prefer to begin by building a model that matches well to existing articles in the language Wikipedia of the subject because I'm not a legal or historical scholar. A model where all officeholders have a replaces (P1365) and replaced by (P1366) property with start and end dates to that the sequence can be walked. William Graham ( talk ) 02:07, 1 March 2021 (UTC)Nine million people[ edit ] [2][2] -- GZWDer ( talk ) 00:11, 1 March 2021 (UTC)
Or: Potential merges. -- Succu ( talk ) 21:16, 1 March 2021 (UTC)Cool. How many have functionally identifiable data like birth or death dates? How many are linked to zero items besides human (Q5) ? How many lack external identifiers (not that these are required: not every human who has ever lived has yet been given a code in a database). Increasing the absolute numbers of items should not distract from structuring the data in a meaningful manner. -Animalparty ( talk ) 22:14, 1 March 2021 (UTC)200,000 merges?One third have family name (P734) , two thirds given name (P735) . It seems it never gets done ;)99,991,000,000 to go? --- Jura 00:49, 2 March 2021 (UTC)Wikidata weekly summary #457[ edit ]+}){kind=logo}
Here's your quick overview of what has been happening around Wikidata over the last week.DiscussionsClosed request for adminship:
Dr.üsenfieber
(unsussesful)New request for comments:
P155/P156 as qualifiers only, rather than as main statements
Events
Upcoming:
SPARQL queries
live on Twitch and in French by Vigneron, March 2 at 18:00 CETUpcoming video: LIVE Wikidata editing #34 Open Data Day -
YouTube
,
Facebook
, March 6Upcoming:
Online Wikidata meetup in Swedish #52
, March 7Upcoming:
Wikidata bug triage hour
about Lexemes, March 22ndUpcoming:
Wikidata-based Data Sprint hosted by the University of New Brunswick
. One Wikidata data set will be provided on 11th March 2021 and various teams will have 2 hours to run a set of SPARQL queries against the Wikidata Query Service (WDQS) and showcase their results.
Press, articles, blog posts, videos
Blogpost:
Wikidata and Correspondence Archives
(Enriching basic metadata with a knowledge graph)Blogpost:
The promise of Wikidata
- How journalists can use the crowdsourced open knowledge base as a data source (at DataJournalism.com)Video: Accra Archive Wikidata and Wikipedia Workshop (GLAMS Campaign Ghana) -
YouTube
Video: COVID-19 coverage on Wikidata -
YouTube
Video: Identify and describe items of bibliographic interest (articles, monographs, authors) on Wikidata (in Italian) -
YouTube
Video: Visualizing the global research ecosystem via Wikidata and Scholia -
YouTube
Video: Demo: How to upload new bibliography and create dashboards on Wikidata -
YouTube
Video: Reconciliation Open Refine Wikidata (in Swedish) -
YouTube
Video: Reconciling researchers to Wikidata via Google Sheets -
YouTube
Video: LIVE Wikidata editing #33 -
YouTube
,
Facebook
Video: How to create new Wikidata item (in Dutch) -
YouTube
Video: Merging Wikidata items (in Dutch) -
YouTube
Tool of the week
EditSum
, a new user script which allows to attach custom summary text to any label/statement/sitelink/etc. modification.Other Noteworthy Stuff
User:Nikki/LexemeInterwikiLinks.js
, is a userscript that adds Wiktionary interwiki links in the sidebar on Lexeme pages. (It links to pages corresponding to the first lemma and puts the lexeme language's Wiktionary first, followed by languages in the user's Babel box).
User:Lucas Werkmeister/addStatementCountsToCategories.js
, is a userscript that shows the number of statements of the linked item for all pages in a category.
Shared Citations
, a proposal arising from the WikiCite project, for a central reference management database supporting all Wikimedia projects, with significant relationship to Wikidata. Seeking feedback.
Modèle:Indice de diversité de genre
(Template:Gender diversity index) is a new template in the French Wikipedia which use P21 (gender property) to count the number of people by gender mentioned in an article. It helps to find articles which "forget" to cite women.Lexeme JSON dumps are now available as a collection of individual lexeme data in the regular JSON format, separate from the regular Wikidata dumps containing Items and Properties.
phab:T264883
We found a way to improve the performance of scrolling on the Item page by changing how we move the Property labels as you scroll through the page
. You should see the effect after the next deployment.
BBC Things
includes links to Wikidata to provide a single reference for the growing collection of entities that matter to the BBC and their audiences.Did you know?Newest
properties
:
General datatypes:
number of at bats
,
number of hits
,
bases on balls
,
runs batted in
,
letterer
,
sensors
,
FAQ URL
,
set during recurring event
,
stolen bases
,
doubles hit
,
triples hit
External identifiers:
Germanistenverzeichnis ID
,
uta-net.com song ID
,
uta-net.com artist ID
,
AllMusic genre/style ID
,
DicoPolHiS ID
,
EuroBabeIndex.com ID
,
Sauvons nos tombes cemetery ID
,
LombardiaBeniCulturali archive producer person ID
,
LombardiaBeniCulturali archive producer organization ID
,
LombardiaBeniCulturali archive producer family ID
,
BookBub author ID
,
TlF artist ID
,
Encyclopédie berbère article ID
,
Protagonisti della storia delle scienze della mente ID
,
English Placenames MADS ID
,
Norwegian State Administration Database ID
,
teatral.ro play/theater ID
,
CineFAN.ro title ID
,
CinemaRX title ID
,
Sinemalar title ID
,
Swissvote ID
,
Bourgogne-Franche-Comté inventory identifier
,
Île-de-France inventory identifier
,
Normandie inventory identifier
,
Pays de la Loire inventory identifier
,
Wisconsin Architecture and History Inventory ID
,
Dizionario biografico online degli anarchici italiani ID
,
Swedish Literature Bank place ID
,
Opera Online conductor ID
,
Discogs genre ID
,
Discogs style ID
,
Danmarks Adresseregister named street ID
,
bashenc.online ID
,
Provenio UUID
,
JedeSchule.de ID
,
ARAE ID
,
Encyclopedia Titanica ID
,
U.S. Masters Swimming ID
,
DzygaMDB person ID
,
NLS place type ID
,
Archivo Linz de la Transición Española ID
New
property proposals
to review:
General datatypes:
demographics of topic
,
strikeouts
,
district heating
,
number of signatories
,
opt-out
,
payer
,
secondary topic
,
grant number
,
Future Salaries ID
,
Index égalité professionnelle F/H
,
Commons incompatible image URL
,
verbal ability
External identifiers:
Diccionari de la traducció catalana ID
,
ANPI person ID
,
ANPI person numeric ID
,
APS author ID
,
EEVA author ID
,
Archives West finding aid ID
,
BiographySampo person ID
,
Discord server numeric ID
,
Discord user numeric ID
,
CUT ID
,
Amathus ID
,
EUC ID
,
UPSA ID
,
RePEc EconPapers ID
,
Dark Horse contributor ID
,
ComiXology publisher ID
,
Austrian Newspapers Online ID
,
Cyprus Library ID
,
MyMusic artist ID
,
LFCHistory.net player ID
,
MeSH qualifier ID
Query examples:
Hungarian church buildings sorted by confessions
(
Source
)
Where Czechs most died if not in their place of birth
(
Source
)
Most popular tonalities
(
Source
)Newest
WikiProjects
:
WikiProject Templates
for templates in WikidataDevelopmentWorking on first version of small tool that lets you get the average ORES quality score for a list of Items and find the lowest-quality Items in the batch so it's easier to improve them.Taking a closer look at what larger improvements we want to make to Lexemes later this year.Thinking through different ways how we can technically get mismatches between Wikidata's data and other databases so we can later expose them.Thinking through what the first version of the REST API should contain and what should come later.Fixed an issue with whitespaces when editing Lexemes (
phab:T250550
)Made sure all languages show up in the language selector for monolingual text Properties at least with their language code because them not showing up was very confusing (
phab:T124758
)Fixed an issue with generating correct links for external IDs with + (
phab:T271126
)Fixing an issue with Property selector not falling back from language variant to major language (
phab:T272712
)Continuing to build out the
Query Builder
and focusing on input for quantity and date queries (
phab:T268942
and
phab:T272697
)Due to the planned delay of the release of MediaWiki 1.36, the Wikibase team has been working on preparing a Wikibase update that includes new functionality (such as the “Federated Properties” feature) based on v1.35. To that end, we started backporting certain features and fixes into the Wikibase 1.35 release. Follow our progress
here
.
You can see all open tickets related to Wikidata here
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 .
Monthly TasksAdd labels, in your own language(s), for the new properties listed above.Comment on property proposals: all open proposals Contribute to a Showcase item .Help translate or proofread the interface and documentation pages, in your own language! Help merge identical items across Wikimedia projects.Help write the next summary! Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 14:44, 1 March 2021 (UTC) How do I connect the video game developer Iron Gate Studio (Q105725001) to the publisher Coffee Stain Studios (Q3178586) ?[ edit ]I know for a fact that the publisher mentioned is connected to the video game developer. There's no mention on the internet about the video game developer being a subsidiary of this publisher. Should I mention the publisher and the developer only for the game Valheim (Q105100327) , or should I also mention their partnership in their QIDs? Tetizeraz ( talk ) 21:15, 1 March 2021 (UTC)
If you can't provide a reference, don't add it. --- Jura 00:51, 2 March 2021 (UTC)Wikifunctions logo contest[ edit ] Hello. Please help to choose a design concept for the logo of the new Wikifunctions wiki. Voting starts today and will be open for 2 weeks. If you would like to participate, then please learn more and vote now at Meta-Wiki. Thank you! -- Quiddity (WMF)01:45, 2 March 2021 (UTC)
Academic publishers preprint policies[ edit ]The page on ENWP: w:List of academic publishers by preprint policy has a structured table of publisher policies. How would it be best to encode these into wikidata? A possible way of organising data on the item of a publisher (e.g. Wiley (Q1479654) ):
Statement: permits (P8738) preprint (Q580922) (or possibly create item for "submission from / sharing of preprint") Qualifier: prohibits (P8739) create items for common restrictions e.g. "commercial preprint server" or "version after peer review"Qualifier: has quality (P1552) alternatively the inverse of the above e.g. "Non-commercial preprint server only" or "version before peer review only"Qualifier: Not sure how to encode conditions such as "If preprint is CCBY, then must pay APC"Qualifier: start time (P580) if people want to add in when different publishers/journals changed policyReference: quotation (P1683) if people want to quote the policy txt (along with reference URL (P854) , obv.)Please reply at w:Talk:List_of_academic_publishers_by_preprint_policy#Draft_wikidata_encoding to keep discussion centralised. Thanks in advance!. T.Shafee(evo&evo) ( talk ) 05:04, 2 March 2021 (UTC)
Please discuss this onwiki. --- Jura 09:43, 2 March 2021 (UTC) @ Jura1 : When you say onwiki, so you mean wikidata or enwp? T.Shafee(evo&evo) ( talk ) 10:35, 3 March 2021 (UTC)Underscore Smith and unknown Smith (label)[ edit ]Interesting find: Q100924725 (and a few others) use "_" for the missing first name in the label. A past import went with "unknown" ( Q75646725 ). I also came across others that merely used the family name in these cases. Either has its advantages. "_" probably works better when copied to nl. @ IagoQnsi , Edoderoo , GZWDer : --- Jura 09:41, 2 March 2021 (UTC)
See also Allen (Q15999764) which the missing first name is completely left out in the label.-- GZWDer ( talk ) 20:47, 2 March 2021 (UTC)Also rdfs:label "Smith"@en . --- Jura 08:31, 4 March 2021 (UTC)File:HMS 'Sappho' capturing the Danish brig 'Admiral Jawl', 2 March 1808- ships engaged RMG A4461.tiff[ edit ]This picture has been assigned a Q number, it is one of two. One q number has been assigned to two different pictures. The artist for both is Francis Sartorius (the younger). Commons has 5 images of two pictures. Broichmore ( talk ) 11:17, 2 March 2021 (UTC)
Are you sure? HMS Sappho capturing the Danish brig 'Admiral Jawl', 2 March 1808: surrender of the brig (Q50919903) and HMS Sappho capturing the Danish brig 'Admiral Jawl', 2 March 1808: surrender of the brig (Q50919903) each point to a single distinct image on commons. Where exactly is the " One q number has been assigned to two different pictures"? -- Tagishsimon ( talk ) 21:09, 2 March 2021 (UTC) @ Broichmore , Tagishsimon : you're both being very unclear. Broichmore, is talking about multiple pictures and one qid without providing any links. Tagishsimon just linked the same picture twice.I see that Commons:Category:Admiral_Yawl_(ship,_1808) was created, which has 5 pictures so I guess we're talking about these. HMS 'Sappho' capturing the Danish brig 'Admiral Jawl', 2 March 1808: ships engaged (Q50863142) with a shooting image HMS Sappho capturing the Danish brig 'Admiral Jawl', 2 March 1808: surrender of the brig (Q50919903) with a broken sails image Looks like one of the image was linking to the wrong one. You can just change it to the right one . Multichill ( talk ) 19:37, 3 March 2021 (UTC)A demoted page[ edit ]_-_HMS_'Sappho'_Capturing_the_Danish_Brig_'Admiral_Jawl',_2_March_1808,_Ships_Engaged_-_BHC0582_-_Royal_Museums_Greenwich.jpg<]<)+}){kind=link}
+}){kind=link}
Greetings to all. I wanted to change the status of this item, last.fm in Farsi wikipedia from good article because the page has been demoted and does not have good article status anymore but the page is protectded and I am not able to do so, so to any who is able: could you please be a dear and remove the good article badge? Thanks in advance Vahid ( talk ) 12:10, 2 March 2021 (UTC)
This item is not protected so as an autoconfirmed user you can change it by yourself at Special:SetSiteLink/Q183718/fawiki .-- GZWDer ( talk ) 20:49, 2 March 2021 (UTC)Logo Update[ edit ]Hello, I am new user trying and still learning wikidata, I am trying to create wikidata for company , just for information , i am not associated with company anyway, this is for learning process , i will also willing use some other profile as well.
Help me to upload logo, it is not in Commons . – The preceding unsigned comment was added by Keith8221 ( talk • contribs ) at 12:16, 2 March 2021 (UTC).
If you are not associated with the company you likely don't have any right to put their logo licensed under a CC license. ChristianKl ❪ ✉ ❫ 15:52, 2 March 2021 (UTC)@ Keith8221 : You can only upload it for Wikipedia fairuse in Wikipedia. -- BoldLuis ( talk ) 16:53, 2 March 2021 (UTC)Both of the above answers overlook that there are many logos on Commons, without CC licences, because they fall below the " threshold of originality ". See c:Category:Logos . We'd need a link to a copy of the logo before we can advise whether that applies in this case. Andy Mabbett (Pigsonthewing); Talk to Andy ; Andy's edits 19:03, 4 March 2021 (UTC)Sorting by a listeria table property[ edit ]Question originally asked at Template_talk:Wikidata_list#Sorting_by_a_qualifier_property
Any ideas on how to sort a
listeria table
by a qualifier property (e.g.
|sort=P106/Q3809586/P582
)? The example below still seems to just sort by ascending QID (
see my sandbox
).
T.Shafee(evo&evo)
(
talk
) 09:59, 3 March 2021 (UTC)
Necesito que agreguen el enlace a wikimedia commons.
Script (style of handwriting)[ edit ]I'd like to be able to record that a manuscript is written in secretary hand (Q16933853) . The current property writing system (P282) is restricted to <instance of> alphabet, writing system, or orthographic transcription and has a short list of one-of constraints.
This seems to have been solved for manuscripts in uncial script (Q784235) by adding <instance of> Latin script (Q8229) to "uncial script". Is that the way to go about this? - PKM ( talk ) 19:58, 3 March 2021 (UTC)
@ PKM : I think a new property "script style", to take values that were instances or subclasses of script (Q33260112) would be the right way forward. It could be overloaded onto property writing system (P282) , but I am not sure it would be right -- item writing system (Q8192) says that it encompasses script (Q63801299) : set of symbols of a writing system and orthography (Q43091) : set of conventions regulating the way of using a writing system, but not script (Q33260112) : style of handwritten language -- so it looks to me like something to identify the latter would be usefully orthogonal to writing system (P282) . Jheald ( talk ) 23:38, 3 March 2021 (UTC)@ PKM :: Proposed: Wikidata:Property proposal/writing style . Jheald ( talk ) 09:03, 4 March 2021 (UTC)"Also known as" for historical names?[ edit ]When an entity (e.g. a newspaper) has a historical name it no longer uses, should that name be included in the "also known as" alias field near the top, or should it only be included as title (P1476) with start time (P580) and end time (P582) qualifiers? {{u| Sdkb }} talk 21:12, 3 March 2021 (UTC)
I usually do both, especially for "official name" of businesses. [edited]] - PKM ( talk ) 21:21, 3 March 2021 (UTC)If the alternates are functionally interchangeable besides name, then it's probably a good idea to list them as aliases (but nobody really knows anything here, we're all just blind fools doing whatever we think makes sense: so I could be wrong). If the entities are more substantially different, then it might make more sense to create a separate item for the historic entity. For instance, scholarly journals and newspapers may go through different titles over the years, but keep the same volume and issue numbering. Each title may have its own set of catalogue identifiers, and for ideal bibliographic displaying the accurate title separate items are warranted, connected by replaces (P1365) , follows (P155) , etc. Businesses and organizations that change names as result of mergers or corporate restructuring probably also warrant distinct item, as the parent organization(s) and notable executives may only be applicable to the one of the items. Simple name changes of schools, companies, and geographic places that don't change materially following name changes may not warrant separate items. -Animalparty ( talk ) 22:54, 3 March 2021 (UTC)Normally, anything that is in labels, descriptions and aliases should be in statements as well. If you don't add a former title as alias, you can't select its item with that title. --- Jura 08:28, 4 March 2021 (UTC)Yes, it belongs in both alias and statements. However official name (P1448) is more approriate for the name of a newspaper then title (P1476) . Having the information in the alias makes it easy for people who create an item that wants to link to the newspaper where the source uses the old name to find the item. ChristianKl ❪ ✉ ❫ 11:11, 5 March 2021 (UTC)querying and displaying images with author/copyright[ edit ]On Querying image (P18) , the result at query.wikidata.org will be an image thumb with a larger size in a lightbox, which restrict's its usage to very private occasions because I cannot fulfill CC attribution requirements (especially when embedding the result). What would be a feasible approach to solve this? I placed a similar question @ Commons talk:Structured data , but it might exist a different solution here, like openening the image in the Commons image viewer (like in the item page). Any ideas are appreciated … thanks! Please ping me for an answer -- Elya ( talk ) 21:22, 3 March 2021 (UTC)
People have said that "click through" attribution is sufficient, and that's what Wikipedia uses. If you click the image you go the page on Commons with the details. Ghouston ( talk ) 01:50, 4 March 2021 (UTC) @ Elya : The solution would be either or both of representing the copyright status and/or licence for the image in Commons structured data, and as a qualifier of the P18 value ( copyright license (P275) , for instance) such that reports could access one or other value. -- Tagishsimon ( talk ) 02:06, 4 March 2021 (UTC) @ Tagishsimon , yes, we have this data at structured Commons, but how to retrieve it? I could start a project completely out of the Query Service and combine 2 APIs, however, it would be nice to retrieve them via the Query service. Writing a bot that copies structured data from Commons to Wikidata as qualifiers … ? Rather not, I think.@ Ghouston , thanks, but not exactly. Check out this random map query: Churches in Wittenberg . no chance to get to the image attributions. Yes, this particular output is giving no way to get to the Commons image page, so it's inadequate. Perhaps the underlying software could be modified. Ghouston ( talk ) 09:15, 4 March 2021 (UTC)I might try however to additionally output the Commons file page as hyperlink in the map, which would be a no-api but sufficient solution. Thanks for thinking around with me ;-) If anybody is aware of an API approach, still highly appreciated! -- Elya ( talk ) 06:22, 4 March 2021 (UTC)@ Elya : this technically works, but not as optimal, as multiple requests (first to WDQS, then to commons API, maybe then to WCQS).SELECT?item?itemLabel?pbLabel?cat?coord?img(IF(BOUND(?img),?usage,"")AS?usg)WITH{SELECT?item(SAMPLE(?cat)AS?cat)(SAMPLE(?coord)AS?coord)(SAMPLE(?img)AS?img)WHERE{wd:Q75849591wdt:P527[wdt:P527?item;wdt:P361?pb].?pbwdt:P31wd:Q76598130.?itemwdt:P625?coord.OPTIONAL{?itemwdt:P373?cat.}OPTIONAL{?itemwdt:P18?img.}}GROUP BY?item}as%itemsWHERE{INCLUDE%items.BIND(STRAFTER(wikibase:decodeUri(STR(?img)),"http://commons.wikimedia.org/wiki/Special:FilePath/")AS?fileTitle)SERVICEwikibase:mwapi{bd:serviceParamwikibase:endpoint"commons.wikimedia.org";wikibase:api"Generator";wikibase:limit"once";mwapi:generator"allpages";mwapi:gapfrom?fileTitle;mwapi:gapnamespace6;# NS_FILEmwapi:gaplimit"1";mwapi:prop"imageinfo";mwapi:iiprop"extmetadata";mwapi:iiextmetadatafilter"UsageTerms".?usagewikibase:apiOutput"imageinfo/ii/extmetadata/UsageTerms/@value".}SERVICEwikibase:label{bd:serviceParamwikibase:language"de".}} Try it! There are few other interesting fields in extmetadata you may want to use. Note, that it does not take multiple licenses into account, for example, for https://commons.wikimedia.org/wiki/File:Wittenberg_Schlosskirche.JPG it shows only "Public Domain". -- Lockal ( talk ) 16:11, 4 March 2021 (UTC) Lockal , oh, wow … I'll have to dig into that, maybe with the folks at „request a query“ which I bother a lot recently, because my own map query is a bit more complex than this church example. Only one thing: is it possible to get not only the license but also the author? -- Elya ( talk ) Oops, I forgot to add a link I used for debugging - https://commons.wikimedia.org/w/api.php?action=query&titles=File:Lutherstadt_Wittenberg,Kirchplatz,Stadtpfarrkirche_St._Marien.jpg|File:Wittenberg_Schlosskirche.JPG&prop=imageinfo&iilimit=50&iiprop=extmetadata ( api help ). There is an "Artist" field, so updated query is here . Also, you may want to start with WCQS + P180 (depicts) instead of WDQS + P18 (image). -- Lockal ( talk ) 18:15, 4 March 2021 (UTC)I beg to suggest that SPARQL queries federated across wikidata and commons is not the way to go. If the licence / author / whatever data is in commons structured data, then it can be reported on and added to the wikidata P18 statements as qualifiers, such that your report can be based on wikidata only. Q78227747#P18 -- Tagishsimon ( talk ) 20:13, 4 March 2021 (UTC)Archiving options ?[ edit ]+}){kind=link}
+}){kind=link}
What archiving options are currently supported for talk pages on Wikidata ?
Is there one where a thread will stay on the talk page until someone adds an "I think this thread can be archived now" template, and then it gets automatically archived eg 2 days later ?
I think I've seen this on other WMF wikis. Jheald ( talk ) 22:59, 3 March 2021 (UTC)
Aha! {{ Section resolved }} is what I'm after. And it looks like User:SpBot will take care of things from there ( Special:Contributions/SpBot ). Jheald ( talk ) 23:23, 3 March 2021 (UTC)Focus languages for improvements to the lexicographic extension of Wikidata and Abstract Wikipedia[ edit ]Hi. We would like to find two or three language communities who would be good matches to help to start and guide some long-term improvements to the lexicographic data part of Wikidata, and the closely related work in the Wikifunctions wiki and the Abstract Wikipedia project, over the next few years. Participating communities will hopefully find that this project will lead to long-term growth in content in Wikipedia and Wiktionary in and about their language. See Wikidata:Lexicographical data/Focus languages for more information. Please help us identify potential good matches. More details are on that page. Thank you! Quiddity (WMF) ( talk ) 00:09, 4 March 2021 (UTC)
Change on formatter URL[ edit ]On February 10, Rashinseita changed the statement formatter URL (P1630) for the property BSD Portal athlete ID (P4650) . I reversed this change two days ago. Even so, the old formatter is still used. For example, if you follow the preferred link for the data object Susanne Kreher (Q60193698) , you come to the page https://web.archive.org/web/*/http://www.bsd-portal.de/sport/skeleton/athleten/#536 and not the page http://www.bsd-portal.de/sport/skeleton/athleten/#536 . How long will it take to use the new formatter or do I need to change anything? -- Gymnicus ( talk ) 14:19, 4 March 2021 (UTC)
The question is settled. It was due to the cache. After I have cleared the cache, the link is now to the correct page. -- Gymnicus ( talk ) 14:33, 4 March 2021 (UTC)| I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. -- Gymnicus ( talk ) 14:33, 4 March 2021 (UTC) |
Hi, an Indonesian editor noticed vandalism in a BLP entry. The editor wondered if the following words could be added to the AbuseFilter/11:
wikt:bangsat wikt:lonteIs here the correct place to ask for this kind of addition to abusefilter? Also, please block Ixarising1 ( talk • contribs • logs ) for vandalism. Thanks. Bennylin ( talk ) 15:12, 4 March 2021 (UTC)
DannyS712 is the last person to edit that filter, so if we ping him he can probably fix that. :-) Jon Harald Søby ( talk ) 15:33, 4 March 2021 (UTC) I was just updating deprecated variables - I'm not familiar with the filter, sorry. DannyS712 ( talk ) 17:39, 4 March 2021 (UTC)What's the general consensus regarding blocking/filtering profanities and such in Wikidata? I suppose this is also a problem in many languages short description? Is there a general strategy taken by Wikidata to combat such vandalism? Maybe each language can be assigned a specific filter of bad words (after making sure they are really bad and such). I don't want this to be just a stopgap solution. I manage such filters in id.wiki, so if you need some general syntax help, I can probably help with that. Bennylin ( talk ) 18:28, 4 March 2021 (UTC)
Library of Congress identifier[ edit ]I want to connect https://www.loc.gov/item/02004585/ to Records of Officers and Men in the Civil War, 1861-1865 (Q105755689) , but it doesn't seem to fit any of the Library of Congress identifier schemes, am I missing something, or just use the url? -- RAN ( talk ) 15:39, 4 March 2021 (UTC)
The formatter URL in Library of Congress Control Number (LCCN) (bibliographic) (P1144) is https://www.loc.gov/item/$1/ so that property would seem to achieve the link. Heaven knows whether the regex will be happy. -- Tagishsimon ( talk ) 20:40, 4 March 2021 (UTC) Excellent, thanks. I always wondered what they other LCCN number was for. -- RAN ( talk ) 00:03, 5 March 2021 (UTC)Systematic human abuse at Wikidata and Metawiki[ edit ]How negligent WMF staff can be?
https://www.wikidata.org/w/index.php?title=User_talk:Multichill&diff=prev&oldid=1296609455 https://www.wikidata.org/w/index.php?title=User_talk:Andreasmperu&diff=prev&oldid=1296611601 https://www.wikidata.org/w/index.php?title=User_talk:Rschen7754&diff=prev&oldid=1296623823 https://www.wikidata.org/w/index.php?title=User_talk:Jasper_Deng&diff=prev&oldid=1296625692 176.15.141.169176.15.141.169 19:50, 4 March 2021 (UTC)
Sometimes they don't clean the coffee cups before going home. Did you have a point, or are you just grinding an axe? -- Tagishsimon ( talk ) 20:01, 4 March 2021 (UTC) If you see the issue happened in one page repeatly, you may request protection at WD:AN .-- GZWDer ( talk ) 20:34, 4 March 2021 (UTC)Verifiability of data about myself[ edit ]I've changed my name and gender. How can I provide verifiable citations about these changes to my own data? Marnanel ( talk ) 21:32, 4 March 2021 (UTC) (aka Thomas Thurman (Q90844917) )
That's a great question. Because Wikidata includes items for people who are not actually notable (e.g. relatives of notable people, candidates for minor offices, people imported from random databases, etc.), how do we expect those items to be maintained, especially given that incorrect data about living people can cause actual harm to those people? Kaldari ( talk ) 23:09, 4 March 2021 (UTC)@ Marnanel : Assuming there are no public sources such as newspaper articles that you can refer us to, the only suggestion I can think of at the moment would be to email privacy
wikimedia.org with evidence of the changes and request that they update the information. If that doesn't work, I would suggest posting a request at the
Administrators' noticeboard
. I went ahead and removed the gender from
Q90844917
(as it was unreferenced anyway). Good luck.
Kaldari
(
talk
) 23:23, 4 March 2021 (UTC)
Help:Sources
explains how to reference information on Wikidata, emailing WMF isn't mentioned and I don't quite see how that could be an acceptable way of referencing.. ---
Jura
07:06, 5 March 2021 (UTC)It depends on current statements - see
Wikidata:Autobiography#On_Wikidata
. If statements are unsourced you can just remove them. If statements are sourced, you can contact the source owner and ask them to update info (otherwise even WMF cannot do anything - you would just trigger algorithms which will reimport old data either in the same element or creating a duplicate). --
Lockal
(
talk
) 07:31, 5 March 2021 (UTC)I doubt that it would be possible to change the name of a candidate in a 2016 election.
Ghouston
(
talk
) 10:07, 5 March 2021 (UTC)Perhaps if you had something like a twitter account, which could be verified as belonging to the candidate in the 2016 election, then it would be possible to publish whatever biographical information about yourself that you liked, and this would be accepted as a source for Wikidata.
Ghouston
(
talk
) 10:26, 5 March 2021 (UTC)Q1687151[
edit
]Two people were improperly merged, I am not sure if I know how to de-merge properly yet. See Jens Dietrich (Q1687151) . -- RAN ( talk ) 23:57, 4 March 2021 (UTC)
Hopefully sorted. Now Jens Dietrich Zimmermann (Q3177184) and Jens Dietrich (Q1687151) . -- Tagishsimon ( talk ) 00:10, 5 March 2021 (UTC)Invitation to join new Wikiproject: Early Modern England and Wales[ edit ]We are building out a new project, Wikidata:WikiProject Early Modern England and Wales . The purpose of this project is to improve Wikidata's coverage of England and Wales in the 1500s and 1600s, with a particular focus on building out items needed to understand developing transport networks in the period before mass industrialisation. We'll be working in partnership with the collaborative Viae Regiae (Q105547906) project which is building a Gazetteer of Early Modern England and Wales (Q105548625) . You can learn more about the Viae Regiae project on its website .
We want to enrich Wikidata's coverage of maps, cartography, manuscript itineraries, and historic places and people. We're just getting started - come join us! - PKM ( talk ) 00:45, 5 March 2021 (UTC)
Heads up: page protections of "highly used items"[ edit ]A couple of months ago I proposed a bot task to indefinitely semiprotect "highly used items" as per Wikidata:Page protection policy#Highly used items . I have not been able to kick this off due to Covid lockdown constraints that leave little time for Wikidata, unfortunately, but now I am pretty much ready to go and want to let you know that this is going to happen within the next days. There are roughly 25.000 items to receive indefinite semiprotection, and fewer than 100 which do not qualify for protection under this scheme any longer and need to be unprotected. The plan is to ramp this up over a couple of days with a series of manually executed bot runs; once this is done, an unsupervised weekly job will manage the protections (protect items which newly fall into this scheme, and unprotect those which do not any longer).
I do not actively seek for input at this point; previous thorough discussions have already taken place in the bot approval process and the request for admin rights for the bot account User:MsynABot . Nevertheless, you may comment here and I will read all the input :-) — MisterSynergy ( talk ) 09:29, 5 March 2021 (UTC)
thanks for doing this. BrokenSegue ( talk ) 17:25, 5 March 2021 (UTC)Update: the first ~1.5k protections have been added, but I did receive complaints about how the protection log entries render on watchlists on English Wikipedia. There is now a phabricator task at phab:T276613 where I want to wait for some more input by the dev team before I can proceed. — MisterSynergy ( talk ) 21:18, 5 March 2021 (UTC)
The Wikidata consultation about the Universal Code of Conduct is closed[ edit ]As you can read from the title, the second phase of the consultation about the Universal Code of Conduct is now closed. This means that the phase in which several communities (Arabian, Bengali, Italian, Korean, Malay, Nepalese, Polish, Yoruba, plus Wikidata and Wikimedia Commons) commented with their concerns, suggestions, ideas and opinion is now over.
Now, we facilitators will work to collect and sum up all of your feedback and answers. The results and the relative data will then be published on Meta (you'll be noticed when this will happen), and will also be available to the Committee that will draft the second part of the UCoC, regarding the implementation of the Code and the reporting system.
This doesn't mean that the discussion is over! There will be new rounds of consultations on Meta and with our numerous Affiliates, and there is space also for a community discussion here on Wikidata about implementing ourselves the UCoC. I'll be glad to give a help as a volunteer , if it will be so.
Meanwhile, I want to thank all the people who took part to the discussions , reached to me in private, answered the survey or were victim of my requests for participating! You've been great, and I truly thank you for your help!
If you want to keep in touch, keep following the page about the UCoC here or on Meta , and please let your voice be heard!
Cheers, -- Sannita (WMF) ( talk ) 16:01, 5 March 2021 (UTC)
White field[ edit ]On right half of screen on item pages I have big white field. I use FireFox 86.0 Windows 10. FireFox 56.0.2 with same OS hadn’t this problem. 217.117.125.88 17:55, 5 March 2021 (UTC)
Ordering statement values[ edit ]I am currently developing a page for the fictional solar system depicted in Kerbal Space Program I must have done this link incorrectly, so just search the above item. ERBuermann ( talk ) 18:11, 5 March 2021 (UTC) . I wanted to list the planetary systems in order, but I forgot to link the page about the central sun. How do I change the order that the statement values appear in? ERBuermann ( talk ) 18:10, 5 March 2021 (UTC)
https://www.wikidata.org/wiki/User:Tohaomg/rearrange_values.js -- Tagishsimon ( talk ) 18:18, 5 March 2021 (UTC)order doesn't have meaning on wikidata. you can reorder things but it's not meaningful and you should assume it'll get shuffled. BrokenSegue ( talk ) 19:57, 5 March 2021 (UTC) Order does have meaning in the UI. It will not be shuffled unless someone shuffles it. -- Tagishsimon ( talk ) 20:16, 5 March 2021 (UTC) @ Tagishsimon : I mean it has meaning only in that it is preserved. But it has no semantic meaning to wikidata and a bot or another user would be totally free to mess with the order as part of a refactor. Honestly I think the backend API should shuffle the order just to avoid people trying to assign meaning to the statement order. BrokenSegue ( talk ) 20:47, 5 March 2021 (UTC) Sure, I know what you mean. But equally when consulting items with, for instance, 10s of P39s, it's more easy when they're in date order. When reading qualifiers, start date before end date is probably more intuitive & arguably requires less brain-power to comprehend, than end before start. All manner of standarised ordering and standardised wording (e.g. for descriptions) helps the user; which is (also) what we should be about. Agreed that more could be done server-side, were we to agree a rule base. -- Tagishsimon ( talk ) 21:06, 5 March 2021 (UTC) hmmm, maybe we should implement sorting of statements front-end (alphabetica/series ordinal/etc). could be a plugin or something. BrokenSegue ( talk ) 21:11, 5 March 2021 (UTC)Q55107400 and Q28772011[ edit ]Hello, I'm working on Palace in Bologna with QAnswer. I merged Q55107400 with Q28772011 because both are about the same palace. But Q28772011 is also about a museum. Perhups should it be possible to use Q55107400 redirect as an element only for museum ?-- Patafisik ( talk ) 18:21, 5 March 2021 (UTC)
Probably better not to have merged them. The palace is a building. It has within it - at the moment - a museum. These are two distinct things, which can be linked, as separate items, by properties such as 'location'. I see you have made may label changes since the merge, but I'm inclined to wind back the merge. -- Tagishsimon ( talk ) 18:29, 5 March 2021 (UTC)Is case sensitivity considered acceptable for multiple statements, or merge ?[ edit ]Having multiple entries under the taxon common name property (P1843) which simply differ in their case sensitivity is not an uncommon issue, usually driven by imports from different sources which use different standards.
For example, the page for Corvus corax under taxon common name, language English has entries for 'Common Raven' and 'common raven'. Obviously these refer to the same data and the duplication seems to just be taking up space.
Is it acceptable to combine these and their references into a single entry, or is there some rule or guideline that says no, you have to leave them both in place ?
Thanks CanadianCodhead ( talk ) 19:04, 5 March 2021 (UTC)
if two items represent the same concept they should be merged. even if they have totally different labels (or nearly the same labels). BrokenSegue ( talk ) 19:56, 5 March 2021 (UTC) oh I was confused ignore that. Oh yeah I think you want to delete one but don't ask me which. BrokenSegue ( talk ) 20:01, 5 March 2021 (UTC)I would say merge, no need to delete, the external sources we loaded here, may be linking back to us. -- RAN ( talk ) 22:40, 5 March 2021 (UTC)Deleting one common name over another could cause issues. Common names of different organisms in different countries can have different standards. So removing one capitalization in favor of another would be favoring one country's norms over another country's. -- EncycloPetey ( talk ) 22:55, 5 March 2021 (UTC)
