...
The reference architecture is Indiana/INSITE from collaboratives as seen in Multi-Instance Reference Architectures/wiki/spaces/OTD/pages/26575389:
- One EdFi_Admin
- One EdFi_Security
- One API, deployed and configured in DistrictSpecific mode.
- Mulitple ODS databases, one per district.
- One Admin App installation, capable of managing all the defined district databases.
- A given Admin App user is limited to which ODS instance databases they access.
...
Subsequent Enhancement: Once that's implemented, the First Time Setup process could be enhanced to cut down on the initial setup of the already-present District databases: if the list of existing database can be inferred or queried (they correspond with EdOrg Ids afterall), First Time Setup could attempt to register them automatically. Then, an admin would only have to register an instance if a new database were to be set up for the collaborative.
Ticket Tracking
See the Epic
for the high level layout of ticket dependencies, and for the individual tickets spelling out the implementation plan. Jira Legacy server Ed-Fi Issue Tracker serverId e04b01cb-fd08-30cd-a7d6-c8f664ef7691 key AA-602