Besides Circulation, How else is the print collection being used? Reporting on uses other than circulation.
Download as PPT, PDF0 likes448 views
The document discusses the usage of print collections beyond circulation at William Paterson University, highlighting declining circulation and the need to justify physical collections. It describes enhancements made to the Voyager system to record historical browse transactions and the significant difference between browse counts and circulation counts. The goal is to filter out browses from items charged prior to discharge, with updated tables and reports facilitating this analysis.
Besides Circulation, How else is the print collection being used? Reporting on uses other than circulation.
- 1. Besides Circulation, How else is the print collection being used? Reporting on uses other than circulation. Ray Schwartz, Systems Specialist Librarian, schwartzr2@wpunj.edu William Paterson University of New Jersey ELUNA 2015 Minneapolis MN May 6, 2015
- 2. The Context • Declining circulation • Need to justify physical collection • Need to justify continuing expenses • Need to assess use of Reference collection
- 4. Steps taken to enhance use • For microform and print serials Created an online form to request what we own. Uses OpenURL with discovery service and vendor databases. ILL/DD scans and emails article to patron.
- 5. What about the Monographic Collection? and what about Browses?
- 6. Recording of Browses • Voyager records the 'historical browses' of each item in the item level record. • No dates or times are associated with the counts.
- 7. With version 9 of Voyager Configuration to Record Browse Date and Time Purpose of the Enhancement This enhancement saves the date and time in the Voyager database for browse transactions. Description An Events table has been added to the Voyager system to record details for specific transactions. The option must be enabled to save the date and time for browse transactions.
- 9. New Tables Event event_id number(32) item_id number(32) item_type_code varchar2(10) item_location_id number(32) patron_id number(32) patron_group_code varchar2(10) oper_id varchar2(10) circ_location_id number(32) event_type_id number(32) event_date date event_xml blob Added for historical browse support Event_item_status Event_id number(32) Item_status number(32) Added for historical browse support Event_type event_type_id number(32) event_type_code varchar2(10) event_type_desc varchar2(250) retain_event char(1) retain_patron_id char(1) Added for historical browse support
- 10. Started Counting and What Happened! • All discharges without a prior charge are counted as a browses. • Browse counts as compared to circulation counts were insanely high—3 to 5 times more than circulation.
- 11. Now WHAT TO DO!!!
- 12. Goal Filter out all browses from an item those status was charged prior to the discharge on that day.
- 13. MySQL
- 14. Browses Table
- 18. All three tables are updated daily from the Voyager database.
- 20. ColdFusion – Browses Table
- 21. Returns all the records in the left table (A) that do not match any records in the right table (B). Left excluding JOIN From http://www.codeproject.com/Articles/33052/Visual-Representation-of-SQL-Joins
- 22. ColdFusion – Monthly Browse Report