Property talk:P492
Jump to navigation
Jump to search
Documentation
OMIM ID
Online "Mendelian Inheritance in Man" catalogue codes for diseases, genes, or phenotypes
Online "Mendelian Inheritance in Man" catalogue codes for diseases, genes, or phenotypes
[create Create a translatable help page (preferably in English) for this property to be included here]
List of violations of this constraint: Database reports/Constraint violations/P492#Format, hourly updated report, SPARQL
Type “physiological condition (Q7189713), gene (Q7187), disease (Q12136)”: item must contain property “instance of (P31), subclass of (P279)” with classes “physiological condition (Q7189713), gene (Q7187), disease (Q12136)” or their subclasses (defined using subclass of (P279)). (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/P492#Type Q7189713, Q7187, Q12136, 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/P492#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): 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/P492#Scope, SPARQL
Modified single value constraint
Lists items having more than one value, except if one of the statements has a mapping relation type (P4390) qualifier, see discusion below. Please don't switch on the normal single value0 constraint, use this instead. (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P492#Modified single value constraint
Lists items having more than one value, except if one of the statements has a mapping relation type (P4390) qualifier, see discusion below. Please don't switch on the normal single value0 constraint, use this instead. (Help)
Violations query:
SELECT DISTINCT ?item ?itemLabel ?count ?sample1 ?sample2 ?exception WHERE { { SELECT ?item (COUNT(?value) AS ?count) (MIN(?value) AS ?sample1) (MAX(?value) AS ?sample2) { ?item wdt:P492 ?value . MINUS { ?item p:P492 ?stmt. ?stmt pq:P4390 [] } } GROUP BY ?item HAVING ( ?count > 1 ) } . SERVICE wikibase:label { bd:serviceParam wikibase:language "en" } . } ORDER BY DESC(?count)
List of this constraint violations: Database reports/Complex constraint violations/P492#Modified single value constraint
Pattern ^PS(\d{6})$ will be automatically replaced to \1. Testing: TODO list |
|
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
OMIM has mixed entries
[edit]Clearly the distinct values constraint does not reflect reality. OMIM has entries containing:
- gene + phenotype (example: 100650), count: 41
- "predominantly phenotypes" as they call it, which is also gene + phenotype (example: 108700), count: 1750
- gene (example: 108780), count: 16140
- phenotype (example: 112240), count: 7171
So I'm removing the constraint. --SCIdude (talk) 15:24, 19 August 2019 (UTC)
modified single value constraint
[edit]The complex constraint I just added lists all violating items where none of the statements has a mapping relation qualifier. I'm proposing to remove the current single value constraint because it gives false positives, see https://phabricator.wikimedia.org/T242079. Please give your opinion. --SCIdude (talk) 14:44, 10 January 2020 (UTC)
- Wouldn't adding the separator (P4155) = mapping relation type (P4390) do the same?
- Not sure if using mapping relation type (P4390) here is a good idea, but that's another question. --- Jura 16:42, 21 June 2021 (UTC)