Multi-value widget for properties

[kirillt]

We now incorporate user-defined metadata known as properties, which are essentially key-value pairs. For instance, a book resource could have a property like "title": "Moby Dick". However, property values might differ when sourced from various devices, leading to potential conflicts. In such cases, users must have the option to manually select the correct value to resolve these conflicts. Internally, we represent a property by a key coupled with a list of values. So it may be simply "title": ["Moby Dick"] in conflict-free scenarios, or "title": ["Moby Dick", "Moby-Dick; or, The Whale"] when an alternative value exists.

---

A view for representing such fields would be handy:

• In normal case, we have 1 value, so the view just displays it
• When there are N > 1 values:
  • random value from N is selected and displayed
  • conflict label is displayed in the corner of the view
• User can tap on the conflict label and see the other values as versions list
• User can select the preferred value from the versions list

When the user selects a value from versions list, all elements from the corresponding Set must be erased except the selected one.

[kirillt]

In an alternative design, acknowledging that users may accept multiple values for a property, we could accommodate this diversity. For example, a user might appreciate having property values in various languages, accessing them as needed. This approach would enable users to choose a preferred value of a property while retaining additional values.

In this design, we treat other values as alternatives, and not as conflicts. And we must preserve all values for same property.