On AirTable we have the table named "Verifications" with the various fields, eg, feedback (how did you hear about us), their pull request supplied by the GitHub API Automation, and an image of their PCB. There are several flaws with this design - primarily as this was only supposed to be a temporary solution but ended up becoming riddled with hacky solutions that don't work long-term.
Steps along the way
IDs
1. Reviewers still have to view IDs, which should be offloaded to the centralized YSWS System. No (onboard) reviewer should have to review another ID.
It's not clear to submitters if they should be re-verifying their proof of high school enrollment, hoping to implement YSWS Verifier on the FillOut form with @24c02.
User Verification
If a user is already in the Slack and has completed the YSWS Verification form, a Slack-link bridge should be used to get the user's Slack ID and check if they're already in the YSWS system.
Users in the Slack but not in the YSWS verification system should be redirected to completing the YSWS form before continuing. This makes it so no IDs are handled by us and we can be 100% sure that this user is who they say they are and we have tangible proof.
Manage multiple PCBs made by a single user
It isn't clear to submitters if they should submit another verification form per PCB they make.
AirTable should have a singular record for each user linked to another AirTable record of every pull request they've made and the individual status of that pull request. With our current workflow, we barely ever log pull requests from users who submit more than one PCB, these simply aren't tracked.
There are many redundant questions on the Fillout form to just, how did you hear about OnBoard, how can we improve, is this first PCB, etc etc.
OnBoard Pull Request Template should explicitly inquire if it's their first submission yet
We need to check and make sure to see if they've already submitted before, and if not, verify if they've at least submitted the YSWS Verification Form.
This involves allocating the pull request to the user's profile on the AirTable and in adjacent to, verifying that they have no other Grants/PRs on GitHub or Slack ID matches.
HCB Grant
A set automation to link grants on HCB with AirTable, using the HCB API.
On AirTable we have the table named "Verifications" with the various fields, eg, feedback (how did you hear about us), their pull request supplied by the GitHub API Automation, and an image of their PCB. There are several flaws with this design - primarily as this was only supposed to be a temporary solution but ended up becoming riddled with hacky solutions that don't work long-term.
Steps along the way
IDs
1. Reviewers still have to view IDs, which should be offloaded to the centralized YSWS System. No (onboard) reviewer should have to review another ID.User Verification
If a user is already in the Slack and has completed the YSWS Verification form, a Slack-link bridge should be used to get the user's Slack ID and check if they're already in the YSWS system.Users in the Slack but not in the YSWS verification system should be redirected to completing the YSWS form before continuing. This makes it so no IDs are handled by us and we can be 100% sure that this user is who they say they are and we have tangible proof.Manage multiple PCBs made by a single user
It isn't clear to submitters if they should submit another verification form per PCB they make.
AirTable should have a singular record for each user linked to another AirTable record of every pull request they've made and the individual status of that pull request. With our current workflow, we barely ever log pull requests from users who submit more than one PCB, these simply aren't tracked.
There are many redundant questions on the Fillout form to just, how did you hear about OnBoard, how can we improve, is this first PCB, etc etc.OnBoard Pull Request Template should explicitly inquire if it's their first submission yet
We need to check and make sure to see if they've already submitted before, and if not, verify if they've at least submitted the YSWS Verification Form.This involves allocating the pull request to the user's profile on the AirTable and in adjacent to, verifying that they have no other Grants/PRs on GitHub or Slack ID matches.
HCB Grant