Meeting 2017 11 6 Backend

Participants

Present: Kai, Shaz, Reday, Humzah(?)

Agenda (to discuss)

Progress update

Action Points from last meeting

Reday

• Store Profile into local storage, check if local storage has something, if not do authentication, else load stuff.
• Add buttons back to history map, and store profile and logged in check in localstorage, use that to check if account is logged in, and use that to trigger button functionality.
• If user click the sensemap button during a session, the login module will check if it is the same user and only send a new login event to historyMap if it is a different user.
• Discuss this with Kai when there is some code there.

Shaz

• Update the functions for the nodes and sessions to use the dynamic access key.
• document updated functions about the changes related to the dynamic key.
• create a update function for the access key: generate a new key for each new user login session of the same user.

Discussion Points

Arrange Meeting with Reday in Regards of Message Passing in chrome

Next meeting time

Action Points

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.