bug #8494
Updated by Katja Luther over 4 years ago
to be done see also #8489 also #8385#note-51, #8385#note-52 ~~Why Why does the nomenclatural code not provide a default? Is this wanted? Does ABCD not need a nomenclatural code? I remember ABCD distinguishes botanical, zoological, ... by itself so maybe this parameter is not needed and only comes from the super class? If so, we should remove it. If not, and if a null value is not explicitly handled without using a default instead we should define the usage of default here, I guess. But I don't know the import so well so maybe there is a reason for the current implementation.~~ implementation. => mostly the nomenclatural code comes from the biocase response, but sometimes it is missing and then the import needs the nomenclatural code for namecreation now the preferred Nomenclatural code of the instance is used as default. 8385#note-55 ~~In general we should distinguish clearly between the list of available providers (may it be ABCD providers or DNA providers) and the default or predefined single values for the import configuration which provider to use for ABCD and for DNA. This is currently still mixed up. (But might be a new ticket)~~ #8385#note-56: ~~This is fixed but still "Restore default" does not completely remove the preference (and even does not clear the existing list, what I would expect)~~