Change Details

== Wikidata Analytics Request == > This task was generated using the [Wikidata Analytics](https://phabricator.wikimedia.org/project/profile/5408) request form. Please use the task template linked on our project page to create issues for the team. Thank you! === Purpose === > Please provide as much context as possible as well as what the produced insights or services will be used for. {T370416} * Identify SPARQL queries that should ideally go to [[ https://www.wikidata.org/wiki/Wikidata:Data_access#Search | Elasticsearch ]] instead of WDQS. === Specific Results === > Please detail the specific results that the task should deliver. * Identify WDQS SPARQL queries that only retrieve Items based on a simple statement (e.g. Which Item has IMDb ID "tt0133093"?) === Desired Outputs === > Please list the desired outputs of this task. [] Initial simple identification algorithm that can be used in T370854 (and iteratively improved on later). === Notes === * Using Elasticsearch for Wikidata this should currently work for all properties with "external identifier", "string", "item", "property", "lexeme", "form" and "sense" datatypes, except published in (`P1433`) and cites (`P2860`), which are currently omitted for performance reasons. Also, it is impossible to make use of Class hierarchy. === Open Questions === * Should we only focus on the SPARQL equivalents of `haswbstatement`, or should we also go for `inlabel`, `wbstatementquantity`, `hasdescription`, or `haslabel`? === Deadline === > Please make the time sensitivity of this task clear with a date that it should be completed by. If there is no specific date, then the task will be triaged based on its priority. DD.MM.YYYY --- **Information below this point is filled out by the task assignee.** == Assignee Planning == === Sub Tasks === > A full breakdown of the steps to complete this task. [ ] subtask === Estimation === Estimate: Actual: === Data === > The tables that will be referenced in this task. - link_to_table === Notes === > Things that came up during the completion of this task, questions to be answered and follow up tasks. - Note

== Wikidata Analytics Request == > This task was generated using the [Wikidata Analytics](https://phabricator.wikimedia.org/project/profile/5408) request form. Please use the task template linked on our project page to create issues for the team. Thank you! === Purpose === > Please provide as much context as possible as well as what the produced insights or services will be used for. {T370416} * Identify SPARQL queries that should ideally go to [[ https://www.wikidata.org/wiki/Wikidata:Data_access#Search | Elasticsearch ]] instead of WDQS. === Specific Results === > Please detail the specific results that the task should deliver. * Identify WDQS SPARQL queries that only retrieve Items based on a simple statement (e.g. Which Item has IMDb ID "tt0133093"?) === Desired Outputs === > Please list the desired outputs of this task. [] Initial simple identification algorithm that can be used in T370854 (and iteratively improved on later). === Notes === * Using Elasticsearch for Wikidata this should currently work for all properties with "external identifier", "string", "item", "property", "lexeme", "form" and "sense" datatypes, except published in (`P1433`) and cites (`P2860`), which are currently omitted for performance reasons. Also, it is impossible to make use of Class hierarchy. === Open Questions === * Should we only focus on the SPARQL equivalents of `haswbstatement`, or should we also go for `inlabel`, `wbstatementquantity`, `hasdescription`, or `haslabel`? === Deadline === > Please make the time sensitivity of this task clear with a date that it should be completed by. If there is no specific date, then the task will be triaged based on its priority. DD.MM.YYYY --- **Information below this point is filled out by the task assignee.** == Assignee Planning == === Sub Tasks === > A full breakdown of the steps to complete this task. [] Check scope of task - Is this for just items or also other entities like properties and lexemes as T370848 was? [] Explore idea of deriving simple queries via the number of subject node values from `discovery.processed_external_sparql_query` [] Check query results with WMF and stakeholders [] Share baseline identification method === Estimation === Estimate: 1 day Actual: === Data === > The tables that will be referenced in this task. - `discovery.processed_external_sparql_query` - `triples.subjectNode.nodeValue` will be used to derive the number of triples and their characteristics === Notes === > Things that came up during the completion of this task, questions to be answered and follow up tasks. - Note

== Wikidata Analytics Request == > This task was generated using the [Wikidata Analytics](https://phabricator.wikimedia.org/project/profile/5408) request form. Please use the task template linked on our project page to create issues for the team. Thank you! === Purpose === > Please provide as much context as possible as well as what the produced insights or services will be used for. {T370416} * Identify SPARQL queries that should ideally go to [[ https://www.wikidata.org/wiki/Wikidata:Data_access#Search | Elasticsearch ]] instead of WDQS. === Specific Results === > Please detail the specific results that the task should deliver. * Identify WDQS SPARQL queries that only retrieve Items based on a simple statement (e.g. Which Item has IMDb ID "tt0133093"?) === Desired Outputs === > Please list the desired outputs of this task. [] Initial simple identification algorithm that can be used in T370854 (and iteratively improved on later). === Notes === * Using Elasticsearch for Wikidata this should currently work for all properties with "external identifier", "string", "item", "property", "lexeme", "form" and "sense" datatypes, except published in (`P1433`) and cites (`P2860`), which are currently omitted for performance reasons. Also, it is impossible to make use of Class hierarchy. === Open Questions === * Should we only focus on the SPARQL equivalents of `haswbstatement`, or should we also go for `inlabel`, `wbstatementquantity`, `hasdescription`, or `haslabel`? === Deadline === > Please make the time sensitivity of this task clear with a date that it should be completed by. If there is no specific date, then the task will be triaged based on its priority. DD.MM.YYYY --- **Information below this point is filled out by the task assignee.** == Assignee Planning == === Sub Tasks === > A full breakdown of the steps to complete this task. [ ] subtask] Check scope of task - Is this for just items or also other entities like properties and lexemes as T370848 was? [] Explore idea of deriving simple queries via the number of subject node values from `discovery.processed_external_sparql_query` [] Check query results with WMF and stakeholders [] Share baseline identification method === Estimation === Estimate: 1 day Actual: === Data === > The tables that will be referenced in this task. - link_to_table`discovery.processed_external_sparql_query` - `triples.subjectNode.nodeValue` will be used to derive the number of triples and their characteristics === Notes === > Things that came up during the completion of this task, questions to be answered and follow up tasks. - Note