User:Tomodachi94/Properties pre-flight checklist

This page is a work in progress, not an article or policy, and may be incomplete and/or unreliable. Please offer suggestions on the talk page. বাংলা | català | čeština | Deutsch | English | español | فارسی | suomi | français | हिन्दी | magyar | italiano | 日本語 | 한국어 | Lëtzebuergesch | latviešu | македонски | Bahasa Melayu | မြန်မာဘာသာ | norsk bokmål | Nederlands | ਪੰਜਾਬੀ | polski | پنجابی | português | português do Brasil | română | Scots | shqip | slovenščina | српски / srpski | svenska | Türkçe | русский | українська | 中文（简体） | +/−

A checklist to run through on every property creation. Feel free to correct errors, but please don't add new items without consulting me first on my talk page.

Before creation

• Has it been a week since the initial proposal?
• Are there any outstanding issues pointed out in the discussion?
• Are there any major flaws with the proposal?

During creation

• Add labels in all provided languages.
• Add labels in languages I am proficient in.
• Add proper instance of (P31) statements:
  • Add Wikidata property for an identifier (Q19847637) if it is an identifier.
  • Add items related to the property's fields of study.
  • Here's a list of all instance of (P31) statements for properties, courtesy of Wd-Ryan: https://w.wiki/6T5c
  • Add Wikidata property for an identifier that suggests notability (Q62589316) or Wikidata property for an identifier that does not imply notability (Q62589320).
• Add a value for country (P17) if appropriate.
• Add other properties from the proposal itself, like formatter URL (P1630), source website for the property (P1896), applicable 'stated in' value (P9073), property usage examples, format as a regular expression (P1793), expected completeness (P2429), stability of property value (P2668), etc.
• Add the appropriate constraints:
  • For identifiers, I probably want single-value constraint (Q19474404) and distinct-values constraint (Q21502410).
    • If the property proposal provided a regular expression for verification, add format constraint (Q21502404) with the format as a regular expression (P1793) qualifier.
    • For identifiers with lexemes, add lexeme requires language constraint (Q55819106) with the item of property constraint (P2305) qualifier.
  • Always add subject type constraint (Q21503250) with class (P2308), relation (P2309), and constraint status (P2316) as qualifiers for properties for items.
  • Always add allowed-entity-types constraint (Q52004125) with item of property constraint (P2305) as a qualifier.
  • Always add property scope constraint (Q53869507) with property scope (P5314) as a qualifier.
• Add related properties.
• Copy the examples from the property usage examples onto their item pages using the new property. This is optional but recommended.

After creation

• Create an item for the property:
  • Add Wikidata property, instance of unique identifier, assigned by, etc. as appropriate to the new item.
    • Ensure that Wikidata property has a symmetric statement on the property's page.
• Create the property's talk page:
  • Add Template:Property documentation to the property's talk page at the very top.
  • Add the appropriate templates from the relevant WikiProjects (they should be noted in the request).
• After everything else, mark it as done on the property proposal page:
  • Change the status from ready to the property's P-ID.
  • Leave a message which pings everyone involved in the property unless the person indicates with a template that they don't want a ping.

    This is mostly automated with User:Tomodachi94/ping all users involved in discussion.js; just be conscious of the no ping template.