1 / 26

Navigating Alma Fulfillment Issues During the Implementation Process

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

orien
Download Presentation

Navigating Alma Fulfillment Issues During the Implementation Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Navigating Alma Fulfillment Issues During the Implementation Process Chris Martin North Dakota State University Libraries

  2. 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

  3. Fulfillment Staff for NDSU Libraries • 7 FTE in Access Services • 5 FTE working with fulfillment • 18 student workers

  4. How will… • …we provide effective ILL services? • …our course reserves setup work? • …our patrons book study rooms?

  5. ILL: Consortia and Networks • Local Consortium: Tri-College • State Consortium: ODIN • Regional Networks: MnPALS and Minitex

  6. ILL: Pre-Alma Setup • Aleph ILL • OCLC WorldShare • ILLiad • Millennium

  7. ALEPH ILL

  8. ILL: Additional Factors • Non-OCLC ODIN partners • Extra steps for partners with OCLC • Lack of “personal account” features

  9. ILL: Challenges with Alma • No third-party/ISO request capabilities • Unclear status of Alma ILL in general

  10. ILL: What We Needed • Effective requesting with all of our partners • A reduction in our systems count • A better overall patron experience

  11. ILL: The Solution • Aleph ILL within ODIN and the region • ILLiad in the region and elsewhere • ILLiad personal accounts for our patrons

  12. ILL: Today • June 2013: ILLiad borrowing launch • All borrowing requests run through ILLiad • Alma: psuedo-patron lending circulation • 1,500+ registered ILLiad users

  13. Reserves: Pre-Alma Setup • Millennium • Internal Libraries server • OPAC search box

  14. Reserves: Record Structure • Bib level: ENG 120 • Item level: ENG 120-1 • Item level: ENG 120-2

  15. Reserves: Challenges with Alma • Changes in records structure • Record migration issues • Excessive printing

  16. Reserves: What We Needed • Usable records and data • Link resolving for e-reserves • Proper scoping in Primo • An overall shift in our approach

  17. Reserves: The Solution • Clean data • Best practices • Same e-reserve practices • Separate search tab in Primo

  18. Reserves: Primo Searching

  19. Bookings: Pre-Alma Setup • Millennium back end • Millennium OPAC • OPAC facet linking to bookings module

  20. Bookings: Challenges with Alma • Delay in Alma bookings launch • Alma bookings logic and approach

  21. 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

  22. 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

  23. Bookings: Today • August 2013: OpenRoom launch • Default “basic” (mobile-friendly) view • Several other patron-friendly features

  24. OpenRoom - Mobile

  25. Questions?

More Related