Presentation is loading. Please wait.

Presentation is loading. Please wait.

ICIS requirements gathering meeting (outputs) Workflows for statistics 10-13 June 2008.

Similar presentations


Presentation on theme: "ICIS requirements gathering meeting (outputs) Workflows for statistics 10-13 June 2008."— Presentation transcript:

1 ICIS requirements gathering meeting (outputs) Workflows for statistics June 2008

2 Statistical framework DB of Statistics and Reference Data DB of Statistics and Reference Data Fishstat + Fishery Statistical Working System (with reference data system) Questionnaires FiStatWS

3 Statistical outputs DB of Statistics and Reference Data DB of Statistics and Reference Data Fishstat + Yearbooks Fishery Statistical Working System (with reference data system) FiStatWS PDF reportsTuna AtlasXML output Web output

4 The StatQuery family Its a java library Its a java library Can be invoked in several ways Can be invoked in several ways Its rule is to take statistical queries, and produce an output in form of time series according to a pre-defined XML format. Its rule is to take statistical queries, and produce an output in form of time series according to a pre-defined XML format. XML time series can be used to produce several types of outputs. XML time series can be used to produce several types of outputs. Query panel YearbooksPDF quest.Tuna Atlas Static XML files Web output Web invocation XML output

5 …for your attention ! Thank you…

6 FishStat+

7 FiStatWS output FIGISFIGIS DB FIGIS DATAENTRY AREA Dataset Production Produced in several layouts Data obtained through a basic query panel Possibility of export on several formats

8 StatQuery input - I

9 StatQuery input - II Command Use file=filename Indicates a file in which the parameters are stored. This method is indicated in the following paragraph (Indirect mode). Refer to this paragraph ion order to understand how the input file is structured. ds=dataset name Name of the dataset. Must be exactly the same as defined in StatQuery.xml (case-sensitive). Refer to Appendix A, second column (Dataset ID) of the table Warning: This parameter is mandatory! k1=keyname....k5=keyname Key order (from most to less significant). The key order is important for query execution - k1 is the leftmost column. Key name must be defined in StatQuery.xml as id attribute of Key element. Refer to Appendix A, last column (Columns ID) of the table, keycolumn type. Warning: if you refer to the keys, in whatever mode, you must specify this parameter k1v=1|0...k5v=1|0 Whether the key 1..5 is visible. By default no any key is visible. keyname_v=1|0 The same, like the precedent, but key is addressed by name rather than position. This may be more convenient when query is prodced by an HTML form (since key order is not known when displaying the form but key names are) Warning: if you use this specification mode, you must specify before the Key order using k1=keyname....k5=keyname k1h=hierarchyID, or keyname_h=hierarchyID Hierarchy for key, by key position or name. Default is 0 (flat keys). Warning: if you use this specification mode, you must specify before the Key order using k1=keyname....k5=keyname alltotals=1 Output all totals, even totals of only one record joinser=1 Output all time series(parameters) in one table, for example, Quantities and values together

10 StatQuery input - III

11 StatQuery outputs - I

12 StatQuery outputs - II

13 StatQuery outputs - III

14 StatQuery outputs - IV

15 StatQuery outputs - V


Download ppt "ICIS requirements gathering meeting (outputs) Workflows for statistics 10-13 June 2008."

Similar presentations


Ads by Google