wiki:CoPCallAgenda

Version 344 (modified by GarthBraithwaite_STG, 2 weeks ago) (diff)

--

CoP Call Agenda

IBIS-PH is website software that allows public health practitioners access to publicly-owned health data. The IBIS-PH Community of Practice (CoP) is the stakeholder group for the software. Monthly CoP conference calls allow CoP members to communicate with each other and the IBIS-PH contractors who provide software development and support.


CONFERENCE CALL

Monday, July 20, 2020 - 3:00 to 5:00 EST (1:00 to 3:00 PM MST) NM/NJ Hosting.

Dial-in: (‪US‬) ‪+1 (646) 749-3112‬ - Meeting ID/Access Code: 973-631-485#‬


AGENDA ITEMS

  1. Review agenda and add items as needed...
  2. v3.0 Updates:
    • Query module updates that include using centralized admin based XML files with ability to only include named dimensions so that special dimension xml files can be defined as needed per module XML file.
    • Saved Query and Self Registered User UI updates.
  3. NM migration progress report (need to discuss effort and time needed dealing with converting content and cleaning up content).
    • nmibis-admin
    • nmibis-view
    • Query Modules
  4. Help Needed. We need help to write appropriate help popup copy and with training videos.
  5. Version 3 adopters need to take inventory of their static pages. These pages should be heavily scrutinized 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. We can discuss scenarios.
  6. All adopters should routinely run a website link checker to verify that their pages do not have broken links. If dead or broken links are found they should be fixed or removed from the page. You should check with your IT group to determine their preferred tool. While not inclusive of your site the W3C's single page validator still provides some basic info that will test your basic menu and footer links https://validator.w3.org/checklink. They also have a css validator https://jigsaw.w3.org/css-validator/validator.
  7. ICD-10 CM - updates?
  8. Review and discuss future Version 3.x priorities. Things like:
    • 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.
    • Side by side maps.
    • Heat map layers to capture different results on a single map.
    • New user interface to allow users ability to control map choropleths, charts, and exporting data.
    • New user interface to allow users the ability define their own indicator reports and save those definitions.
    • Development funding.
  9. Adopter migration schedule.

STANDING AGENDA ITEMS

PARKING LOT - OLD, NOT-TOO-ACTIVE AGENDA ITEMS

  1. Introduction and Training Videos Status Update
    • 4-video playlist for new adopters Describes types of IBIS-PH content and how it's maintained. (Lois)
    • Adding an area labels layer to your map, editing GeoJSON in QGIS (Chris Wenker)
    • Modifying an IBIS map definition - choropleth groups and colors, adding new map definitions (Lois Haggard, Paul Leo)
    • Creating Dynamic Grouping Variables for an IBIS Query (Tong Zheng)
    • Wiki Formatting - When, Where and How It's Used in IBIS-View (Kim Neerings)
    • The Subversion (SVN) file repository - basics (Lois Haggard, Paul Leo)
  2. IBISQ Testing (Lois, Paul, Tong)

IF TIME & INTEREST or FUTURE AGENDA ITEMS


ALL COP MEMBERS: PLEASE BE PREPARED TO DISCUSS YOUR TICKETS.

  • When you submit a ticket, leave the Milestone=Unassigned and Version=Unknown and the ticket will come up on ticket report number 1 New Tickets for CoP Review
  • If you have new or open tickets please review them and be prepared to discuss them on the CoP call. You can run the {1} New Tickets for CoP Review report to see current tickets. The purposes of discussing tickets are to a) communicate an idea to the community, and b) to identify and track IBIS-PH software issues. (Note that once a ticket has been marked to be worked then that ticket is only discussed on the CoP call for the purpose of moving the effort forward.)