Displayed value should be that with highest verification number

[edwardchalstrey1]

... or the most commonly entered value, rather than the most recent

[tomalrussell]

This is not at all obvious to me - why should the displayed value not be the most recently edited?

What implications does this have for editing flows, from a user perspective:

• What happens when I edit an already-verified value? Does that new value show in any way?
• How do I see if a non-verified or less-verified value has been set?
• If one value is verified, how can I assert that another value should be the correct one?
• If an edit is malicious (however mildly so) and verified, how would I correct or remove it?
• How is "most commonly entered" calculated?
• How can I understand what values have been entered, how commonly, and how often verified?

And then in implementation on the backend:

• currently, all edits are recorded in the edit history, and the current value for each attribute is stored in the buildings table
• currently, all verifications (per user, building, attribute) are stored in another table; verification count for the current is calculated in the application code
• what data model changes would be required?
• what API changes would be required?