Meeting 2017 11 16 Backend

Participants

Present: Shaz, Kai, Reday

Agenda (to discuss)

Progress update

Action Points from last meeting

Reday

• Load the list of saved sessions in history map once user logged in.
• use a new session key for each new session (after user re-logged in).
• store the user session using local storage.

Shaz

• Generating the session key from the backend/API, instead of the client end.
• Research the possibility of using R to automate the statistical analysis, such as Plumber (https://github.com/trestletech/plumber) and Rserve (https://www.rforge.net/Rserve/), or fetch the data from the SenseMap API and do then do the analysis in R, such as https://www.programmableweb.com/news/how-to-access-any-restful-api-using-r-language/how-to/2017/07/21.

Discussion Points

Redays Proposal to scrap Popup and revert back to direct login with save and load in historyMapPage.html (can be achieved today even)

Chrome Behavior issues across older operating Systems

Action Points

Shaz

• Only need one function to generate a new key for an email address. No need to have previous key when a user logged in again.
• Research how to trigger R script remotely, so we don't have to manually run the code every time.

Reday

• Move the login functions to the background page browser action. Run login when user click the SenseMap button. Once logged in, call background.js to start historymap.
• Update save/load to use the session key generated by the API;
• Load the list of saved sessions in history map once user logged in.

Kai

• Change SenseMap icon colour.