260 likes | 394 Views
Navigating Alma Fulfillment Issues During the Implementation Process. Chris Martin North Dakota State University Libraries. Moving to Alma. December 2011: Alma early adopter program November 2012: Alma and Primo implementation kickoff June 2013 : Alma and Primo launch
E N D
Navigating Alma Fulfillment Issues During the Implementation Process Chris Martin North Dakota State University Libraries
Moving to Alma • December 2011: Alma early adopter program • November 2012: Alma and Primo implementation kickoff • June 2013: Alma and Primo launch • June 2013: III Millennium contract ends
Fulfillment Staff for NDSU Libraries • 7 FTE in Access Services • 5 FTE working with fulfillment • 18 student workers
How will… • …we provide effective ILL services? • …our course reserves setup work? • …our patrons book study rooms?
ILL: Consortia and Networks • Local Consortium: Tri-College • State Consortium: ODIN • Regional Networks: MnPALS and Minitex
ILL: Pre-Alma Setup • Aleph ILL • OCLC WorldShare • ILLiad • Millennium
ILL: Additional Factors • Non-OCLC ODIN partners • Extra steps for partners with OCLC • Lack of “personal account” features
ILL: Challenges with Alma • No third-party/ISO request capabilities • Unclear status of Alma ILL in general
ILL: What We Needed • Effective requesting with all of our partners • A reduction in our systems count • A better overall patron experience
ILL: The Solution • Aleph ILL within ODIN and the region • ILLiad in the region and elsewhere • ILLiad personal accounts for our patrons
ILL: Today • June 2013: ILLiad borrowing launch • All borrowing requests run through ILLiad • Alma: psuedo-patron lending circulation • 1,500+ registered ILLiad users
Reserves: Pre-Alma Setup • Millennium • Internal Libraries server • OPAC search box
Reserves: Record Structure • Bib level: ENG 120 • Item level: ENG 120-1 • Item level: ENG 120-2
Reserves: Challenges with Alma • Changes in records structure • Record migration issues • Excessive printing
Reserves: What We Needed • Usable records and data • Link resolving for e-reserves • Proper scoping in Primo • An overall shift in our approach
Reserves: The Solution • Clean data • Best practices • Same e-reserve practices • Separate search tab in Primo
Bookings: Pre-Alma Setup • Millennium back end • Millennium OPAC • OPAC facet linking to bookings module
Bookings: Challenges with Alma • Delay in Alma bookings launch • Alma bookings logic and approach
Bookings: What We Needed • A significant improvement for patrons • A system that would play nice with Alma • A design that could be integrated with our new website
Bookings: The Solution • OpenRoom: open-source bookings system • All key circulation in Alma, along with Alma’s Change Due Date function • Direct link on front page of website
Bookings: Today • August 2013: OpenRoom launch • Default “basic” (mobile-friendly) view • Several other patron-friendly features