Behaviour: Save and Load

Starting

• SenesMap always starts with an empty historyMap, whether the user is logged in or not.
• Whether logged or not, user is not prompted to enter a session name until
  • User is to close the SenesMap/HistoryMap Window, or
  • User is to start a new session using the 'new' button, or
  • Any other scenario that will clear the historyMap.

Load

• After user logs in, he/she sees a list of saved sessions automatically, the 'load' button becomes available, if there is any saved sessions;
  • User can then continue current session without entering a session name;
  • Not possible to 'load' if user is not logged in.
• (Load Scenario) User can open the list of saved session by clicking the 'load' button and continue one of the saved sessions by selecting it;
• (New Scenario) Or user can start a new session by typing a new session name.
  • This is the only option is there is no saved sessions.
• If there is unsaved progress in the current historyMap (for either the 'load' or 'new' scenario), user will be prompted to save it (as a session) before loading a previous session.
• There is a 'load' button that stops current session and allow user to continue a previous saved session.
  • The UI of the 'load' is the same as that for the session selection after log in.

Save

• When a user performs any action that changes the history map, such information is saved automatically
  • Some examples: open a page (new node added), highlight text in a page (text added to node).
  • User does not need to do anything, such as selecting save from menu.
• There is a 'pause' button to stop recording user action in history map:
  • User can 'un-pause' to continue the session later;
  • (This is 'implementation' not 'behaviour') Technically, the data ares still saved as usual and the only difference is that they are marked as 'hidden' so don't show up in history map.

Optional

• Search session: user can search for a saved session using a search field:
  • Only useful for one user when there many sessions, such as 20+;
  • This can be useful later when sessions are shared and it is possible to search other user's sessions.