Separate databases

[sheggen]

There are essentially four databases needed for the system:

1. The login server (BC uses Shibboleth). This provides the application with the logged in user identity and authorization.
2. The main db. This provides the application with active work college information (student's current and past positions, approval status, ...) and is the database we created for the system.
3. The Tracy Ultratime system. This provides the application with all static work study information (all available positions, all departments, all supervisors, ...). This database is external to the existing application, but Peewee models exist for it already.
4. Banner. This provides the application with a database to hold official records of employment. After a student is hired in our system, the record is added to Banner.

Item 1 should be handled probably through Flask login. The implementer should be able to choose the type of login service they want to use (local login, shibboleth, LDAP, ...).

Item 2 is fully within the existing application. No changes should be needed here.

Item 3 was implemented for testing/development purposes. It should be fully implementable if the user choses to use it (on install).

Item 4 is completely external, with the exception of hooks to write to that database. It should be integrated into the application as well. It only exists because our LSF system had to be able to work with the existing records which were held here. In theory, it could go away (option to make it go away?) and the existing application serves as the record of hiring and firing of students.