T he UN I LINC Alma Implementation Helen Loosli Library Applications Specialist amp Training Coordinator helenloosliunilinceduau What is UNILINC A notforprofit company founded in 1978 to support a network of ID: 380139
Download Presentation The PPT/PDF document "What was different?" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
What was different?The UNILINC Alma Implementation
Helen LoosliLibrary Applications Specialist & Training Coordinatorhelen.loosli@unilinc.edu.au Slide2
What is UNILINC?A not-for-profit company founded in 1978 to support a network of higher education and special librariesThe central bibliographic database is the heart of UNILINC. It reflects the holdings of all member
libraries and has done so since its inceptionCurrently there are 21 member libraries ranging in size from 3 multi campus universities through medium to small private colleges plus 2 research libraries.Member institutions have campuses across Australia and overseasUNILINC office is a separate entity to the 21 member librariesUNILINC provides library systems, developments, services and training to its MembersSlide3
Our Institutions
Our InstitutionsSlide4
UNILINC before Alma
ILMS
Aleph
Digital Assets
Management /
Repositories
DigiTool; Digital
Commons …
ERM
Verde
O
PAC
KB
*
..SFX..
ILL
Aleph
Discovery
Primo
bX
Link resolver
SFX
Primo
Central
Index
A
U
T
H
E
N
T
I
C
A
T
I
O
N
*
KB=Knowledge BaseSlide5
Out with the old!Slide6
Project TeamNameRoles
Rona WadeExecutive Director & CEOTony Cargnelutti
Associate Director, Alma Project Director
Bronwyn King
Alma Project Implementation Manager,
Functional & Data Expert
Jenny Clarke
Applications Support Services,
Functional & Data Expert: Acquisitions, Digital,
eResources
, Resource Management, End User Systems & Trainer
Clare
Decena
Web Development & Services,
Functional & Data Expert: Discovery & End User Systems
Helen
Loosli
Applications Support Services,
Functional & Data Expert:
Fulfillment,
Resource Sharing, ILL, End User Systems & Trainer
Tanya Holm
Applications Support Services, Alma Analytics Specialist / Trainer
Brent Knigge
Consultant Application Development and Systems SupportGlenda Henderson
Consultant Metadata, Standards & Quality Control,
Functional & Data Expert
Fred Piper
Consultant Applications & Systems;
Functional & Data Expert: Authentication & End User Systems
Melanie Fitter
UNILINC
/ Ex
Libris Project ManagerDirector, Resource Management Professional Services, APAC …….Slide7
Alma / Alma-Primo Project Timeline
Nov 2013:Meeting of all Members to discuss move to Alma
Mar 2014:
Formal implementation began
May – Nov 2014:
UNILINC staff trained
Oct 2014:
Alma environment and test migration completed
Dec 2014:
UNILINC staff certified for Alma
Dec 2014:
Alma-Primo environment setup and copy/install completed by Ex
Libris
Dec 2014:
UNILINC staff commenced Alma and Alma-Primo configuration and developments
Jan 2015:
Member “familiarisation” sessions
commenced
May – June 2015:
Formal training of members conducted
June 2015:
Essential Alma and Alma-Primo setup completed
June 22
nd
2015:
Alma and Alma-Primo switch to productionSlide8
UNILINC’s consortial objectives for AlmaBy STP we had to be able to have the following functions and structures operational:Network Zone – 1Institution Zones –
20, Multi Site IZs – 10 Community Zone/PCI sites – 12Non PCI – 9Primo Views – 25New Primo Members – 6 Acquisitions – 12
ILL Sites - 6Slide9
Aleph PreparationCollection rationalisationsItem status and process status rationalisationsBib and holdings deletions and tidyingPrivate patron data removal and patron purgesAcquisitions data purgesGeneration of a variety of Aleph legacy data reports
e.g. patron loan historySlide10
Alma Project TasksExtensive configuration of the NZ and 21 IZsCustomisation of letters for 21 institutions (ongoing)Setup of 320 staff usersU-resolver setupConversion of the Technical Migration status (post-STP)Workflow recommendations and developments
ISO ILL workaroundsSlide11
Alma Integration TasksSelf-check integrations (SIP2) 3 vendors, at 4 institutions, across 13 librariesCoutts EOD and EOCR (
shelf ready)EDI (in and out) – 9 vendorsTalis AspireEzproxy (15 institutions)SIS (patron data loads)Z39.50 in and out (Libraries Australia, Te Puna, WorldCat
,
EndNote,
etc
)
SpinOMatic
for label printing
Google
Scholar
Printing
in general (Namtuk, Outlook and
printers with email capability)Slide12
Alma-Primo Project TasksExtensive BO configuration and CSS customisation for the 22 migrated viewsSetup of 6 new Primo views for those institutions still using the Aleph OPACIntegrations: Equella, DigiTool and MetaLib
Setup of PDS Authentication: Shibboleth, LDAP, Alma (standard) and Alma (development)Creation of legacy Basket reports (not migrated)Slide13
Critical UNILINC Developments Primo Aleph to Alma permalink redirection/mappingDevelopment of a locally hosted database and staff interface for sensitive patron dataBursar process (OTB Bursar process not adequate)Development of special PDS authentication method for Primo for Members with external patrons but no external authentication systemReplication of existing Aleph reports in Alma Analytics
Replication of existing new titles lists using Analytics, APIs and HTMLSlide14
Some observations...Cultural shiftLibrariesUNILINC staff
AlmaLack of staff user granularityInventory management - lack of inventory “drag and drop”Bib templatesUnfortunate that Alma NRs lack regular expression capability
Analytics
Some great OTB reports
Variety of output format and widget and dashboard capability
It is not real time and sometimes environment not updated for 48 hours
Makes scheduling difficult
Miss direct SQL querying of data
Alma-Primo
Much more integrated with the ILS
Less able to customise OVP aspects e.g. request form elementsSlide15
Given scale and complexity the Alma/Alma-Primo implementation was very successful !First consortium to implement Alma within the APAC regionSlide16
Bilby Thank you.Slide17Slide18Slide19Slide20Slide21
Project Background – was slide 7Member of the Australia New Zealand Collaborative Partnership (2009) in developing region specific functionality for AlmaMigration delayed by choice until
the Network Zone / consortial functionality had been sufficiently developedMigration requirements included Full ILL integration (still in testing)Full digital functionality (DigiTool) still in developmentFull Libraries Australia integration (Print resources -
Y
es, Electronic – No)Slide22
UNILINC with Alma was slide 6
Primo
(discovery)
Alma
(management)
Primo Central; bX; etc…
KB
mobile views
APIs
integration
collaboration
APIs
data servicesSlide23
Training and OrientationProduced 16 customised training videosProduced customised training materialsDeveloped customised programs for
face to face and videoconference trainingConducted many one-on-one videoconferences post-STPSlide24
Implementation is ongoing...Export to Libraries AustraliaResource Sharing/ILLCopyright compliance process for Digitisation Requests Creation of Confluence Wiki for UNILINC FAQs Alma-Primo
Sandbox setupAssorted leftover Alma and Primo tasks (more Analytics reports, setup of local extension fields, local authorities, further Primo customisation, eBook repository imports, etc)Slide25
Why AlmaAlma promised an integrated workflow for Electronic, Print and Digital resource processingAlma would replace 4 disparate systems all requiring high levels of support.With Aleph the loading of e-resources requires complex processesAlma replaces 2 knowledgebases
(SFX and Verde) with 1Alma promised a high level of consortial functionalityOur Member libraries were keen to adopt new technologiesSlide26
Miscellaneous EZproxy Authentication for 2 MembersSetup of Members’ Alma support area on the UNILINC website (Drupal)Maintenance of project documentation in Confluence (UNILINC) and BaseCamp
(Ex Libris)Setup and use of Jira to manage project tasks and issues