Requirements for the Participant Record Dashboard v3

[sofiatajide]

Dependency

• After either of these issues are completed, update the requirements documented in this issue and in the roadmap
  • Create script that rolls up the data from the participant record sheets #7759
  • Refine the dashboard using a live data source from 0 data - to partially populated - to full #7761

Overview

We need to outline the requirements for the Participant Record Dashboard to ensure clear priorities, resource allocation, and effective management as we move forward with development.

Action Items

• Create Spreadsheet (version analysis feature sets)
• Go through the Roadmap and find any features/requirements it mentions, adding to a comment below
  • move the data to the sheet
• Review V1
  • find additional features
  • indicate all the features it has and write any notes
  • Get sign-off
• Review V2
  • find additional features
  • indicate all the features it has and write any notes
  • Get sign-off
• Review each open and closed issue to determine if there were other requirements, not developed, but talked about (even if they were dismissed)

Resources/Instructions

• Google Drive Folder: Participant Record Card
• Roadmap this dashboard: HfLA website: Dashboard Roadmap: Participant Record
• Requirements Document HfLA website: Dashboard Requirements: Participant Reocrd v3

Related Issues

• Project Board (see all issues): HfLA Dashboards: Project Board, Participant record
• This issue is part of this epic: Epic: Participant Record Dashboard #7509
• Create participant record sample for V3+ of participant record dashboard #7710
  • Create script that rolls up the data from the participant record sheets #7759
• Refine the dashboard using a live data source from 0 data - to partially populated - to full #7761
• Participant Record Dashboard: Documentation for users #8063

Participant Record Card Dashboard Prototype Links and Notes

We provide a custom URL in the offer letter (PDF), that delivers arguments to the script, that populates the User Report see Report_Lookup-Draft2. Program managers can see all the User Reports by going to List of Users, IDs and Passcodes and using the ID and Passcode with the User Report, or see aggregate data by going to the All Users Report. Engagements will be recorded on a tab of the List of Users, IDs and Passcodes.

• V3 (WIP)
  • Spreadsheet TWE: ISXX Participant Record Card: Week XX - WIP
  • Draft Spreadsheet User_Report_Lookup-Draft2
  • Draft Spreadsheet [All Users Report]
  • Draft Spreadsheet [List of Users, IDs and Passcodes]
  • Draft Spreadsheet [List of Users, IDs and Passcodes, Engagements]
• V2
  • Looker Dashboard All Interns
    • located in the internship-ba@hackforla.org account
    • Form (Edit): TWE: ISS Participation Record - Form
    • Responses Sheet: Spreadsheet used by the looker dashboard TWE: IS22 Participation Record (Responses), Instructions tab - This tab, explains the other tabs
    • Form (View):TWE: IS22 Participation Record - makeup entry
    • Notes: The process worked fine as long as the interns remembered to fill in the form to time out once done, which they often forgot to. We started using the makeup form to get tentative time out times, after which the data was manually manipulated to fill in the missing time outs, in TWE: IS22 Participation Record (Responses), Data tab
• v1
  • Spreadsheet Prototype: Participation Record and Attendance Sheet (IS21)
    • Notes: This is the original Participation Record spreadsheet before we had the form and the dashboard.

Requirements

• Presented in Spreadsheet Form Dashboard - Participation Record - Competitive or Comparative Analysis - enables you to see the difference between versions and is a simplified list of all the features across versions (past, present and future).
• Requirements Document HfLA website: Dashboard Requirements: Participation Record v3 - for the new features for the next MVP

Reason for major redesign

• Through discussion with Rabia (the original dashboard builder/maintainer), we determined that the V2 makeup entry required too much manual intervention. Additionally, it was too similar to a job where you have to clock in/out, instead of how contract tech workers report their hours via a weekly reporting tool.

Who will build

• Rabia's role is at a CTS administrative representative for the OPT program. So with Bonnie she figures out what we need to get from the users and what we can provide. She built the previous prototypes but will not be building v3. That will happen with people from Data Science

Emojis

Emojis and their meanings to the dashboard

Emojis
🤩 = Over expectation
😎 = Meets Expectation
😓 = 99.9 to 71% of expected
😭 = 70% or less of expected

Over expectation

🤩

Meets Expectation

😎

99.9 to 71% of expected

😓

70% or less of expected

😭