query-928022ef6f964ed6a9570fb1bc79f505
Frequency table of uses of properties in direct claims, qualifiers and references and its values in a given language%4 as the predicate. Both values were set in named subquery schema:description) was used as the language code and Malayalam (language code for ml. ?countInQualifiersResults of the query sorted by %4 as the predicate. Both values were set in named subquery schema:description) was used as the language code and Korean (language code for ko. ?countInReferencesResults of the query sorted by Someone asked me if I could add a condition to the query so that it shows those properties that have description in English, but don't have a description in a given language. when a property has a description in that language or not. Thus, it would be possible to sort the table by any column and at the same time see if the property has description in that language. No or YesI thought that the query would be more useful if it included all the properties in the results and show a column that show , etc.) Quechua for "qu", Korean for "ko", Spanish for "es" statement. In that line, change the string with the language code of the language you are interested in (e.g. FILTER. The line that needs to be edited is the one that have the %4For setting the language that this query will search for missing values (e.g. missing labels, or missing descriptions), you need to edit the named subquery There are two main modifications that can be done to the query for making the results more useful . You might want to do this if you are only interested in knowing whether a property has a description in a given language or not, so having the descriptions in the result of the query is not that useful.?valueDon't show the column .%4 statement in the named subquery OPTIONAL) in a given language. To do this, just change the predicate that is used in the (P2559)Wikidata usage instructions or even properties (e.g. skos:altLabel), aliases (i.e. schema:description, descriptions (i.e. rdfs:labelNote that the query could be reused for listing properties that might be missing a label (i.e. . T323423NOTE: This query shows inaccurate information for some properties due to a bug. I already reported it in Frequency table of uses of properties in direct claims, qualifiers and references and its values in a given languageThe following query has been prepared by User:Rdrg109. Following query will help to find the missing lables and descriptions of ml language. %4 as the predicate. Both values were set in named subquery schema:description) was used as the language code and Malayalam (language code for ml. ?countInQualifiersResults of the query sorted by %4 as the predicate. Both values were set in named subquery schema:description) was used as the language code and Korean (language code for ko. ?countInReferencesResults of the query sorted by Someone asked me if I could add a condition to the query so that it shows those properties that have description in English, but don't have a description in a given language. when a property has a description in that language or not. Thus, it would be possible to sort the table by any column and at the same time see if the property has description in that language. No or YesI thought that the query would be more useful if it included all the properties in the results and show a column that show , etc.) Quechua for "qu", Korean for "ko", Spanish for "es" statement. In that line, change the string with the language code of the language you are interested in (e.g. FILTER. The line that needs to be edited is the one that have the %4For setting the language that this query will search for missing values (e.g. missing labels, or missing descriptions), you need to edit the named subquery There are two main modifications that can be done to the query for making the results more useful . You might want to do this if you are only interested in knowing whether a property has a description in a given language or not, so having the descriptions in the result of the query is not that useful.?valueDon't show the column .%4 statement in the named subquery OPTIONAL) in a given language. To do this, just change the predicate that is used in the (P2559)Wikidata usage instructions or even properties (e.g. skos:altLabel), aliases (i.e. schema:description, descriptions (i.e. rdfs:labelNote that the query could be reused for listing properties that might be missing a label (i.e. . T323423NOTE: This query shows inaccurate information for some properties due to a bug. I already reported it in
Use at
- https://query.wikidata.org/sparql
PREFIX wikibase: <http://wikiba.se/ontology#>
PREFIX schema: <http://schema.org/>
PREFIX bd: <http://www.bigdata.com/rdf#>
SELECT
?property
?propertyLabel
?value
?valueExists
?countInDirectClaims
?countInQualifiers
?countInReferences
{
{
SELECT * {
{
SELECT * {
INCLUDE %a.
OPTIONAL{INCLUDE %1}
OPTIONAL{INCLUDE %2}
OPTIONAL{INCLUDE %3}
OPTIONAL {
?property schema:description ?value
FILTER(LANG(?value) = "ml").
}
BIND(IF(BOUND(?value), "Yes", "No") AS ?valueExists).
}
}
BIND(IF(BOUND(?countInDirectClaims), ?countInDirectClaims, 0) AS ?countInDirectClaims)
BIND(IF(BOUND(?countInQualifiers), ?countInQualifiers, 0) AS ?countInQualifiers)
BIND(IF(BOUND(?countInReferences), ?countInReferences, 0) AS ?countInReferences)
}
}
SERVICE wikibase:label {bd:serviceParam wikibase:language "en"}.
}
Query found at
- https://www.wikidata.org/wiki/User:Akbarali/Most_used_properties_in_direct_claims,_qualifiers_and_references
- https://www.wikidata.org/wiki/User:Rdrg109/1/25