Because Overdrive information is being brought in real time, network
connectivity can impact how quickly information is brought in. We know that we
have libraries with very slow connectivity, so I am hoping that we can have a
LSE setting for the Overdrive API functionality at the org unit level.
This is so we can:
a) turn the Overdrive piece on and off. (and have the default Sitka set to true)
b) be able to turn off the Overdrive integration at the org unit level (eg. set
BHA to false) so that if network connectivity makes it unusable in eg.
Hazelton, we have the ability to turn it off for them only.
Original issue reported on code.google.com by lau...@ldsphome.com on 3 Sep 2014 at 2:55
Original issue reported on code.google.com by
lau...@ldsphome.com
on 3 Sep 2014 at 2:55