BTW, I already have two (slightly related) questions I'd like to discuss with somebody from the core team in the context of editing of properties in the UI: 1. It would be useful to allow configuration of data types for certain properties, so that users can only enter date values into properties expected to contain a date, etc. At least in the first step, keeping this configuration outside UI should be absolutely sufficient. Anyway, am I right that the current data model of DataHub has no place for defining a type for particular properties (all of them are simply strings)? If so, is there a recommendation how to change it (where to put the type definitions)? 2. Certain properties may be expected to contain only values from a specific list of values (i.e. the data type for that property would be a reference to the particular list of values). Similarly to the previous point - would you have a suggestion where to put such lists of values? Again, configuration of those lists may stay outside of UI at least in the beginning, because it isn't supposed to change dynamically. I assume that the same DB table should be used for all such lists of values with rows containing combinations of the particular list of values and an allowed value (plus possibly a tenant reference in the future once multi-tenancy is supported as suggested by @rhythmic-zoo-52859). Any comments and suggestions are most welcome. :-)