OTUs can be created from taxon names, but that makes it possible for them to exist without a OTU name (via OTU edit screen).
If images are batch imported from morphbank, these OTUs cannot be associated to them (this explains part of bug ID:3074200). These OTUs are available for other functions (eg matrix, material), however.
Anonymous
What view are you looking at? What form are you looking at? (paste the non-base part of the URL). You don't have to have any name for an OTU. You should still be able to select the OTU by using (typing) the TaxonName in the dropdown or using an OTU id?
Suppose you create a taxon name via /taxon_name/new .
Then you want an OTU for that taxon name, so you go to /otu/new and pull the taxon name in the first field, but you're lazy so that's all you do.
MX does not complain the OTU does not have a "name".
However, some features won't work for an OTU like that. For example, if you try to import pictures from Morphbank that are attached to that taxon name via morphbank_image/MB_batch_load , MX will not find that OTU (it's searching in the 'otu_name' field, which is blank in this case).
It will instead try to locate the OTU that has a name that most closely matches the import (and in my case that was a different genus).
Still happening so I thought I'd better report.