Create Table: event_history

[ericvennemeyer]

Overview

We need to create the event_history table so that we can update a shared data store across hackforla.org, vrms, civictechjobs, and tables (onboarding) project.

Details

A table and a model are the same thing

Action Items

• decide if we're using django-simple-history for this table
  • release Create Table: permission_history #37 from ice box
  • release Create Table: project_status_history #67 from ice box
• identify and document table description (see spreadsheet under Resources)
  • if not, reach out to PD leads
• compare and check off the data fields (below) against the ERD. Note any fields in the ERD that's missing from the list. (see Resources)
• compare the check off associated tables (below) against the ERD. Note any associated tables in the ERD that's missing from the list (see Resources)
• create a single model in Django (defining schema)
• write a test for the relationships this model will have with other models (e.g., creating a user and assigning them a set of permissions on a project).
• write an API end point
• write API unit tests
• document the endpoint

Resources/Instructions

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

Description

A history of events

Data Fields

1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)

   • (PK) id - int - Record Id
   • (FK) event_id - int - Record Id
   • (FK) project_id - int - Record Id
   • description - varchar
   • video_conference_url - url varchar
   • (FK) location_id - int - Record Id
   • alt_location_name - varchar
   • alt_address1 - varchar
   • alt_address2 - varchar
   • alt_location_city - varchar
   • alt_location_state - varchar(2)
   • alt_location_zip - varchar
   • start_date_time - timestamp
   • duration_in_min - int
   • (FK) recurring_event_id - int - Record Id
   • created - timestamp
   • check_in_ready - boolean

2. In ERD only (having items here indicates a mismatch, which requires a review)

   • None

Associated Tables

1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)

   • location (many-to-one)
   • project (many-to-one)
   • recurring_event (many-to-one)
   • event (implied one-to-one)

2. In ERD only (having items here indicates a mismatch, which requires a review)

   • None

[ExperimentsInHonesty]

@Neecolaa will create a requirements for this so @fyliu can evaluate the plug in

[fyliu]

django-simple-history is the plug-in Django app

[fyliu]

@brdeleon this issue is not ready for backend to work on yet. Please find one that has the smiley emoji in the title.

You can tell if it's ready for backend by looking at the "role: ..." tag in the issue. I see there's only one ready issue left. I'll check the board to see if more issues are ready to work on.

[fyliu]

This table is being removed in the new event schema design

• Epic: Redesign event schema #88

The ERD and spreadsheet is already changed to remove this table.

There's no need to remove code since this one was not yet coded.

We should move any unfinished tasks into new issues and close this one:

• create issue to evaluate django-simple-history plugin for history models - Evaluate django-simple-history for history tables #181

[fyliu]

Closing this since there's nothing more to do. This table has be designed out because we no longer want to have a table to hold past individual event instances. Our new design will have recurrences information in the event itself.