Template talk:Property documentation/Archive 3

From Wikidata
Jump to navigation Jump to search
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Current uses not shown anymore

Hi Jura1! Thanks for adding the search form to the documentation. It looks like since this change, the number of current uses of the property is not shown anymore (for instance on Property_talk:P350). I found that useful - would it be possible to have both? − Pintoch (talk) 10:45, 31 May 2018 (UTC)

Never mind, it looks like it is not actually related to your change… I will investigate. − Pintoch (talk) 10:48, 31 May 2018 (UTC)
@Pasleim: any idea what is happening? − Pintoch (talk) 10:53, 31 May 2018 (UTC)
It may be worth storing this data in JSON instead of a #switch, as it’s less error-prone, although it can’t be processed without Lua (I don’t know if anything else uses it apart from the property documentation, which is already Lua). If an admin converts a page into JSON using Special:ChangeContentModel, as far as I know, syntax errors simply can’t be saved. --Tacsipacsi (talk) 17:49, 31 May 2018 (UTC)
The problem is the numbers, not the format. Please don't convert it. It would break the charts
--- Jura 18:21, 31 May 2018 (UTC)
If converted correctly, it shouldn’t break anything, although I don’t know which charts you’re speaking about. And why would wrong numbers break the output (apart from displaying wrong numbers)? As theoretically any number can occur, the module should handle any number. —Tacsipacsi (talk) 22:57, 31 May 2018 (UTC)

Provided background color to Help section

Provided background color to Help section (diff). For example, see Property talk:P5230. This edit was done because formerly "Help" section was difficult to distinguish from bare talk. If there are any problems or better ideas about this edit, post here about that, or directly edit the template. Thanks. --Was a bee (talk) 03:06, 17 June 2018 (UTC)

Lua errors

Wikidata:WikiProject Ships/Properties missing has bunch of errors caused by this template. Anybody knows how to fix them?--Jarekt (talk) 17:48, 30 November 2018 (UTC)

Obviously, the page is not a "property documentation". Matěj Suchánek (talk) 11:17, 2 December 2018 (UTC)

Should we add a link to NavelGazer?

It is sometimes useful for finding out the main users of a property or if it's mainly added by bots or manually. --Marsupium (talk) 11:43, 1 April 2019 (UTC)

Can't translate "<chart by item creation date>"?

Module:I18n/property documentation found nothing about this. --Liuxinyu970226 (talk) 23:21, 8 September 2019 (UTC)

Can be added. --Matěj Suchánek (talk) 16:35, 9 September 2019 (UTC)

It seems to be Template:Property documentation (even without any fields) that makes it fail. I think it happened days after edits I did to any of the involved pages ( Property:P443, Property talk:P443 or this Mdoule:Property documentation). --- Jura 13:27, 28 February 2020 (UTC)

In no event shall any on-wiki content cause a production error, it’s a MediaWiki bug (maybe caused by on-wiki errors, but even then it should be caught by MediaWiki earlier and should fail more gracefully). Reported on Phabricator. —Tacsipacsi (talk) 17:06, 28 February 2020 (UTC)

Single value constraint violations query partially broken

Hi! As reported here, the query for single value constraint violations doesn't work for identifiers having more than one formatter URL (e.g. try this). Could someone fix it? Thanks, --Epìdosis 13:02, 14 March 2020 (UTC)

Done. The constraint violation report will probably need separate fixing; that’s up to Ivan A. Krestinin, as he still hasn’t published the source code yet. (I’d much appreciate publishing it, in order to increase the bus factor (Q1812883) of the report updates.) —Tacsipacsi (talk) 16:42, 14 March 2020 (UTC)
By the way, the named subquery may even speed up things, as now the database is forced to get the format URL only once. I don’t know how data is physically stored on disk, but I don’t think data about the property itself and data about the items using the property would be likely to be efficiently queriable after each other, so separating these seems for me a good way to improve the query time. —Tacsipacsi (talk) 00:11, 16 March 2020 (UTC)

Current uses

In footedness (P8006) it's use in Qualifier is 2 which is from its own example. Property that is used in its own page should not be counted. Same with Main statement because instance of (P31) is also used in its own page. Hddty (talk) 15:15, 2 August 2020 (UTC)

I recently spearheaded the creation of new property, extinction date (P8556). There is an error, however, shown at the top of Property talk:P8556 that says,

 Lua error in Module:Property_documentation at line 738: Tried to read nil global forQualifierUse.

This seems to be a bug in this module, can somebody here help sort it out? I think I saw the same error on a different property page before, so I don't think this is a one-off. -The-erinaceous-one (talk) 04:41, 26 August 2020 (UTC)

Fixed --Matěj Suchánek (talk) 09:34, 26 August 2020 (UTC)

Map

Hello. Among the links that are generated automatically, we could have one leading to a request creating a map of all the items that use both the property and coordinate location (P625). This would be extremely useful, in particular for all properties that are defined as a Wikidata property for authority control for places (Q19829908). It could be named 'Map of items'. Thierry Caro (talk) 20:17, 7 September 2020 (UTC)

An example for Hikr waypoint ID (P8593). Thierry Caro (talk) 12:10, 12 September 2020 (UTC)
  • If we do, maybe we should set an upper limit to avoid properties with many uses.
    Alternatively, for these we could add an additional filter (e.g. samples, first 1000, filter by country). --- Jura 12:15, 12 September 2020 (UTC)
I'm fine with a limit. Maybe I would pick higher than 1,000 results though. I have successfully displayed maps with tens of thousands of points in the past. So I'd go for 10,000, maybe. Thierry Caro (talk) 22:04, 15 September 2020 (UTC)

List of mainspace pages linking to the property

In the lists section, it would be useful to have a link to Special:WhatLinksHere in the format of https://www.wikidata.org/w/index.php?title=Special%3AWhatLinksHere&target=foobar&namespace=0. This is useful because sometimes properties are used more than once in once page (especially if they are qualifiers). NMaia (talk) 06:14, 24 September 2020 (UTC)

Giving more visibility to property documentation

I contribute to wikidata since the beginning. Still Wikidata is very complex. My opinion is that there is a lack of editorial content and documentation.

I've only discovered recently that when you click on the Discussion page of a property you can find this documentation template.

I think that it would be very useful to have a dedicated page for property documentation. This page could be something like Property:P1001/Documentation and be accessible from a tabset just close to the Discussion page.

It could include recommendations on how to use the property but also statistics on the use of the property on Wikidata and sisters projects.

What do you think? PAC2 (talk) 06:39, 27 October 2020 (UTC)

All this information is already available on the talk page (including statistics). I don’t think spreading information over more pages is a good solution, but an indication about the talk page containing documentation may be useful. I’m not sure about the how, though. Renaming the talk tab? That’s not easy to do in an internationalized way. Adding a new tab? A bit confusing to have two tabs pointing to the same page. Does anyone have a better idea? —Tacsipacsi (talk) 10:02, 27 October 2020 (UTC)

Link to Schemas using a property

Could you please add a link to search for Schemas using a property? E.g. for P21:

https://www.wikidata.org/w/index.php?search=%22wdt%3AP21+%22&title=Special:Search&profile=advanced&fulltext=1&advancedSearch-current=%7B%7D&ns640=1

Note the space after property ID to not get false positives. -- JakobVoss (talk) 17:15, 2 November 2020 (UTC)

Mobile version

Property documentation doesn't appear on mobile devices, confirm? Fgnievinski (talk) 01:44, 12 November 2021 (UTC)

@Fgnievinski: It does, if you click or tap the “Read as wiki page” link at the bottom. Without the click, the software only shows what it considers to be discussion (but this mode is being phased out in favor of discussion tools working on the “Read as wiki page” interface, hopefully eventually making this extra click unnecessary). —Tacsipacsi (talk) 02:35, 12 November 2021 (UTC)

Additional lists / queries

Queries based on the following might be useful additions:

The above queries run for Art UK artist ID (P1367), which is used on about 24,000 items.

It might be possible to run such queries on properties with even more uses, if efficiency improvements can be found. But even if limited to properties with no more than about this number of uses, I think they would be quite useful additions. Jheald (talk) 15:33, 11 March 2022 (UTC)

More efficient query for non-ID properties, with sample values: https://w.wiki/4wUq (for property Art UK artwork ID (P1679)). Jheald (talk) 16:15, 11 March 2022 (UTC)
For properties used on larger numbers of items, e.g. WikiTree person ID (P2949) : stats for IDs ; non-IDs ; and sitelinks, using statistical sampling with bd:sample -- Jheald (talk) 10:58, 27 July 2023 (UTC)

Lists

For discussion, please use #Discussion. Feel free to annotate the points.