KLAS v7.8 is coming!
After two years of small updates, we’re really close to bidding farewell to KLAS v7.7 and rolling over to v7.8. This will not be a big change at all from your perspective, but I want to give you a heads-up about what’s coming and why.
The first KLAS v7.8 release will likely include other fixes and improvements, but the update triggering the version change should be completely invisible. That update is to Open Edge (OE), the framework and programming language we use to build the KLAS interface. The new version of OE will provide us access to new options for programming KLAS, keep us up to date and allow us to get any bug fixes on that end of things. However, nothing should change to the look and feel of KLAS. How it runs, what is available for users, and how we support it will all remain the same.
To make sure the update to the back-end doesn’t introduce any problems on the front-end, we’ll be doing a lot of rigorous testing. We’ll also rely on feedback from our Early Release customers even more than usual so we can be sure we haven’t missed anything. Fortunately, we do not anticipate any changes or problems. This won’t be a major conversion (like the one from 7.6 to 7.7), just a big update.
So, in short, v7.8 will be an update for us, but not any different for you. Don’t worry, we’ll keep those bi-weekly small updates coming with all the bug fixes, improvements, and new features we can squeeze into them.
So... whatever happened to v.8?
If you attended the 2018 KLAS Users’ Conference in Idaho, you probably remember testing our prototype user interface for the web-based KLAS v.8. It’s something that we and you were really excited about, so it makes sense that we get questions about it on occasion.
For quite a while, we didn’t have much to say. That’s because, right after the 2018 conference, we realized just how big the need was to get Duplication on Demand up and running at full scale ASAP. We shifted gears pretty hard, switching our attention to: taking Scribe from a proof-of-concept to a fully-realized appliance capable of supporting a library’s full circulation; getting Gutenberg integration in place; and building screens, workflows, and features to support this whole new approach to service.
Additionally, we needed to keep up with the development needs of our IRC/IMC customers, bring new customers online, and keep everything else running. That “keep everything else running” was complicated by the deployment of 7.7 and all the development needed to support it, and a massive server crash that prompted our migration to all cloud hosting.
Unfortunately, the pivot to duplication ate up the time and resources we’d hoped to devote to KLAS v.8. But there’s is good news! With Duplication on Demand finally getting to be as robust and fully-featured as we envisioned, and the needs of our IRC / IMCs lining up with some things we needed to do anyways... we’re finally able to provide an update: we are at work on the foundations of v.8!
To be clear, it’s still a very long road ahead. Building an entirely new UI (informed by the prototypes and user testing from 2018, and everything new we’ve added to KLAS since) is a huge undertaking requiring a lot of development resources. However, the other major task will be the need for the UI to communicate with the database storing all of your information by way of APIs. Finally, the APIs needed to be built and implemented so that they allow existing programs in KLAS to function alongside any user interface we build moving forward—we know from painful experience that we can’t rebuild all of KLAS at once and release an entirely new interface with everything you need ready and working on day 1.
We’re excited to say this key building block, the suite of APIs that will provide the machine-to-machine communications needed for v.8 to function, is now underway!
You may have noticed these APIs cropping up in Release Lists this year, and more are coming. For now, IRCs that maintain student data, orders, and catalog info in more than one system are using and will be using these APIs to integrate with third party systems, but the beauty of APIs is that once they are in place, any compatible system can use them. The programming we’re doing now to integrate with other systems will be the thing that allows us to integrate with the browser-based KLAS v.8 in the future (while still allowing the v.7 interface to be used during the transition).
How long will this take? It’s really hard to say. It ultimately depends on what other development is needed, what new needs crop up which we haven’t anticipated, and what resources open up for us to take this on. But getting the APIs in place is incredibly important foundational work, and we’re really excited to finally get them on the front burner and in progress.
