The End of Nostradamus Killing Predictive Checkin without Feeling Guilty Young Joo Moon, Boston College Bob Persing, Univ. of Pennsylvania NASIG 2013 conference June 7, 2013
Our namesake 16 th -century French mystic Best known for making many grand, specific, and inaccurate predictions about future history (nice beard, though)
History of predictive checkin systems 1940s: the Kardex
History of predictive checkin systems 1950s, 1960s: computers! (sort of) Not so much for checkin as for creating printed lists of serials
History of predictive checkin systems 1970s: a time of beginnings OCLC Advisory Committee on Serials Serial bib. records start appearing Serials Control System (SCS) ISSN standard (1971, 1975) CONSER founded (1976)
History of predictive checkin systems 1980s: change happens quickly Major systems reach market: NOTIS Innovacq VTLS OCLC SC350 Many others Faxon: Linx, SC-10
History of predictive checkin systems 1980s: some foundational standards ANSI/NISO Z39.42 (summary holdings) MARC Format For Holdings Data Z39.44 (serial holdings superseded Z39.42) Z39.57 (nonserial holdings) ASC X12
History of predictive checkin systems 1990s: true prediction arrives Innovative NOTIS VTLS Many other systems try prediction LC builds in-house system, but then migrates to Voyager
History of predictive checkin systems 1990s: important standards work Separate ISSN for each format EDIFACT data transmission standard Initial CONSER work on sharing publication patterns (early 1990s) Z39.71 supersedes both Z39.44 and Z39.57 SICI (serial item & contribution identifier) DOI (digital object identifier)
History of predictive checkin systems Late 1990s: some players drop out OCLC SC350 NOTIS Ameritech manages to kill them both! Faxon Others jump in Endeavor
History of predictive checkin systems 2000s: more standards work CONSER Publication Patterns Project / OCLC 891 field DLF ERMI Much serials-related ILS work, but more focused on ERM, knowledgebases
History of predictive checkin systems 2010s: next generation of systems Two case studies: Alma Kuali OLE
Living without Predictive Checkin Boston College s Experience with Alma
Boston College Founded in1863 Private, Jesuits 11 schools/colleges Students 14,000 undergrad 9,000 graduate 5,000 Faculty 725 3 campuses Main campus- Chestnut Hill
Boston College University Libraries ARL member 8 libraries Collections print 3 million ebook 400,000 Materials Budget $9,536,496 (FY12 excluding Law)
BC and Alma Migrated from Aleph to Alma in June 2012 (1 st institution to migrate to Alma) Development partner since 2009 Deeply involved in design and development
What is Alma? URM (Unified Resource Management) Supports the entire suite of library operations selection, acquisition, metadata management, digitization, and fulfillment for the full spectrum of library materials, regardless of format or location Focuses on unified management of all of a library s resources Workflow-driven
What is Alma? Cloud environment Replaces individual data silos: Aleph, ERM, SFX Primo (Holmes) sits on top: Discovery layer Browser based: Firefox6+, Chrome3+, IE8+ Can be accessed from any computer or internet device Can take multiple metadata formats: MARC, Dublin Core and MODS
Alma Development Jan 08-June 10 URM Conceptual design with development partners completed Five Partner Releases from June 2010 to October 2011 June 1st Partner Release delivered November 2010 Dec 10- Jan 12 2010 Partners testing PR 2nd Partner 2 PR 5 in SaaS Release Cloud with own delivered data migrated 2012 General Release BC Live (7/2)
Periodical collections in BC Periodical Collection print 6,340 ejournal 34,919 (including aggregators) Periodical Budget $4,917,173 (FY12) ejournal: $4,037,484 print journal: $879,689
Print Periodical Checkin in Alma Checkin function linked to orders with specific order types Physical Subscription Physical Standing Order Non-monograph Alma does not support predictive pattern functionality Alma considers serials check-in as receiving physical items
Print Periodical Checkin in Alma
Print Periodical Checkin in Alma
Print Periodical Checkin in Alma
Print Periodical Checkin in Alma
Print Periodical Checkin in Alma
Standing Order Checkin in Alma S.O. Order Types Physical Standing Order Monograph Physical Standing Order Non-monograph Standing Order Non-monograph Multiple items can be associated with a single holding (acts like a periodical)
Standing Order Checkin in Alma Standing Order Monograph Applied to analytical series (acts like a monograph) Cannot be received using periodicals receiving (different workflow is applied) Individual record created for each vol. Umbrella order is created linked to holdings of individual vol.
Print Periodical Claims in Alma Order record has Expected Receipt Date, Claiming Grace Period and Subscription Interval When the Expected Receipt Date + Claiming Grace period arrives and if no issue was received, Alma sends the PO line to the claims task list When an issue arrives, Expected Receipt Date is updated by Receipt Date + Subscription Interval
Print Periodical Claims in Alma
Print Periodical Claims in Alma Vendor record has Expected Receipt after Ordering (days) and Claim Grace Period (days) that are used as default values when creating a new order
Print Periodical Claims in Alma Claims Task List For getting a list of titles to be claimed For adding communications For manually updating Expected Receipt Date
Print Periodical Claims in Alma
Print Periodical Claims in Alma
Print Periodical Claims in Alma
Periodical Binding in Alma Alma supports binding functionality. From the Items screen, the items to be bound can be selected, and then clicks on the option Bind Items
Periodical Binding in Alma
Overall Experience Saves a lot of staff time enables restructuring/refocusing Expects the number of print periodicals continue to decrease (e-only is preferred) Satisfaction/fulfillment level remains about the same
Kuali OLE partnership
Kuali OLE Precis Open-source ILS Fully web-based (no clients) Data format-neutral (not just MARC) Intended to handle all formats equally No preference for tangible or electronic No OPAC Sister project: GOKb (open-source community-supported knowledgebase)
Kuali OLE timeline 2008-2010: initial design discussions, partner recruitment Project started out independent, but joined Kuali Foundation, an umbrella organization of higher-ed open source software projects, in 2009 2011: release 0.3 2012: release 0.6 2013: releases 0.8, 1.0 2014: releases 1.5, 2.0
Kuali OLE Serials Development 2011 survey of partners Some partners have fully-predictive systems currently, some don t All partners still checking in print serials, to one degree or another All partners reported steep decreases in print serial subscriptions in last 15 years All partners doing some claiming, though less than in past
Kuali OLE Serials Development 2011: OLE Select & Acquire Team wrote white paper, laying out three options: 1) passive receipt 2) action-date-based receipt 3) full prediction, with patterns
Kuali OLE Serials Development S&A Team and OLE Functional Council came to consensus on option #2 don t fight the last war
Kuali OLE Serials Development 2012: Serials team formed to write specs Discussed needs at their institutions Read user stories submitted by partner library staffs Wrote functional specifications, describing how the functionality should work
Kuali OLE Serials Development Consensus on team: full prediction not worth it for the number of titles we still get Still need some trigger for claiming, though Only real resistance came from law libraries Still heavily print-based
Kuali OLE Serials Development Wrote specifications for free-standing serials receiving record Designed mockups of receiving and receipt history screens In Excel! Serials receiving not fully coded yet, but mockup is at: http://tinyurl.com/olesermockup
Kuali OLE Serials mockup
Thank you! Questions? Bob Persing (persing@upenn.edu) Young Joo Moon (moonyo@bc.edu)