Skip to content

Create Table: permission_history #37

@Neecolaa

Description

@Neecolaa

Dependency

Overview

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

  • 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
  • Check to see if open issues in FK status below
    • If all Issues listed are closed (or there are no FKs), then skip the next 3 steps
      • comment out the code after you create it (see FK Status below for open/closed state)
      • add an action item on the open issue to uncomment the code line you commented out when that issue's table is created.
      • Provide your file and line number as a permalink under resources in that issue

Resources/Instructions

Description

When a permission is overwritten in #22 a record of it will be stored in this table instead of being deleted.

All records that have dateEnded from the Permission table will be moved here 1:12 AM Pacific Time

Data Fields

Name Type FK Table FK table Issue(s)
user int user #15
project int project #16
permission_type int permission_type #24
practice_area int practice_area #63
granted timestamp
ended timestamp
created_by int - User ID of who first granted the permission
updated_by int - User ID of who last changed the permission
  1. In ERD only (having items here indicates a mismatch, which requires a review)
    • None

FK status

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)

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

    • None

Metadata

Metadata

Assignees

Labels

PII: TRUETable or function has or uses Personally Identifiable Information (PII)complexity: mediumStraightforward but some complexity (e.g., involves multiple files)feature: table creationp-feature: permissionsrole: back ends: VRMSstakeholder: VRMSs: orgstakeholder: the org (includes stats)size: 1ptCan be done in 4-6 hours

Type

No type

Projects

Status

🏗In progress-actively working

Relationships

None yet

Development

No branches or pull requests

Issue actions