Opened 7 years ago

Last modified 4 years ago

#169 new Enhancement

Presentation of Query Selections

Reported by: Lois Haggard Owned by: Lois
Priority: -Low Milestone: Needs Analysis
Component: View-App Version: Parking Lot
Severity: Major Effort Keywords: query selection


I would like to provide query selections options similar to the way WISQARS does. Here is their query selection page URL:

WISQARS allows single selections (radio buttons) of classes from lists of non-mutually-exclusive selections.

Change History (10)

comment:1 Changed 7 years ago by Garth Braithwaite

Owner: set to unassigned

comment:2 Changed 7 years ago by Eleanor Howell

Keywords: query selection added

comment:3 Changed 6 years ago by Kathryn Marti

Milestone: Unassigned2.2 - Testing
Owner: set to Lois

comment:4 Changed 6 years ago by Kathryn Marti

Owner: changed from Lois to Lois Haggard

comment:5 Changed 5 years ago by Garth Braithwaite

Milestone: 2.2 - Testing
Version: UnknownParking Lot

comment:6 Changed 4 years ago by Garth Braithwaite

Milestone: 2.3 - Testing
Owner: changed from Lois Haggard to Lois
Version: Parking Lot1.8

Not sure what is being asked for. IBIS-View has always had the ability to have single selections in either radio or list selection form???

comment:7 Changed 4 years ago by Lois Haggard

We're actually trying to replicate the way cancer sites are selected on this website:

It is an indented list that allows the user to make one selection, and their selection includes all the records beneath that level of the list. For example, in the following list, the user who selects "Leukemia" would get counts and rates for all nine types of leukemia - everything in the list. The user who selects Lymphocytic leukemia would get counts and rates for those three types of lymphocytic leukemia (codes 35011, 35012 and 35013), and the user who selects a single, specific (end node) type of leukemia would get counts and rates for only that one type of leukemia.

  • Leukemia
    • Lymphocytic Leukemia
      • 35011, Acute Lymphocytic Leukemia
      • 35012, Chronic Lymphocytic Leukemia
      • 35013, Other Lymphocytic Leukemia
    • Myeloid and Monocytic Leukemia
      • 35021, Acute Myeloid Leukemia
      • 35031, Acute Monocytic Leukemia
      • 35022, Chronic Myeloid Leukemia
      • 35023, Other Myeloid (Monocytic) Leukemia
    • Other Leukemia
      • 35041, Other Acute Leukemia
      • 35043, Aleukemic, subleukemic and NOS

I had mentioned the notion of radio buttons earlier because we don't need to allow the user to make more than one selection. BUT the selection he or she makes will need to include everything in the list/tree underneath that selection.

We tried using dimension files that included the dimension values for each level of selection, but it worked for the first two levels, only. If the user went further down the tree than two levels, it didn't work. I know that's vague, and I'll work on getting more specific information about what exactly happened. So stay tuned on this one.

comment:8 Changed 4 years ago by Garth Braithwaite

It might work if you name each mid SELECTION with a NAME and VALUE that matches a DIMENSION NAME/VALUE pair. You'd then have to have backend code that knows what to do with the selections passed. If the value being returned matches a DIMENSION NAME & VALUE it should display (if the user has privs). If this doesn't work then I think what you're talking about is a rollup capability that would require a pretty extensive refactoring.

comment:9 Changed 4 years ago by Lois Haggard

Milestone: 2.3 - TestingNeeds Analysis

comment:10 Changed 4 years ago by Lois Haggard

Severity: UnknownMajor Effort
Version: 1.8Parking Lot
Note: See TracTickets for help on using tickets.