search

OpenConceptLab / ocl_issues

Issues for all OCL repos. NOTE: Install ZenHub Browser Extension and request access to the OCL Roadmap board to view all issues and to contribute
4 stars 1 forks source link

User should have option not to auto-import Mappings to retired concepts #1396

Open gracepotma opened 1 year ago

gracepotma commented 1 year ago

(@paynejd and @bmamlin do you agree with this?)

I propose: When a user goes through the "Add to Collection" workflow and wants all mapped concepts imported, e.g. as we often do with CIEL concepts, we should have the option (or perhaps this should be the default behavior) to NOT have mappings to retired concepts included.

Right now there's a mismatch: the Mappings to retired concepts are auto-imported, but the retired concepts themselves are not auto-imported. I think this created for us the situation in https://github.com/OpenConceptLab/ocl_issues/issues/1395

jamlung-ri commented 1 year ago

@paynejd @paulsonder This seems like another level of control that the user should have when using $cascade. Users should get to choose whether or not retired target concepts are cascaded and/or returned. Let's include this as part of the work in #1378.

@paynejd I forget if we talked about this in this morning's Cascade deep dive, but is this something that the user should be able to control using the $cascade feature?