<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>Implementing serials predictive check-in</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Joanne</mods:namePart><mods:namePart type="family">Rowan</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Predictive check-in has arrived.  From the December 2014 update, Alma started introducing new features to enable predictive check-in to be set up.  The University of Auckland had recently migrated to Alma from Voyager and was keen to start using predictive check-in again.  I will take you thorugh the process of how the University of Auckland went about setting up predictive check-in.  The session will cover how we used normalization rules to remove our existing 866 field in the holdings record; created the 863 field from our existing item records; and then use the 863 field to recreate our 866 fields.  I will also look at how we added the 853 fields for the predictive pattern.  I will discuss the issues we faced and how we overcome them.</mods:abstract><mods:originInfo><mods:dateIssued encoding="iso8601">2015-05-08</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>