This PR adds a new app, "units", along with an identically-named model, which intends to serve as a bridge between our program data and teledata for colleges, departments, and organizations.
Because "organizations" and "departments" are loosely (i.e. not) defined, the Unit model is similarly loosely-defined--a Unit can map to an existing College in the programs app, as well as Departments or Organizations in teledata. Units can have one parent Unit and many child Units.
The new map-units command will generate fresh Units and perform the actual mapping process between program data and teledata. Existing Units are deleted during this step--the mapping script is not at a point yet where we can accurately make matches against existing Units.
This PR also includes some admin interface adjustments to make it easier to navigate from Colleges/Departments/Organizations and their respective Units, as well as between parent and child Units.
This PR adds a new app, "units", along with an identically-named model, which intends to serve as a bridge between our program data and teledata for colleges, departments, and organizations.
Because "organizations" and "departments" are loosely (i.e. not) defined, the Unit model is similarly loosely-defined--a Unit can map to an existing College in the programs app, as well as Departments or Organizations in teledata. Units can have one parent Unit and many child Units.
The new map-units command will generate fresh Units and perform the actual mapping process between program data and teledata. Existing Units are deleted during this step--the mapping script is not at a point yet where we can accurately make matches against existing Units.
This PR also includes some admin interface adjustments to make it easier to navigate from Colleges/Departments/Organizations and their respective Units, as well as between parent and child Units.