Skip to content

Instantly share code, notes, and snippets.

@darrensapalo

darrensapalo/GW360 Update.md

Created October 15, 2020 06:05
Show Gist options
  • Save darrensapalo/1a63ee5b78a1718178e029462a2e95f1 to your computer and use it in GitHub Desktop.
Save darrensapalo/1a63ee5b78a1718178e029462a2e95f1 to your computer and use it in GitHub Desktop.
Download ZIP
Planning for deployment by Oct 19, 2020
Raw
GW360 Update.md

Meeting

Thursday, October 15, 11:30AM-1:00PM (PHT)

  • Seth
  • Darren
  • Baron
  • Drew

Expected Timeline

  • Monday (Oct 19) - Client uses GoodWorker360, logs in, creates mentor matching, etc.

  • Sunday afternoon (Oct 18) - Production deployment.

  • Sunday morning - Staging integration testing.

  • Saturday evening (Oct 17) - Finish all related tasks

    • missing KPIs
    • omnivore integration
    • cron jobs integrated
    • Test out user registration workflow.

Tasks

Seth

  1. Fill up Google Sheets to prioritize which KPIs to include/exclude
  2. Determine all of the API query details necessary to get the data of the employee data
  3. Revisit and document GoodWorker360 score computation

davph.io Dev team

  1. Test a manual postman request as defined by Seth. Report any issues with Seth.
  2. Resume Seth's WIP omnivore integration (following seth's details on the google sheets).
  3. Double check cron job implementation.

Situation

  • KPIs
    • We have a documentation on all of the KPIs we want to support (see phase 2 project proposal).
    • We currently have missing KPI implementations on the omnivore service.
    • The GoodWorker360 system is built such that it is expecting that the data already exists- an assumption agreed between by both parties when splitting up the work.
    • An Implicit assumption we have is that:
      • all of the KPIs requested on the phase 2 document have been reviewed in the omnivore API documentation
      • all of the ticket data retrieved from omnivore have been verified to possible to generate as KPI

Challenge

  1. Retrieve omnivore data via API reuest
  2. received data
  3. Perform some transformation
  4. Prepare KPI into gw360 format
  • The problem we're solving right now is [how to insert the KPI data given the omnivore tickets]

Task 1: For each KPI, determine their queries

Seth, please fill up the google sheets details for the KPI data.

Task 2: Identify which KPIs you sense may not be feasible

  • Which KPIs do you not feel confident about?
  • Which KPIs should we prioritize?

Darren and Baron can give feedback on which KPIs we feel confident the system will be able to generate.

Seth's inquiries

  • Queries

    • How are employee and the restaurant KPIs differentiated in the code?
    • How do we deal with days worked KPIs (its a little more complicated)?

  • Multiple users in one account

    • Recommended to just let them share one account for now. Can build out user roles later on as a separate module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment