oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OODT-158) QuerySets for XMLPS
Date Fri, 14 Dec 2012 00:34:20 GMT

     [ https://issues.apache.org/jira/browse/OODT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris A. Mattmann updated OODT-158:
-----------------------------------

    Fix Version/s:     (was: 0.5)
                   0.6

- push out to 0.6
                
> QuerySets for XMLPS
> -------------------
>
>                 Key: OODT-158
>                 URL: https://issues.apache.org/jira/browse/OODT-158
>             Project: OODT
>          Issue Type: Improvement
>          Components: xmlps
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>              Labels: bakedin, query, queryset, xmlps
>             Fix For: 0.6
>
>
> [~davekale] and I have been discussing the notion of "query sets" for XMLPS. These would
turn long, huge queryStrings for XMLPS, e.g.,:
> {noformat}
> http://host:8080/grid/prod?q=RETURN=ID%20AND%20RETURN=UnitNumber%20AND%20RETURN=AcctNum%20AND%20RETURN=HospitalAdmitDate%20AND%20RETURN=AdmitDateTime%20AND%20RETURN=AdmitDate%20AND%20RETURN=AdmitTime%20AND%20RETURN=Service%20AND%20RETURN=AdmitCategory%20AND%20RETURN=ZipCode%20AND%20RETURN=ZipRegion%20AND%20RETURN=Origin%20AND%20RETURN=ReferringHospital%20AND%20RETURN=Doctor%20AND%20RETURN=ReferringService%20AND%20RETURN=DischargeCondition%20AND%20RETURN=Disposition%20AND%20RETURN=Payment%20AND%20RETURN=PICULocation%20AND%20RETURN=DischargeDateTime%20AND%20RETURN=DischargeDate%20AND%20RETURN=DischargeTime%20AND%20RETURN=Planned%20AND%20RETURN=PRISM%20AND%20RETURN=MortProb%20AND%20RETURN=OperativeType%20AND%20RETURN=isScheduled%20AND%20RETURN=isTrauma%20AND%20RETURN=FEStudy%20AND%20RETURN=Weight%20AND%20RETURN=Height%20AND%20RETURN=HeadCircumference%20AND%20RETURN=AdmitPCPC%20AND%20RETURN=DischargePCPC%20AND%20RETURN=AdmitPOPC%20AND%20RETURN=DischargePOPC%20AND%20RETURN=ToDoList%20AND%20RETURN=Bed%20AND%20RETURN=Resident%20AND%20RETURN=isVerified%20AND%20RETURN=VerifiedBy%20AND%20RETURN=OrganDonor%20AND%20RETURN=OrganProcurementNotified%20AND%20RETURN=DeathReason%20AND%20RETURN=DischargeNote%20AND%20RETURN=OriginText%20AND%20RETURN=DispositionText%20AND%20RETURN=DeathNote%20AND%20RETURN=DeathFellow%20AND%20RETURN=DeathAttending%20AND%20RETURN=HospDCDate%20AND%20RETURN=HospDCStatus%20AND%20RETURN=ADT%20AND%20RETURN=BillingSameIllness%20AND%20RETURN=BillingSameIllnessDate%20AND%20RETURN=BillingAccident%20AND%20RETURN=BillingAccidentType%20AND%20RETURN=BillingEmergentService%20AND%20RETURN=BillingSimilarIllness%20AND%20RETURN=BillingSimilarIllnessDate%20AND%20RETURN=BillingAccidentDate%20AND%20RETURN=upsize_ts%20AND%20RETURN=FirstVital%20AND%20RETURN=LastVital%20AND%20RETURN=influenza_like_illness
> {noformat}
> into something like:
> {noformat}
> http://host:8080/grid/prod?q=RETURN%3DPICUDBQSET
> {noformat}
> which would then require some configuration say in XMLPS, something like:
> {code:xml}
> <ps:config ...>
> ...
>  <querySet name="PICUDBQSET">
>   <field id="f1"/>
>   <field id="f2"/>
>   ...
>  </querySet>
> </ps:config>
> {code}
> In other words, we're talking about baked-in, canned queries for XMLPS prod servers that
are mainly used for dumping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message