At Cornell, we have an instance where we have a location (Kroch Asia) that does not have a service point.  It is actually supported by another locations service point.

Wendy Wilcox
Access Services Librarian
Olin, Kroch, and Uris Libraries
Cornell University
101D Olin Library
607-254-6241
ww83@cornell.edu 


On Wed, Sep 26, 2018 at 7:52 AM Cate Boerema <cboerema@ebsco.com> wrote:

Hello RA SMEs,

 

The developers are reconsidering the location-to-service point architecture and I’ve got a question for you that will inform their thinking.  The question is: should at least one service point be required for every location?

 

Emma and I were discussing this and we realized that, probably, each location should have a service point.  After all, if you try to check in an item whose location doesn’t have a service point, you won’t know if it’s home.  You won’t be able to calculate its overdue fees (because the fee/fine tables will be associated with the service point) and you won’t know the shelving lag time.  There probably many more impacts I am not thinking of at the moment. 

 

Our original designs (and, in fact, what has been implemented so far) support the ability to add locations to a service point.  If we need to require at least one service point per location, we are going to need to switch that around and ask users to add service points to locations instead.

 

Let me know if you have any quick thoughts on this.  I’ll try to get 10 minutes on the agenda for tomorrow to discuss further.

 

Thanks much!

 

Cate