The following features will be added:

• remove corresponding asset file, when source is deleted
• ensured redux correctly implemented:
  • default store would load sessionStorage, otherwise default to anonymous user
  • reduced various component conditional logic depending on redux / sessionStorage
• optimize logic storing dataset(s) into the database
• replace jsonschema, with custom validation
• created front-end validators for /login, and /registration (similar to backend logic)
• enhance puppet syntax
  • consolidate puppet/environment/*/package/manifest/*.pp by iterating packages.yaml
• replace default flask session cookie implementation with redis
• use redux to conditionally render usermenu
• update reactjs createClass with native javascript syntax
• redirect /login to frontpage, if user already logged-in
• redirect /register to frontpage, if user already logged-in
• create frontpage for overall application
• create preconfiguration documentation page
• implement secured https url
• implement gitmagic
• implemented flask-jwt-extended for token authentication for programmatic-api
• web-interface to allow users to save current prediction
• web-interface to allow users to review all past predictions
• added additional unit tests for saving, and retrieving prediction results
• added additional unit tests for token based uathentication
• enhance documentation to detail process of saving, and retrieving prediction results
• add application tray for logged-in users
• ensure webcompilers can run via windows host changes
• ensure application is cross browser compliant
• updated puppetagent to version 4.9.x in our Vagrantfile
  • adjusted puppet syntax to comply with version 4.9.x
• partition unit test logic from .travis.yml into build/ bash script, for manual reusability
• store dataset into nosql database
• restructure database connections
  • rather than continuously opening, and closing connection per transaction / session
• added bgc, and bgr sample datasets in preparation for upcoming milestones

Note: instead of the DOM dynamically requesting information from the database, the database will send out corresponding information, when portions of the database tables change, and detected via the trigger property. This will mean the DOM will always have the latest information, without the need to refresh the DOM.