INN-REACH Reports - Calendar

The calendar below is in the process of being updated by the ICS Committee to have more current information and to be more readable. To view the updated calendar for INN-Reach reports, see the page at: www.ohiolink.edu/content/inn_reach_report_calendar_and_instructions. Feedback can be sent to Theda Schwing at tschwing@ohiolink.edu

This calendar outlines when INN-Reach reports should be run, and it starts with December, when the first round of institutional overdue reports is due.

 

For directions on how to run the reports mentioned, go here

If you have questions about these reports, please contact your institution's PCIRC contact, ICS representative, or OhioLINK Support.

 

DECEMBER 1 - 15

___Generate institutional overdues report for main library and branches for all items more than 60-days overdue.

___Search stacks of main library and branches for all items on the list.

___Check in any items found.

___Generate institutional overdues report again for main library and branches in order by patron institution and name.

___Send reports to p-circ contact at patrons’ institutions.

___Run in-transit too long report weekly

___Run paged too long and requested too long once.

 

December 15 – 31

___Check patron records and record current status of each item on the list sent by the owning library.

___Return annotated list to p-circ contact at owning library.

___Run in-transit too long report weekly

___Run paged too long and requested too long once.

___Optional: run returned too long and received too long once.

 

January

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.

 

February

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Remove invalid virtual records from Returned Too Long list.

___Optional: run returned too long and received too long once.

 

March

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.

April

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Remove invalid virtual records from Returned Too Long list.

___Optional: run returned too long and received too long once.

 

May

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.

 

June 1 - 15

___Generate institutional overdues report for main library and branches for allitems more than 60-days overdue.

___Search stacks of main library and branches for all items on the list.

___Check in any items found.

___Generate institutional overdues report again for main library and branches, using 365 days as the minimum number of days overdue. Put report in order bypatron institution and name.

___Send reports to p-circ contact at patron’s institutions.

___Run in-transit too long report weekly

___Run paged too long and requested too long once.

 

June 16 – 30

___Borrowing library check patron’s records and record current status of each item on the list sent by the owning library.

___Return annotated list to p-circ contact at owning library.

___Owning library – update status to “missing” of any items In Transit, OL Received, OL Returned or Lost and Billed for more than 365 days; add appropriate note of explanation to item records.

___Run in-transit too long report weekly

___Run paged too long and requested too long once.

___Optional: run returned too long and received too long once.

 

July

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.

 

August

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Remove invalid virtual records from Returned Too Long list.

___Optional: run returned too long and received too long once.

 

 

September

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.

 

October

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Remove invalid virtual records from Returned Too Long list.

___Optional: run returned too long and received too long once.

 

November

___Run in-transit too long report weekly

___Run paged too long and requested too long twice.

___Optional: run returned too long and received too long once.