Currently slots with enum ranges have the autocomplete cell type applied. NMDC usability testing identified that it was potentially confusing that once an item is chosen and the user opens options dropdown again, it appears that the selection option is the only available option. This is an artifact of the autocomplete cell type's behavior of filtering the option based on what has been typed in.
Another option for slots with enum ranges is the dropdown field type. That cell type will always show all of the options. Typing in the input does not filter the available options but does highlight the matching ones. Folks on the 16 June 2022 NMDC Infrastructure Sync call seemed to agree this was a good trade-off.
I'd propose changing DataHarmonizer to allow opting into the use of the dropdown cell type (retaining the autocomplete cell type as the default) and doing the actual opt-in in this repo and the nmdc-server repo.
Currently slots with enum ranges have the autocomplete cell type applied. NMDC usability testing identified that it was potentially confusing that once an item is chosen and the user opens options dropdown again, it appears that the selection option is the only available option. This is an artifact of the autocomplete cell type's behavior of filtering the option based on what has been typed in.
Another option for slots with enum ranges is the dropdown field type. That cell type will always show all of the options. Typing in the input does not filter the available options but does highlight the matching ones. Folks on the 16 June 2022 NMDC Infrastructure Sync call seemed to agree this was a good trade-off.
I'd propose changing DataHarmonizer to allow opting into the use of the dropdown cell type (retaining the autocomplete cell type as the default) and doing the actual opt-in in this repo and the nmdc-server repo.