Create Table: organization (formerly brigade)

[ericvennemeyer]

Overview

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

Resources/Instructions

• See People Depot Resources wiki page for links
  • ERD
  • Table and Field Definitions
  • API Endpoint
• See the wiki page for instructions.

Description

List of organizations (formerly brigades)

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()
   • time_zone - 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)

   • recurring_event (one-to-many) Update Table: recurring_event (rename to event) #173
   • user_check (one-to-many) Create Table: user_check #80

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

   • None

[Neecolaa]

This table will be renamed to organization

Updates needed:

• Update Issues
  • this issue
  • connected issues
    • recurring_event
    • user_check
• Update ERD
  • name
  • connected fields
• Update Spreadsheet
  • table tab
    • name
    • connections
  • fields tab
    • name
    • connected fields (brigade_id changed to org_id)

After updates

• remove erd/ss label
• return to prioritized backlog
• hide this comment

[Neecolaa]

Questions:

• Do we want to create a new issue for updating the event table? Or should we wait until we know what we're doing with Epic: Redesign event schema #88
• Are we renaming the permission type adminBrigade (to adminOrg or something similar)?

[fyliu]

We talked about the first one at the meeting but I want to comment so it's recorded.
We don't need to wait for the event schema redesign. Event will still reference organization in the same way. So it's fine to create an issue now to update the event table.

The other thing we talked about was whether we want to create the relationship between organization and affiliate, whether it's a sponsor and/or partner. Currently, there's no relationship and the affiliate object just has the fields is_org_partner and is_org_sponsor in it.

[ExperimentsInHonesty]

@Neecolaa do you feel you have enough answers in order to finish this issue?