For example, We should not display "kilogram" when trying to add lengths. This is important because there're many items whose labels are the same as units'. There're several units call pound.
|Open||None||T56318 Quantity datatype (tracking)|
|Open||None||T68580 Better support for exact values in Quantity DataType|
|Resolved||daniel||T140997 When guessing quantity precision from digits, use the +/-0.5 rule rather than the +/-1 rule|
|Open||None||T133042 Quantity datatype precision (tracking)|
|Resolved||Lydia_Pintscher||T115269 [Story] When a Quantity is entered with no uncertainty/bounds given, do not guess uncertainty/bounds until needed.|
|Resolved||thiemowmde||T115270 Allow QuantityValue objects to have empty/no bounds set|
|Resolved||daniel||T105623 [Task] Investigate quantification of quantity precision (+/- 1 or +/- 0.5)|
|Open||None||T77977 [Epic] Unit support|
|Declined||Lydia_Pintscher||T110998 Hide non-useful items from unit selection|
|Resolved||Lydia_Pintscher||T142086 [Task] announce quantity changes|
|Resolved||Ladsgroup||T142087 [Task] prepare bot for quantity change fixes|
|Open||None||T112247 [RFC] Create a "number" datatype for exact values|
|Resolved||Ladsgroup||T154168 Quantity changes broke ORES|
We want to allow any item on Wikidata to be selected as a unit. This is just the same way as you can enter any item as a value in a statement without restrictions. What we do need is better ranking for units that are used a lot. We have a separate ticket for that.