| matthiasmullie | |
| Feb 11 2020, 1:16 PM |
| F31552245: set-units.png | |
| Feb 14 2020, 8:02 PM |
T239474 will add support for units to the quantity input type.
The units autocomplete will make it possible to search for items to act as unit, but not all of them make as much sense.
E.g. when looking up "cm", you're way more likely to want to use "centimeter" as a unit, than "Cameroon".
The autocomplete should boost some items that are good candidates for units.
See T312962 for the Wikibase equivalent of this.
It might be possible to use the unit conversions (UnitStorage interface) for this – any item with a unit conversion from (centimeter) or to it (meter) is probably a useful unit.
This looks like a decent list of unit entities: https://query.wikidata.org/#prefix%20wdt%3A%20%3Chttp%3A%2F%2Fwww.wikidata.org%2Fprop%2Fdirect%2F%3E%0ASELECT%20%3Fitem%20%3FitemLabel%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP5061%20%3Fdummy0%20.%0A%20%20SERVICE%20wikibase%3Alabel%20%7Bbd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20%7D%0A%7D
I think the unit conversions are also ultimately derived from the Wikidata statements (rOMWCa15236c286d8: Add more units for conversion indicates a maintenance script), but I don’t know the details. I just think it would be nice to avoid an extra config if we already have the unit conversions (but up to you, of course).
F31552245 is a nice mock up.
When adding a unit, we want to have suggestions that make sense. That makes me think of https://github.com/Wikidata-lib/PropertySuggester . Isn't that extension suitable to also suggest what units to add? That would also solve the Cameroon problem on Wikidata.
This task was mentioned in the Bug Triage Hour at the Wikidata Data Quality Days 2022.