Workflow

[avbhatt]

Map user/helper process for first design.

i.e. 1) user highlights + right-clicks 2) notification on helper page 3) helper clicks and navigates to page 4) help commences

[avbhatt]

• Connect users on same website
  • Same website = checking if exact path, or common parent
    • i.e. example.com/a/b/c == example.com a/b/c == example.com/a/b ?
  • Notify all helpers on same webpage, and continue notifying all helpers who visit webpage until a helper accepts help request, at which point we remove all outstanding notifications from helpers’ menus.
  • Add buttons/feedback option for users to close chat and fire events for the interaction being helpful/we proceed to annotation, or interaction wasn’t helpful and they can decide if they want to wait for another helper (need to maintain list of helpers that have already talked to a user / maybe a block list for users to make sure they don’t have to keep talking to certain helpers).

[ianphilm]

Every time a helper travels to new URL, fire event that pings DB for outstanding issues, populating them in the notifications menu. We do need way to synchronously update helper clients when an outstanding issue in the DB is removed, so that all helper clients remove an issue when it has been dealt with by other helper/removed by the user.

[ianphilm]

When a user initiates right-click event, save necessary context about event (to start out, probably just the URL they're currently on) and save to an "outstanding issues" DB, which will somehow notify all active helpers on page of a user that needs help.

[avbhatt]

Initial plans concluded.