This has been suggested and discussed within CUBI. Initially, we have technically allowed multiple protocol reference values per process as ISA-Tab allows it. However, I don't believe we have ever seen a study in our systems where this would be a case.
The suggestion is: don't allow editing protocol ref values, always autofill new rows to the default value and thus force each cell in the column to a single protocol.
Auto-selecting the default filled value and preventing editing is already the default. Or at least it should be, see #1875.
If there is an agreement upon disabling this functionality for good, we can proceed as follows:
Disable updating column configuration for protocol columns in the UI
Disable and remove the cell editor for protocol columns
Update sheet configuration saving accordingly
Make sure legacy configs still work!
TBD: How do we handle if an ISA-Tab containing multiple protocol ref values per column is imported into SODAR? (This may be a very theoretical situation, but still)
Prohibit importing it altogether?
OR, render it as is but prohibit editing the column and autofill the column for new rows with one value (which?)
Since this issue involves removing code from the Vue app rather than adding it, implementing this before #994 should be a no-brainer.
This has been suggested and discussed within CUBI. Initially, we have technically allowed multiple protocol reference values per process as ISA-Tab allows it. However, I don't believe we have ever seen a study in our systems where this would be a case.
The suggestion is: don't allow editing protocol ref values, always autofill new rows to the default value and thus force each cell in the column to a single protocol.
Auto-selecting the default filled value and preventing editing is already the default. Or at least it should be, see #1875.
If there is an agreement upon disabling this functionality for good, we can proceed as follows:
TBD: How do we handle if an ISA-Tab containing multiple protocol ref values per column is imported into SODAR? (This may be a very theoretical situation, but still)
Since this issue involves removing code from the Vue app rather than adding it, implementing this before #994 should be a no-brainer.