Create DTO models for working groups data
To better support Working Groups, we should be using persisted data rather than a hardcoded JSON list of entities. This will enable us to manage this remotely in the future through a login and UI.
Tables
WorkingGroup
| Column | type | Nullable |
|---|---|---|
| alias | string (PK) | X |
| title | string | X |
| status | enum * | X |
| parentOrganization | string | X |
| logo | string (URL) | |
| description | string |
*: Status enum should allow for proposed, active, and archived
WorkingGroupResources
| Column | type | Nullable |
|---|---|---|
| id | int (auto-increment, PK) | X |
| workingGroup | string (FK) | X |
| charter | string | |
| website | string | |
| members | string | |
| sponsorship | string | |
| contactForm | string |
WorkingGroupParticipationAgreements
| Column | type | Nullable |
|---|---|---|
| id | int (auto-increment, PK) | X |
| workingGroup | string (FK) | X |
| type | enum * | X |
| documentId | string | X |
| string |
*: Type enum should allow for organizational and individual currently
WorkingGroupLevels
| Column | type | Nullable |
|---|---|---|
| id | int (auto-increment, PK) | X |
| workingGroup | string (FK) | X |
| relation | string | X |
Edited by Martin Lowe