Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Table: location #44

Closed
18 of 21 tasks
Neecolaa opened this issue Sep 3, 2022 · 1 comment · Fixed by #135
Closed
18 of 21 tasks

Create Table: location #44

Neecolaa opened this issue Sep 3, 2022 · 1 comment · Fixed by #135
Assignees
Labels
complexity: missing feature: table creation p-feature: events PII: TRUE Table or function has or uses Personally Identifiable Information (PII) role: back end s: hackforla.org stakeholder: hackforla.org website s: VRMS stakeholder: VRMS size: 2pt Can be done in 7-12 hours

Comments

@Neecolaa
Copy link
Member

Neecolaa commented Sep 3, 2022

Overview

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

  • add issue link to the tables tab of the spreadsheet
  • identify and document table description (see spreadsheet under Resources)
  • 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)
    • Review and correct discrepancies
  • 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

Description

Location to be used in event and recurring event.

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
    • name - varchar
    • address_line1 - varchar
    • address_line2 - varchar
    • city - varchar
    • state - varchar
    • zip - varchar
    • phone - varchar
  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)

    • event (one-to-many)
    • event_history (one-to-many)
    • recurring_event (one-to-many)
  2. In ERD only (having items here indicates a mismatch, which requires a review)

@Neecolaa
Copy link
Member Author

Neecolaa commented Sep 3, 2022

Since the project table does have project linked to location, I'm going to assume it was just overlooked when I was writing in the relationships into the spreadsheet. I'll fix it now, but I did want a record of the discrepancy just in case.

  • Add relationship between location and project to location's list in the spreadsheet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: missing feature: table creation p-feature: events PII: TRUE Table or function has or uses Personally Identifiable Information (PII) role: back end s: hackforla.org stakeholder: hackforla.org website s: VRMS stakeholder: VRMS size: 2pt Can be done in 7-12 hours
Projects
Status: ✅Done
4 participants