A Project funded by JISC: 2002-2005
IoNode
|
Key Documents: |
After completion of the learner record and redesigned business processes specifications, work turned to the development of technical specifications for the supporting SHELL infrastructure (the database, portal and hub) and the transactions required for communication to and from the hub.
Unfortunately, there was a lack of agreement with various suppliers regarding the open source use of their code, and this, together with earlier delays caused by the difficulties in securing a replacement team leader was to cause delays in implementation.
Phosphorix proposed the development of an interface agent (ioAgent) to act as the means of communication between student record systems and the SHELL hub. By mid 2003, the funding for the purchase of ioAgents was agreed, with all bar one of the partners proposing to use this route. (One partner wished to develop their own interface to the hub). Phosphorix, in co-operation with ETL Solutions undertook the development of this interface agent, producing a specification for message exchange. Phosphorix suggested the use of a native open source database called Xindice for the development of the learner record database.
Each ioAgent required a 'plug-in' to interface to the particular record system in use by the project partner. Capita provided Phosphorix with an API for Unit-e, but stated that they did not plan to develop a plug-in for HEMIS. At that time, the University Registry were considering Unit-e as a replacement for HEMIS. Although HEMIS was not scheduled for replacement until after the end date for SHELL, there was an expectation that SHELL would be the vehicle to deliver partnership data to HEMIS. Furthermore, despite earlier expressions of interest, other suppliers declined to provide plug-ins for systems used in partner colleges, leaving this development to be borne by the project.
- test bed
- admin portal
Project Website managed by Jon Yorke