Edit

I don't know if we really need "db preference" as explicit value. It makes it more difficult to understand and there is almost no added value (compared to "default". So we only need "default" and the list of explicit values. If "default" is chosen then the preference is deleted from the local preferences.

I would show the value of the db preference in the drop down, but with ("global") or ("db") behind

Katja Luther wrote:

I would show the value of the db preference in the drop down, but with ("global") or ("db") behind

OK, if this is not an explicit entry but if it is only added to the anyway existing entry for this value. Maybe "recommended" is another possible label. A bit long but standard for many such cases.

For nomencl.Code. implementation is still missing or incorrect. Also we may discuss if in DB prefs we should allow "Use default" which is currently not available but by default nom.code is set to ICNAFP

Andreas Müller wrote:

Choosing "default" for local preference "nomenclatural status" has no effect. It uses the explicitly chosen values from the list above. Anyway, if "default" is chosen the list should select only those status which are available according to the default/dbPrefs. Also the list should be disabled I guess.

For ranks it is the opposite.

For the above issues see also #8323#note-4

with the new implementation of distribution status with different subjects if allowOverride=false in DB prefs this does not disable the local pref button for this pref. I did not check if the local pref is used in this case.

We need to guarantee that even for disallowOverride the local pref is always disabled. This must be the case even if the DB pref subject is defined more generic. Only if a specific subject allows override while a more generic disallows especially for this subject local prefs should be available.
Anyway, the area specific distribution status still needs to be implemented for local prefs. Currently it only exists for DB prefs.

See also #7920#note-19