hackforla / hackforla/peopledepot

Create Table: Event Occurrence Change

Open
#614 1 comment 0 reactions 0 assignees View on GitHub
complexity: missing feature: table creation p-feature: events PII: TRUE ready for dev lead role: back end s: CTJ s: hackforla.org s: tables s: VRMS size: 2pt
Dominant language
Python
Stars
14
Forks
37
Avg merge
9d 15h
Merged PRs (30d)
5

Description

### Overview

We need to create the eventoccurencechange 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 if the table has a description (see spreadsheet under Resources)
- [ ] If not, reach out to PD leads
- [ ] Identify and document (below) what other tables are associated (see ERD under 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 in Swagger

### Resources/Instructions

- See [People Depot Resources wiki page](https://github.com/hackforla/peopledepot/wiki/Resources-and-Links) for links
- ERD
- Spreadsheet: [PD: Table and field explanations, Current Field Permission tab](https://docs.google.com/spreadsheets/d/1x_zZ8JLS2hO-zG0jUocOJmX16jh-DF5dccrd_OEGNZ0/edit?gid=749942651)
- API Endpoint
- See [this Wiki page](https://github.com/hackforla/peopledepot/wiki/Create-Table-issues-data-gathering-workflow) for instructions on the data-gathering workflow for Create Table issues
- Spreadsheet [PD: Table and field explanations, Current Field Permissions](https://docs.google.com/spreadsheets/d/1x_zZ8JLS2hO-zG0jUocOJmX16jh-DF5dccrd_OEGNZ0/edit?gid=749942651#gid=749942651)

### Items to document (referenced above)

- [ADD ITEMS TO DOCUMENT]

#### Description

- Contains user-modified event data fields for an event occurrence that correspond to the parent event's fields. Unchanged fields will be null.

### Data Fields

- [ ] Copied from spreadsheet and confirmed according to ERD

Name | Type | FK Table | FK Table Issue(s) | Nullable | Comment
-- | -- | -- | -- | -- | --
event | uuid | event | #14 & #173 | True | points to parent event. this doesn't seem necessary?
start_time | DateTimeField | event | #14 & #173 | True | should be start_time_change like the other fields?
name_change | varchar | | | True |
description_change | varchar | | | True |
start_time_change | DateTimeField | | | True |
duration_in_min_change | int | | | True |
video_conference_url_change | URLField | | | True |
location_change | UUID | | | True |
additional_info_change | varchar | | | True |
must_attend_change | JSON[ ] | | | True |
should_attend_change | JSON[ ] | | | True |
could_attend_change | JSON[ ] | | | True |

### FK status
- #145
- #173

#### Swagger Endpoint Link

- [ADD SWAGGER ENDPOINT LINK]

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.