SDIS data model extension: add Division

[florianm]

Problem

This issue combines changes to the data model and how they integrate.

New: Division

A new concept, the Division, shall be added to SDIS. Divisions shall match the corporate structure exactly. Science Projects are expected from Divisions BCS, RFMS, CEM, BGPA, ZPA, RIA.

SDIS Programs shall belong to exactly one Division.

The currently existing Programs shall all belong to BCS.

Kings Park Science and Perth Zoo Science are two Programs underneath BCS, although they are conducted by members of BCPA or ZPA, respectively. Additionally, members of BGPA, ZPA, or RIA could conduct Science Projects outside BCS scope and instead under affiliation with BGPA, ZPA, or RIA.

As SDIS Programs correspond to the administrative units directly underneath Divisions, and DBCA officers can create Projects under any Program, each Program should belong to exactly one Division.

Projects belong to exactly one Program

With the precedent of existing SDIS Projects run in collaboration between several Programs, it is sufficient to link each Project to its main (if several) or only Program. This simplifies the approval structure.

Users belong to exactly one Division

Users may need to create a Project for their own division, or for another division. This is possible for members of BGPA or Perth Zoo, who could participate in projects which are either classified under Kings Park Science or Zoo Science (both BCS), or regional projects (under the BGPA Service Division or Perth Zoo Service Division).

If future reporting requirements should include Projects beyond BCS, the linkage between DBCA officers, their Projects, Programs, and Divisions is represented through Project Team Membership. Any grouping can be presented through this existing data structure.

Therefore, SDIS Users must not be restricted to any single Division, and it is not necessary to maintain SDIS Users’ affiliation with one or many Divisions.

Feature

• [x] Add model "Division"
• [x] Programs are owned by exactly one Division: add FK Program.division
• [x] Create Divisions: BCS, RFMS, CEM, BGPA, ZPA, RIA
• [x] Link existing Programs to BCS
• [x] Create Programs for other Divisions: nine RFMS Regions, five CEM branches, etc. Nominate respective leader as Program leader.
• [x] Add FK User.division to link a User to their Division.
• [x] When creating a new Project, DO NOT restrict available Programs to User.division. (Could do, but explicitly allowed in requirements)

[florianm]

Added CEM and RFMS units to https://sdis-uat.dbca.wa.gov.au/pythia/program/. Did not yet add BGPA, RIA, ZPA units as this is only UAT. Once confirmed in scope, can add all to PROD.

[florianm]

Discuss:

• How do output programs and research functions relate to projects outside of BCS?
• If they don't apply to other projects, do we get away with "select one if this is a BCS project"?

[florianm]

A new project defaults to the User's Program, but the user can choose any other program. Since every Program links to its Division, the linkage between a User's Division and a new Project's Division is given through the default program.