<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri, sans-serif" size="2">
<div>Hello,</div>
<div>We have recently been updating how we keep data on reference transactions in the library. In the past most units kept data in Reftracker <a href="http://resources.library.yale.edu/reftrack/Reporting.aspx"><font color="#0000FF"><u>http://resources.library.yale.edu/reftrack/Reporting.aspx</u></font></a>
but staff used different terminology, fields, and definitions of reference, which made it fairly impossible to measure and understand reference activity across the library. </div>
<div> </div>
<div>I’ve now met with most of the major units who keep data in Reftracker. Fields have been streamlined to reduce the number of question types recorded to three categories: reference, directional and other. Units may use the notes field and tagging for more
detailed record keeping. </div>
<div> </div>
<div>Many units now have written definitions of the data they are recording; all are linked from Reftracker under ‘Codes’ see <a href="https://collaborate.library.yale.edu/usability/Service%20Tracker%20Codebooks/general.docx"><font color="#0000FF"><u>https://collaborate.library.yale.edu/usability/Service%20Tracker%20Codebooks/general.docx</u></font></a>
An example of how the new data can be used to compare reference activity in February across the library <a href="https://collaborate.library.yale.edu/usability/Library%20Stats/February%202011.aspx"><font color="#0000FF"><u>https://collaborate.library.yale.edu/usability/Library%20Stats/February%202011.aspx</u></font></a></div>
<div> </div>
<div>Work still to be done (to be completed in April): </div>
<ol style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>New tool for exporting tagging data</li><li>Import of data from Aeon to Reftracker (for Manuscripts and Archives)</li><li>Creation of new fields in Reftracker to record instruction data (staff will have one place to enter their reference and instruction data)</li><li>Creation of a desktop application for data input which will prevent the current problems with unwanted timeouts from the system.</li></ol>
<div style="padding-left: 18pt; "> </div>
<div>Longer term we’ll be working on a more flexible reporting system and thinking about ways to add data from staff on Circulation Desks. I will be working with Mike Friscia and Scott Matheson on this.</div>
<div> </div>
<div>I would urge everyone to try to use Reftracker to its full potential. We’ve already used it to better understand services needed at the Sterling Information Desk and virtual reference. Used correctly, Reftracker can be a powerful tool. </div>
<div> </div>
<div>If you are using Reftracker, please continue to record all your reference transactions there. If you haven’t yet updated how you are recording data, if you have questions, or if you need help with Reftracker, please contact me. </div>
<div> </div>
<div>Thanks,</div>
<div>Katie Bauer</div>
<div> </div>
<div> </div>
<div> </div>
</font>
</body>
</html>