Changes between Version 353 and Version 354 of CoPCallAgenda


Ignore:
Timestamp:
08/18/20 11:24:48 (5 weeks ago)
Author:
GarthBraithwaite_STG
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CoPCallAgenda

    v353 v354  
    2020 * Saved Query and Self Registered User UI demo.
    2121 * Discuss, and demo, how you can use saved queries for creating "system" type queries (even if you don't want end user saved queries on your site).  We can show Lois's COVID pages as one example for using saved queries.
    22  * Apply query demo (note: when turned on it is only available when a new module is loaded).
     22 * Apply query demo.  Technical notes when enabled:
     23    * To turn on no login is needed,
     24    * Only applied when a new module is loaded from the query/result or query/builder request (so by design is NOT applied to saved queries),
     25    * Only supplements default values - does not override and replace,
     26    * Only is able to set values that 100% match the dimension name and value (refer back to this when we discuss the query module cleanup effort below).
    2327 * Review kendo charts and grid.  This includes interaction between chart and grid, grid export, copy and paste, grouping, drag and drop columns, column options in general, how the admin app and charts.xml file works, adding custom chart definitions for a query module's default chart, and anything else you'd like to know about.
    24281. NM migration progress report (need to discuss effort and time needed dealing with converting content and cleaning up content).
    2529 * nmibis-admin
    2630 * nmibis-view
    27  * Query Modules.  Need to make sure that everyone understand the minimum effort of migration.  MEASURE => MEASURE_NAME, DATA_SOURCE => DATA_SOURCE_NAME, if you want confidence limits etc you'll need to implement ANCILLARY_VALUE entries, and your dimensions will need a SORT_ORDER if you want them ordered correctly.  All the other effort (which is likely large) is cleanup needed for future integration of IP datasets and QM datasets.
     31 * Query Modules. 
     32    * Discuss the minimum effort of migration. 
     33       * MEASURE => MEASURE_NAME,
     34       * DATA_SOURCE => DATA_SOURCE_NAME,
     35       * ANCILLARY_VALUEs - if you want confidence limits etc you'll need to implement ANCILLARY_VALUE entries,
     36       * DIMENSION_VALUEs SORT_ORDER - your dimension values will likely need a SORT_ORDER for data to display in the exact order you want them. 
     37    * All the other effort (which is likely large) is cleanup needed for future integration of IP datasets and QM datasets and for new functionality.
    28381. Help Needed.  We need help to write appropriate help popup copy and with training videos (see [http://ibis.hhdw.org/ibisph-view/] for an example).  This includes:
    2939 * Defining the various users.