generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Labels
PII: TRUETable or function has or uses Personally Identifiable Information (PII)Table or function has or uses Personally Identifiable Information (PII)complexity: mediumStraightforward but some complexity (e.g., involves multiple files)Straightforward but some complexity (e.g., involves multiple files)feature: table creationp-feature: permissionsrole: back ends: VRMSstakeholder: VRMSstakeholder: VRMSs: orgstakeholder: the org (includes stats)stakeholder: the org (includes stats)size: 1ptCan be done in 4-6 hoursCan be done in 4-6 hours
Milestone
Description
Dependency
- Create Table: user permission #22
-
Evaluate django-simple-history for history tables #181- no longer applies
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
-
- If all Issues listed are closed (or there are no FKs), then skip the next 3 steps
Resources/Instructions
- See People Depot Resources wiki page for links
- ERD
- Table and Field Definitions
- API Endpoint
- See the wiki page for 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 |
- In ERD only (having items here indicates a mismatch, which requires a review)
- None
FK status
- Create Table: permission_type #24
- Create Table: practice_area #63
- Create Table: project #16
- Create Table: User #15
Associated Tables
-
Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)
- permission_type (many-to-one) Create Table: permission_type #24
- practice_area (many-to-one) Create Table: practice_area #63
- project (many-to-one) Create Table: project #16
- user (many-to-one) Create Table: User #15
-
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)Table or function has or uses Personally Identifiable Information (PII)complexity: mediumStraightforward but some complexity (e.g., involves multiple files)Straightforward but some complexity (e.g., involves multiple files)feature: table creationp-feature: permissionsrole: back ends: VRMSstakeholder: VRMSstakeholder: VRMSs: orgstakeholder: the org (includes stats)stakeholder: the org (includes stats)size: 1ptCan be done in 4-6 hoursCan be done in 4-6 hours
Type
Projects
Status
🏗In progress-actively working