EUGEX was originally created to provide student data to from SITS to other university systems.  The principle aim of the system was to rationalise the plethora of interfaces that previously existed onto the student record via a generic system.  To reduce the potential performance impact on the main SITS database, EUGEX was implemented on a separate server, using Oracle Streams to copy the relevant SITS data in near real-time before processing it in the EUGEX system proper. In some cases these new interfaces provided by EUGEX replicated the existing feeds from DACS.  Since then, EUGEX has also been used to provide information to new systems (PPMD, PebblePad, ECA, ThankQ) and to provide the BOXI universe for ESSMU.

The history of EUGEX has been that several projects have taken locally optimal decisions that have led to an inconsistent overall architecture and some operational problems.  Users and support staff have experienced some problems with EUGEX as currently implemented.  The dependencies and procedures seem to be more complex than initially planned and documentation has not kept pace with development.

To address these problems, this project will review the EUGEX architecture and produce guidelines for the future development of data feeds from the student record to downstream systems.

Please see http://www.old.projects.ed.ac.uk/areas/student/sacs/STU219/index.shtml for information related to this project before 01-Aug-2012.