<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>Alma Analytics and Acquisitions Codes with Consortium Standard Consideration and Implication</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Kristy</mods:namePart><mods:namePart type="family">Lee</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Davin</mods:namePart><mods:namePart type="family">Pate</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>In this presentation, members of the Analytics Working Group are going to focus on working with acquisitions data, and to show how the acquisitions codes are used in analytics reports: &#13;
&#13;
Codes as input parameters to create reports to track types of purchases in specific subject areas.  &#13;
Fund structure (or fund codes) can facilitate and identify subject specific collection development&#13;
Use case (University of Texas at Dallas) - Cost/spending analysis reports &#13;
Possible use of reporting codes (primary, secondary &amp; tertiary), fund structures and Purchase Order Line (POL) types to gather consistent data in consortium (State University of New York SUNY Libraries Consortium) Network Zone (NZ) analytics reports</mods:abstract><mods:originInfo><mods:dateIssued encoding="iso8601">2019-05-03</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>