Update Table: recurring_event (rename to event)

[Neecolaa]

Overview

We need to update the recurring_event table model (now the event table model) to utilize the practice area table instead of the outdated role table.

Details

The initial model issue is #14

Discussion leading to this change is here: https://github.com/hackforla/peopledepot/discussions/170

Action Items

• [x] Update schema information
  • [x] add/remove given columns from Entity Relationship Diagram (ERD)
  • [x] add/remove given columns from PD: Table and Field definitions
  • [x] make additional schema changes (if needed)
  • [x] remove the ERD/SS update label after these changes are made.
    • Permission is needed to edit the ERD and table spreadsheet.
• [x] Rename Django model
• [x] Update existing Django model
• [ ] Write a test for the new relationships this model will have with other models (e.g., creating a user and assigning them a set of permissions on a project) if any.
• [x] Update API end point
• [x] Update API unit tests
• [ ] Document the endpoint in Swagger
• [x] Take #88 out of the ice box

Changes Needed

Columns to Remove

• [x] must_roles - int[] (role_id)
• [x] should_roles - int[] (role_id)
• [x] could_roles - int[] (role_id)

Columns to Add

• [x] must_attend - JSON[]
• [x] should_attend - JSON[]
• [x] could_attend - JSON[]

Additional Changes

• [x] Change name from recurring_event to event
  • [x] in schema
  • [x] in django
• [x] Add example JSON to the ERD somehow
  • This could be handled by adding a stickynote to the ERD, or maybe a link to a new tab in the spreadsheet. JSON Example:

    [{practice_area: engineering, permission_level: practiceLeadProject},{practice_area: pm, permission_level: practiceLeadProject}]

    Resources

• See People Depot Resources wiki page for links
  • ERD
  • Table and Field Definitions
  • API Endpoint

[fyliu]

• I forgot about this issue. Thanks @Neecolaa for pointing this out. This one should've been done before #88. I was working on #88 and it

  • deletes the event and event_history tables and
  • renames recurring_event to event.

• So @Neecolaa applied the schema changes from this issue to the new event table. I think we can close this issue and update and implement #47. That table hasn't been made into a django model yet.

Related tasks:

• [ ] update #47 with the new table structure already part of #88
• [x] create issue to remove recurring_event table and django model if it's not already created #180
• [x] write note in #49 about it being removed

[Neecolaa]

Pull request #85 already added the recurring_event table. It seems more worth it to just rename that table, rather than removing it now and later replacing it with a slightly different event table.

Update Table issues are only for when a table is already created. If not, we just revise the existing issue and leave a comment.

[fyliu]

Okay, We'll do the rename then. I was thinking of going the other way. We'll see if django is smart enough to do a database rename or if it'll drop and create a new table.

I was originally thinking it's simpler to redo this from scratch in 1 step rather than make these changes and then add the recurrence field in #88 which would be 2 steps. But now I see it's probably better to make smaller changes.

[fyliu]

Looks like some changes in this issue wasn't implemented in code. I'm creating a new issue for them.