feature request #3958
Handle CDMPreference table
It is implemented in model but not yet used and not filled with any data. Methods in Service layer are also missing.
Keep in UML milestone as we may need a data updater (e.g. #3658). Move otherwise.
Decisions for the syntax of the different fields:
/ (Database wide)
/editor (??) for purely TaxEditor related preferences (e.g. show ID in supplemental data view)
predicate: No required structure, but package like structure with dot separators makes sence
allows starts with search to return lists of values
Case insensitive (?)
each predicate might be defined by as a constant of an enum
object: up to the predicate to implement
Difficulties may occur when trying to match filters (subjects). An object that requires a preference (e.g. a TaxonName requires a list of available ranks) may match to multiple filters which map to different values (e.g. because the name is used in multiple classifications)
for details see: #3555, see also open issues there
related #5004, #3773, #5969