Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WMRC: Used Oil Collection Center (UOCC) Inspection Report Automation #428

Open
3 tasks
jacobdadams opened this issue Jun 3, 2024 · 7 comments
Open
3 tasks
Assignees
Labels
paying This issue earns $$

Comments

@jacobdadams
Copy link
Member

Benefit

An automated system using Survey123, webhooks, and Make will speed up the UOCC inspection process and make sure reports are both being saved to the right locations and go out to relevant parties immediately. Will allow WMRC to get rid of paper form process.

Acceptance Criteria

  • Suvey123 version of existing forms, with "switch" question to include the proper health department inspectors.
  • Make automation to generate the report, email it to the inspectors and people being inspected, and save it to Google Drive
  • Feature services containing the inspector lists and UOCCs so that the survey doesn't have to be republished every time they're updated

Notes

One of the Local Health Departments (LHDs) has already done a proof of concept, we just need to implement it statewide.

Risks

  • Difficulties translating the Survey123 form
  • Funding for Make automation
  • Credits for report generation

Issue Reference

refs #

@steveoh
Copy link
Member

steveoh commented Jun 3, 2024

We need to find out if the state have an enterprise account for Make or at least an approval to use it? We pay for IFTTT already if that could be used although DTS has asked us not to increase our use of it.

@jacobdadams jacobdadams self-assigned this Jun 3, 2024
@nathankota
Copy link
Contributor

Sprint 4

  • get in touch with Ted Sonnenberg (sp?) from WMRC

@steveoh steveoh added the carry forward This task was carried forward into the next quarter label Aug 20, 2024
@jacobdadams jacobdadams added the paying This issue earns $$ label Sep 5, 2024
@jacobdadams
Copy link
Member Author

jacobdadams commented Sep 5, 2024

25.1.5

Met with Ted Sonnenberg, Rachel Boyer, and Stevie on 5 Sept to discuss next steps.

Goal

S123 form that will provide a different list of inspectors (from feature service) and UOCCs (from feature service) based on LHD. Gateway condition will be a code that each LHD has. S123 and all supporting data will be public.

After a response is submitted, a Make workflow will generate a PDF report and save it to a Google Drive folder based on the LHD. If possible, it will also look for a "email me a copy" question and if yes, send a copy of the PDF to the email address provided by the UOCC. The Make workflow will also save the data in a google sheet, with a separate tab for each LHD if possible.

Tasks

  • Contact Jonathan Dutrow to get copy of XLSForm and Make automation workflow
  • See if Make can condition on a response in the data to send copy to UOCC
  • See if Make can send the data to different tabs in a Google Sheet
  • Set up Inspector and UOCC feature services (may be able to use existing facility layer from map to get UOCC info)
  • Create Survey
  • Create Make Automation

@jacobdadams
Copy link
Member Author

25.1.6

WMRC shuffled funds around and removed the end-of-September deadline. Now this can be finished in early Q2.

@gregbunce gregbunce removed the carry forward This task was carried forward into the next quarter label Sep 26, 2024
@jacobdadams
Copy link
Member Author

25.2.1

Started working on S123 copy over

@jacobdadams
Copy link
Member Author

25.2.3

Fighting with S123 Connect and LibreOffice not being able to update the XLSForm document.

@jacobdadams
Copy link
Member Author

25.2.4

Meeting with WMRC folks on UOCC stuff on 4 Dec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
paying This issue earns $$
Projects
Status: No status
Development

No branches or pull requests

4 participants