We have a limited set of supported datatypes so can not query for everything. We want to expand the range of datatypes we support.
This ticket is for tracking support for additional datatypes.
Currently not supported:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T291422 support for additional datatypes in the Query Builder | |||
| Resolved | Arian_Bozorg | T328528 Add new datatypes to Query Builder | |||
| Resolved | noarave | T329204 Add lexeme datatype support to Query Builder | |||
| Resolved | noarave | T329205 Add form datatype support to Query Builder | |||
| Resolved | noarave | T329206 Add sense datatype support to Query Builder | |||
| Resolved | HasanAkgun_WMDE | T329207 Add property datatype support to Query Builder | |||
| Resolved | hoo | T329824 Add URL datatype support to query builder |
Please can we have one as 'does or does not have page on Wikimedia project'? This will allow people to very easily create redlists for wikiprojects and it would also be very useful when working with partner organisations.
Here's a list of which of the existing WiKit components could be used to input values for properties with unsupported data types. Happy to move it to the task description of this or the subsequent tickets to be created:
| Data type | WiKit component | Feasibility/ Observations |
| Image | Lookup component with thumbnails | ❌ WiKit does not provide a Thumbnail component, so image selection (e.g. in the Value field) wouldn't be feasible by default. As discussed, the new feature here might be related rather to only finding items that include images, instead of providing a specific one as a value |
| Geoshape | Lookup | ✅ |
| Tabular data | Lookup | ✅ |
| URL | Input component with type=URL? | ❌ Missing in WiKit |
| External ID | TextInput | ✅ |
| Property | Lookup | ✅ |
| Coordinate | InputWithExtender, IconOnly button, Checkbox | ❌ Rather than reusing, this would require combining existing components to create a brand-new pattern |
| Monolingual text | InputWithExtender, IconOnly button, TextInput | ❌ Rather than reusing, this would require combining existing components to create a brand-new pattern |
| Musical notation | TextArea or TextInput | ❓ Input looks simple, but if the logic to translate the input into an image should be part of the component, then this would require extra work/an extension of WiKit's capabilities |
| Mathematical expression | TextArea or TextInput | ❓ Input looks simple, but if the logic to translate the input into an image should be part of the component, then this would require extra work/an extension of WiKit's capabilities |
| Lexeme | Lookup | ✅ |
| Form | Lookup | ✅ |
| Sense | Lookup | ✅ |
Thanks so much Sarai, this is really really helpful.
I think the way to move forward would be to add only the data types that require values added via existing Wikit components i.e. "lookup".
This would include in prioritised order:
That's T289946. We cover it in a different ticket since it doesn't require support for additional datatypes but a separate thing specific to sitelinks.