<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>Check Your expectations: Testing self check in a consortium environment</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Natasha</mods:namePart><mods:namePart type="family">Allen</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Suzanna</mods:namePart><mods:namePart type="family">Conrad</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>In the spring of 2016, the California State University (CSU) System began the process of creating formalized self-check testing procedures for campuses utilizing self-check in anticipation of our switch to Alma in June of 2017. Ten of 23 CSU campuses have self-check machines in service. Each campus presented its own unique challenges for migrating to a new system including various self-check vendors, options on self-check machines, authentication procedures, and usage of automated materials handling systems. Our group of five was tasked with creating standardized goals and procedures for linking our self-check systems to Alma despite myriad configurations.&#13;
&#13;
Our goal for this presentation will be to share experiences and provide ideas on how to create formalized testing procedures in a consortial environment. We will discuss how we communicated during the project, documented progress, as well as provide insight into troubleshooting problems that arose during the testing process.</mods:abstract><mods:originInfo><mods:dateIssued encoding="iso8601">2017</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>