Abstract
Most automated library systems include a transaction logging component. Yet this fact may be among the best kept secrets in the automated library arena. Often only a few people within a library are aware of its existence, and even fewer have access to the transaction log data. This is unfortunate, since the concrete data garnered by transaction logs can provide bibliographic instructors, reference staff members, systems librarians, and system designers with unique and valuable insights into the patron/system interaction.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
