Importing project that uses unknown/missing catalogue uses random other catalogue

[hardfalcon]

It appears that if you import a project which uses a catalogue that the importing RDMO instance doesn't know, another random catalogue is used instead without even showing a warning. This bug was found by @jmfrenzel.

[jochenklar]

It should be the first catalog that is used, I guess we should add a warning in the import screen.

[jmfrenzel]

It should be the first catalog that is used, I guess we should add a warning in the import screen.

can confirm that it is the first catalog (first according to the catalog order in the instance).

More importantly that first catalog is selected even when this catalog has the not available flag set.

[jochenklar]

More importantly that first catalog is selected even when this catalog has the not available flag set.

Yeah, this is not optimal.

[hardfalcon]

Wouldn't it be better to outright reject the import if it uses an unknown catalog? My fear is that people assume some sort of "sane" behavior if the catalog used doesn't actually fit the questions answered, when IMO there is no "sane" behavior to handle this other than reject the import in the first place.

[jochenklar]

I beg to differ, catalogs can be chnged in RDMO and sometimes you want to import a project into an instance which does not have this catalog. I think we just need to make the behavior more visible.

[jochenklar]

Will be part of RDMO 2.2.0.