Collection usage report: issues field in items table
I'm trying to assess the usage of a particular collection and am wondering if the 'issues' field in the items table represents all issues: Ie., both from the old_issues and issues tables. If the total number of issues is represented in this field, the report would not need to join these tables ...which is what I'm hoping. Thanks! -- Chad Roseburg Automation Dept. North Central Regional Library
Hi Chad, On Fri, Jan 10, 2014 at 3:02 PM, Chad Roseburg <croseburg@ncrl.org> wrote:
I'm trying to assess the usage of a particular collection and am wondering if the 'issues' field in the items table represents all issues: Ie., both from the old_issues and issues tables.
Yes -- items.issues gets incremented every time an item is checked out, so if all you need is a count, you don't need to include either the issues or old_issues tables in your query. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (2)
-
Chad Roseburg -
Galen Charlton