Another +1 to Terran's thoughts. >From my perspective, as the one who has to train the staff, being able to move >certain functions entirely out of the staff client will be easier to explain >to them than letting them stick with the client with these new interfaces. >It's going to be painful for them regardless, but I'd rather rip off the >bandaid than slowly peel it back.
Kate Butler Technology Librarian Rodgers Memorial Library (Hudson, NH) http://www.rodgerslibrary.org/ From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Rogan Hamby Sent: Friday, April 04, 2014 10:40 AM To: Evergreen Discussion Group Cc: Evergreen Development Discussion List Subject: Re: [OPEN-ILS-GENERAL] browser staff feedback request / integration At the Hack-A-Way we discussed the piecemeal method of integrating the new staff client into the XUL app as a way of easing people into it. I've always been OK with that approach but I don't prefer it. I think we would waste precious resources trying to frankenstein them. On Fri, Apr 4, 2014 at 10:32 AM, Dan Scott <d...@coffeecode.net<mailto:d...@coffeecode.net>> wrote: On Fri, Apr 04, 2014 at 10:25:56AM -0400, McCanna, Terran wrote: My preference would be to leave the existing client as is (with the exception of bug fixes, etc.), but to offer the browser-based modules as options once they become available. My reasons for this are: 1) It will allow for indepth use of the new module in a production environment to uncover any bugs or performance issues while still having a known entity as a backup. No amount of testing is going to uncover all of the odd little problems like working in a live environment will. 2) When moving back and forth between the two environments, staff will be more aware of the improved user interface and performance, and I believe they will be more eager to transition completely to the new environment. 3) The browser-based circulation module may offer some immediate relief to those frontline circ staff who are struggling with antiquated machines and slow networks. 4) The new modules can begin to be thoroughly tested on mobile devices that cannot run the current client. +1 to what Terran says. Let's forgo the complications of trying to force new-style development into an aging security / performance / functionality-impaired container and instead focus on fleshing out the browser-based modules on a workflow-by-workflow basis as much as possible, so that some staff (as Terran says) can benefit ASAP and help us find where we can optimize workflows or where we've missed yet another piece of existing functionality that most sites don't use but that is critical to another site's workflow. -- Rogan Hamby, MLS, CCNP, MIA Managers Headquarters Library and Reference Services, York County Library System "You don't have to burn books to destroy a culture. Just get people to stop reading them." ― Ray Bradbury<https://www.goodreads.com/author/show/1630.Ray_Bradbury> "You can never get a cup of tea large enough or a book long enough to suit me." ― C.S. Lewis<http://www.goodreads.com/author/show/1069006.C_S_Lewis>
