Create Table: user_employment_change

[fyliu]

Overview

We need to create the user_employment_change 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

• [x] identify and document table description (see spreadsheet under Resources)
  • [x] if not, reach out to PD leads
• [x] 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)
• [x] 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

Missing

• from the ERD, it looks like the table records the time and type of a user's employment change
• from the table name, it feels like each record should record a single employment change, similar to the job history in a resume or CV. the last_updated field suggests that a record can be updated. This field doesn't make sense.

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)

   • Missing

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

   • (PK) id - int
   • (FK) user_id - int
   • (FK) soc_detailed_id - int
   • last_updated - DateTimeField

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)

   • [ ] soc_detailed (many-to-one)
   • [ ] user (many-to-one)

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

   • None

[fyliu]

Problems:

1. Missing description
   1. See discussion above
2. Missing data fields in spreadsheet
   1. I added the ERD fields to the spreadsheet
3. last_updated is a confusing name
   1. last_updated sounds like it pertains to the database record of the change rather than the date the change happened
   2. maybe something like "change_date", or "new_employment_date", or "employment_change_date", or "employment_updated_on"

[Neecolaa]

Action items:

• [ ] Change last_updated to employment_change_date on SS
• [ ] Change last_updated to employment_change_date on ERD
• [ ] Clarify description

After these are done, the architect labels can be removed and replaced with back end labels