Wikidata:WikiProject Data Quality/Issues/P642/Strategy
Do not create the corresponding Wikidata talk page just yet!
We are waiting for a decision to move an existing talk page into that page name, so it needs to remain vacant for the time being.
If you have some idea of what some section below should contain, and the section is still void of regular text (in contrast to subheadings), simply add your content yourself. There is no need to discuss it unless it contradicts or would change existing content. If it does, you may still add your idea to the end of the section, marked as a Comment with your signature and timestamp at the end. You may also use the
Comment mark if you merely have a question or want to make a remark that should not be part of the content once the talk page is available.
Areas of work
editWikidata namespaces
editThe following table lists number of instances in each namespace at the start of the of (P642) deprecation project. Don't bother updating it; current numbers can be tabulated on a status page if desired.
Namespace | of (P642) count | Action |
---|---|---|
Main | > 10,000,000 | Convert |
User | 741 | Announce |
Wikidata | 1,589 | Investigate |
File | ? | Investigate |
MediaWiki | 1 | Investigate |
Template | 19 | Investigate |
Help | 105 | Convert |
Category | 0 | No action |
Property | 208 | Convert |
Query | 0 | No action |
Lexeme | 7 | Convert manually |
EntitySchema | 4 | Investigate |
TimedText | 0 | No action |
Module | 7 | Investigate |
Translations | 35 | Investigate |
Gadget | 0 | No action |
Gadget definition | 0 | No action |
Associated talk namespaces will not be considered, as they contain historical discussions that should not be modified.
Q item statements
editProperty statements
editLexeme statements
editHelp pages
editWikidata pages
editWikipedia
editWikimedia Commons
editStored queries
editSearch methods
editSPARQL queries
editSPARQL can be used to search the Main Q item, Property and Lexeme namespaces for specific instances of triples involving of (P642) or other entities satisfying certain criteria.
Tabulated use case format
editUseful columns:
- Use case ID
- Use case query
- Number of matches
- Sample item
- Triple match criteria
- Main statement property
- Subject item criteria
- Main value data type or object item criteria
- of (P642) qualifier value item criteria
- Other criteria
- Other qualifiers
- References
- Rank
- Labels
- Descriptions
- Aliases
- Proposed handling
- Current status
Use case ID
editUse case query
editThe Template:Wdquery template allows for queries easily accessed via an inline link.
Triple match criteria
editAbbreviated notation
editProposed handling
editCurrent status
editTable layout
editFor the general use case format: All of the useful columns, except Other criteria
Special-purpose tables may use a different set of columns.
Preparatory statistics
editTable theme selection
editMediawiki page full-text search
editThe full-text search feature is less versatile, but can be used in any namespace, not just those with contents based on triples.
Replacement guide
editProperties to use
editExisting properties
editWhen looking for other properties to replace of (P642), one that should be avoided is country (P17). While the documentation claims it indicates the physical location of the subject, it isn't always used in that way, as it's sometimes used with multiple values for embassies, to indicate both the the country to which the embassy belongs and the country to which it's addressed (neither of which is necessarily the country where the embassy is physically located). It's also quite limited, as its value type must always be a country (Q6256).
Potentially useful properties:
Subject type \ Value type | Any type | Person, organization, country |
---|---|---|
Any type | ||
Building, region |
New properties
editExample use cases
editLabels
editTrial and evaluation period
editVerify that the new properties don't suffer from the same ambiguity and translation problem as of (P642).
Selected languages to check: English, German, French, Spanish, Russian, Hebrew, Arabic, Chinese.
Sub-property relations
editProperty class assignments
editConstraints
editMostly for new properties created, but constraints applied to existing properties may be considered for change as well.
Allowed entities
editAt least same entities allowed as for of (P642).
Entity types
editScope
editProperties directly replacing of (P642) in place must be allowed as qualifiers. If appropriate, using them for main value statements may be allowed as well, but shouldn't be enabled unnecessarily (without at least one motivated use case).
Value types
editRequired properties
editWildcard replacement
editAutomation
editManual intervention
editCommunity outreach
editReporting effort status
editSee Wikidata:WikiProject Data Quality/Issues/P642 for primary status information. That page should contain:
- Statement of purpose of this project
- General scope and quantified size of project
- Current statistics indicating how much is left to do
- Updated work plan
- Log of significant changes or additions, such as new properties proposed or created
- Tabulated use case queries showing past, current and future statement bulk edits
- Notable special cases being handled manually
Comment Should we try to maintain table entries for past bulk edits completed, such as the deprecation of the ten million proper motion statements? --SM5POR (talk) 23:47, 21 December 2022 (UTC)
Documentation and tutorials
editUpdate documentation in Help and Wikidata namespaces on the choice of appropriate qualifiers where of (P642) has been mentioned until now.
Languages and translation
editVerify that newly created properties receieve labels and descriptions in those languages for which of (P642) has labels or descriptions.
Verify translations of updated Help pages.
Coordination with other projects
editAnnouncements
editAnnounce publicly when key milestones in the of (P642) deprecation effort have been completed, advising editors and concerned users to pay attention to the changes.