Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

team_volunteer notes

EvyTurk edited this page Sep 30, 2017 · 6 revisions

Just a scrap sheet for notes for team volunteer. All team members welcome to contribute / update / correct.

SCOPE

  1. Volunteer reporting by SMS
    • Step 1: Support current solution
      • send correctly formatted message with codes to report on events
      • single case and aggregate reporting
    • Step 2: better parsing
    • Step 3: Parsing with validation by user
    • Step 4: Machine learning / speech recognition (voice messages) INBOUND
  • send rapport via sms
  • same each time
  • #, *, 0-9 (parsing part 1- must have)
  • two types of rapports a) single case (EVENT,GENDER,AGE) b) aggregated (EVENT, # of cases, 4 categories (M<5, M>5, F<5, F>5)
  • removing non relevant text (parsing part 2)

How to deal with?

  • duplicates a) SMS (syncing, Gateway either system or people - sending duplicates

b) sending the same SMS twice or more type of data, wrong margin?

-keep all original sms a) registered mobile number b) not registered mobile number (as a minimum)

OUTBOUND- FEEDBACK LOOP

  • each report responds with feedback sms a) generic (not enough) b) country specific c) per CBS project data d) multi language (must be defined on user level) CASES: " did you mean that.... is this correct?"; "Thank you...." ....

  • Send manual message to volunteers based on a) contry b)CBS project data c)User data

-Message types a) No reply b) Conversations (conversation each volunteer)

  1. Volunteer Feedback ->
    • Automated feedback
      • variation
    • Customized by CBS Project
    • Volunteer info that is part of an alert -> provide feedback
    • supporting multiple languages
    • Daily updates to the volunteers

DEPENDENCIES

  • Project deployment

    • Subset of Health events valid for this CBS Project
    • SMS gateways
      • We MAY need to know which gateway to use for which volunteer (or it might be handled by sms gateway component)
  • Volunteer Administration

    • Forms to register volunteers
      • phone provider
      • phone type?
      • GPS location
      • SMS gateway to reach this subscriber
      • Opt in / opt out of status updates
  • Feedback to not registered users. " Did you change your phone?"; "Do you wish to register new phone?"
  • " BASE DATA NEEDED BY THIS CONTEXT
  • Receipt and processing of Case Report
    - List of valid Health Events for this CBS Project - SMS Message fields and formatting rules for parsing
  • Feedback to volunteer
    - Volunteer information (language preference, sms gateway, feedback preference)
  • Alert event subscription
    - generated alerts might provoke feedback to a number of volunteers. How can we identify which volunteers provided data to an alert? Or which volunteers are in the same area as an alert, and should get some feedback based on the alert.

*TO DO

  • Roundtable with Admin *General UI *Frontend requirements *How do you use web application today?