<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>DIY Stack Maps in Primo</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Craig</mods:namePart><mods:namePart type="family">Thomas</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Jill</mods:namePart><mods:namePart type="family">Thomas</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Stack mapping was the last thing on our mind when reference staff requested a small CSS change to Primo locations this summer. However, in the process of clarifying the aims of the request, we not only devised a better way to accomplish them; we also discovered how easy it might be to create our own low-res mapping. We'll show how we employed nothing more than UX analysis, OTB functionality, and existing PDF maps to provide enhanced location names and basic point-of-need maps for virtually every item in our physical inventory. It ain't the Ritz, but feedback indicates it’s good enough for most users.</mods:abstract><mods:classification authority="lcc">Primo</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2019-05-03</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>