Bulk upload/save of a CRTDL #472
Description
Description
The bulk search feature will be introduced as described in this issue (#460, #461). This, however, introduces several challenges for the UI that need to be addressed.
Problem
Currently, when a large CRTDL (100+ criteria) is uploaded or loaded from saved queries, the UI sends all criteria hashes to the backend and retrieves the corresponding criteria-profile data via the endpoint: api/v5/terminology/criteria-profile-data?ids=.
Since many criteria may belong to the same context, a large number of duplicate UI profiles are loaded, reflecting the same underlying data. This leads to unnecessary redundancy and potential performance issues.
ToDo
1.Define a process for handling large CRTDL uploads efficiently.
2. Refactor the UI code to implement this process and avoid duplicate profile loading.