Changes between Version 77 and Version 78 of developmentSchedule


Ignore:
Timestamp:
06/03/20 14:44:54 (4 weeks ago)
Author:
GarthBraithwaite_STG
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • developmentSchedule

    v77 v78  
    44
    55= Version 3.0 - new dataset structure =
    6 '''3rd Round of Testing, full NM data migration to production: End of 2019?'''
     6'''3rd Round of Testing, full NM data migration to production: Mid 2020?'''
    77
    8 Version 3 is mainly an admin backend data release and basic view app conversion to the new structure and latest dependent libraries.  The schedule aligns with NM availability which will provide the time needed to go through and scrutinize all page types, polish the user interface, and perform the data migration from 2.3 to the new data structure.
     8Version 3 was initially going to mainly be an admin backend data release and basic view app conversion to the new structure and latest dependent libraries.  Due to COVID-19 and testing time constraints more functionality has been included in this release. 
     9This includes:
     10- Better understanding of site usability.  All page types have been reviewed and many updated to increase usability.
     11- Simplified site navigation with cleaner and simpler web site layout.
     12- Easier to read text blocks with more white space.
     13- Cleaned up consistent titles with less jargon.
     14- Where applicable consistent top of page control options.
     15- More visually engaging Health Topic pages.
     16- More integrated indicator to topic associations.
     17- New Interactive Summary Indicator Reports.
     18- New community Health Profile report.
     19- Multiple Indicator Report indexes with filtering.
     20- Introduction videos for the different site content and different users.
     21- More help popups/content for admin and view pages.
     22- Content blocks for query results and indicator reports.  This allows IBIS or non IBIS websites to make requests to consume IBIS visualizations and content.
     23- and of course all the backend database changes that clean up kludged data usage and lay the footings for standardized query module and indicator dataset structures.
     24
    925See [wiki:designGoals 3.0 Design Goals] for information about what version 3.0 is trying to accomplish (See [wiki:currentDesign Current Design Thoughts] for current ideas).
    1026