In the course of creating and testing a hierarchy of custom modifiers for my project, I encountered this anomaly with my custom modifiers.
This was discovered in i2b2 v.1.8.2 using Firefox on macOS. Fyi, I am using SQL Server, and WildFly 37 is running on RHEL 9.
I'n not certain whether this is a webclient anomaly, or an anomaly in the ONT cell, but it manifests itself in the webclient.
Imagine using a modifier leaf inside an ontology branch.
For instance, the ontology branch has these paths...
- \Diagnoses\
- \Diagnoses\Musculoskeletal\
- \Diagnoses\Musculoskeletal\Arthritis\
- \Diagnoses\Musculoskeletal\Bone Fracture\
- \Diagnoses\Musculoskeletal\etc...
- \Diagnoses\Sensory\
- \Diagnoses\Sensory\Myopia\
- \Diagnoses\Sensory\Presbyopia\
- \Diagnoses\Sensory\etc...
... and I indicate that my modifier leaf has the following settings:
- M_APPLIED_PATH = '\Diagnoses\Sensory\%'
- M_EXCLUSION_CD = '\Diagnoses\Sensory\'
My goal is for my modifier to show up for all the Sensory diagnoses, but not for the "Sensory" parent folder. Therefore, the M_APPLIED_PATH includes the wildcard '%' at the end, but the M_EXCLUSION_CD does not show that.
This sounds straightforward, but in my experience, that exclusion code did not work. It is displaying at the "Sensory" parent, as well as at the "child" diagnoses.
Am I misunderstanding something, or is this truly a bug?
In the course of creating and testing a hierarchy of custom modifiers for my project, I encountered this anomaly with my custom modifiers.
This was discovered in i2b2 v.1.8.2 using Firefox on macOS. Fyi, I am using SQL Server, and WildFly 37 is running on RHEL 9.
I'n not certain whether this is a webclient anomaly, or an anomaly in the ONT cell, but it manifests itself in the webclient.
Imagine using a modifier leaf inside an ontology branch.
For instance, the ontology branch has these paths...
... and I indicate that my modifier leaf has the following settings:
My goal is for my modifier to show up for all the Sensory diagnoses, but not for the "Sensory" parent folder. Therefore, the M_APPLIED_PATH includes the wildcard '%' at the end, but the M_EXCLUSION_CD does not show that.
This sounds straightforward, but in my experience, that exclusion code did not work. It is displaying at the "Sensory" parent, as well as at the "child" diagnoses.
Am I misunderstanding something, or is this truly a bug?