website icon indicating copy to clipboard operation
website copied to clipboard
verified publisher icon hackforla

Epic: Participant Record Dashboard

Open sofiatajide opened this issue 1 year ago • 111 comments

Overview

We need to manage the work for the participant record dashboard, so that we can prioritize and recruit.

Action Items

  • [x] Go to the participant record tab for the participant record dashboard and copy all of the links in the issue to a comment at the bottom of the issue and indicate whether they are public or private.
  • [x] Copy all of the link lists from the participant record into a comment on this issue
  • [x] Remove duplicates
  • [ ] ~Remove the public private status~
  • [x] Review all the links and organize them into the Resources section below
  • [ ] Revise Participant Record Dashboard Roadmap

Resources/Instructions

Related issues

  • Epic: All Dashboards Epic: #6614
  • Project Board (see all issues): HfLA Dashboards: Project Board, Participant Record
  • https://github.com/hackforla/website/issues/7640
    • https://github.com/hackforla/website/issues/7710
      • https://github.com/hackforla/website/issues/7759
  • https://github.com/hackforla/website/issues/7724
  • https://github.com/hackforla/website/issues/7761

Participant Record Dashboard Prototype Links and Notes

Tutorials

The below link is from an issue that had been worked on related to the dashboard. Because we have several dashboards being developed we have organized a list of all tutorials on the Hack for LA Data Science repo wiki, called Dashboard Resources. If you add a new tutorial to any issues related to this dashboard, make sure they get added to the wiki.

sofiatajide avatar Sep 23 '24 23:09 sofiatajide

Outstanding issues to resolve

  • [x] IS21 Participant Record
    • Do not have access- it currently has PII in it. We have to make a version of it that has intern numbers instead of names
      • discuss with rabia
      • update this issue when that is completed https://github.com/hackforla/internship/issues/193#issuecomment-2357006553
  • [x] Participant Record dashboard - example intern 1
    • [x] Do not have access - it's an old depreciated version.
      • Still looking for current version
      • Found current prototype, see top of issue
    • [ ] public
  • [x] TWE: Participant Record (Work Hours Calculated) - Intern #
    • [ ] Have access, its located in ____
    • [x] public - this is a folder, not a document Internship > IS22 cohort > Participant Record (need to look through this to figure out what is in here and how to link it to the dashboard roadmap.
      • [ ] discuss with rabia
  • [x] Time Sheet (Recorded)
    • [ ] Have access, its located in ____
    • [x] public - The name of this document is TWE: IS22 Participant Record (Responses) - Annie - workbook for a dashboard
      • This was made by a previous PM on the internship project as a practice copy
      • This is no longer needed
  • [x] Participant Record dashboard - Intern 3
    • [x] Do not have access - this is currently broken, but it was a demo of a dashboard for one person.
      • This is no longer needed. We are now only doing a participant record for all people, and you can look yourself up by number.
    • [ ] public
  • [x] Participant Record - Intern 10
    • [x] Do not have access - this one still has its formatting but 1/2 the data is broken. For a full list of these dashboards https://github.com/hackforla/internship/issues/213#issuecomment-2357024291
      • This is no longer needed. We are now only doing a participant record for all people, and you can look yourself up by number.
    • [ ] public
  • [ ] Talk with Data Science CoP leads for formal names of the type of analysis we want to do.
  • [x] Looking for dashboard

ExperimentsInHonesty avatar Sep 29 '24 19:09 ExperimentsInHonesty

Participant Record Dashboard Link and Notes

  • All Interns
  • it is located in the [email protected] account
  • 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 the sheet called 'Data' in the TWE: IS22 Time Card (Responses) spreadsheet

Rabia2219 avatar Oct 03 '24 16:10 Rabia2219

@Rabia2219 The dashboard only is showing intern choices for null and 11. Where is the version where we can see all interns? image

ExperimentsInHonesty avatar Oct 06 '24 16:10 ExperimentsInHonesty

I renamed all the dashboards so it's clearer what is on them.

ExperimentsInHonesty avatar Oct 06 '24 16:10 ExperimentsInHonesty

@Rabia2219 Please explain the tabs on the TWE: IS22 Participant Record (Responses) spreadsheet by updating the instructions tab. and let us know here

ExperimentsInHonesty avatar Oct 06 '24 16:10 ExperimentsInHonesty

@Rabia2219 The dashboard only is showing intern choices for null and 11. Where is the version where we can see all interns? image

@ExperimentsInHonesty the data source was broken, it has been fixed and all the intern numbers are showing now

Rabia2219 avatar Oct 10 '24 17:10 Rabia2219

@Rabia2219 Please explain the tabs on the TWE: IS22 Participant Record (Responses) spreadsheet by updating the instructions tab. and let us know here

@ExperimentsInHonesty Done

Rabia2219 avatar Oct 10 '24 17:10 Rabia2219

@ExperimentsInHonesty Although the dashboard is working as expected, there is some additional processing that is required for the data to be accurate. ETA: Tuesday, October 15th

Rabia2219 avatar Oct 10 '24 18:10 Rabia2219

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, October 8, 2024 at 12:05 AM PST.

HackforLABot avatar Oct 11 '24 07:10 HackforLABot

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, October 15, 2024 at 12:04 AM PST.

HackforLABot avatar Oct 18 '24 07:10 HackforLABot

Notes

  • the data has been processed and the dashboard is working as intended
  • ~new org requirements gathered, delivery ETA Tuesday, October 22nd~ - on hold

Rabia2219 avatar Oct 20 '24 12:10 Rabia2219

@Rabia2219 when we meet next week, we also need to do the following

  • [ ] review the outstanding items in this comment https://github.com/hackforla/website/issues/7509#issuecomment-2381575569

Bonnie needs to Talk with Data Science CoP leads for formal names of the type of analysis we want to do in the HfLA website: Dashboard Roadmap: Participant Record

ExperimentsInHonesty avatar Oct 20 '24 16:10 ExperimentsInHonesty

@sofiatajide Add all the links from the participant record issues to this comment; don't copy in duplicates.

Issues

ExperimentsInHonesty avatar Oct 20 '24 16:10 ExperimentsInHonesty

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, October 22, 2024 at 12:04 AM PST.

HackforLABot avatar Oct 25 '24 07:10 HackforLABot

Discuss with @Rabia2219

  • [x] Participant Record
  • [x] Figure out where these files should be located
    • [ ] option 1 items are staying in this folder with a shortcut in the dashboards folder to the current folder
    • [x] option 2 moving to the Dashboards Google Drive with a shortcut in the original folder

ExperimentsInHonesty avatar Oct 27 '24 16:10 ExperimentsInHonesty

Interview details

  • This interview was not relevant. I have moved the info from this comment to this issue https://github.com/hackforla/website/issues/7539

ExperimentsInHonesty avatar Oct 27 '24 16:10 ExperimentsInHonesty

Discuss with Rabia

This spreadsheet (IS21: TWE: Intern Roster - including applicants) has the intern names and numbers of the applicants

  • [x] We need to discuss if it's even possible to de-identify this sheet by replacing all the names with numbers

Completed de-identifying and its been added to resources

ExperimentsInHonesty avatar Oct 27 '24 16:10 ExperimentsInHonesty

  • [x] Go through all the files that we have indicated are "deprecated" (in this comment and add the following to the end of their filename
- deprecated

ExperimentsInHonesty avatar Oct 27 '24 16:10 ExperimentsInHonesty

On Monday

Added some info to document re this topic

ExperimentsInHonesty avatar Oct 27 '24 16:10 ExperimentsInHonesty

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, October 29, 2024 at 12:04 AM PST.

HackforLABot avatar Nov 01 '24 07:11 HackforLABot

  1. Progress: Created a new issue https://github.com/hackforla/website/issues/7640
  2. Blockers: none
  3. Availability:
  4. ETA:
  5. Pictures or links* (if necessary): N/A
  • remember to add links to the top of the issue if they are going to be needed again.

ExperimentsInHonesty avatar Nov 03 '24 17:11 ExperimentsInHonesty

  • Requirement update https://github.com/hackforla/website/issues/7640#issuecomment-2486583954

ExperimentsInHonesty avatar Nov 06 '24 20:11 ExperimentsInHonesty

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, November 4, 2024 at 11:04 PM PST.

HackforLABot avatar Nov 08 '24 07:11 HackforLABot

  1. Progress: worked on Spreadsheet Dashboard - Participant Record - Competitive or Comparative Analysis Template to add checkboxes for each of the features of the versions
  2. Blockers: none
  3. Availability: at least 6 hrs
  4. ETA:
  5. Pictures or links* (if necessary): N/A
  • remember to add links to the top of the issue if they are going to be needed again.

sofiatajide avatar Nov 10 '24 17:11 sofiatajide

@sofiatajide

  • [x] Create issue: https://github.com/hackforla/website/issues/7759
    • Add issue link to the following issues, where indicated in the top part
      • [x] https://github.com/hackforla/website/issues/7640#issue-2616739845
      • [x] https://github.com/hackforla/website/issues/7710#issue-2641751322
  • [x] Create issue: https://github.com/hackforla/website/issues/7761
    • Add issue link to the following issues, where indicated in the top part
      • [x] https://github.com/hackforla/website/issues/7640#issue-2616739845
      • [x] https://github.com/hackforla/website/issues/7509#issue-2543914963

ExperimentsInHonesty avatar Nov 19 '24 19:11 ExperimentsInHonesty

Instructions
  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."
  1. Progress: Populated sample sheet data (resource 1.01) with data from resource 1.03. issue #7710 Populated sample sheet data (resource 1.02) with data from resource 1.04. issue #7710 Created new Issue #7759 Created new Issue #7761
  2. Blockers: none
  3. Availability: at least 6 hrs
  4. ETA:
  5. Pictures (if necessary): N/A

sofiatajide avatar Nov 24 '24 17:11 sofiatajide

We created a new page in the Hack for LA Data Science repo wiki, called Dashboard Resources - this page has all the tutorial links from each of the issues

ExperimentsInHonesty avatar Nov 27 '24 21:11 ExperimentsInHonesty

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, December 30, 2024 at 11:04 PM PST.

HackforLABot avatar Jan 03 '25 07:01 HackforLABot

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 6, 2025 at 11:04 PM PST.

HackforLABot avatar Jan 10 '25 07:01 HackforLABot

@sofiatajide

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 13, 2025 at 11:04 PM PST.

HackforLABot avatar Jan 17 '25 07:01 HackforLABot