Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.7.09
-
None
-
Query Tool
-
Constraints - Date
-
All Web Browsers
Description
Log into https://www.i2b2.org/webclient/
drag and drop a previous query onto the 1st group panel
Right click on the previous query concept and select 'set date constraint' from the context menu
Set a date constraint , example >12/1/2014 on the date picker pop up.
click OK.
Issue1:
Expected Result: Msg should be displayed to the user that date condtraints cannot be set on previous query.
Actual result: The date picker pop up OK button seem to be non functional and no msg dispalyed to user
Issue2:Click cancel on the date picker pop up after setting date constraint
Now drag and drop a second concept to the same group panel as the previous query,
Expected Result: no date constraint should be set on the previous query
Actual Result: date constraint appears on the previous query concept after adding a second concept to the same group panel
Note: Same issue exists for Patient set as concept
drag and drop a previous query onto the 1st group panel
Right click on the previous query concept and select 'set date constraint' from the context menu
Set a date constraint , example >12/1/2014 on the date picker pop up.
click OK.
Issue1:
Expected Result: Msg should be displayed to the user that date condtraints cannot be set on previous query.
Actual result: The date picker pop up OK button seem to be non functional and no msg dispalyed to user
Issue2:Click cancel on the date picker pop up after setting date constraint
Now drag and drop a second concept to the same group panel as the previous query,
Expected Result: no date constraint should be set on the previous query
Actual Result: date constraint appears on the previous query concept after adding a second concept to the same group panel
Note: Same issue exists for Patient set as concept
Attachments
Activity
Reeta, can you provide the code snippet from the biobank portal? I can't find it.
1) Some of this was fixed in 1.7.11.
2) I added Nich's change to disallow date constraints on previous queries, patient sets, and demographics.
However, demographic constraints can still be set on the demodata because it uses the fact table, not the patient dimension. This is not a bug but we should clean up the demodata in a future release.
2) I added Nich's change to disallow date constraints on previous queries, patient sets, and demographics.
However, demographic constraints can still be set on the demodata because it uses the fact table, not the patient dimension. This is not a bug but we should clean up the demodata in a future release.