Presented as part of the session "Planning for Future OLE Implementations" at Kuali Days 2015. Includes Penn's implementation timeline and progress as of Nov. 2015.
3. 3
Penn’s History with OLE
OLE Planning project
Kuali OLE Founding Partner
Standard roles on teams
Special involvement:
S&A BA
Deliver Lead SME
7. 7
Timeline
Jul/Sep 15
• Servers
• Data load
• Data structures
Oct/Dec 15
• Testing
• Roles/Rules
• Public
interface
testing
Jan/Mar 16
• Training
• Documentation
• Interactions
with local
systems
Apr/Jun 16
• More training
• Production
Data Load
• Begin live
transactions
GO LIVE
July 1
8. 8
HTC engagement
Initial deployment of OLE 1.6
Environment setup
Loading of key data entities - Bib, holding, item, vendor, patron …
Provide operational and logistical consulting
9. 9
Server Setup
Development environment: Setup 1, separate application (OLE) and database (MySQL) servers.
Test environment: Setup 2, a single server for both application (OLE) and database (MySQL).
Server
Identifier
CPU Memory Storage
A 2 core(4 threads) Intel Xeon X5650 @ 2.67GHz 32GB RAM Compellent
SAN (200 GB)
B 4 core(8 threads) Intel Xeon X5650 @ 2.67GHz 24GB RAM Compellent
SAN (200 GB)
C 2 core(4 threads) Intel Xeon E5-4617 @ 2.90GHz 32GB RAM Compellent
SAN (200 GB)
10. 10
Data loading
OLE API
Documentation
ETL tools investigation
Kettle selected
12. 12
Data loading – current status
All bibs. from Voyager production: 5,650,071
All holdings records, from Voyager production: 7,232,589
For e-resources, the holdings records have been converted to OLE e-holdings records.
All item records, from Voyager production: 5,193,115
Locations, item statuses and item types, from Voyager production
15. 15
What’s next
Technical
Upgrades to new releases
1.62.0 (testing now)
2.03.0
Assessment of features
Training
Target for Go-Live: July 1, 2016