Changes between Version 359 and Version 360 of CoPCallAgenda


Ignore:
Timestamp:
09/27/20 16:27:03 (5 weeks ago)
Author:
GarthBraithwaite_STG
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CoPCallAgenda

    v359 v360  
    5454 - Adopter migration schedule.
    5555 - ICD-10 CM - updates?
    56  - 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.
    57  * How much are these content pages being hit? 
    58  * Are low hits because it's not needed or because it's not engaging and/or providing any value to the user?
    59  * Which pages are simply a required page and we really don't care about usefulness?
    60  * How busy are most adopters with simply dealing with the data portion of IBIS and their other duties? 
    61  * Can most content pages can be cleaned up once with little maintenance there after?
    62  * What resources are available?  This includes interns, others within the department or state IT, or outsourcing.
    63  * What can STG help with?  STG can provide the technical assistance on how to implement design.  STG can also help with usability design, graphic creation if needed, and review.
    64 
     56 - Discuss the need for web content development. How busy are you? If enough interest we can likely get resource(s) to help cleanup / scrutinize pages.  Included in this effort are:
     57   * Taking inventory of static pages and navigation.
     58   * How much are these content pages being hit? 
     59   * Why are pages being hit and why they might not be being accessed.  Are low hits because it's not needed or because it's not engaging and/or providing any value to the user?
     60   * Heavily scrutinize page value; 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 ie which pages are simply a required page and we really don't care about usefulness?
     61   * Can/which content pages can be cleaned up once with little maintenance there after?
     62   * What resources are available?  This includes interns, others within the department or state IT, or outsourcing.
     63   * What can STG help with?  STG can provide the technical assistance on how to implement design.  STG can also help with usability design, graphic creation if needed, and review.
    6564 - 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]. 
    6665 - [wiki:supportSchedule Adopter support status and priorities] (Paul/adopters).
    67  - [wiki:developmentSchedule Version 3.0 Development Schedule] (Garth).
     66 - [wiki:developmentSchedule Development Schedule].
    6867 - [http://trac.ibisph.org/trac/report/1 Review open tickets] (Lead by Host, presented by the ticket's author).
    6968 - Discuss related [wiki:HealthSitesOfInterest public health websites] and/or [wiki:TechSitesOfInterest other related websites/techniques/tools].