Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Diane Disbro]

Thank you to all of you for your dedication!

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org

On Tue, May 15, 2018 at 8:07 PM, Kathy Lussier  wrote:

> Hi Diane,
>
> It looks like this one was also fixed and included in last month's 3.07
> and 3.1.1 releases. Hooray for progress!
>
> https://bugs.launchpad.net/evergreen/+bug/1735539
>
> Kathy
>
> On 05/15/2018 07:37 PM, Diane Disbro wrote:
>
> Good evening -
>
> Kathy Lussier says this bug was fixed in 3.0.3 - but the related issue of
> not being able to delete more than one item at a time is still being worked
> on. That is another showstopper for us. We are using 3.0.2 and we still use
> the XUL client.
>
> Thank you.
>
> Diane Disbro
> Branch Manager/Circulation Coordinator
> Union Branch
> Scenic Regional Library
> 308 Hawthorne Drive
> 
> Union, MO 63084
> 
> (636) 583-3224
> ddis...@scenicregional.org
>
> On Tue, May 15, 2018 at 12:09 PM, Walz, Jennifer 
> wrote:
>
>> All –
>>
>>
>>
>>   I will have to strenuously agree with Diane on this one.   If this is
>> non-functional in the web version, it will be a no-go for us.
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Jennifer
>>
>>
>>
>> *From:* Open-ils-general [mailto:open-ils-general-bounc
>> e...@list.georgialibraries.org] *On Behalf Of *Diane Disbro
>> *Sent:* Monday, May 14, 2018 8:11 PM
>> *To:* Evergreen Discussion Group
>> *Subject:* Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal /
>> browser client blockers
>>
>>
>>
>> Good evening -
>>
>>
>>
>> I know there is a bug report for not being able to edit the attributes of
>> more than one item at a time in Webby but I can't find it. XUL allows that
>> function. It is used by circ staff to change shelving locations and
>> circulating library.We positively must have that function. I talked to
>> several people at the conference about this bug and everyone told me that
>> it isn't slated for squashing in any upcoming upgrade.
>>
>>
>>
>> I know that we can use copy buckets to change attributes of more than one
>> item at a time but that makes a simple task more complicated.
>>
>>
>>
>> If I need to submit another bug report about this, let me know.
>>
>>
>>
>> Thank you.
>>
>>
>> Diane Disbro
>>
>> Branch Manager/Circulation Coordinator
>>
>> Union Branch
>>
>> Scenic Regional Library
>>
>> 308 Hawthorne Drive
>> 
>>
>> Union, MO
>> 
>>
>> 
>> 63084
>> 
>>
>> (636) 583-3224
>>
>> ddis...@scenicregional.org
>>
>>
>>
>> On Wed, May 9, 2018 at 3:57 PM, Bill Erickson  wrote:
>>
>> Hi All,
>>
>>
>>
>> We had a discussion at the Evergreen conference hackfest about our plans
>> for removing the XUL staff client from Evergreen, effective with the
>> release of version 3.2.  I wanted to recap some of that here and open the
>> door to any questions or concerns about the process.
>>
>>
>>
>> The key point of discussion centered around ensuring the browser client
>> is up to the task of replacing the XUL client for all users when the XUL
>> client goes away.  (A number of cataloging bugs in particular stood out
>> during the discussion).
>>
>>
>>
>> Of special interest will be input from sites that are already using the
>> browser client in production, but still have some staff using the XUL
>> client, or any sites that delayed migration.  We need details on why they
>> are unable to make the switch to the browser client.
>>
>>
>>
>> To track these, I propose we once again make use of the Launchpad
>> "webstaffblocker" tag to indicate which bugs we consider blockers for
>> migrating away from the XUL client.  These bugs should of course also be
>> marked as High priority.
>>
>>
>>
>> We have a few such bugs already:
>>
>>
>>
>> https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker
>>
>>
>>
>> If you are aware of any bugs that should be added to this list, please
>> add/update the bugs in Launchpad.  Of course, we can't plan when we'll find
>> bugs, but getting the ones we know about solidified sooner than later helps
>> ensure w

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Kathy Lussier]

Hi Diane,

It looks like this one was also fixed and included in last month's 3.07 
and 3.1.1 releases. Hooray for progress!


https://bugs.launchpad.net/evergreen/+bug/1735539

Kathy


On 05/15/2018 07:37 PM, Diane Disbro wrote:

Good evening -

Kathy Lussier says this bug was fixed in 3.0.3 - but the related issue 
of not being able to delete more than one item at a time is still 
being worked on. That is another showstopper for us. We are using 
3.0.2 and we still use the XUL client.


Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO     63084
(636) 583-3224
ddis...@scenicregional.org 

On Tue, May 15, 2018 at 12:09 PM, Walz, Jennifer > wrote:


All –

I will have to strenuously agree with Diane on this one.   If this
is non-functional in the web version, it will be a no-go for us.

Thanks!

Jennifer

*From:*Open-ils-general
[mailto:open-ils-general-boun...@list.georgialibraries.org
] *On
Behalf Of *Diane Disbro
*Sent:* Monday, May 14, 2018 8:11 PM
*To:* Evergreen Discussion Group
*Subject:* Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client
removal / browser client blockers

Good evening -

I know there is a bug report for not being able to edit the
attributes of more than one item at a time in Webby but I can't
find it. XUL allows that function. It is used by circ staff to
change shelving locations and circulating library.We positively
must have that function. I talked to several people at the
conference about this bug and everyone told me that it isn't
slated for squashing in any upcoming upgrade.

I know that we can use copy buckets to change attributes of more
than one item at a time but that makes a simple task more complicated.

If I need to submit another bug report about this, let me know.

Thank you.


Diane Disbro

Branch Manager/Circulation Coordinator

Union Branch

Scenic Regional Library

308 Hawthorne Drive



Union, MO


63084



(636) 583-3224

ddis...@scenicregional.org 

On Wed, May 9, 2018 at 3:57 PM, Bill Erickson mailto:beric...@gmail.com>> wrote:

Hi All,

We had a discussion at the Evergreen conference hackfest about our
plans for removing the XUL staff client from Evergreen, effective
with the release of version 3.2.  I wanted to recap some of that
here and open the door to any questions or concerns about the process.

The key point of discussion centered around ensuring the browser
client is up to the task of replacing the XUL client for all users
when the XUL client goes away.  (A number of cataloging bugs in
particular stood out during the discussion).

Of special interest will be input from sites that are already
using the browser client in production, but still have some staff
using the XUL client, or any sites that delayed migration.  We
need details on why they are unable to make the switch to the
browser client.

To track these, I propose we once again make use of the Launchpad
"webstaffblocker" tag to indicate which bugs we consider blockers
for migrating away from the XUL client.  These bugs should of
course also be marked as High priority.

We have a few such bugs already:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker


If you are aware of any bugs that should be added to this list,
please add/update the bugs in Launchpad.  Of course, we can't plan
when we'll find bugs, but getting the ones we know about
solidified sooner than later helps ensure we can address them
during the 3.2 development cycle.

When determining whether a bug should be a blocker, a good rule of
thumb is that the bug describes a feature or work flow that's
regularly performed by staff in the XUL client that either has no
analog in the browser client or requires an untenable number of
extra steps in the browser client to accomplish.

Please feel free to add anything I missed from the discussion or
reply with questions, etc.

Thanks,

-b




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

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Diane Disbro]

Good evening -

Kathy Lussier says this bug was fixed in 3.0.3 - but the related issue of
not being able to delete more than one item at a time is still being worked
on. That is another showstopper for us. We are using 3.0.2 and we still use
the XUL client.

Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org

On Tue, May 15, 2018 at 12:09 PM, Walz, Jennifer  wrote:

> All –
>
>
>
>   I will have to strenuously agree with Diane on this one.   If this is
> non-functional in the web version, it will be a no-go for us.
>
>
>
> Thanks!
>
>
>
> Jennifer
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Diane Disbro
> *Sent:* Monday, May 14, 2018 8:11 PM
> *To:* Evergreen Discussion Group
> *Subject:* Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal /
> browser client blockers
>
>
>
> Good evening -
>
>
>
> I know there is a bug report for not being able to edit the attributes of
> more than one item at a time in Webby but I can't find it. XUL allows that
> function. It is used by circ staff to change shelving locations and
> circulating library.We positively must have that function. I talked to
> several people at the conference about this bug and everyone told me that
> it isn't slated for squashing in any upcoming upgrade.
>
>
>
> I know that we can use copy buckets to change attributes of more than one
> item at a time but that makes a simple task more complicated.
>
>
>
> If I need to submit another bug report about this, let me know.
>
>
>
> Thank you.
>
>
> Diane Disbro
>
> Branch Manager/Circulation Coordinator
>
> Union Branch
>
> Scenic Regional Library
>
> 308 Hawthorne Drive
> 
>
> Union, MO
> 
>   63084
> 
>
> (636) 583-3224
>
> ddis...@scenicregional.org
>
>
>
> On Wed, May 9, 2018 at 3:57 PM, Bill Erickson  wrote:
>
> Hi All,
>
>
>
> We had a discussion at the Evergreen conference hackfest about our plans
> for removing the XUL staff client from Evergreen, effective with the
> release of version 3.2.  I wanted to recap some of that here and open the
> door to any questions or concerns about the process.
>
>
>
> The key point of discussion centered around ensuring the browser client is
> up to the task of replacing the XUL client for all users when the XUL
> client goes away.  (A number of cataloging bugs in particular stood out
> during the discussion).
>
>
>
> Of special interest will be input from sites that are already using the
> browser client in production, but still have some staff using the XUL
> client, or any sites that delayed migration.  We need details on why they
> are unable to make the switch to the browser client.
>
>
>
> To track these, I propose we once again make use of the Launchpad
> "webstaffblocker" tag to indicate which bugs we consider blockers for
> migrating away from the XUL client.  These bugs should of course also be
> marked as High priority.
>
>
>
> We have a few such bugs already:
>
>
>
> https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker
>
>
>
> If you are aware of any bugs that should be added to this list, please
> add/update the bugs in Launchpad.  Of course, we can't plan when we'll find
> bugs, but getting the ones we know about solidified sooner than later helps
> ensure we can address them during the 3.2 development cycle.
>
>
>
> When determining whether a bug should be a blocker, a good rule of thumb
> is that the bug describes a feature or work flow that's regularly performed
> by staff in the XUL client that either has no analog in the browser client
> or requires an untenable number of extra steps in the browser client to
> accomplish.
>
>
>
> Please feel free to add anything I missed from the discussion or reply
> with questions, etc.
>
>
>
> Thanks,
>
>
>
> -b
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Kathy Lussier]

I just wanted to add a note that the fix for the bug where batch edits 
could not be performed on copies with differing required statistical 
categories  has been tested and added to Evergreen. It will be available 
in the next Evergreen maintenance releases (3.1.2 and 3.0.8).


Kathy


On 05/15/2018 01:09 PM, Walz, Jennifer wrote:


All –

I will have to strenuously agree with Diane on this one. If this is 
non-functional in the web version, it will be a no-go for us.


Thanks!

Jennifer

*From:*Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] *On Behalf 
Of *Diane Disbro

*Sent:* Monday, May 14, 2018 8:11 PM
*To:* Evergreen Discussion Group
*Subject:* Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal 
/ browser client blockers


Good evening -

I know there is a bug report for not being able to edit the attributes 
of more than one item at a time in Webby but I can't find it. XUL 
allows that function. It is used by circ staff to change shelving 
locations and circulating library.We positively must have that 
function. I talked to several people at the conference about this bug 
and everyone told me that it isn't slated for squashing in any 
upcoming upgrade.


I know that we can use copy buckets to change attributes of more than 
one item at a time but that makes a simple task more complicated.


If I need to submit another bug report about this, let me know.

Thank you.


Diane Disbro

Branch Manager/Circulation Coordinator

Union Branch

Scenic Regional Library

308 Hawthorne Drive

Union, MO     63084

(636) 583-3224

ddis...@scenicregional.org 

On Wed, May 9, 2018 at 3:57 PM, Bill Erickson > wrote:


Hi All,

We had a discussion at the Evergreen conference hackfest about our 
plans for removing the XUL staff client from Evergreen, effective with 
the release of version 3.2.  I wanted to recap some of that here and 
open the door to any questions or concerns about the process.


The key point of discussion centered around ensuring the browser 
client is up to the task of replacing the XUL client for all users 
when the XUL client goes away.  (A number of cataloging bugs in 
particular stood out during the discussion).


Of special interest will be input from sites that are already using 
the browser client in production, but still have some staff using the 
XUL client, or any sites that delayed migration.  We need details on 
why they are unable to make the switch to the browser client.


To track these, I propose we once again make use of the Launchpad 
"webstaffblocker" tag to indicate which bugs we consider blockers for 
migrating away from the XUL client.  These bugs should of course also 
be marked as High priority.


We have a few such bugs already:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker

If you are aware of any bugs that should be added to this list, please 
add/update the bugs in Launchpad.  Of course, we can't plan when we'll 
find bugs, but getting the ones we know about solidified sooner than 
later helps ensure we can address them during the 3.2 development cycle.


When determining whether a bug should be a blocker, a good rule of 
thumb is that the bug describes a feature or work flow that's 
regularly performed by staff in the XUL client that either has no 
analog in the browser client or requires an untenable number of extra 
steps in the browser client to accomplish.


Please feel free to add anything I missed from the discussion or reply 
with questions, etc.


Thanks,

-b



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

[OPEN-ILS-GENERAL] Edelweiss Analytics script

[Andrea Buntz Neiman]

Hi Evergreeners!

I wanted to let you know that Equinox has written a script to export data
from Evergreen & FTP it into the Edelweiss Analytics service provided by
Above The Treeline.  This script is available under the GPL 2+, and can be
found here:

http://git.evergreen-ils.org/?p=contrib/equinox.git;a=tree;f=above_the_treeline;hb=master

The directory includes both the script itself and some administrator-level
documentation.

Many thanks to Above The Treeline for funding this development, and for
Richland Public Library for being the first user!

Andrea


-- 
Andrea Buntz Neiman
Project Manager for Software Development
Equinox Open Library Initiative
abnei...@equinoxinitiative.org
1-877-OPEN-ILS (673-6457)
*www.equinoxinitiative.org *

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Walz, Jennifer]

All –

  I will have to strenuously agree with Diane on this one.   If this is 
non-functional in the web version, it will be a no-go for us.

Thanks!

Jennifer

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Diane 
Disbro
Sent: Monday, May 14, 2018 8:11 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser 
client blockers

Good evening -

I know there is a bug report for not being able to edit the attributes of more 
than one item at a time in Webby but I can't find it. XUL allows that function. 
It is used by circ staff to change shelving locations and circulating 
library.We positively must have that function. I talked to several people at 
the conference about this bug and everyone told me that it isn't slated for 
squashing in any upcoming upgrade.

I know that we can use copy buckets to change attributes of more than one item 
at a time but that makes a simple task more complicated.

If I need to submit another bug report about this, let me know.

Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org

On Wed, May 9, 2018 at 3:57 PM, Bill Erickson 
mailto:beric...@gmail.com>> wrote:
Hi All,

We had a discussion at the Evergreen conference hackfest about our plans for 
removing the XUL staff client from Evergreen, effective with the release of 
version 3.2.  I wanted to recap some of that here and open the door to any 
questions or concerns about the process.

The key point of discussion centered around ensuring the browser client is up 
to the task of replacing the XUL client for all users when the XUL client goes 
away.  (A number of cataloging bugs in particular stood out during the 
discussion).

Of special interest will be input from sites that are already using the browser 
client in production, but still have some staff using the XUL client, or any 
sites that delayed migration.  We need details on why they are unable to make 
the switch to the browser client.

To track these, I propose we once again make use of the Launchpad 
"webstaffblocker" tag to indicate which bugs we consider blockers for migrating 
away from the XUL client.  These bugs should of course also be marked as High 
priority.

We have a few such bugs already:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker

If you are aware of any bugs that should be added to this list, please 
add/update the bugs in Launchpad.  Of course, we can't plan when we'll find 
bugs, but getting the ones we know about solidified sooner than later helps 
ensure we can address them during the 3.2 development cycle.

When determining whether a bug should be a blocker, a good rule of thumb is 
that the bug describes a feature or work flow that's regularly performed by 
staff in the XUL client that either has no analog in the browser client or 
requires an untenable number of extra steps in the browser client to accomplish.

Please feel free to add anything I missed from the discussion or reply with 
questions, etc.

Thanks,

-b

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Andrea Buntz Neiman]

>
> There is also a bug related to batch editing volumes, which is not
> available - https://bugs.launchpad.net/evergreen/+bug/1739290. If I
> remember correctly, this bug was on the list Andrea sent out that would be
> a tackled as part of the web client cataloging bug fix project.
>

Confirmed, if we secure sufficient funding we will attempt a fix for that
bug.  As a general note, bugs fixed as part of that project will be
targeted to 3.2 and backported as appropriate.

Andrea

On Tue, May 15, 2018 at 7:59 AM Kathy Lussier  wrote:

> Hi Diane,
>
> This bug was fixed in the 3.0.3 release.
> https://bugs.launchpad.net/evergreen/+bug/1691861 Because the bug has a
> Fix Released status, it isn't automatically retrieved when you do a search
> on LP. You need to use the advanced search options to find bugs with a fix
> that have already been rolled into a release.
>
> There is also a related bug
> https://bugs.launchpad.net/evergreen/+bug/1738893 that has a fix
> available for testing.
>
> There is also a bug related to batch editing volumes, which is not
> available - https://bugs.launchpad.net/evergreen/+bug/1739290. If I
> remember correctly, this bug was on the list Andrea sent out that would be
> a tackled as part of the web client cataloging bug fix project.
>
> Kathy
>
> On 05/14/2018 08:10 PM, Diane Disbro wrote:
>
> Good evening -
>
> I know there is a bug report for not being able to edit the attributes of
> more than one item at a time in Webby but I can't find it. XUL allows that
> function. It is used by circ staff to change shelving locations and
> circulating library.We positively must have that function. I talked to
> several people at the conference about this bug and everyone told me that
> it isn't slated for squashing in any upcoming upgrade.
>
> I know that we can use copy buckets to change attributes of more than one
> item at a time but that makes a simple task more complicated.
>
> If I need to submit another bug report about this, let me know.
>
> Thank you.
>
> Diane Disbro
> Branch Manager/Circulation Coordinator
> Union Branch
> Scenic Regional Library
> 308 Hawthorne Drive
> Union, MO 63084
> (636) 583-3224
> ddis...@scenicregional.org
>
> On Wed, May 9, 2018 at 3:57 PM, Bill Erickson  wrote:
>
>> Hi All,
>>
>> We had a discussion at the Evergreen conference hackfest about our plans
>> for removing the XUL staff client from Evergreen, effective with the
>> release of version 3.2.  I wanted to recap some of that here and open the
>> door to any questions or concerns about the process.
>>
>> The key point of discussion centered around ensuring the browser client
>> is up to the task of replacing the XUL client for all users when the XUL
>> client goes away.  (A number of cataloging bugs in particular stood out
>> during the discussion).
>>
>> Of special interest will be input from sites that are already using the
>> browser client in production, but still have some staff using the XUL
>> client, or any sites that delayed migration.  We need details on why they
>> are unable to make the switch to the browser client.
>>
>> To track these, I propose we once again make use of the Launchpad
>> "webstaffblocker" tag to indicate which bugs we consider blockers for
>> migrating away from the XUL client.  These bugs should of course also be
>> marked as High priority.
>>
>> We have a few such bugs already:
>>
>> https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker
>>
>> If you are aware of any bugs that should be added to this list, please
>> add/update the bugs in Launchpad.  Of course, we can't plan when we'll find
>> bugs, but getting the ones we know about solidified sooner than later helps
>> ensure we can address them during the 3.2 development cycle.
>>
>> When determining whether a bug should be a blocker, a good rule of thumb
>> is that the bug describes a feature or work flow that's regularly performed
>> by staff in the XUL client that either has no analog in the browser client
>> or requires an untenable number of extra steps in the browser client to
>> accomplish.
>>
>> Please feel free to add anything I missed from the discussion or reply
>> with questions, etc.
>>
>> Thanks,
>>
>> -b
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

-- 
Andrea Buntz Neiman
Project Manager for Software Development
Equinox Open Library Initiative
abnei...@equinoxinitiative.org
1-877-OPEN-ILS (673-6457)
*www.equinoxinitiative.org *

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[Kathy Lussier]

Hi Diane,

This bug was fixed in the 3.0.3 release. 
https://bugs.launchpad.net/evergreen/+bug/1691861 Because the bug has a 
Fix Released status, it isn't automatically retrieved when you do a 
search on LP. You need to use the advanced search options to find bugs 
with a fix that have already been rolled into a release.


There is also a related bug 
https://bugs.launchpad.net/evergreen/+bug/1738893 that has a fix 
available for testing.


There is also a bug related to batch editing volumes, which is not 
available - https://bugs.launchpad.net/evergreen/+bug/1739290. If I 
remember correctly, this bug was on the list Andrea sent out that would 
be a tackled as part of the web client cataloging bug fix project.


Kathy


On 05/14/2018 08:10 PM, Diane Disbro wrote:

Good evening -

I know there is a bug report for not being able to edit the attributes 
of more than one item at a time in Webby but I can't find it. XUL 
allows that function. It is used by circ staff to change shelving 
locations and circulating library.We positively must have that 
function. I talked to several people at the conference about this bug 
and everyone told me that it isn't slated for squashing in any 
upcoming upgrade.


I know that we can use copy buckets to change attributes of more than 
one item at a time but that makes a simple task more complicated.


If I need to submit another bug report about this, let me know.

Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO     63084
(636) 583-3224
ddis...@scenicregional.org 

On Wed, May 9, 2018 at 3:57 PM, Bill Erickson > wrote:


Hi All,

We had a discussion at the Evergreen conference hackfest about our
plans for removing the XUL staff client from Evergreen, effective
with the release of version 3.2.  I wanted to recap some of that
here and open the door to any questions or concerns about the process.

The key point of discussion centered around ensuring the browser
client is up to the task of replacing the XUL client for all users
when the XUL client goes away. (A number of cataloging bugs in
particular stood out during the discussion).

Of special interest will be input from sites that are already
using the browser client in production, but still have some staff
using the XUL client, or any sites that delayed migration.  We
need details on why they are unable to make the switch to the
browser client.

To track these, I propose we once again make use of the Launchpad
"webstaffblocker" tag to indicate which bugs we consider blockers
for migrating away from the XUL client.  These bugs should of
course also be marked as High priority.

We have a few such bugs already:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker


If you are aware of any bugs that should be added to this list,
please add/update the bugs in Launchpad.  Of course, we can't plan
when we'll find bugs, but getting the ones we know about
solidified sooner than later helps ensure we can address them
during the 3.2 development cycle.

When determining whether a bug should be a blocker, a good rule of
thumb is that the bug describes a feature or work flow that's
regularly performed by staff in the XUL client that either has no
analog in the browser client or requires an untenable number of
extra steps in the browser client to accomplish.

Please feel free to add anything I missed from the discussion or
reply with questions, etc.

Thanks,

-b








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

Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser client blockers

[scott.tho...@sparkpa.org]

Hi Diane,
 Could this be the bug? https://bugs.launchpad.net/evergreen/+bug/1746536

Scott

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Diane 
Disbro
Sent: Monday, May 14, 2018 8:11 PM
To: Evergreen Discussion Group 
Subject: Re: [OPEN-ILS-GENERAL] 3.2 Preparing for XUL client removal / browser 
client blockers

Good evening -

I know there is a bug report for not being able to edit the attributes of more 
than one item at a time in Webby but I can't find it. XUL allows that function. 
It is used by circ staff to change shelving locations and circulating 
library.We positively must have that function. I talked to several people at 
the conference about this bug and everyone told me that it isn't slated for 
squashing in any upcoming upgrade.

I know that we can use copy buckets to change attributes of more than one item 
at a time but that makes a simple task more complicated.

If I need to submit another bug report about this, let me know.

Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org

On Wed, May 9, 2018 at 3:57 PM, Bill Erickson 
mailto:beric...@gmail.com>> wrote:
Hi All,

We had a discussion at the Evergreen conference hackfest about our plans for 
removing the XUL staff client from Evergreen, effective with the release of 
version 3.2.  I wanted to recap some of that here and open the door to any 
questions or concerns about the process.

The key point of discussion centered around ensuring the browser client is up 
to the task of replacing the XUL client for all users when the XUL client goes 
away.  (A number of cataloging bugs in particular stood out during the 
discussion).

Of special interest will be input from sites that are already using the browser 
client in production, but still have some staff using the XUL client, or any 
sites that delayed migration.  We need details on why they are unable to make 
the switch to the browser client.

To track these, I propose we once again make use of the Launchpad 
"webstaffblocker" tag to indicate which bugs we consider blockers for migrating 
away from the XUL client.  These bugs should of course also be marked as High 
priority.

We have a few such bugs already:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker

If you are aware of any bugs that should be added to this list, please 
add/update the bugs in Launchpad.  Of course, we can't plan when we'll find 
bugs, but getting the ones we know about solidified sooner than later helps 
ensure we can address them during the 3.2 development cycle.

When determining whether a bug should be a blocker, a good rule of thumb is 
that the bug describes a feature or work flow that's regularly performed by 
staff in the XUL client that either has no analog in the browser client or 
requires an untenable number of extra steps in the browser client to accomplish.

Please feel free to add anything I missed from the discussion or reply with 
questions, etc.

Thanks,

-b