Opened 8 years ago
Closed 8 years ago
#284 closed Defect (Fixed)
Proxy variables are needed in IBIS 2.3 query application URL
Reported by: | Tong Zheng | Owned by: | Tong |
---|---|---|---|
Priority: | !!Urgent | Milestone: | Unassigned |
Component: | View-App | Version: | 2.3 |
Severity: | Unknown | Keywords: | query url |
Cc: | garth.braithwaite@…, kmarti@…, lois.haggard@…, pleo84103@…, mmccord@…, tzheng@… |
Description
Proxy variables are gone from the query application URL on IBIS 2.3. It causes two problems:
- Customized age, year, diagnosis ICD codes etc..
- Dynamic grouped year groups and age groups.
IBIS 2.2 is working fine. Cgi app gets the info from this URL and regroup year/age etc.. http://hlcbsas/cgi-bin/hi_iq_func2.1?config=%2Fsrv%2Fibis-q%2Fmodules%2Fmort%2FMort_CV.cfg&sas=0&func=CrudeRate_cv.def&YearProxy=YearGrp5_99-Pres&YearGrp5_99-Pres=2004-2008&CauseDeathProxy=ICDNCHS50&AgeGrpProxy=AgeGrp11&GeoProxy=GeoLHD&cross1=YearProxy
IBIS 2.3 is not working because the proxy didn't get passed to query URL. The cgi app can't process regrouping:
The value of YearGrp5_99-Pres=2004-2008
doesn’t exist in dataset. Cgi app does need "YearProxy?" to regroup those years on backend. The query result gets this error message:
<ERROR ID='31'> <CODE>31</CODE> <DESCRIPTION>
Invalid data type for cross variable. 3
</DESCRIPTION> </ERROR>
In one case, IBIS 2.3 query url would work with no proxy passed when there is no need to regroup variables on backend. eg,
Year value "2013" is coded in dataset and no need to regroup. Therefore, all single years and predefined age and diagnosis groups work fine.
Change History (3)
comment:1 Changed 8 years ago by
comment:3 Changed 8 years ago by
Resolution: | → Fixed |
---|---|
Status: | new → closed |
I tried on New Mexico test site: http://ibistest.health.state.nm.us/ibisph-view/query/builder/mort/MortCnty/CrudeRate.html for the proxy variable problem. I found an issue same as Utah. This is the url:
http://10.135.2.142/cgi-bin/hi_iq_func.exe?config=E:\ibisq\qModules\mort\Mort13.cfg&sas=0&test=0&func=NM_CrudeRateFrame.def&GeoRes=1&Year9=2011-2013&cross1=Year9
I am just making sure this is not only an Utah specific problem.