On the Search tab for concepts, you can choose multiple rows and then 'Add To Concept Set' using Descendants/Exclude/Mapped. This is good and prevents a lot of clicking when you want to add many concepts as exclusions or descendants:
However, there are other concept set lists where a user may want to choose a set of concepts and add them to the concept set as exclusions (for example, on Included Concepts):
The use-case is: I have made my concept set expression with including descendants, and when I am looking at the included concepts, there are some I want to exclude. So, we should be able to multi-select on the included concept tab, and it also makes sense on the 'included source codes' because there may be a reason to add source codes to a concept set. (Who am I to judge what users want to do :) )
Now, it is redundant to be inside the Included Concepts tab and then add the concept to the concept set, so maybe it could be framed that the only action you can take in the included concepts is to set the concept as an exclusion. I'm not sure this is the correct approach, but at the very least we should be able to select concepts from the included concepts view and add those back into the concept set expression (as an include/exclude/descendant options set.
On the Search tab for concepts, you can choose multiple rows and then 'Add To Concept Set' using Descendants/Exclude/Mapped. This is good and prevents a lot of clicking when you want to add many concepts as exclusions or descendants:
However, there are other concept set lists where a user may want to choose a set of concepts and add them to the concept set as exclusions (for example, on Included Concepts):
The use-case is: I have made my concept set expression with including descendants, and when I am looking at the included concepts, there are some I want to exclude. So, we should be able to multi-select on the included concept tab, and it also makes sense on the 'included source codes' because there may be a reason to add source codes to a concept set. (Who am I to judge what users want to do :) )
Now, it is redundant to be inside the Included Concepts tab and then add the concept to the concept set, so maybe it could be framed that the only action you can take in the included concepts is to set the concept as an exclusion. I'm not sure this is the correct approach, but at the very least we should be able to select concepts from the included concepts view and add those back into the concept set expression (as an include/exclude/descendant options set.