Purpose: Institutions that allow items to transit between service points to fill requests will want to run a report periodically - probably daily - that lists items that are in transit to or from a particular service point that should have arrived by now, based on expected transit times. The report must contain bib information, item call #, item barcode, etc as well as the service point an item is coming from, where it is going to, and when it became in transit.

NOTE - The concept of "average travel time" between service points has been discussed in passing but not defined or analyzed. An expected transit time is probably needed for any time an item is travelling between service points, not just to fill a request.

Some thin thread implementation ideas:

• Augment Requests csv to include "Date in transit" (the date the item went in transit), "From service point" and "To service point"

• OR create specialized csv for this purpose with Requests that are in Transit, "From service point" and "To service point" and "Days in transit"

• AND/OR modify the Requests app search results to add this data as additional columns (but the list of columns is already too long to fit on one page...)