You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many properties could benefit from automatic suggestions based on current values.
Example:
all boolean values (or closed to boolean): whether the awaited value is yes, no, maybe, 1, 0, -, the feature would suggest the 2, 3 or 4 always given values
properties with few values; eg. when a barcode is used for different products, the multiple property could be yes, 2, 3, >3 (other values would not be useful)
Rationale
Avoid creating complex types of values: data types, closed lists, taxonomies, etc.
Follow one of the core Open Food Facts principle: let the users enter any data for their needs, and, eventually, standardize later on; this way, the standards or lists of values are led by the usages
Design
It should show all the values before typing when the number of current values is less than 4-5
Values should be sorted by most given values
After typing the two first chars, it should show the X possible values containing these two chars
It should not suggest anything when the number of possible values is more than 100 (?)
The value entered should remain free. This feature does not constrain anything.
Implementation
It should first ask the API for the /key statistics, to know how many values are existing.
Many properties could benefit from automatic suggestions based on current values.
Example:
yes
,no
,maybe
,1
,0
,-
, the feature would suggest the 2, 3 or 4 always given valuesmultiple
property could beyes
,2
,3
,>3
(other values would not be useful)Rationale
Design
Implementation
The text was updated successfully, but these errors were encountered: