I was selecting concepts to be included in concept set under Atlas.
Let’s say I have a concept called “ABC” which has 2 children “DEF” and “GHI”. I add the concept “ABC” and select “include descendants”. So in to total I see now 3 included concepts in my concept set.
But let’s say that without realizing the “GHI” is a child of “ABC”, I add the concept “GHI” again to the concept set separately.
When I executed the generated SQL for codeset, I see that there are duplicate concepts in codesets based on what I defined.
Q1) Doesn’t Atlas ignore the duplicates?
Q2) Only problem with having duplicates will be that the query will take long time to run. Is there any other problem to having duplicate concept ids?
Q3) Let’s say I have two concept sets C1 and C2. Is there anyway to check the overlapping concepts between these two concepts in Atlas? I know we can do in SQL but is it possible in Atlas?
Q4) I guess the “cart” button is of no use for children concepts. Whether we enable or disable it, concept is going to be part of the concept set. Am I right? Because under the included concepts tab, irrespective whether an item is added into cart or not, I see them in the final list of concepts under codesets. So I guess it’s expected. But wondering whether it’s possible to ignore certain children concepts?
Q5) I see that the cart is enabled or disabled by default (automatically) for few concepts. May I know on what basis it is done?