Changes between Version 79 and Version 80 of developmentSchedule

06/03/20 14:53:24 (8 months ago)



  • developmentSchedule

    v79 v80  
    2222- Content blocks for query results and indicator reports.  This allows IBIS or non IBIS websites to make requests to consume IBIS visualizations and content.
    2323- Better options for splitting and managing content.
     24- Most icons are now implemented using fonts and SVG.  This allows for easy color changes and resizing/scaling via CSS.
    2425- 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.
    3031- Ability to edit and save user defined dataset comparisons along with improved saved data queries UX/UI etc.
    3132- Better searching.  The current search uses Google and presents a list of pages that it thinks is most applicable to the search criteria.  The google result page is hosted by google which causes the user to leave the IBIS site.  It also does not provide any filtering or other discovery type options that would be available with a custom search engine.  For example a user might want to find a query dataset that has the CDC as its datasource with demographic dimensions.   
    32 - Clean up the query modules.  Many query modules contain hard to maintain configurations.  Newer techniques are available to allow sharing and conditional importing of xml files.  This effort will be started with core v3.
     33- Finish scrutinizing and cleaning up the query modules.  This effort includes reviewing hard to maintain configurations.  Newer techniques are available to allow sharing and conditional importing of xml files.  This effort was started with core v3.
    3334- IBISQ to IP dataset Integration.  This includes referencing a dataset query and displaying the result data alongside/with related indicator dataset data.  This also includes importing of query data into an indicator dataset.
    3435- Do in depth analysis to determine if there are better techniques and processes to present rolled up record level data.  This could include putting data into a relational database, processing with "R" , and utilizing R's web API to query data.
    3536- Update the IBIS query builder interface from "steps" to a "walk the user through" wizard type interface.  New interface would handle dependencies dynamically.
    3637- Merge the query builder and results interface (especially considering query data analysis and possibility of using "R").
     38- Replace/rework the dataset selection process.
    3739- Replace the admin app with a modern front end.  This would use current technology which would provide better data validation, deletion capabilities, consistent editing and publishing of all content  including query modules, html content, indicator datasets, etc.  This could also be implemented by doing away with the admin app and creating an "edit" feature within the view app that allows inline editing and management of content.
    3840- Better, more integrated content management and publishing (see above).
    3941- Data interfaces with external sites.  This includes pushing IBIS data to other apps like Socrata as well as query interface with allows users to retrieve and display outside data inside their IBIS site (CDC api etc).
    4042- More mapping options with Chloropleths, weighted heat maps, and other thematic maps.  This could also include multiple simpler, smaller, lighter maps as well as integration with ESRI mapping etc.
    41 - Advanced Visualization dashboards.  This could include:
     43- Creation of story/advanced Visualization dashboards.  This could include:
    4244  * Integrated data table/chart/maps (similar current interactive indicator views but with inclusion of the mapping and other display control options like playing a slider or walking a chart/map through a set of years).
    4345  * Health topic or indicator story boards,