Property talk:P1424

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

topic's main template
the main template relating to a topic

Represents	Wikimedia template (Q11266439)
Data type	Item
Example	Syngnathiformes (Q650692) → Template:Taxonomy/Syngnathiformes (Q14464882) human (Q5) → Template:Infobox person (Q6249834) Basshunter (Q383541) → Template:Basshunter (Q8090653)
Robot and gadget jobs	DeltaBot does the following jobs: Add inverse statements from P1423
Tracking: usage	Category:Pages using Wikidata property P1424 (Q61035447)
See also	corresponding template (P2667), topic's main category (P910), template or module that populates category (P4329)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P1424 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 40,813 Main statement 40,800 >99.9% of uses Qualifier 11 <0.1% of uses Reference 2 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Inverse property of “template has topic (P1423)”:
if [item A] has this property (topic's main template (P1424)) linked to [item B],
then [item B] should also have property “template has topic (P1423)” linked to [item A]. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1424#inverse, SPARQL

Value type “Wikimedia template (Q11266439), Wikimedia module (Q15184295)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value Wikimedia template (Q11266439), Wikimedia module (Q15184295) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1424#Value type Q11266439, Q15184295, SPARQL

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1424#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1424#Entity types

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1424#Single value, SPARQL

This property is being used by: uk:Шаблон:НП Грузії, uk:Шаблон:Населений пункт Словаччини, uk:Шаблон:Муніципалітет Грузії commons:Template:Structured Data/License Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Single-value?

Micru, hello! Why is it single-value? For example, in Q178048#P1424 it is reasonable to add both infobox and navbox. Wikisaurus (talk) 11:20, 7 October 2018 (UTC)

Then we should perhaps have two specialised properties: "Topic's main infobox" and "Topic's main navbox", and we then should gradually move values to these appropriate specialised properties. --UV (talk) 12:20, 7 October 2018 (UTC)

@Wikisaurus: single value make sense, in you example you simply should add a qualifier, I did it as an example. Cheers, VIGNERON (talk) 13:23, 12 December 2020 (UTC)

Adding date as separator

Hi,

Is there any objections to add point in time (P585) as a separator (P4155) for single-value constraint (Q19474404)? See Q66363643#P1424 for an example where I added applies to part (P518) as a separator (to solve the current constraint) but it's strange and redundant with point in time (P585).

Pinging top-6 user of this property: @Ary29, Kooma, Mr. Ibrahem, Putnik, Florentyna, Wikisaurus:

Cheers, VIGNERON (talk) 13:23, 12 December 2020 (UTC)

@VIGNERON: Hi,

 Weak support (more like a  Comment) Even if these concepts overlap a lot, there is a still small difference: we usually refer more to an edition of an event, therefore numbered according to the year rather than directly to the date of the event. For example, the 2020 Summer Olympics (Q181278) or UEFA Euro 2020 (Q373501), initially scheduled for 2020, are postponed to 2021 due to the Covid-19 pandemic, but from what I see, "2020" as a number has been kept. It seems a bit wonky but maybe we should add point in time (P585) and put both each time. — Baidax ^💬 13:51, 12 December 2020 (UTC)

No support from my side. From the experiences from the past, a couple of bots right after such changes modifying the pages a second time, getting the pages out of the former reach (scheme). Additionally, maintenance is from my side much more difficult with sub-properties then with direct properties. --Florentyna (talk) 20:30, 13 December 2020 (UTC)

Property change proposal

I suggested as part of the Wikidata:Property_proposal/Change_template-topic_property_names_and_scopes that we should rename this property to topic has template.

Many topics cover a number of templates, as mentioned in the proposal and the section of above.

Inversely, a template can have many topics.

That is why I think the current proposal should include renaming this property and renaming the inverse property template has topic (P1423) to template has topic.

This establishes a system comparable to that of part of (P361)/has part(s) (P527).

Please see the proposal and discuss this change on the Proposal.

--Lectrician1 (talk) 20:35, 27 January 2021 (UTC)

Done. Property scope expanded and property constraints updated. --Lectrician1 (talk) 14:07, 4 February 2021 (UTC)

• @Lectrician1: Please change back. Otherwise you'd get hundreds values in places like Q11032#P1424... --Infovarius (talk) 22:46, 26 February 2021 (UTC)
  • @Infovarius: I mean, we could just delete this property (topic's main template (P1424)) and just have the one-way connection of template has topic (P1423). --Lectrician1 (talk) 02:28, 27 February 2021 (UTC)
    • It has been changed-back. --Lectrician1 (talk) 17:33, 4 March 2021 (UTC)