Changes between Version 358 and Version 359 of CoPCallAgenda


Ignore:
Timestamp:
09/27/20 16:15:41 (4 weeks ago)
Author:
GarthBraithwaite_STG
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CoPCallAgenda

    v358 v359  
    2828 * What should be the main leading content for those help popups. 
    2929 * Should their be more technical definitions that follow the main help content?
    30 1. Interest in reviewing centralized, decentralized, hybrid query module XML files.  This meeting would be a working meeting that walks through the different use cases, and the pros and cons of each.
    31 1. Determine how best to deal with chart, map, and grids.  This is likely a separate meeting.  Discussion needs to include:
     301. Interest in meeting(s) to walk through the version 3 apps.
     31
     32__SEPERATE MEETINGS ONCE ADOPTERS START MIGRATION__
     33
     341. Review centralized, decentralized, hybrid query module XML files.  This meeting would be a working meeting that walks through the different use cases, and the pros and cons of each.
     351. Determine how best to deal with chart, map, and grids.  Discussion needs to include:
    3236 * Centralized file that contains all (likely large and very confusing for admin editors),
    3337 * Admin app having a general list for users to select from in query and view with ability to enter custom name for the actual view,
    3438 * QMs to include certain chart defs or use the CHART_NAME
    35 1. Need to go through the QM fields and make consist with IP datasets (another meeting but needs to happen).
    36 1. Interest in reviewing and setting up followup meetings for future Version 3.x priorities?  Things like:
     391. Updating the QM fields to make consist with IP datasets.
     401. How you can use saved queries for creating "system" type queries (even if you don't want end user saved queries on your site). 
     411. Other advanced usages where IBIS data visualizations can be pulled into other websites and/or into static story pages.
     421. What is possible and how to use other non IBIS data visualization usages within an indicator view.
     431. Follow up meetings for future Version 3.x priorities?  Includes:
     44 * Enhancement Tickets
    3745 * What is the query to indicator auto update feature and how it should work.  There are several use cases like admin based where a user presses a button to run a saved query to update the indicator dataset values.  Another is to define an indicator dataset and a link to a saved query definition.  This then has questions about caching etc.
    3846 * Side by side maps.
     
    4149 * New user interface to allow users the ability define their own indicator reports and save those definitions.
    4250 * User defined comparisons (ie sets of indicators, peer groups etc.).
    43  * Initiatives (new HP 2020).
     51 * Initiatives (new HP 2030).
    4452
    4553__STANDING AGENDA ITEMS__
    4654 - Adopter migration schedule.
    4755 - ICD-10 CM - updates?
    48  - 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.
    4956 - Discuss the need for web content development. Version 3 adopters need to take inventory of their static pages.  These pages should be heavily scrutinized with considerations like the value of the page, how much is it being used, why is it not being used, resources needed to make it useful, resources needed to maintain, and website requirements.
    5057 * How much are these content pages being hit?