<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>Boman, Craig</title>
<link href="http://hdl.handle.net/2374.MIA/6138" rel="alternate"/>
<subtitle>Craig Boman</subtitle>
<id>http://hdl.handle.net/2374.MIA/6138</id>
<updated>2026-04-05T18:43:52Z</updated>
<dc:date>2026-04-05T18:43:52Z</dc:date>
<entry>
<title>Between the Sheets: a Library-wide Inventory with Google</title>
<link href="http://hdl.handle.net/2374.MIA/6180" rel="alternate"/>
<author>
<name>Boman, Craig</name>
</author>
<author>
<name>Voelker, Ray</name>
</author>
<id>http://hdl.handle.net/2374.MIA/6180</id>
<updated>2017-11-22T19:19:52Z</updated>
<summary type="text">Between the Sheets: a Library-wide Inventory with Google
Boman, Craig; Voelker, Ray
When it comes to taking an inventory of physical items, libraries often rely on their traditional integrated library system’s (ILS) à la carte add ons; outside vendors; or other possibly outdated, complex, and often expensive methods. For libraries with shrinking budgets and other limited resources, high costs can put these methods out of reach.&#13;
&#13;
At the University of Dayton Libraries, we set out to develop an inexpensive and reasonably easy-to-use method for conducting a library-wide physical item inventory. In this article, we explain a custom built Google Sheets-based library inventory system, along with some code for the implementation of a RESTful API (written in PHP) that interacts with our ILS. We will also explain our use of Google Apps scripts in our Google Sheet, which are crucial to our systems.&#13;
&#13;
Although this method used a specific ILS (Innovative Interfaces’ Sierra product) and custom-built RESTful APIs, it may be possible to use similar approaches with other ILS software. Additional notes include areas for improvement and recommendations for interoperability with other ILS systems.
</summary>
</entry>
</feed>
