[OPEN-ILS-DEV] Informal vote to apply XUL-removal patch to 3.2

Fri Aug 31 10:33:36 EDT 2018

I don't think so. I haven't found the pattern for when I an item can't be
edited, and it may or not involve parts being assigned, but the solution
I've found is to edit it in the XUL client. Changing it's status in XUL
seems to "unlock" it, and afterwards we can change it's status in the web
client as well, which sounds like a different bug. That said, our
cataloging department has completely given up on the web client and I still
use XUL if I have to edit many items. In the web client I have to scan
everything twice, once to edit them, and then another time to see if any of
the edits failed. And if any have failed then the only solution I have
found is to go to XUL.

Interestingly, the "Mark item as missing" action from the actions menu does
not seem to be affected by this bug. It's only changes made with Edit Item
Attributes that seem to be affected.

Someone at CW MARS may have more data on this bug. I can't imagine that
Forbes Library is the only library in our consortium to have submitted it.

Benjamin Kalish
Forbes Library / 413-587-1012 / bkalish at forbeslibrary.org

Support Forbes Library:

   - Consider giving a gift <http://www.forbeslibrary.org/giving> to Forbes
   Library
   - Vote for the Friends of Forbes in the Florence Bank Community Grant
   Program <https://www.florencebank.com/vote>.
   - Join the Friends the Forbes today <https://forbeslibrary.org/friends/>!

Currently reading: *Guastavino Vaulting: The Art of Structural Tile* by
John Ochsendorf
Just Finished: *There's a Mystery There: The Primal Vision of Maurice
Sendak* by Jonathan Cott

For information about accessibility at the library, please see:
http://forbeslibrary.org/accessibility/

On Wed, Aug 29, 2018 at 6:20 PM Kathy Lussier <klussier at masslnc.org> wrote:

> Hi Ben,
>
> Are you referring to the bug where copies cannot be edited after a part
> has been assigned? If so, that bug has been fixed.
> https://bugs.launchpad.net/evergreen/+bug/1739271
>
> Kathy
>
> On Wed, Aug 29, 2018, 12:53 PM Benjamin Kalish <bkalish at forbeslibrary.org>
> wrote:
>
>> Hopefully this is missing from the webstaffblocker list because it's
>> already been fixed, but I couldn't confirm that on launchpad. We've had an
>> ongoing problem where item status changes made from "Edit Item Attributes"
>> in the web client are not saved, and the only workaround we've found at my
>> library has been to use the XUL client. We've submitted this bug to our
>> consortium (CW MARS) but I don't know for sure whether or not it was ever
>> submitted on LaunchPad. It is a big deal though! If it hasn't been fixed
>> than I honestly don't know what we would do without access to the XUL
>> client.
>>
>> Benjamin Kalish
>> Forbes Library / 413-587-1012 / bkalish at forbeslibrary.org
>>
>> Support Forbes Library:
>>
>>    - Consider giving a gift <http://www.forbeslibrary.org/giving> to
>>    Forbes Library
>>    - Vote for the Friends of Forbes in the Florence Bank Community Grant
>>    Program <https://www.florencebank.com/vote>.
>>    - Join the Friends the Forbes today
>>    <https://forbeslibrary.org/friends/>!
>>
>>
>> Currently reading: *Guastavino Vaulting: The Art of Structural Tile* by
>> John Ochsendorf
>> Just Finished: *There's a Mystery There: The Primal Vision of Maurice
>> Sendak* by Jonathan Cott
>>
>> For information about accessibility at the library, please see:
>> http://forbeslibrary.org/accessibility/
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Aug 29, 2018 at 12:40 PM Kathy Lussier <klussier at masslnc.org>
>> wrote:
>>
>>> Thank you for that assessment Galen. I'll note that the bugs that gave
>>> me the biggest concern were in the small category. The type to selection
>>> bug is indeed a big issue, particularly for large consortia who have to
>>> navigate through a large list of libraries. But my largest concern are with
>>> those bugs that don't have a good workaround aside from performing the
>>> action in the xul client.
>>>
>>> Kathy
>>>
>>> --
>>> Kathy Lussier
>>> Project Coordinator
>>> Massachusetts Library Network Cooperative
>>> (508) 343-0128klussier at masslnc.org
>>>
>>>
>>>
>>> On Wed, Aug 29, 2018 at 12:23 PM Galen Charlton <
>>> gmc at equinoxinitiative.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> Here's my classification of the current open bugs tagged as
>>>> webstaffblocker:
>>>>
>>>> Small (i.e., likely can be fixed in two weeks)
>>>> ---------------------------------------
>>>> https://bugs.launchpad.net/evergreen/+bug/1773191 Untranslatable Last
>>>> Billing Type values
>>>> https://bugs.launchpad.net/evergreen/+bug/1770959 Web staff client:
>>>> strings translated via staff client are displayed untranslated
>>>> https://bugs.launchpad.net/evergreen/+bug/1781641 Web Client: Cannot
>>>> Override Patron Message Block
>>>> https://bugs.launchpad.net/evergreen/+bug/1781235 Web Client:
>>>> Sometimes Unable to Change Primary Patron Barcode within "See All" Box
>>>> https://bugs.launchpad.net/evergreen/+bug/1746536 web client: cannot
>>>> edit vol/call number in item status
>>>> https://bugs.launchpad.net/evergreen/+bug/1745427 Web Client: Serials
>>>> - Predict New Issues Defaults to Previous Pattern
>>>> https://bugs.launchpad.net/evergreen/+bug/1552778 Web client check-in
>>>> "effective date" and check-out "specific due date" should also include
>>>> times
>>>>
>>>> Higher-effort
>>>> -------------
>>>> https://bugs.launchpad.net/evergreen/+bug/1511742 webclient: Need
>>>> ability to type to selection in some menus
>>>>
>>>> Patch exists, may need some tweaks
>>>> ----------------------------------
>>>> https://bugs.launchpad.net/evergreen/+bug/1755258 webclient: LDAP not
>>>> working -- but works for stand alone client
>>>>
>>>> Overall, I think we can reasonably hope to resolve these over the next
>>>> couple weeks, although I specifically want to call out LP#1511742 as
>>>> the one bug that I think will require the most effort.
>>>>
>>>> Consequently, I am +1 for planning on disabling the XUL client in 3.2,
>>>> especially in light of plans for extending the support period for 3.1,
>>>> but do think that this decision needs to be evaluated and finalized at
>>>> the end of the upcoming bug-squashing week.
>>>>
>>>> Regards,
>>>>
>>>> Galen
>>>>
>>>> On Wed, Aug 29, 2018 at 11:57 AM Bill Erickson <berickxx at gmail.com>
>>>> wrote:
>>>> >> Devs,
>>>> >
>>>> > I'd like to have an informal vote on whether we should remove (well,
>>>> disable) the XUL client in 3.2.  Delaying the decision is complicating the
>>>> release process.  If it's clear which way the wind is blowing, we can set a
>>>> date for the final vote and patching.
>>>> >
>>>> > Knowing what you know today about outstanding webstaff blockers (a
>>>> few were just added), would you vote to proceed with XUL removal?  Can I
>>>> get a show of hands, yea or nay?
>>>> >
>>>> > Thanks,
>>>> >
>>>> > -b
>>>> >
>>>>
>>>>
>>>> --
>>>> Galen Charlton
>>>> Implementation and Services Manager
>>>> Equinox Open Library Initiative
>>>> phone:  1-877-OPEN-ILS (673-6457)
>>>> email:  gmc at equinoxInitiative.org
>>>> web:  https://equinoxInitiative.org
>>>> direct: +1 770-709-5581
>>>> cell:   +1 404-984-4366
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20180831/9f619ab7/attachment.html>