Update Table: sponsor_partner

Overview

We need to update the sponsor_partner table model to accommodate for different sponsor/partner models (project vs org level).

Because we can have project level sponsors and partners that are not org-level sponsors/partners, we are going to remove the is_sponsor boolean and replace it with both an is_org_sponsor boolean and an is_org_partner boolean. Discussion about this is also here: https://github.com/hackforla/peopledepot/issues/65#issuecomment-1563579917

Originally posted by @Neecolaa in https://github.com/hackforla/peopledepot/issues/76#issuecomment-1563672260

Details

The initial model issue is #76

Discussion leading to this change is here: https://github.com/hackforla/peopledepot/issues/65#issuecomment-1563579917

There can be sponsors or partners at the org level as well as for individual projects. The same entity cannot be both a sponsor and a partner for a single project, but can be both a sponsor and a partner to the organization itself. The sponsor/partner levels are:

project partner
project sponsor
org partner
org sponsor

Action Items

[x] Update schema information
- [x] add/remove given columns from Entity Relationship Diagram (ERD)
- [x] add/remove given columns from PD: Table and Field definitions
  - Permission is needed to edit the ERD and table spreadsheet.
[ ] Update existing Django model
[ ] 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
[ ] take #182 out of the ice box if this is the last dependency

Changes Needed

Columns to Remove

[x] is_sponsor - boolean

Columns to Add

[x] is_org_sponsor - boolean
[x] is_org_partner - boolean

Additional Changes

None

Resources

See People Depot Resources wiki page for links
- ERD
- Table and Field Definitions
- API Endpoint

hackforla / peopledepot

Update Table: sponsor_partner #162