Skip to content

HfLA: Summer 2025 Potluck: Second Status Check for 'Not OK to Attend' #53

Description

@Rabia2219

Overview

We need to recheck the status of the people marked 'Not OK to Attend' in the first status check so that we can determine if they are members otherwise, mark which message to send them

Action Items

  • open resource 1.0
  • if cell A2 is green and has the message Status check is up-to-date
    • copy the message in a new comment
      - Date: 
      Status check is up to date for Not OK to Attend
      
    • add the day's date
    • save the comment
  • if cell A2 is red and has the message Need to perform status check
    • copy the message in the copy block in a new comment
    • add the day's date
    • complete the tasks
      #### Secondary Status Check for 'Not OK to Attend'
      - Date: 
      - [ ] open resource 2.0
      - [ ] for rows with no data in column K, open their Meetup Profile link in column D
      - [ ] click on `Membership details` (right side on picture, under `Shared groups`)
      - [ ] scroll down to `Attendance history` (shows all the HfLA events they RSVPed for)
      - [ ] if it shows that they RSVPed for any `Hack for LA Civic Tech Volunteer Intro and ONBOARDING (online)` 
        - [ ] access resource 3.0
        - [ ] sort it by the date shown on Meetup (if there are multiple dates, choose the latest one)
        - [ ] check to see if the name on Meetup matches any name in the filtered list
        - if not found,
          - [ ] go back to resource 2.0
          - [ ] in column K, add the date of onboarding from Meetup, using the YYYY-MM-DD format
          - [ ] access the `not_ok_to_attend` tab
          - [ ] check the box in either column F or G, conditional on guests
          - [ ] access the `messagingtypes` tab
          - [ ] copy the appropriate messaging type
          - [ ] paste it as a link in column K for the name
          - [ ] add the month in column E
      - [ ] if it shows that they attended a special event only (e.g. LinkedIn Workshop) with a <img width="40" height="20" alt="Image" src="https://github.com/user-attachments/assets/d5c62f79-6648-4316-af93-f257570c5a66" />
        - [ ] go back to resource 2.0
        - [ ] in column K, add the date of the special event from Meetup, using the YYYY-MM-DD format
        - [ ] access the `not_ok_to_attend` tab
        - [ ] check the box in column J
        - [ ] access the `messagingtypes` tab
        - [ ] copy the message type `Attended Special Event Only`
        - [ ] paste it as a link in column K for the name
        - [ ] add the name of the special event in column E
      - [ ] if it shows that they have RSVPed for the picnic only with a <img width="40" height="20" alt="Image" src="https://github.com/user-attachments/assets/c32b1ddd-9edd-4434-9770-4c4f4d37b826" />   
        - [ ] go back to resource 2.0
        - [ ] in column K, add `none`
        - [ ] access the `not_ok_to_attend` tab
        - [ ] check the box in column I
        - [ ] access the `messagingtypes` tab
        - [ ] copy the message type `Signed Up for Picnic Only`
        - [ ] paste it as a link in column K for the name
      - [ ] if it shows that they will attend a future `Hack for LA Civic Tech Volunteer Intro and ONBOARDING (online)` event with a <img width="40" height="20" alt="Image" src="https://github.com/user-attachments/assets/c32b1ddd-9edd-4434-9770-4c4f4d37b826" />
        - [ ] go back to resource 2.0
        - [ ] in column K, add the date of the future onboarding from Meetup, using the YYYY-MM-DD format
        - [ ] access the `not_ok_to_attend` tab
        - [ ] check the box in column I
        - [ ] access the `messagingtypes` tab
        - [ ] copy the message type `Signed Up for a Future Onboarding`
        - [ ] paste it as a link in column K for the name
        - [ ] add the month in column E
      - [ ] check #51 for the assignee
      - [ ] tag them in a new comment and let them know that new messages need to be sent out
      

Resources/Instructions

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
New Issue Approval

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions