Change Details

The **quantity** property, when used as a qualifier for 'depicts', indicates the quantity of the thing-that-is-depicted Example from wikidata https://www.wikidata.org/wiki/Q1195035 (see depicts > human > quantity, etc) I can think of 2 different options for implementing searching on quantity Option 1 We can store the qualifier in the normal way like this `P180=Q5[P1114=2]` (see T193407), in which case we would only be able to find exact matches. For example a user could search for images depicting exactly 1 cat, but could not search for images with >1 cats Option 2 Use the Wikidata Query Service (WDQS) to run a SPARQL query (which allows operators like `>` and `<`), and then use the ids as a filter for an elasticsearch query - basically we'd ask WDQS for all pictures depicting 'cat' with quantity qualifier >1, then search elasticsearch for anything else we wanted to search for but only among the (max 1000) IDs we got from WDQS. Option 2 seems (to me) to be more practically useful. The deepcat feature uses WDQS with elasticsearch, so we could base our approach on the deepcat code (see https://gerrit.wikimedia.org/r/#/c/405059/)

The **quantity** property, when used as a qualifier for 'depicts', indicates the quantity of the thing-that-is-depicted Example from wikidata https://www.wikidata.org/wiki/Q1195035 (see depicts > human > quantity, etc) I can think of 2 different options for implementing searching on quantity Option 1 We can store the qualifier in the normal way like this `P180=Q5[P1114=2]` (see T193407), in which case we would only be able to find exact matches. For example a user could search for images depicting exactly 1 cat, but could not search for images with >1 cats Option 2 Use the Wikidata Query Service (WDQS) to run a SPARQL query (which allows operators like `>` and `<`), and then use the ids as a filter for an elasticsearch query - basically we'd ask WDQS for all pictures depicting 'cat' with quantity qualifier >1, then search elasticsearch for anything else we wanted to search for but only among the (max 1000) IDs we got from WDQS. Option 2 seems (to me) to be more practically useful. The deepcat feature uses WDQS with elasticsearch, so we could base our approach on the deepcat code (see https://gerrit.wikimedia.org/r/#/c/405059/) Note that there are currently **1219** depicts statements in wikidata with a 'quantity' qualifier

The **quantity** property, when used as a qualifier for 'depicts', indicates the quantity of the thing-that-is-depicted Example from wikidata https://www.wikidata.org/wiki/Q1195035 (see depicts > human > quantity, etc) I can think of 2 different options for implementing searching on quantity Option 1 We can store the qualifier in the normal way like this `P180=Q5[P1114=2]` (see T193407), in which case we would only be able to find exact matches. For example a user could search for images depicting exactly 1 cat, but could not search for images with >1 cats Option 2 Use the Wikidata Query Service (WDQS) to run a SPARQL query (which allows operators like `>` and `<`), and then use the ids as a filter for an elasticsearch query - basically we'd ask WDQS for all pictures depicting 'cat' with quantity qualifier >1, then search elasticsearch for anything else we wanted to search for but only among the (max 1000) IDs we got from WDQS. Option 2 seems (to me) to be more practically useful. The deepcat feature uses WDQS with elasticsearch, so we could base our approach on the deepcat code (see https://gerrit.wikimedia.org/r/#/c/405059/) Note that there are currently **1219** depicts statements in wikidata with a 'quantity' qualifier