Understand
Requirements, dependencies, record behavior and the operational realities across eleven registered locations.
→Flagship transformation · 2022–23
Symphony to Medad:
eleven locations, one route.
A live ILS migration is a systems problem, a data problem and a people problem at the same time. The route has to hold all three.
SCROLL TO TRACE THE ROUTE↓
01THE ASSIGNMENT
Change the platform
without losing the service.
As Project Lead, I brought requirements, migration, integrations, testing, production readiness and operational governance into one delivery route for the transition from Symphony to Medad.
11registered locations
~400Kbibliographic records
~1.15Mitem / copy records
MARCH ’23go-live
02THE DELIVERY ROUTE
The migration was treated as a sequence of decisions, each leaving the next team with better evidence.
Prepare
Migration rules, interfaces, testing, cutover decisions and a path that protected service continuity.
→Move
Approximately 400K bibliographic records and approximately 1.15M item / copy records into the new platform.
→Continue
A compatibility layer and surrounding tools kept dependent services useful after go-live.
→03CONTINUITY LAYER
The migration ended.
The interfaces still had to work.
Stacks and other discovery services were built to talk to Symphony’s API, so without a compatibility layer they would have stopped working at cutover. The Medad Wrapper API reproduced the required behavior and kept those integrations useful after the platform change.
DEPENDENT SERVICESSTACKS
COMPATIBILITY LAYER
NEW PLATFORMMEDAD
04OUTCOME
Outcome:
continuity after cutover.
The result is more than a successful go-live. It is a maintained path for staff, members, integrations and the data itself—plus a toolkit that keeps the new service improving.
Return to the work ledger ↗