Certain metadata concepts which originate from Snomed international end up with multiple (different) FQNs when Snomed is loaded.
An example of this is
Metadata -> Role (SOLOR)
Which in snomed is " Concept model attribute (attribute)"
Our LanguageCoordinateImpl has a mechanism to rank modules, which should help with this, but in practice, doesn't, because it requires all modules to be placed into the ranking list - and the ranking list only contains basic ones like SnomedCore. In practice, Snomed has a bunch of different modules, and enumerating them all prior to the SOLOR module isn't a good solution.
Perhaps a mechianism to allow modules to be ranked lower than others, rather than higher. That, or take into account the module hierarchy when listing higher priority modules, so all related child modules are included.
I think the default config should rank the SOLOR module the lowest, and metadata that only exists for the KOMET GUI should be on its own module, so that the KOMET gui can specify a module ranking that requests its metadata first...