Hi all,

I'm pleased to announce that we were able quickly find development partners to fund this project. Many thanks to PaILS, Evergreen Indiana, and SC LENDS, who joined Georgia PINES and Sitka, to fund this important improvement to the web client. Many thanks to the other sites that also showed interest in helping move this project forward.

This was a great example of many Evergreeners joining together to make the transition to the web client a little easier for l of alour users. What a great community!


On 03/19/2018 10:00 AM, Kathy Lussier wrote:
Hi all,

I've been working with Georgia PINES and Sitka on a web client bug fix project that would allow report templates built in the old client to convert to the new web client format as soon as they are opened in the web client. Currently, if you try cloning an old reports template in the new client, it opens in an old editor that does not carry over True / False fields for the templates, does not have support for nullability, as well as some other problems. More information on this bug is available at https://bugs.launchpad.net/evergreen/+bug/1642344.

This project is a bit larger than some of our other web client bug fixing projects. We have a quote from Equinox, and Georgia and Sitka have committed funds to the project, but more funding is needed to proceed with the project. This development is expected to ease the transition to reports in the web client by giving staff the ability to work with their existing templates rather than creating them all from scratch.

The tech specs for the project are available at https://yeti.esilibrary.com/dev/public/techspecs/clone_reports.pdf. If we can commit to the project soon, we expect it can be completed in just a few months, making it available for the 3.2 release, which is the release when the XUL client will be entirely moved from Evergreen.

If anyone is interested in helping us out, please send me a direct email!

Thank you!

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
Twitter: http://www.twitter.com/kmlussier

Reply via email to