Meeting 2018 01 11 Backend

Participants

Present: Kai, Reday, Shaz

Agenda (to discuss)

Progress update

Action Points from last meeting

Reday

• Add API functionality to new overlay
• Look over API code for saving
• Maybe delete unused code (?)

Kai

• Unknown?

Shaz

• Unknown?

Discussion Points

Reday:

What I want to ask shaz:

• Can we make it so when we add nodes, we dont ask for a structure and just add everything it takes?
• Can I have it in the API that asks for a SessionID/SessionName and add nodes to that session

What I did:

• removed Localstorage userprofile code
• used Message Passing thanks to kai
• Added check for Session to make load button visable
• Added Automatic Session Date in Input Box of create Session
• Some smaller changes when interacting with api

TODO:

• Give life to Session Loading (need kais UI code for that)
• Make some changes to Session Save
• Maybeeee delete some comments that we do not use ?

Project timeline update

Next meeting time

Action Points

Reday

• Try put the node information in the 'nodeAdditionalInfo' field and see if that work. If so, Shaz will remove the fields in the current node schema that is not needed for database search.
• 'Attach' the 'load' and 'save' UI with the API code.

Kai

• Add session loading UI

Shaz

• create a new collection in mongoDB to store SenseMap setting data
• create API functions that returns/create/update the setting data
• SenseMap changes according to the setting data, or even output the setting data in console log.
• Add setting information to the saved session data, so it is clear what the setting is when a session is saved.