Uploaded image for project: 'i2b2 Web Client'
  1. i2b2 Web Client
  2. WEBCLIENT-123

Order of events not maintained when running a previous temporal query

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.7.05
    • 1.7.06
    • Web Client
    • None
    • Query Tool
    • Temporal Queries
    • i2b2 Web Client
    • All Web Browsers
    • Hide
      STEPS TO REPRODUCE / TEST:

      1. Run a Temporal Query making sure you have a temporal relationship defined that has two events. (define order of events tab).

      2. Click on the Clear button to clear the Query Tool.

      3. Drag the Temporal Query you just ran from Previous Queries to the Query Tool.

      4. Go to the Define order of events tab and notice the relationship you defined is not displaying correctly.

      5. Run the query (do not change anything).

      6. Notice in the sent xml that the subquery constraint is sending what is now defined in the query tool instead of what was defined when the temporal query was initially run.
      Show
      STEPS TO REPRODUCE / TEST: 1. Run a Temporal Query making sure you have a temporal relationship defined that has two events. (define order of events tab). 2. Click on the Clear button to clear the Query Tool. 3. Drag the Temporal Query you just ran from Previous Queries to the Query Tool. 4. Go to the Define order of events tab and notice the relationship you defined is not displaying correctly. 5. Run the query (do not change anything). 6. Notice in the sent xml that the subquery constraint is sending what is now defined in the query tool instead of what was defined when the temporal query was initially run.
    • Hide
      Test Date: 06/04/2015
      Build Number:
      Test Status: Completed (Passed Testing)

      Clients Tested :
           i2b2 Web Client

      Environments Tested :
           Browsers: Chrome, Firefox, Internet Explorer, and Safari
           Databases: Not applicable for this test
           Client OS: Mac OS and Windows

      Test Comments:
      Tested with the latest web client build and it appears to be working correctly. The “order of events” defined in the original temporal query are maintained when you drop the previous temporal query into the Query Tool.

      ISSUES FOUND:
      An unrelated issue was found that may have been introduced when the fix for this issue was made. A separate issue has been submitted. Please see WEBCLIENT-126 for additional information.
      Show
      Test Date: 06/04/2015 Build Number: Test Status: Completed (Passed Testing) Clients Tested :      i2b2 Web Client Environments Tested :      Browsers: Chrome, Firefox, Internet Explorer, and Safari      Databases: Not applicable for this test      Client OS: Mac OS and Windows Test Comments: Tested with the latest web client build and it appears to be working correctly. The “order of events” defined in the original temporal query are maintained when you drop the previous temporal query into the Query Tool. ISSUES FOUND: An unrelated issue was found that may have been introduced when the fix for this issue was made. A separate issue has been submitted. Please see WEBCLIENT-126 for additional information.

    Description

      The order of events defined when running a temporal query is not defaulting correctly when the previous temporal query is added to the Query Tool.

      When you go to the Define Order of Events page the events for the defined relationship are all defaulting to 1.

      For Example:

      Temporal Relationship when the first Temporal Query is run:

      Start of the First Ever Event 1
      - occurs before -
      Start of the First Ever Event 2


      Temporal Relationship that displays when drop the previous Temporal Query into the Query Tool:

      Start of the First Ever Event 1
      - occurs before -
      Start of the First Ever Event 1


      IMPORTANT: This is not just a display issue. If you run the previous Temporal Query without making edits to the event relationship, they will be sent in the xml as Event 1.

           <subquery_constraint>
      <first_query>
      <query_id>Event 1</query_id>
      <join_column>STARTDATE</join_column>
      <aggregate_operator>FIRST</aggregate_operator>
      </first_query>
      <operator>LESS</operator>
      <second_query>
      <query_id>Event 1</query_id>
      <join_column>STARTDATE</join_column>
      <aggregate_operator>FIRST</aggregate_operator>
      </second_query>
      </subquery_constraint>


      This issue is happening in all browsers.
       

      Attachments

        Activity

          jmd86 Janice Donahoe added a comment -
          The fix for this issue was included in the 1.7.06 release.

          i2b2 version 1.7.06 was released on August 12, 2015.
          jmd86 Janice Donahoe added a comment - The fix for this issue was included in the 1.7.06 release. i2b2 version 1.7.06 was released on August 12, 2015.

          People

            jmd86 Janice Donahoe
            jmd86 Janice Donahoe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: