Overview
Background
The LMP002 project has been initiated for Implementation of a next generation Library Services platform to replace the Voyager Library Management System, which has been in place since 1999. The scope of this initiative will encompass the back-office systems underpinning staff workflows, and any interfaces including links to discovery, and to corporate services (including identity management, finance, and patron feeds from golden sources of staff and student data).
LMP004 is sub project of the main project and has been initiated to cover project activities aligned to the integration of University of Edinburgh Identity Management system (IDM) with the new Library Management system provided by 3rd party supplier.
Scope
This sub project will cover development for patron data feed from golden sources (IDM, EUGEX and HR) of staff and student data into the new library application as per business requirements collated as part of the Procurement ITT tender process. These are as follows from Integration; User Requirements extract as noted below:
No | Users Requirements |
9.7 | The system must allow the import and management of user data: - automatically from an identity management system, and manually by individual entry or bulk load; - using definable match-points for updates (e.g.. user ID / EDUNIIDMSID); - with data expired automatically based on data fields (such as expiry date). |
9.8 | The system should accept feeds of patrons, preferably by real-time XML messaging of patron data changes from the Oracle SOA suite, including partial updates of only changed elements. Alternative but less desirable options could include scheduled PULL based XML feeds from a URL in the Identity Management System, or periodic loading of patron files in a format such as CSV. |
9.9 | The system should allow user data to be automatically suspended, expired and removed without losing historical transaction information. |
9.10 | The system should allow patron groups and rights to be selected from the most permissive group attribute they hold (for example, in order ascending: Visitor, Undergraduate Student, Postgraduate Student, and Staff). |
Please note as per LMP002 project brief, the following item is deemed out of scope for this project:
- Self registration for public users will be managed using PHP version of existing process being updated by Library team.
Objectives
- To allow the import and management of user data automatically from the University's Identity Management System (IDM) to the new Library Management Services application and the acceptance of feeds of patrons on a regular basis
Deliverables
- The delivery of period bulk feed from IDM into the Library Management system (MUST)
- The delivery of a change based feed on demand (SHOULD)
- MyED channel changes linking to the new Library Management system
Benefits
The integration of IDM with the Library Management Platform Implementation project will deliver on implementation of the new system :
- Improving and streamlining business processes, staff resourcing and capacity
- Moving to a new Library Management Platform will allow all library collections to be effectively managed and discovered within a single system. This brings efficiency and workflow savings to the library by managing all resources within a single system, and making them more easily discoverable to library users.
The anticipated benefits of;
- Comprehensive integration with Identity Management System which will be measured by eliminating the need for manual work-around for patron update feeds; reducing risk of complaints as a result (e.g.. patron record expired illegitimately).
- Single sign on access to Library record, improving service for users.
Success Criteria
- Import and management of data automatically from the IDM system and manually by individual entry or bulk load
- Capable of using definable match-points for updates using User ID / EDUNIIDMSID
- Accept feeds of patron data
- Allows user to be automatically suspended, expired and removed without losing historical transaction information
- Allow patron groups and rights to be selected from the most permissive group attribute they hold (for example, in order ascending: Visitor, Undergraduate Student, Postgraduate Student, and Staff).