"Sounds like an easy patch" In fairness to the dev team, web browsers make it VERY hard to write to the local file system because of security considerations. In order to save outside of the browser, it will likely require installing some sort of helper application.

And as another small point of clarification, I think this technically gets stored in the IndexedDB or localStorage which are *somewhat* safer than just the plain browser cache.

I'm still in favor of doing something better, but it will likely require a "helper" application to get installed on the computers.

The way we have been doing it seems outdated and precarious for libraries. Sounds like an easy patch to me because solving the issue after we've lost information is not so easily done.

It is reckless to store the data in the browser cache.

Storing the transactions in a separate file would be much more beneficial and would allow for periodic backups to be made to ensure that all transactions during an extended offline period are not lost.

The browser cache is extremely unreliable. We need this fixed to use Leap Offline.

Using LEAP Offline is become increasingly more difficult as our Organization adjusts to changes in multiple software applications and more stringent Privacy demands. Much of this difficulty comes from having these files in a browser cache that can easily be lost for a variety of reasons. A better way should be considered at this point.

Reliance on browser cache for this data is too risky for our library. Another commenter suggested data files that could be uploaded instead. That improvement would encourage my library to use Leap Offline. Currently, I can't recommend it for use.

I’d like to add our request to find an offline solution that does not rely on the browser cache as well. It’s just too risky in so many ways so we have never used Leap offline. Our alternate solution no longer works so it would be ideal if Innovative provided a better Leap solution.

@Amy, this is where we are, too. As a municipal department, we don't have our own IT, and our city IT is never going to agree with the Leap Offline setup.

Updating that we have now managed to move the majority of our staff over to Leap for patron services, but will have to continue to maintain a couple of staff client stations at every member library for Polaris offline because the Leap Offline dependence on browser cache is a total non-started with all IT admins involved. They've literally said they'd rather have staff use pencil and paper.
All we really need is the ability to backup the offline files to a hard drive or somewhere outside of the browser cache.

Would definitely be nice to have an offline source provided on a hard drive when local system internet is down!

I understand the technical limitation of using a browser-based application and trying to manage offline transactions. Like Laura suggested, I could see a dedicated offline application being useful (perhaps a basic executable that doesn't require an installer?... really just needs to store numbers in a few columns...) or a button that allows staff to export the cached data to a file that could be saved and uploaded later? All the data should be pretty anonymous already, so the potential security risk of exporting offline transactions seems minimal.

Leap offline mode is absolutely unuseable for us. Any need to reboot a machine or otherwise clear a cache result in loss of ALL the collected data. Many of our users try these as troubleshooting steps for various problems before calling us. Using Leap Offline is putting our staff in a situation that impacts them negatively for taking steps that would otherwise be the right thing to do. They are not tech people. They do not understand what may reset a cache and what might not nor do they understand how a web app makes use of the cache they just cleared to store all the data they've created up to that point while in offline mode. We actually have to install the client on every desk PC just to handle offline mode. If the client stops working because it isn't being maintained this will create an issue for us big enough to make us consider switching away from Polaris to something more reliable. There needs to be a better solution for offline mode even if it is a dedicated utility application.

Please, please find a solution for this. It just seems with such sophisticated and expensive software, you wouldn't need to rely on browser cache for offline transactions.

Yes, please!

As mentioned by others, we have libraries who use Leap for circulation, but revert to the offline client because of the fear of loosing data.

I agree with the comments above. Leap offline is not a reliable solution for our library. We need a better way to work offline without risking our transactions.

Due to the risk of data loss, we cannot consider Leap offline a viable option at this time. Not relying on saved data in the browser cache would be a significant improvement.

We are a cooperative library system and have 14 member libraries, each with their own IT support and each with their own desktop security and browser settings. (Which we aren't able to control.) The concern about working offline in leap and losing data if the cache is cleared has been a hurdle to libraries adopting Leap at the circ desk.

We use Leap exclusively for front-line work EXCEPT we still use the offline version of the Polaris client for this very reason. We struggle whenever we go offline because our staff is no longer familiar with the client at all. It's as though they are being asked to use two completely unrelated systems that just happen to access the same databases. It would be great if Leap Offline could be modified to reduce the risk of losing transactions.

Saving the information in the browser cache could lead to catastrophic data loss. This renders the offline capabilities of Leap as unusable in many organizations.