Beth Picknally Camden Goldstein Director of Information Processing
2
Van Pelt Library University of Pennsylvania
Presenter
Presentation Notes
U Penn, private, Ivy league in Philadelphia 12+ libraries, 2 commons, one storage facility
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
Presenter
Presentation Notes
Bd, FC, TC, SME teams S&A BA – Bob Persing Deliver Lead SME – Emily Batista
4
Pre-Implementation OLE Assessment 2014 Review of 1.5 & 2.0 specs Decision to delay to 3.0
Must-Have Lists
Presenter
Presentation Notes
Reviewed 1.5 which was in production and specs for upcoming 2.0 ; This review happen as Chicago and Lehigh were going live. Admin Co reviewed the report and decided to delay until 3.0 in July of 2016 Shared with the partners Note: 1.6 was added to roadmap after we did this initial review Must Haves – grew out of this report and evolved as the releases were scoped Bob Persing is Penn’s OLE project manager
5
Penn’s Implementation Teams Penn OLE Coordination Team Penn OLE Functional Team Penn OLE Technical Team
Presenter
Presentation Notes
Coordination: Senior admins and dept ; Functional: Closer to work will also call on standing groups to work on specific items (e.g. Budget grp working on Chart of Accounts) Technical: chiefly staff from LTS
6
Penn’s Implementation Tools Confluence Penn Box Jira
Presenter
Presentation Notes
Confluence – broader info for all library staff Penn Box – team documents, shared editing Jira –ticketing
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
Presenter
Presentation Notes
July-September 2015 Bring three new OLE instances online on Penn servers Populate instances with Penn data Start planning structures for data types, such as: fund accounting,locations,item statuses and types October-December 2015 Start testing with a stable local copy of OLE, refreshed on a regular, public schedule Finalize plans for each type of data loading Start planning: roles and permissions, circulation rule matrix Start testing interface with DLA-D Make master list of regularly-scheduled jobs to be run January-March 2016: Begin hands-on training of staff Write local documentation Test interactions with outside systems (BEN, OCLC, Relais, etc.) April-May 2016: Finish staff training Make Day One plan Begin data loading onto production server June 2016: begin some functions (like new ordering) on OLE June 1 finish old fiscal year on Voyager do final data load from Voyager to OLE come up live in production on OLE no later than 7/1 ; dependent on timing of 3.0 release Currently about a month behind
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
Presenter
Presentation Notes
a. Initial deployment of KOLE 1.6 - Installation of code base, upgrades and patches to OLE 1.6 latest sprints and any subsequent patches during the Work-Order timeframe b. Environment setup - Setup collaborative work packages for deploying and operationalizing KOLE server environment c. Loading of key data entities - Bib, holding, item, vendor, patron and other acquisition related data like purchase orders, invoices and chart of accounts d. Provide operational and logistical consulting and advice during the implementation project timeline to LTS staff on best practice, provide background information, fill gaps in documentation, and other informational guidance.
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)
Presenter
Presentation Notes
Thanks to Grover McKenzie: There are several different possible configurations available to run OLE. The distribution of different components is shown in the diagram below; each box represents a single server, with the letters keyed to the specification table below.
10
Data loading OLE API Documentation
ETL tools investigation Kettle selected
Presenter
Presentation Notes
Wanted to use a reproducible method for data loading; HTC investigation; comparison of OLE API with open source ETL tools ETL = Extract, Transform and Load Kettle http://etl-tools.info/en/pentaho/kettle-etl.htm
11
Presenter
Presentation Notes
Transformation for the non-MARC part of the bib records.
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
Presenter
Presentation Notes
1.6.2-r24565 as of 10/6/15 Counts from dev.ole.:�bibs: 5,650,071�holdings: 7,232,589 (of which 1,287,869 are e-holdings)�items: 5,193,115
13
Presenter
Presentation Notes
Penn’s data: search results
14
Presenter
Presentation Notes
Penn data: Location codes
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
