You are here
IGS Database
Description: A "managed" IGS database. We manage local data for PhD students such as location and milestones. This information is predominantly held in a "single admin user developed and managed" system although some information is also held in the School Database. Most of this information will not in the future be held in EUCLID. In one sense this should be part of the EUCLID Informatics Enhancements project, however, due to its implementation plan it is being separately tracked.
Deliverables: An IGS database in PostgreSQL managed by School computing staff. We are not at this stage defining any common interface system to the IGS database. We expect the continuation of the Access Frontend at least initially (the School Database Revamp project may provide an alternative once complete).
Customer: IGS (Anna Hobbes)
Case statement: The current IGS support database is a mixture of the School Database and an Access Database (personal on one machine with only one admin staff having experience and knowledge of using and running it). The Access Database is slowly being migrated to a postgresql service for testing however the IGS could not be responsible for where this associates with central data (not just applicable to PhD students). So, to avoid duplication of data and effort and to ensure the IGS have a centrally managed database with better support, we should take this on.
Status:
Timescales: TBD
Priority: High - external request.
Time: Less than one month.
Proposal: See plan.
Resources: Effort.
Plan: Review IGS requirements. Develop an "approved" data model. Implement data model in PostgreSQL. Populate with existing data from the School Database and IGS Access Database. Re-develop interfaces to other School systems (such as web page generation and mailing lists) - these will probably use existing technology until the School Database Revamp goes ahead.
Dependencies: The School Database Revamp project to a certain extent. The University web site re-development to a certain extent as well. Local systems using existing information in the IGS School Database (eg. PhD contact information on generated web pages).
Risks: Agreeing a model. Requirements "expand". Making sure what is done would be compatible with any future central database technology.
Milestones
| Proposed date | Achieved date | Name | Description |
|---|---|---|---|
| 2009-04-30 | DataModel | Produce agreed data model. | |
| 2009-04-30 | Model | Implement data model in PostgreSQL database | |
| 2009-04-30 | Populate | Populate model with existing IGS data | |
| 2009-05-31 | Access | Setup local Access access to the model in PostgreSQL | |
| 2009-06-30 | Systems | Re-implement local processes to use new IGS data model and PostgreSQL database. |