Wishlist: reporter sources for Inter-system transits

[Chris Sharp]

PINES has always tracked "IntraPINES Loans" or transits between county/regional library systems, not including any transits within each system from one branch to another. This allows us to track the number of items sent through our Inter-system courier for contracting/billing purposes. We currently use an SQL script to do this, but I think it's time to consider adding views/sources to the DB/reporter to make this process easier and more available to end users. It's likely any consortium with a centralized courier would also benefit from this type of report.

Branch on the way.

[Elizabeth Davis (elidavis)]

In PaILS, we have few different layers of resource sharing and so this would be very helpful for when we are reporting out transits amongst those layers.

[Galen Charlton (gmc)]

I may be jumping the gun on the branch, but one thing that occurs to me is that making the new reporting sources dependent on assumptions about OU depth should be avoided: not every Evergreen system's OU hierarchy is set up so that each OU at depth 1 is a system.

Consequently, I am imagining sources that might do something like this:

[1] Count or list transits between the descendants of a pair of OUs. This would cover inter-system transits between any given pair of systems/super-systems regardless of their respective depths.
[2] Count or list transits between the descendants of one OU and every other OU in the system. This would cover reporting on inter-system transits when you don't immediately care what the other end of the transit is.

But like I said, I may well be jumping the gun and will now just await the branch. :)