Morpho

Morpho allows enumerated value codes/definitions to be "imported from another table", although "imported" is somewhat of a misnomer because they are simply documented by reference (i.e., via entityCodeList in EML), and this only works within a single DP. This feature does not directly address the common use case of wanting to reuse identical (or similar) enumerated domains for different attributes, especially across DPs.

One approach might be to allow code/definition sets to be imported (copied) from any documented enumeratedDomain field that contains codeDefinitions, in any locally saved DP. This would require a GUI element to allow the user to select the desired DP, data table, and attribute to import from.

A second approach might be to provide a mechanism for users to save any existing code/definition sets to a local "registry" (in their morpho cache), and then import only from that code/definition registry. This would require a GUI element for saving (and probably naming) the codes/definitions from within the column documentation editor for enumerated domain attributes, and some modification of what the existing import button does.

After import, the codes/definitions should be editable for tweaking.

The general motivations for this bug are similar to those expressed for other forms of templating, namely in bug 1532 (for data packages) and bug 2851 (for attributes).