Meeting 2017 10 16 Backend

Participants

Present: Shaz, Reday, Kai

Agenda (to discuss)

Progress update

Action Points from last meeting

Shaz

• API: update a node
• Generate a secret key for a session once user is logged in/authenticated.

Reday

• Remove 'nodeoff'
• Move the saving and loading code to a new file.

Kai

• Move 'nodes' to background page
• Make SenseMap open-source by change the global secret key

Reday

• Cleaned UP, Code for Loading and Saving are now in Separate Documents.
• Removed Node OFF, also removed code from browser provenance to the Saving Document.
• Fixed Bugs with saving and pausing.
• Even more buttons.... Sorry, One for retrieving User Session Information and one to load the actual selected Session.
• Users can now Select their desired session that they want to load in the User Profile Box.
• Closed Login ISSUE for now.
• Made a new Branch for SaveLoad called rebuild-SaveLoad.
• Pushed current state of SaveLoad to rebuild-Login.

Discussion Points

Reday

• Update in regards of Code
• Question for "nodes" to backend
• The Bug where nodes do not get added to the new session yet still remains, Can we investigate this please ?
• Ohh and I would like to push the changes from rebuild-login once everyone is happy with save and load.

Kai

• Code refactoring
  • by 'module' not 'file type'
  • turn existing code into modules: history map, login, knowledge map, etc.
  • new 'data' component using the REST API and Chrome Storage API (not HTML5 local storage)

Action Points

Shaz

• add the parentTabId and from to the mongodb node schema.
• Generate a secret key for a session once user is logged in/authenticated.
• find a way to access the mongodb on mlab remotely.

Reday

• Create a github issue about 'nodes only added to the first session'.
• Remove the save/load code from the 'login' branch and merge the 'login' branch with 'rebuild'

Kai

• Code refactoring
  • reorganise files by by 'module' not 'file type'
  • turn existing code into modules: history map, login, knowledge map, etc.
  • new 'data' component using the REST API and Chrome Storage API (not HTML5 local storage)