[WEBCLIENT-289] Inconsistent representation of modifier concepts in web client Created: 21/Oct/16  Updated: 16/Mar/20

Status: New
Project: i2b2 Web Client
Component/s: None
Affects Version/s: None
Fix Version/s: TBD

Type: Bug Priority: Major
Reporter: Marcos Davila Assignee: Nich
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Affects View/s:
Navigate Terms
i2b2 Feature/s:
Modifiers
Participant/s:

 Description   
This ticket reports two separate but related bugs which leads to a visual contradiction given certain parameter combinations in the metadata.

Bug # 1:

The first bug involves the improper visual representation of a modifier in an ontology when the C_HLEVEL is incorrect. So far, my understanding of the interaction between M_APPLIED_PATH and C_HLEVEL is that M_APPLIED_PATH specifies the root from which the modifier should hang, and in respect to the modifier treats this path as a new root with "C_HLEVEL = 0". This requires that the modifier have a C_HLEVEL value of 1. If the C_HLEVEL value is greater than 1, the modifier shows up as a regular leaf node. What I expect to happen is that the modifier should not be visible at all, since there is a gap between the "modifier root" specified by M_APPLIED_PATH and the ontological entry specified by C_FULLNAME.

Bug # 2:

This bug builds upon the first bug and occurs when we wish to create modifier folders or containers and to populate them with modifier leaf nodes. The C_FULLNAME for these modifier leaf nodes must include the C_FULLNAME of the modifier parent folder and the C_HLEVEL must be one greater than the modifier parent folder, similar to how regular folders/containers and leaf nodes are nested. However, the M_APPLIED_PATH must be the value of the C_PATH of the parent folder in order for the modifier to nest, essentially "skipping" over a level we have created. If M_APPLIED_PATH is any other value, including the C_FULLNAME of the parent folder, the modifier will not appear within the modifier folder. I expected that the rules for M_APPLIED_PATH would extend to modifier folders as well as regular folders, but it seems that there are no support for modifier concepts for this field.

 Comments   
Comment by Marcos Davila [ 15/Feb/17 ]
With the help of the consortium I've discovered that the bug triggers only when the parent folder of the modifier in C_FULLNAME is the same as the location provided in M_APPLIED_PATH. In other words, if I had a C_FULLNAME value of '\i2b2\Diagnoses\ModifierName\' and an M_APPLIED_PATH of '\i2b2\Diagnoses\%', a leaf node of the modifier generates on the same level as the modifier folder. The simple solution is to change the C_FULLNAME so that it is not the same as M_APPLIED_PATH. I feel like this shouldn't occur even if one chose to host the modifiers and the concepts on the same hierarchy.
Generated at Sun Jul 20 01:09:58 UTC 2025 using Jira 8.20.11#820011-sha1:0629dd8d260e3954ece49053e565d01dabe11609.