Hoopla integration with Polaris
The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.
Joyce Peter
shared this idea
-
Quick update: We are in talks with Hoopla about API requirements. Until those are in place we won't be able to move forward with implementing this enhancement. Any insight into the parameters libraries would like to use to choose which records to import from the Hoopla collection would be helpful!
