[OPEN-ILS-GENERAL] Evergreen 3.5.0 Released

[Bill Erickson]

Hi Everyone,

I'm excited to announce the release of Evergreen 3.5.0!

Galen has kindly posted a blog update with all the juicy details:

https://evergreen-ils.org/evergreen-3-5-0-released/

Thanks again to everyone who helped make this release happen while
simultaneously juggling chainsaws of their own.  It's been a wild ride and
I'm already looking forward to Evergreen 3.6.

-b

[OPEN-ILS-GENERAL] Evergreen 3.5 RC1 Released

[Bill Erickson]

Hi All,

As Co-RM for Evergreen 3.5, I'm proud to announce the first
release candidate for version 3.5 is available for download on the
Evergreen downloads page:

https://evergreen-ils.org/egdownloads/

As you know, this release was delayed quite a bit, but in the meantime we
were able to create and merge more bug fixes and documentation, resulting
in a better release overall.

Big thanks to everyone who contributed!

Testing is always appreciated.  Barring any unexpected issues, I expect
this RC will become the final 3.5.0 release in the next week or so.

Cheers to you all,

-b

Re: [OPEN-ILS-GENERAL] REST API with Libro by Conversight

[Bill Erickson]

Mike, I just rechecked some earlier conversations and confirmed they are
using JSON.  I don't know if they are using the IDL as a stone tablet or a
living document, though.

-b

On Wed, May 27, 2020 at 6:18 PM Bill Erickson  wrote:

> Hi Mike,
>
> I can't say for sure what they're doing.  (I asked if they'd open source
> it, no dice there).  I showed them some code that was using the JSON output
> and talked about the IDL.  I looked at the XML output too, but unless I'm
> missing something, it seemed like you still needed to use the IDL to
> explain the array positions -- I didn't see a way to generate field names.
> Maybe that's just the RPC gateway?
>
> -b
>
> On Wed, May 27, 2020 at 6:03 PM Mike Rylander  wrote:
>
>> Hi Bill,
>>
>> Do you know if they're using the xml output format to avoid having to
>> learn about the IDL mapping?  I'm mostly curious about external use of
>> various OpenSRF entry points, and where any effort might be best spent.
>>
>> Regards,
>>
>> Mike Rylander
>>
>> --   Sent from my phone, please pardon my thumbs.
>>  | Research and Development Manager
>>  | Equinox Open Library Initiative
>>  | phone:  1-877-OPEN-ILS (673-6457)
>>  | email:  mi...@equinoxinitiative.org
>>  | web:  http://EquinoxInitiative.org
>>
>> On Wed, May 27, 2020, 5:14 PM Bill Erickson  wrote:
>>
>>> Hi Lynn,
>>>
>>> We've done some work with Conversight at KCLS.  In our case, they are
>>> using standard Evergreen APIs via the osrf-gateway-v1 and a Supercat feed
>>> for MARC records.  This should not require any local changes.
>>>
>>> We did create one small API tweak to support a certain work flow for
>>> them (including lost items in a certain patron items out call) that I'd be
>>> happy to share.
>>>
>>> -b
>>>
>>>
>>>
>>> On Wed, May 27, 2020 at 5:05 PM Floyd, Angelia Lynn <
>>> lflo...@library.in.gov> wrote:
>>>
>>>> We have had several conversations with Conversight about Libro, and
>>>> adding it for several different libraries.  They prefer to us the REST API
>>>> for access, does anyone have Evergreen set up this way?  That may be able
>>>> to  help me.
>>>>
>>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>> -
>>>> Lynn Floyd
>>>> MIS Supervisor
>>>>
>>>>
>>>> Indiana State Library
>>>> https://www.in.gov/library/
>>>> 315 W Ohio St
>>>> Indianapolis, IN 46202
>>>> 317-232-3290
>>>> lflo...@library.in.gov
>>>>
>>>>
>>>>
>>>

Re: [OPEN-ILS-GENERAL] REST API with Libro by Conversight

[Bill Erickson]

Hi Mike,

I can't say for sure what they're doing.  (I asked if they'd open source
it, no dice there).  I showed them some code that was using the JSON output
and talked about the IDL.  I looked at the XML output too, but unless I'm
missing something, it seemed like you still needed to use the IDL to
explain the array positions -- I didn't see a way to generate field names.
Maybe that's just the RPC gateway?

-b

On Wed, May 27, 2020 at 6:03 PM Mike Rylander  wrote:

> Hi Bill,
>
> Do you know if they're using the xml output format to avoid having to
> learn about the IDL mapping?  I'm mostly curious about external use of
> various OpenSRF entry points, and where any effort might be best spent.
>
> Regards,
>
> Mike Rylander
>
> --   Sent from my phone, please pardon my thumbs.
>  | Research and Development Manager
>  | Equinox Open Library Initiative
>  | phone:  1-877-OPEN-ILS (673-6457)
>  | email:  mi...@equinoxinitiative.org
>  | web:  http://EquinoxInitiative.org
>
> On Wed, May 27, 2020, 5:14 PM Bill Erickson  wrote:
>
>> Hi Lynn,
>>
>> We've done some work with Conversight at KCLS.  In our case, they are
>> using standard Evergreen APIs via the osrf-gateway-v1 and a Supercat feed
>> for MARC records.  This should not require any local changes.
>>
>> We did create one small API tweak to support a certain work flow for them
>> (including lost items in a certain patron items out call) that I'd be happy
>> to share.
>>
>> -b
>>
>>
>>
>> On Wed, May 27, 2020 at 5:05 PM Floyd, Angelia Lynn <
>> lflo...@library.in.gov> wrote:
>>
>>> We have had several conversations with Conversight about Libro, and
>>> adding it for several different libraries.  They prefer to us the REST API
>>> for access, does anyone have Evergreen set up this way?  That may be able
>>> to  help me.
>>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> -
>>> Lynn Floyd
>>> MIS Supervisor
>>>
>>>
>>> Indiana State Library
>>> https://www.in.gov/library/
>>> 315 W Ohio St
>>> Indianapolis, IN 46202
>>> 317-232-3290
>>> lflo...@library.in.gov
>>>
>>>
>>>
>>

Re: [OPEN-ILS-GENERAL] REST API with Libro by Conversight

[Bill Erickson]

Hi Lynn,

We've done some work with Conversight at KCLS.  In our case, they are using
standard Evergreen APIs via the osrf-gateway-v1 and a Supercat feed for
MARC records.  This should not require any local changes.

We did create one small API tweak to support a certain work flow for them
(including lost items in a certain patron items out call) that I'd be happy
to share.

-b



On Wed, May 27, 2020 at 5:05 PM Floyd, Angelia Lynn 
wrote:

> We have had several conversations with Conversight about Libro, and adding
> it for several different libraries.  They prefer to us the REST API for
> access, does anyone have Evergreen set up this way?  That may be able to
> help me.
>
>
>
> Thanks.
>
>
>
> -
> Lynn Floyd
> MIS Supervisor
>
>
> Indiana State Library
> https://www.in.gov/library/
> 315 W Ohio St
> Indianapolis, IN 46202
> 317-232-3290
> lflo...@library.in.gov
>
>
>

Re: [OPEN-ILS-GENERAL] Hold Targeter - Ignore Closing logic change?

[Bill Erickson]

Hi Josh, Jason,

The change in behavior was not intentional.  Thanks for trouble shooting!

-b

On Thu, Apr 30, 2020 at 11:05 AM Jason Stephenson  wrote:

> Josh,
>
> I don't know what the intention was when the new hold targeter was
> written, but I think it is potentially a bug.
>
> Would you mind opening a bug on Launchpad?
>
> Jason
>
> On 4/29/20 11:13 PM, Josh Stompro wrote:
> > Hello, we have been doing curbside pickup, along with using the
> > emergency closing handler to mark all of our locations closed.
> >
> > I was just told that some holds have not been targeting the local
> > copies... which led me to notice that the expected item was getting
> > skipped with a log entry of "skipping copy X at closed org".  That led
> > me to see that we had the following Library Settings set.
> >
> > Target copies for a hold even if copy's circ lib is closed  = True
> > Target copies for a hold even if copy's circ lib is closed IF the circ
> > lib is the hold's pickup lib  = False
> >
> > Now, with the old targeter, this seemed to work fine because the second
> > setting was checked, and if it was false the first setting was checked
> > as a fallback.   (Could someone check my interpretation of the old logic
> > though.)
> >
> https://github.com/evergreen-library-system/Evergreen/blob/7f48513889098e47ee4a9d1b7cdbf5d5fe2ca8bb/Open-ILS/src/perlmods/lib/OpenILS/Application/Storage/Publisher/action.pm#L1362
> >
> > The new targeter doesn't seem to have the same fallthrough logic.  If
> > the circ_lib matches the pickup lib then only
> > the circ.holds.target_when_closed_if_at_pickup_lib setting is checked.
> >
> https://github.com/evergreen-library-system/Evergreen/blob/47f5ddaa8b029d41c710255380260614ef7ea6ae/Open-ILS/src/perlmods/lib/OpenILS/Utils/HoldTargeter.pm#L705
> >
> > I would think this would have caused more havok than it did, but I found
> > that because of bug 1868837, in many cases the local copy was still
> > being selected, so there were still quite a few items being pulled for
> > customers at the same location.
> > https://bugs.launchpad.net/evergreen/+bug/1868837
> >
> > I don't know if this behavior change is really a bug or not.  It made
> > sense to me that the  circ.holds.target_when_closed would take effect if
> > the  circ.holds.target_when_closed_if_at_pickup_lib  setting was set to
> > false, but the current way is perhaps clearer since you don't have to
> > know about the fallthrough behavior.
> >
> > After I changed the circ.holds.target_when_closed_if_at_pickup_lib
> > setting to true and reset all the holds and retargeted, everything again
> > works as expected.
> >
> > Josh
> >
> > --
> > Josh Stompro - IT Director
> > Lake Agassiz Regional Library
> > Desk: 218-233-3757 Ext 139
> > Cell: 218-790-2110
>

Re: [OPEN-ILS-GENERAL] Heads up for Angular translators

[Bill Erickson]

Hi Eva,

On Mon, Mar 9, 2020 at 6:00 AM Cerninakova Eva  wrote:

> Hi Bill,
>
> I have two questions about Angular translations
>
> 1) Would it be possible to provide some feedback like comments or
> explanation to strings containing variables or part of code (preferably
> right in Poeditor) which part of the string to translate and which not.
> It seems obvious , that the parts in quotation marks should not be
> translated, but in some cases I guess it applies not only to the parts
> enclosed in quotation marks.
> E. g. in the string:
> *Error generating print content for template name=" name="INTERPOLATION">{{**name}}{{name}}" / id=" name="INTERPOLATION_1">{{**id}}{{id}}" *
> I suppose the
> *name=*
> is part of the code too and only the
> *Error generating print content for template*
> should be translated (but I would like to be sure about it ;-) )
>
>
It should be safe to ignore any text wrapped in XML elements, specifically
the  elements.  In this example, the following text chunks are meant
to be translated:

[ Error generating print content for template name=" ]
[ " / id=" ]
[ " ] -- after the last 

The name= bit does look like code here, but it's just part of the display
message.

-b

Re: [OPEN-ILS-GENERAL] 3.3 hold targeter usage

[Bill Erickson]

Hi Josh,

Another benefit of soft retargeting is that it updates the hold copy maps
for all holds within the soft retarget interval, regardless of whether a
new target is needed.  This allows you to more frequently add newly
cataloged items to the hold copy maps, making them available for
opportunistic capture.

As for the timing, the more often you run in soft-retarget mode the better,
generally speaking, but it does cause load and there will be a point of
diminishing returns.

We're currently running the hold targeter once a day at midnight
with --retarget-interval "40h" --soft-retarget-interval "16h".  In essence,
each hold targets a copy for 2 days, but each hold is "refreshed" daily.
This seems to work pretty well for us.

-b





On Thu, Mar 5, 2020 at 4:44 PM Josh Stompro 
wrote:

> Hello, I'm trying to understand the new options that come with the new
> hold targeter, and I'm wondering how others are using it.  Is anyone using
> the --soft-retarget-interval right now?
>
> I'm considering using something along the lines of
> hold_targeter.pl --soft-retarget-interval="4 hours"
> --retarget-interval="8 days"
> running every hour.
>
> But I'm worried that this will cause all holds to be checked every hour
> after it has been 4 hours since the last retarget.  Maybe a soft-retarget
> once a day is enough?
>
> What I'm trying to achieve is to avoid the targeting churn where if a hold
> isn't filled immediately, it bounces back and forth between the two most
> appropriate items every retarget interval.
>
> We have a bunch of locations that are only open a couple days a week, so
> every once in a while an item never shows up on their pull list because it
> is always bouncing between two target copies at locations that are only
> open on the day that the item doesn't get targeted.
>
> But I also want to make sure that if the current item is no longer
> available, the hold gets re-targeted in a reasonable amount of time.  But
> maybe this isn't actually needed.  Since staff marking an item missing,
> damaged, withdrawn, etc automatically resets holds targeted to that item,
> and retargets the hold.  So what situations are left that would cause an
> item to no longer be available for a hold?
>
> Canceling a hold transit also seems to reset the hold, so that should be
> covered.
>
> How about staff editing item properties, and changing the status that way?
>
> How about checking out an item to another patron instead of capturing the
> item for a hold?  If a customer grabs an item off the shelf that is also on
> the pull list?  Or if a branch lets customers take items out of the transit
> tub up until it leaves the library?  Is there anything that resets unfilled
> holds that target the same item during a checkout?
>
> --
> Josh Stompro - IT Director
> Lake Agassiz Regional Library
> Desk: 218-233-3757 Ext 139
> Cell: 218-790-2110
>

[OPEN-ILS-GENERAL] Evergreen 3.5 Beta1 released

[Bill Erickson]

Hi All,

I'm proud to announce the first Beta release of Evergreen 3.5.  Files,
changelogs, and release notes are available on the Evergreen downloads page:

https://evergreen-ils.org/egdownloads/

Some feature highlights for the release:

* PostgreSQL 10 support
* New Action/Trigger reactor for patron self-registration events.
* Ability to update notification preferences for existing holds
* SIP2 options to improve Hoopla integration
* Various additions to the experimental Angular staff catalog.
** New MARC Edit interface
** Patron View tab in the record detail page
** New Call Number Browse, including record-specific entry point.
** Patron Search option during holds placement
** Search Results Highlighting
** Catalog Preferences Page

Over the next few weeks we'll be testing the Beta release, including a Bug
Squashing Week starting the 16th, in preparation for the general release.

Special thanks to my co-RM Chris Sharp, Dan Wells for the release assist,
Terran McCanna for leading our feedback fest, and everyone who
contributed to this release!

-b

[OPEN-ILS-GENERAL] Heads up for Angular translators

[Bill Erickson]

Hi All,

The latest batch of user interface strings are now uploaded to our PO
Editor site and are available for translation.  (LP 1862395 --
https://poeditor.com/projects/view?id=218177).  There may be a few
stragglers that are added soon as well.

We typically freeze string translations around release cutting time, but
since the Angular strings were uploaded late in the 3.5 release cycle,
there will be some wiggle room for getting strings merged into the 3.5
release.

Thanks for your patience while we solidify the work flow for managing
Angular translations!

Please reply to the list with any questions about the translation process.

Thanks,

-b

[OPEN-ILS-GENERAL] EG 3.5 feature freeze reminder

[Bill Erickson]

Hi All,

Just a friendly reminder tomorrow, Wednesday 26th (in a time zone of your
choosing), will be the last day to merge new features (Wishlist bugs) for
Evergreen 3.5.  Starting Thursday, we'll begin preparations for cutting the
Beta release, due out mid next week.

Thanks,

-b

[OPEN-ILS-GENERAL] Evergreen 3.5 Development Check-In

[Bill Erickson]

Hi All,

I just wanted to say a few quick words about Evergreen 3.5 development.
Things have been relatively quiet -- at least publicly -- so far, but we're
now entering what I think of as Feature Month for 3.5 (or any Spring
release).  I expect to see a bit more activity over the next few weeks
related to 3.5.

I call this Feature Month since we are 3 weeks out from our Developer
Feedback Fest (week of Feb 17) and 4 weeks out from our Feature Freeze (Feb
26).  At the end of the month, features that made the cut will be merged
and we'll have a good idea how Evergreen 3.5 is going to look.

The Feedback Fest will give us a chance to focus as a group on all of the
Launchpad pull requests, in part so we can merge any last minute features
before the Feature Freeze.  I encourage feature developers to take a few
simple steps *before* the Fest, though:

* Rebase and re-test your feature branches.  With the move to Angular 8 and
a fair amount of attention specifically on browser client code, there are a
lot of opportunities for merge conflicts.

* Make sure your LP bugs have a 3.5-alpha milestone and an importance value
of "Wishlist".

* Recap and/or add test steps, especially to bugs with lots of discussion,
so testers and code reviewers can quickly grasp the intention of the code.

* And of course during the Fest, prompt replies for additional information
or mid-Fest rebasing will help get features merged.

Other suggestions welcome!

As a reminder we have an IRC developer meeting next week.  This will be the
last regularly scheduled developer meeting before the feature freeze, so
it's a good time to bring up any feature-related topics that might require
group discussion or voting.

Thanks,

Bill Erickson, 3.5 Co-RM.

Re: [OPEN-ILS-GENERAL] Custom column configuration

[Bill Erickson]

Hi Beth,

Yes, this is possible (with caveats).  It's still a manual process,
though.

The gist is this:

1. Create a config.org_unit_setting_type which has the same values as the
config.workstation_type you want to replace.

2. Populate the actor.org_unit_setting for the new org unit setting from
one of the matching actor.workstation_setting rows.  (Presumably you have
one that does what you want).

3 Optional: If you want to prevent users from overriding the org unit
setting by applying their own workstation setting values, delete all
actor.workstation_setting rows and the config.workstation_type  for the
replaced setting.

The main caveat is if you perform step 3, then you are forcing /all/ org
units to rely on an org unit setting value, because you are globally
removing the workstation setting.

-b


On Fri, Jan 17, 2020 at 2:55 PM Beth Longwell  wrote:

> Evergreen libraries,
>
> I remember some discussion about deployment of custom column settings but
> can't find the email. We are on 3.4.1 and I am wanting to know if there is
> any way I can set all workstations at one org unit to the same column
> settings.
>
> Thanks,
>
> Beth Ross
> Systems Manager
> Sage Library System
>

[OPEN-ILS-GENERAL] Evergreen 3.5 Roadmap and Schedule

[Bill Erickson]

Hi All,

As one half of the Evergreen 3.5 Co-RM team (along with Chris Sharp), I'd
like to kick off the new release cycle with a call for 3.5 roadmap
entries.  We have started a roadmap page here:

https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.5

If you are working on a project that you expect to be ready for 3.5, please
add it to the wiki page or email Chris or me the details.  As a reminder,
the roadmap is for projects that have people actively working on them, not
wishlist items.

I'd also like to propose the following schedule as a general outline.

xx/yy/zz - Feedback Fest pre-feature freeze?
2/26/20 - Feature freeze
3/4/20   - Beta release
xx/yy/zz - Bug Squashing Week in this gap?
3/25/20 - Release Candidate
4/1/20   - Final release  (April Fools, yes!)

I pushed the GA release to April 1, not only because of April Fools, but
because I may be traveling for part of March which could impact my
availability.

If this schedule is agreeable, I'll follow up with feedback fest proposal
times and add all of this to the general roadmap page:

https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap

Thanks,

-b

Bill Erickson

[OPEN-ILS-GENERAL] Angular staff catalog 3.4 project docs update

[Bill Erickson]

Hi All,

Just a heads up that I've updated the Angular Staff Catalog wiki page to
reflect the state of the project after all the good 3.4 stuff was added.

https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:angular_staff_catalog

Except where otherwise noted, this document reflects features available in
Evergreen 3.4 when the experimental staff catalog is enabled (via library
setting).

Which items in the Pending Development section are the highest priority for
staff?  Have I missed any items in that list?

Thanks,

-b

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Call for Release Manager nominations - Evergreen 3.5

[Bill Erickson]

Hi All,

I would also like to be considered for the role of 3.5 co-RM.  If elected,
this will be my 4th term as RM.  I'm excited about the move to a co-RM
arrangement and I believe I have the experience to offer guidance to my
co-RM.  I also believe this will give us an opportunity to better document
the RM procedures, including the moonlight rituals and secret rune parties.

High level interests for me include all things Angular, specifically
continuing development of the Angular staff catalog and continuing the
migration from Dojo/legacy interfaces to Angular.

Other items on my radar include Angular self-checkout, XUL purging, Angular
MARC editor, OPAC/Bootstrap project (1778972), and more!

I would continue the tradition of a developer feedback fest to keep code
branches moving toward community acceptance and merging.

And finally, I'd like to further explore the idea of creating developer
zones of expertise (working groups, cabals, ...? :) based on knowledge of a
features, work flows, parts of the code stack, etc.  My hope is having
developers feel more ownership to certain parts of the software will
encourage more participation in the patch review and merging process.
Thanks to Galen for mentioning this at the hackaway.

Thanks for the opportunity,

-b

Bill Erickson





On Thu, Oct 24, 2019 at 6:09 AM Chris Sharp 
wrote:

> Hi all,
>
> I'd like to throw my hat in the ring for co-release manager for the
> Evergreen 3.5 release.
>
> About me:
>
>  I've been administering Evergreen in the Georgia PINES consortium since
> 2008 and have been actively involved in support, training, informal
> consulting, and software development in the Evergreen Community ever
> since.   I have contributed to the release build team since 2018.  Also in
> 2018, I was named a core committer for the Evergreen project and in 2019 I
> was named Evergreen Contributor of the Month.  In my position at Georgia
> PINES, I have an end-user-centric perspective for both library patrons and
> staff, and bring a broad knowledge of public library operations, from
> circulation to cataloging, admin, and reports.  This would be my first time
> as release manager.
>
> My proposal:
>
> I would like to serve as a co-release manager to someone who has been
> release manager before, so I can learn the process and hopefully become
> more skilled to be a lead release manager in the future.  I would want to
> help shepherd in major upcoming features, such as acquisitions search
> improvements, Angular 8, and third-party integration (e.g. OpenAthens,
> RBDigital), but also smaller bugfixes that may have been neglected over the
> past few cycles.
>
> I hope you will seriously consider me for this role.  I'm excited to get
> started!
>
> Sincerely,
>
> Chris
>
> On Mon, Oct 21, 2019 at 9:55 AM Galen Charlton 
> wrote:
>
>> Hi,
>>
>> It's now time to decide who will be Release Manager for the spring 2020
>> release of Evergreen, Evergreen 3.5.
>>
>> The Release Manager does not have to be a core committer, but does need
>> to be familiar with Git and have already contributed substantially to the
>> Evergreen project whether it be code or documentation.
>>
>> For this release, I would like to especially encourage people to put in
>> proposals to be co-RMs. A pair of people acting as RM can of course help
>> spread out the work, but it would also be a mechanism for somebody who has
>> previously acted as RM to help mentor somebody who is acting as RM for the
>> first time.
>>
>> Nominations (including self-nominations) are due by 11:59 PM EDT on
>> Friday, 25 October 2019. Nominations should be made by email to
>> open-ils-...@list.georgialibraries.org with a Cc: to
>> open-ils-general@list.georgialibraries.org. Replying to all on this
>> email will also work.
>>
>> Nominees should send an email to both of the above mailing lists a
>> statement about their relationship to the Evergreen community and their
>> goals for the next release. The elected release manager will be expected
>> to follow the typical schedule for a spring release but should provide
>> information on when they intend to set specific milestones such as the beta
>> release.
>>
>> If more than one candidate is nominated, an election will be held in the
>> #evergreen IRC channel on freenode.net on 30 October at 15:00 EDT /
>> 12:00 PDT.
>>
>> Everyone is invited to participate in the voting. Evergreen core
>> committers who cannot make the meeting may submit their vote via email to
>> the open-ils-dev mailing list.
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Implementation and Services Manager
>> Equino

Re: [OPEN-ILS-GENERAL] Web Client and Load Balancer

[Bill Erickson]

On Tue, Sep 3, 2019 at 10:52 AM Jason Stephenson  wrote:

> On 9/3/19 10:11 AM, Bill Erickson wrote:
>
> > After some poking around I made 2 changes
> >
> > 1. Use an IP address (e.g. 127.0.0.1) in the proxy_pass configuration
> > instead of a hostname to bypass DNS.
> > 2. Drop the keepalive timeout from the default of 65s to 5s or so.
>
> There is no keepalive timeout in the nginx proxy configuration, at least
> not the default/sample config.  Are you talking about a different
> setting, or does it need to be added?
>

Sorry, Jason.  See keepalive_timeout in /etc/nginx/nginx.conf.  I have not
yet looked to see if I can override the value in the site config.

-b

Re: [OPEN-ILS-GENERAL] Hatch and Java

[Bill Erickson]

Hi Bob,

We're in the process of migrating to OpenJDK and OpenJFX for Hatch.

See https://bugs.launchpad.net/evergreen/+bug/1817932

Part of this change, once merged, will be that we package the Java bits
into the installer, which means sites will not be required to install Java
separately from Hatch.

-b

On Thu, Apr 18, 2019 at 11:09 AM Bob Wicksall  wrote:

> On April 16th a new message appeared on the Java download pages:
>
>"The Oracle Java License has changed for releases starting April 16,
> 2019."
>
> https://www.java.com/en/download/linux_manual.jsp
>
> Does anyone know if this is just the licensing change we have been talking
> about for the past year?  Is it something new?
>
> What exact Java download is recommended for Hatch on Windows?  Is anyone
> using OpenJDK?
>
> Bob Wicksall
> Computer and Network Services Manager
>
> Pioneer Library System
> 2557 State Rt. 21
> Canandaigua, New York  14424
>
> Voice: (585) 394-8260 ext. 1110
> Fax: (585) 394-1935
>

Re: [OPEN-ILS-GENERAL] Translations in Angular 6+ (Was Evergreen 3.3 Release Update)

[Bill Erickson]

Correction, we export XMB but re-import XTB.

Dan, I have opened https://bugs.launchpad.net/evergreen/+bug/1821067 to
make the changes needed for supporting XMB/XTB files.

On Wed, Mar 20, 2019 at 1:47 PM Bill Erickson  wrote:

> Dan,
>
> Let's be sure to export the current translations before any changes are
> made.  IIRC, we want .xmb format, though it's probably a good idea to
> export a few more formats to be safe.  Once you select a locale, the export
> option is the first/top tool in the toolbar along the right.
>
> I'll go ahead and export the current .xmb file for Czech and commit it to
> a working branch for safe keeping.
>
> -b
>
>
>
> On Wed, Mar 20, 2019 at 12:11 PM Daniel Wells  wrote:
>
>> Hello Eva,
>>
>> Thank you for raising this concern.  I think we are in the process of
>> figuring things out as we go along.
>>
>> Our current best plan (I think) is to use the account we set up with
>> POEditor.com.  It looks like you already have an account there, so at least
>> you are familiar with what I am talking about.  What hasn't been figured
>> out yet is what that overall update process looks like, and what the new
>> build steps will be.  For the first part at least, your input will be very
>> valuable.
>>
>> We did a test import back in November or so (I think it was at the
>> Hack-a-way).  I would like to try to do another import to add any
>> new/changed strings and see what happens, but being a completely new and
>> unfamiliar tool, I am a little afraid of losing any work already put in
>> there.
>>
>> So, a few questions:
>>
>> 1) Based on what you have already done in POEditor, do you think it is a
>> viable solution?
>>
>> 2) I will do my best to preserve what is there, and I hope the re-import
>> does the right thing, but how much would it take to redo the work done
>> there so far if things go very badly?
>>
>> 3) Do you have a planned timeline for upgrading to 3.3?
>>
>> Sincerely,
>> Dan
>>
>>
>> On Mon, Feb 25, 2019 at 11:52 AM Cerninakova Eva  wrote:
>>
>>> Hi Daniel,
>>>
>>> Considering the last year discussion about integrating Angular 6
>>> template translations into the Evergreen translation tools, I would like to
>>> ask a question about translation workflow of Evergreen 3.3 release. Will it
>>> change some way in comparison with previous releases, due the impossibility
>>> to use Launchpad for translations of Angular strings? And if so, how the
>>> Angular strings are supposed to be translated during the 3.3 release
>>> process? (I am asking from translators point of view.)
>>>
>>> Thanks for the answer ;-)
>>> Eva
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---
>>> Mgr. Eva Cerniňáková
>>> cer...@jabok.cz
>>> Tel. +420 211 222 409
>>>
>>> Knihovna Jabok
>>> http:/knihovna.jabok.cz
>>> Tel.  +420 211 222 410
>>> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
>>> Salmovská 8, 120 00 Praha 2
>>>
>>>
>>>
>>> st 20. 2. 2019 v 16:03 odesílatel Daniel Wells 
>>> napsal:
>>>
>>>> Hello all,
>>>>
>>>> Two weeks have slid by once more, and today we mark, ostensibly, the
>>>> feature freeze for Evergreen 3.3.  Any new features not committed by the
>>>> end of the day will need to wait for the 3.4 release in the fall.  Once
>>>> again, here are the feature branches under consideration:
>>>>
>>>>
>>>> https://bugs.launchpad.net/evergreen/+bugs?%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=WISHLIST_option=none%3Alist=86802=Search=title=0
>>>>
>>>>
>>>> As careful observers will note, we still have one week after today
>>>> before the 3.3 beta.  However, this exists not as a time to continue adding
>>>> features, but as a time to make corrections for obvious issues which crop
>>>> up due to feature freeze activity.  The cutoff for new features has
>>>> historically encouraged a mad dash of activity, and this scheduling gap
>>>> exists not as an excuse to postpone such dashings, but to remedy the
>>>> problems it brings.  So I gladly encourage those so inclined to dash as
>>>> madly as ever, but understand that it ends tonight!
>>>>
>>>> Now, that said, if a branch is in an obvious 

Re: [OPEN-ILS-GENERAL] Translations in Angular 6+ (Was Evergreen 3.3 Release Update)

[Bill Erickson]

Dan,

Let's be sure to export the current translations before any changes are
made.  IIRC, we want .xmb format, though it's probably a good idea to
export a few more formats to be safe.  Once you select a locale, the export
option is the first/top tool in the toolbar along the right.

I'll go ahead and export the current .xmb file for Czech and commit it to a
working branch for safe keeping.

-b



On Wed, Mar 20, 2019 at 12:11 PM Daniel Wells  wrote:

> Hello Eva,
>
> Thank you for raising this concern.  I think we are in the process of
> figuring things out as we go along.
>
> Our current best plan (I think) is to use the account we set up with
> POEditor.com.  It looks like you already have an account there, so at least
> you are familiar with what I am talking about.  What hasn't been figured
> out yet is what that overall update process looks like, and what the new
> build steps will be.  For the first part at least, your input will be very
> valuable.
>
> We did a test import back in November or so (I think it was at the
> Hack-a-way).  I would like to try to do another import to add any
> new/changed strings and see what happens, but being a completely new and
> unfamiliar tool, I am a little afraid of losing any work already put in
> there.
>
> So, a few questions:
>
> 1) Based on what you have already done in POEditor, do you think it is a
> viable solution?
>
> 2) I will do my best to preserve what is there, and I hope the re-import
> does the right thing, but how much would it take to redo the work done
> there so far if things go very badly?
>
> 3) Do you have a planned timeline for upgrading to 3.3?
>
> Sincerely,
> Dan
>
>
> On Mon, Feb 25, 2019 at 11:52 AM Cerninakova Eva  wrote:
>
>> Hi Daniel,
>>
>> Considering the last year discussion about integrating Angular 6 template
>> translations into the Evergreen translation tools, I would like to ask a
>> question about translation workflow of Evergreen 3.3 release. Will it
>> change some way in comparison with previous releases, due the impossibility
>> to use Launchpad for translations of Angular strings? And if so, how the
>> Angular strings are supposed to be translated during the 3.3 release
>> process? (I am asking from translators point of view.)
>>
>> Thanks for the answer ;-)
>> Eva
>>
>>
>>
>>
>>
>>
>>
>> ---
>> Mgr. Eva Cerniňáková
>> cer...@jabok.cz
>> Tel. +420 211 222 409
>>
>> Knihovna Jabok
>> http:/knihovna.jabok.cz
>> Tel.  +420 211 222 410
>> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
>> Salmovská 8, 120 00 Praha 2
>>
>>
>>
>> st 20. 2. 2019 v 16:03 odesílatel Daniel Wells 
>> napsal:
>>
>>> Hello all,
>>>
>>> Two weeks have slid by once more, and today we mark, ostensibly, the
>>> feature freeze for Evergreen 3.3.  Any new features not committed by the
>>> end of the day will need to wait for the 3.4 release in the fall.  Once
>>> again, here are the feature branches under consideration:
>>>
>>>
>>> https://bugs.launchpad.net/evergreen/+bugs?%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=WISHLIST_option=none%3Alist=86802=Search=title=0
>>>
>>>
>>> As careful observers will note, we still have one week after today
>>> before the 3.3 beta.  However, this exists not as a time to continue adding
>>> features, but as a time to make corrections for obvious issues which crop
>>> up due to feature freeze activity.  The cutoff for new features has
>>> historically encouraged a mad dash of activity, and this scheduling gap
>>> exists not as an excuse to postpone such dashings, but to remedy the
>>> problems it brings.  So I gladly encourage those so inclined to dash as
>>> madly as ever, but understand that it ends tonight!
>>>
>>> Now, that said, if a branch is in an obvious state of active review and
>>> revision, yet doesn't make the cutoff, please let me know and we can
>>> probably work it in.  I intend to start doing internal building and testing
>>> starting tomorrow morning, and will not be terribly keen on straggling code
>>> walking in unannounced.  Thank you for your diligence and understanding.
>>>
>>> Sincerely,
>>> Dan
>>>
>>>
>>> On Wed, Feb 6, 2019 at 12:40 PM Daniel Wells  wrote:
>>>
 Dearest fellow Evergreeners,

 After several months of quiet contemplation and tireless toiling by
 many members of the Evergreen community, it is past time for a brief
 message from me, your minimalist 3.3 release manager.

 First, as we enter this final trimester of the release process, it
 seems worth revisiting the originally proposed timeline:

 2/20/19 - Feature freeze
 2/27/19 - Beta release
 3/20/19 - Release Candidate
 3/27/19 - Final release

 Accordingly, we are now exactly two weeks away from our intended
 feature freeze date.  Please recall, however, that there is now a one week
 buffer between feature cutoff and the actual beta release, so if we reach

Re: [OPEN-ILS-GENERAL] Angular staff catalog dev update / demo server

[Bill Erickson]

On Tue, Mar 12, 2019 at 12:16 PM Jennifer Bruch  wrote:

> Hi Bill,
> question about the staff catalog functionality. How would one go about
> opening up one or more records from a results list in a new tab? When I try
> to right click on one, the new tab opens but fails to load.
>
>
Good question.  We definitely want those links to behave like standard
browser links.  I've opened a bug to address this:
https://bugs.launchpad.net/evergreen/+bug/1819745

-b



>

[OPEN-ILS-GENERAL] Angular staff catalog dev update / demo server

[Bill Erickson]

Hi All,

I just wanted to give an update on the staff catalog work that started back
in 3.2.

As of 3.3, it's possible to enable the "experimental" catalog in the
browser client via library setting.  When enabled, a new menu option will
appear in the Cataloging menu called "Staff Catalog (Experimental)".  While
the catalog is not ready for prime time, it's come a long way between 3.2
and 3.3, and I think it's a good time for some brave users to kick the
tires and let us know how things are looking.

Note it's also possible to access the staff catalog without enabling the
menu option by navigating to https://example.org/eg2/staff/catalog

To make testing and review a little bit easier I have also set up a demo
server at https://evgdemo.kcls.org/eg/staff  It contains the Concerto data
set and users can log in with admin / demo123  (please be nice).

My hope is to keep this server running the latest catalog patches for
review at least for the next few months.  It is currently running Evergreen
master plus the following patches:

https://bugs.launchpad.net/evergreen/+bug/1819053
https://bugs.launchpad.net/evergreen/+bug/1819498
https://bugs.launchpad.net/evergreen/+bug/1818288

I have updated the staff catalog wiki page to include the above patches.

https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:angular_staff_catalog

Any feedback here, Launchpad, etc. appreciated.

Thanks,

-b

Re: [OPEN-ILS-GENERAL] Developers' Meeting for Today Postponed

[Bill Erickson]

Replying to thread as a reminder we have a meeting today...

-b

On Thu, Dec 6, 2018 at 8:03 AM Goben, Anna  wrote:

> I've added an entry to the Dev meeting agenda for setting the 2019
> Hack-A-Way dates.  We have a bit of flexibility with our preferred site at
> the moment, so we can try to target a good time for everyone to travel.
> The survey link is on the agenda or you can access it here:
> https://goo.gl/forms/Ts3o6bo9OsmsAe2w1
>
> Thanks!
> -Anna
>
> Anna Goben
> Evergreen Indiana Coordinator
> Indiana State Library
> 140 N Senate Ave
> Indianapolis, IN 46204
> 317-234-6624
> Fax: 317-232-3713
>
> -Original Message-
> From: Open-ils-general [mailto:
> open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason
> Stephenson
> Sent: Wednesday, December 05, 2018 3:22 PM
> To: OpenILS General List 
> Subject: [OPEN-ILS-GENERAL] Developers' Meeting for Today Postponed
>
>  This is an EXTERNAL email. Exercise caution. DO NOT open attachments
> or click links from unknown senders or unexpected email. 
> 
>
> Hi, all.
>
> The developers' IRC meeting that was scheduled for today at 3:00 PM EST
> has been rescheduled to next Wednesday, 12 December 2018 at 3:00 PM EST or
> 20:00 UTC.
>
> I have started a draft agenda if anyone has anything to add:
>
> https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2018-12-12
>
> Cheers,
> Jason
>

Re: [OPEN-ILS-GENERAL] Angular Discussion During Hack-A-Way

[Bill Erickson]

And here's my slides:

http://git.evergreen-ils.org/?p=working/random.git;a=blob_plain;f=ang6-toturial.html;hb=refs/heads/collab/berick/ang6-tutorial#(1)

On Mon, Nov 5, 2018 at 4:30 PM Rogan Hamby 
wrote:

> I'd like to thank everyone for bearing with us while we work out some
> kinks with the new AV setup.  I think it went well and I'll be reviewing
> the audio on it this evening to see what we can improve on but for anyone
> who missed it Galen and Bill's presentation is available here:
>
> https://youtu.be/VbdgUT5Omp8
>
> One thing I personally learned is that the scheduled YouTube event has
> some awkwardness with the interface that makes it simple to share screens
> (and thus slides) which is why we started a second livestream feed.  So,
> the future events may not be "scheduled" in the Youtube language specific
> sense but things we have specific times for I will still send out
> notifications in advance to the community lists and via the community
> Twitter channel and Facebook.
>
>
>
> Rogan Hamby, MLIS
>
> Data and Project Analyst
>
> Equinox Open Library Initiative
>
> phone:  1-877-OPEN-ILS (673-6457)
>
> email:  ro...@equinoxinitiative.org
> web:  http://EquinoxInitiative.org
>

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] 3.2 Getting back on schedule

[Bill Erickson]

Galen,

Thanks for committing to work on these bugs!  Delaying the RC until Monday
the 24th sounds like a good plan, given the resource commitment.

And thanks to Kathy as well.

-b



On Tue, Sep 18, 2018 at 3:21 PM Kathy Lussier  wrote:

> I can commit to testing patches for any of those bugs.
>
> Kathy
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128kluss...@masslnc.org
>
>
>
> On Tue, Sep 18, 2018 at 3:13 PM Galen Charlton 
> wrote:
>
>> Hi,
>>
>> On Mon, Sep 17, 2018 at 4:50 PM Bill Erickson  wrote:
>> > A few web staff blockers remain.  Most of them have been there for
>> months, though, so I don't think another few days here or there is going to
>> make much difference.
>> >
>> > If that's an unfair assessment, let me know.
>>
>> Of the remaining open webstaffblocker bugs, I can commit to having
>> patches by Friday for the following ones:
>>
>> * https://bugs.launchpad.net/evergreen/+bug/1745427 (predict new
>> issues defaults to previous pattern)
>>
>> * https://bugs.launchpad.net/evergreen/+bug/1791340 (Web Client Hourly
>> Loan Checkin Time Wrong)
>> * https://bugs.launchpad.net/evergreen/+bug/1789442 (Web client: When
>> editing an hourly due date the time is automatically changed to 12:00
>> am)
>> * https://bugs.launchpad.net/evergreen/+bug/1552778 (Web client
>> check-in "effective date" and check-out "specific due date" should
>> also include times)
>>
>> Note that for the two above that the fix I'm thinking of would either
>> require an OpenSRF update, as the main change is a fix to
>> cleanse_ISO8601, or (my preferred approach) copying cleanse_ISO8601
>> over to Evergreen as (say) clean_ISO8601 and updating references
>> everywhere -- straightforward, but obviously would require a fair
>> amount of testing across the board.
>>
>> I think that amelioration, if not total fixes, should be straightforward
>> for:
>>
>> * https://bugs.launchpad.net/evergreen/+bug/1773191 (Untranslatable
>> Last Billing Type values)
>> * https://bugs.launchpad.net/evergreen/+bug/1791335 (Transferring
>> items and vol/items does not maintain stat cats)
>>
>> One that has a good start by Cesar, but looks like needs more discussion
>> is:
>>
>> * https://bugs.launchpad.net/evergreen/+bug/1746536 (web client:
>> cannot edit vol/call number in item status)
>>
>> If folks can commit to helping out with the last three in particular
>> and with testing patches for the first four, I think there would be
>> benefit to delaying the RC to the 24th to make it a true release
>> candidate.  That said, this is a position I hold at +0.75, as it would
>> be reasonable for us to also choose to make 3.2.1 a hard target for
>> those bugs.
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Implementation and Services Manager
>> Equinox Open Library Initiative
>> phone:  1-877-OPEN-ILS (673-6457)
>> email:  g...@equinoxinitiative.org
>> web:  https://equinoxInitiative.org
>> direct: +1 770-709-5581
>> cell:   +1 404-984-4366
>>
>

[OPEN-ILS-GENERAL] 3.2 Getting back on schedule

[Bill Erickson]

Hi All,

Evergreen 3.2 Beta1 was released just over a week ago followed by a
successful bug squashing week.  In that time, bugs have been found and bugs
have been squashed, as is the way, but I have not seen any new issues arise
that warrant delaying the 3.2 release schedule any further.

A few web staff blockers remain.  Most of them have been there for months,
though, so I don't think another few days here or there is going to make
much difference.

If that's an unfair assessment, let me know.

I will spend some time on bug 1787274 over the next 2 days.  It's been
difficult to track down, because so far we have not been able to recreate
the issue.  However, there should be some stop-gap solutions we can apply
before the RC is cut.

That means the release candidate build will be cut Wednesday of this week,
with the general availability build the following week.

-b

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen 3.2 Beta available for download

[Bill Erickson]

Blog entry as promised:

https://evergreen-ils.org/evergreen-3-2-first-beta-release-available/

I'd also like to give an RM shout-out to all the last-minute code wrangling
and release help from Galen Charlton, Dan Wells, Kathy Lussier, Jane
Sandberg, Remington Steed, and Jason Stephenson.  (Sincere apologies if I
left anyone out -- it was a hectic week!)

And as always, thanks to everyone in the community for making this release
possible!

-b


On Mon, Sep 10, 2018 at 9:41 AM Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Thank you Bill and all of the developers and testers! We're very excited
> about a lot of the bug fixes and new features in this one!!!
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> tmcca...@georgialibraries.org
>
> * The GPLS office is in the midst of relocating offices. We may be reached
> by all of the current mechanisms during the transition, but to ensure the
> most prompt response, please use the Help Desk:
> https://help.georgialibraries.org
>
>
> On Sun, Sep 9, 2018 at 8:02 PM, Bill Erickson  wrote:
>
>> Hi All,
>>
>> Just a quick heads up the first beta release of Evergreen 3.2 is
>> available for download on the Evergreen downloads page:
>> https://evergreen-ils.org/egdownloads/ . I'll post a more substantive
>> blog entry tomorrow about the release.  For now, I wanted to be sure this
>> week's bug squashers were aware the download was available.
>>
>> Good hunting!
>>
>> -b
>>
>
>

[OPEN-ILS-GENERAL] Evergreen 3.2 Beta available for download

[Bill Erickson]

Hi All,

Just a quick heads up the first beta release of Evergreen 3.2 is available
for download on the Evergreen downloads page:
https://evergreen-ils.org/egdownloads/ . I'll post a more substantive blog
entry tomorrow about the release.  For now, I wanted to be sure this week's
bug squashers were aware the download was available.

Good hunting!

-b

Re: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Bill Erickson]

On Tue, Aug 28, 2018 at 7:39 PM Dan Wells  wrote:

> Bill, I think this sounds fine, but would make two possible suggestions.
>

Thanks for the feedback, Dan.


>
> 1) I think we should get some kind of release built before bug-squashing
> week, to be usable for anyone wanting that sort of testing path during the
> following week.  That could easily happen late on the 7th, or we could
> XUL/Angular merge on the 6th and have the 7th to build.  Whether this is
> branded as an alpha or a beta1 doesn't matter too much, though if it is
> "feature complete", beta1 seems more correct.
>

Good point.  XUL merging will happen later, but again that should be a
relatively small change at the code level, so I'm fine calling the Sept 7
build Beta 1.


>
> 2) It is reasonable to expect this might lead to a need for a beta2, but
> my preference would be to make that call a little later on, as needed.  It
> is easy to add more delays, but assuming we'll need them all now means
> we'll never get the time back :)
>
>
Schedule update v3:

Feature freeze Sept 4th.
Angular merge by Sept 6th.
Beta 1 Sept 7th.
Bug Squashing Sept 10-14
XUL vote (and subsequent patching if approved) Sept 17th.
Remaining milestones TBD.

-b


> Just my two cents.
>
> Dan
>
> ____
> From: Open-ils-general 
> on behalf of Bill Erickson 
> Sent: Tuesday, August 28, 2018 6:11:01 PM
> To: Public Open-ILS tech discussion
> Cc: open-ils-general@list.georgialibraries.org
> Subject: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature
>   freeze and more)
>
> Breaking this message out specifically to discuss extending the 3.2
> release schedule.
>
> We have a lot of competing priorities at the moment.  This week really
> should be about wrapping up feature merges, but the pending Beta is forcing
> us to address a number of outstanding issues, and each depends on the other.
>
> Extending the release schedule seems perfectly reasonable to me.  My only
> concern is determining how best to leverage the Sept 10-14 bug squashing
> week.  Ideally, all major changes would be merged so we can work out the
> kinks during the group bug squashing.
>
> That means features, XUL removal, and Angular merging would need to be
> done by the end of next week, with time to spare to ensure all this chaos
> leaves us with a usable code base for testers.
>
> To buy us some breathing room in the short term, I'll make this proposal:
>
> Feature freeze pushed to Sept 4th.
> XUL and Angular merge freeze Sept 7th.
> Bug Squashing Sept 10-14
> Beta Sept 19th (remaining targets pushed back 2 weeks as well).
>
> This may not be the extension you were hoping for Kathy, and we can
> certainly modify this, but this at least gives us a little time to focus
> specifically on wrapping up the big ticket items before bug squashing
> ensues.
>
> Suitable compromise for now?  Thoughts?
>
> Thanks,
>
> -b
>
>
>
>
> On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier  <mailto:kluss...@masslnc.org>> wrote:
> Hi Bill,
>
> In looking at the list of showstoppers, I see one has a pullrequest, so it
> seems reasonable it could be tested and merged soon. For the other bugs,
> does anyone have a sense of whether any are particularly complex? Or are
> they mostly straightforward bugs that just haven't been addressed yet due
> to lack of tuits? If it's the latter, could we consider delaying the full
> release (with xul removal) until the showstoppers are fixed?
>
> I'm concerned about the breakage that is likely to occur the longer we
> continue to make the xul client available in our releases, but these bugs
> were identified as real issues in getting libraries to adopt the web
> client. At this time, there are just a handful of remaining showstoppers,
> and if we can commit to getting them resolved before the full release, I
> think it will make a smoother transition to 3.2 for our libraries.
>
> Kathy
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> kluss...@masslnc.org<mailto:kluss...@masslnc.org>
>
>
> On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  beric...@gmail.com>> wrote:
> Hi Scott,
>
> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org scott.tho...@sparkpa.org>  scott.tho...@sparkpa.org>> wrote:
> Hi Bill,
> I have two questions about this:
>
>
> 1.   You mentioned a vote. Who is the “we” that votes?
>
> Good question.  This would be a core developer vote.   I started typing
> this as a developer list message, then added the general list just before
> sending...
>
> From my perspective, this vote is more about getting 

Re: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Bill Erickson]

It occurs to me the XUL removal patch will not be as architecturally
significant as I had been thinking.  We will not (yet) be deleting the
entire directory tree, so the impact should be minimal for rest of the
Evergreen code.  Given that, extending the deadline for XUL removal a bit
further makes sense.

Updated proposal:

Feature freeze Sept 4th.
Angular merge by Sept 6th.
Bug Squashing Sept 10-14
XUL vote (and subsequent removal if approved) Sept 17th.
Beta Sept 19th (remaining targets pushed back 2 weeks as well).

Perhaps we can squash some of these blockers during the bug squashing week.

Comments welcome.

-b

On Tue, Aug 28, 2018 at 6:11 PM Bill Erickson  wrote:

> Breaking this message out specifically to discuss extending the 3.2
> release schedule.
>
> We have a lot of competing priorities at the moment.  This week really
> should be about wrapping up feature merges, but the pending Beta is forcing
> us to address a number of outstanding issues, and each depends on the other.
>
> Extending the release schedule seems perfectly reasonable to me.  My only
> concern is determining how best to leverage the Sept 10-14 bug squashing
> week.  Ideally, all major changes would be merged so we can work out the
> kinks during the group bug squashing.
>
> That means features, XUL removal, and Angular merging would need to be
> done by the end of next week, with time to spare to ensure all this chaos
> leaves us with a usable code base for testers.
>
> To buy us some breathing room in the short term, I'll make this proposal:
>
> Feature freeze pushed to Sept 4th.
> XUL and Angular merge freeze Sept 7th.
> Bug Squashing Sept 10-14
> Beta Sept 19th (remaining targets pushed back 2 weeks as well).
>
> This may not be the extension you were hoping for Kathy, and we can
> certainly modify this, but this at least gives us a little time to focus
> specifically on wrapping up the big ticket items before bug squashing
> ensues.
>
> Suitable compromise for now?  Thoughts?
>
> Thanks,
>
> -b
>
>
>
>
> On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier 
> wrote:
>
>> Hi Bill,
>>
>> In looking at the list of showstoppers, I see one has a pullrequest, so
>> it seems reasonable it could be tested and merged soon. For the other bugs,
>> does anyone have a sense of whether any are particularly complex? Or are
>> they mostly straightforward bugs that just haven't been addressed yet due
>> to lack of tuits? If it's the latter, could we consider delaying the full
>> release (with xul removal) until the showstoppers are fixed?
>>
>> I'm concerned about the breakage that is likely to occur the longer we
>> continue to make the xul client available in our releases, but these bugs
>> were identified as real issues in getting libraries to adopt the web
>> client. At this time, there are just a handful of remaining showstoppers,
>> and if we can commit to getting them resolved before the full release, I
>> think it will make a smoother transition to 3.2 for our libraries.
>>
>> Kathy
>>
>> --
>> Kathy Lussier
>> Project Coordinator
>> Massachusetts Library Network Cooperative
>> (508) 343-0128kluss...@masslnc.org
>>
>>
>>
>> On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  wrote:
>>
>>> Hi Scott,
>>>
>>> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
>>> scott.tho...@sparkpa.org> wrote:
>>>
>>>> Hi Bill,
>>>>
>>>> I have two questions about this:
>>>>
>>>>
>>>>
>>>> 1.   You mentioned a vote. Who is the “we” that votes?
>>>>
>>> Good question.  This would be a core developer vote.   I started typing
>>> this as a developer list message, then added the general list just before
>>> sending...
>>>
>>> From my perspective, this vote is more about getting a public record of
>>> developer buy-in (or otherwise) as is typically the case before proceeding
>>> with a large architectural change.  It also acts as a "should we do this?"
>>> safety valve.  However, I call the vote now because in my opinion as RM we
>>> are ready to proceed and I suspect that's what we'll decide.  It's not done
>>> 'til it's done, though.
>>>
>>> It's also worth reminding everyone we are also providing extended
>>> support for Evergreen 3.1, so users can continue using the XUL client for a
>>> longer period of time.  Normally, a release is supported for 12 months of
>>> bug fixes, plus 3 months of security fixes.  3.1 will be supported for a
>>> longer period of time -- dur

[OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Bill Erickson]

Breaking this message out specifically to discuss extending the 3.2 release
schedule.

We have a lot of competing priorities at the moment.  This week really
should be about wrapping up feature merges, but the pending Beta is forcing
us to address a number of outstanding issues, and each depends on the other.

Extending the release schedule seems perfectly reasonable to me.  My only
concern is determining how best to leverage the Sept 10-14 bug squashing
week.  Ideally, all major changes would be merged so we can work out the
kinks during the group bug squashing.

That means features, XUL removal, and Angular merging would need to be done
by the end of next week, with time to spare to ensure all this chaos leaves
us with a usable code base for testers.

To buy us some breathing room in the short term, I'll make this proposal:

Feature freeze pushed to Sept 4th.
XUL and Angular merge freeze Sept 7th.
Bug Squashing Sept 10-14
Beta Sept 19th (remaining targets pushed back 2 weeks as well).

This may not be the extension you were hoping for Kathy, and we can
certainly modify this, but this at least gives us a little time to focus
specifically on wrapping up the big ticket items before bug squashing
ensues.

Suitable compromise for now?  Thoughts?

Thanks,

-b




On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier  wrote:

> Hi Bill,
>
> In looking at the list of showstoppers, I see one has a pullrequest, so it
> seems reasonable it could be tested and merged soon. For the other bugs,
> does anyone have a sense of whether any are particularly complex? Or are
> they mostly straightforward bugs that just haven't been addressed yet due
> to lack of tuits? If it's the latter, could we consider delaying the full
> release (with xul removal) until the showstoppers are fixed?
>
> I'm concerned about the breakage that is likely to occur the longer we
> continue to make the xul client available in our releases, but these bugs
> were identified as real issues in getting libraries to adopt the web
> client. At this time, there are just a handful of remaining showstoppers,
> and if we can commit to getting them resolved before the full release, I
> think it will make a smoother transition to 3.2 for our libraries.
>
> Kathy
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128kluss...@masslnc.org
>
>
>
> On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  wrote:
>
>> Hi Scott,
>>
>> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
>> scott.tho...@sparkpa.org> wrote:
>>
>>> Hi Bill,
>>>
>>> I have two questions about this:
>>>
>>>
>>>
>>> 1.   You mentioned a vote. Who is the “we” that votes?
>>>
>> Good question.  This would be a core developer vote.   I started typing
>> this as a developer list message, then added the general list just before
>> sending...
>>
>> From my perspective, this vote is more about getting a public record of
>> developer buy-in (or otherwise) as is typically the case before proceeding
>> with a large architectural change.  It also acts as a "should we do this?"
>> safety valve.  However, I call the vote now because in my opinion as RM we
>> are ready to proceed and I suspect that's what we'll decide.  It's not done
>> 'til it's done, though.
>>
>> It's also worth reminding everyone we are also providing extended support
>> for Evergreen 3.1, so users can continue using the XUL client for a longer
>> period of time.  Normally, a release is supported for 12 months of bug
>> fixes, plus 3 months of security fixes.  3.1 will be supported for a longer
>> period of time -- duration TBD -- so sites will have more time before
>> needing to upgrade to 3.2.  This will buy us more time in the community to
>> continue squashing bugs as well.
>>
>>> 2.   If it is determined that not enough blockers are fixed, does
>>> this mean that a 3.2 version of XUL will be made available and XUL will not
>>> be removed until 3.3
>>>
>>> Yes, if the core developers vote not to proceed with XUL removal, it
>> would be delayed until the next release cycle (3.3).
>>
>> Just to offer some perspective, from the dev side it's not just a
>> question of how many web staff blockers remain, but how much work is
>> required to resolve each, who can sign up to fix them, how many sites they
>> likely affect, how much developer time will be siphoned away from fixing
>> these issues trying to maintain XUL in 3.2 (!), the fact the XUL is already
>> a little bit broken in 3.2 based on the agreement it would it would be
>> removed, etc, etc.
>>
>> Thanks,
>>
>> -b
>>
>>
>>

Re: [OPEN-ILS-GENERAL] 3.2 feature freeze and more

[Bill Erickson]

Hi Scott,

On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
scott.tho...@sparkpa.org> wrote:

> Hi Bill,
>
> I have two questions about this:
>
>
>
> 1.   You mentioned a vote. Who is the “we” that votes?
>
Good question.  This would be a core developer vote.   I started typing
this as a developer list message, then added the general list just before
sending...

>From my perspective, this vote is more about getting a public record of
developer buy-in (or otherwise) as is typically the case before proceeding
with a large architectural change.  It also acts as a "should we do this?"
safety valve.  However, I call the vote now because in my opinion as RM we
are ready to proceed and I suspect that's what we'll decide.  It's not done
'til it's done, though.

It's also worth reminding everyone we are also providing extended support
for Evergreen 3.1, so users can continue using the XUL client for a longer
period of time.  Normally, a release is supported for 12 months of bug
fixes, plus 3 months of security fixes.  3.1 will be supported for a longer
period of time -- duration TBD -- so sites will have more time before
needing to upgrade to 3.2.  This will buy us more time in the community to
continue squashing bugs as well.

> 2.   If it is determined that not enough blockers are fixed, does
> this mean that a 3.2 version of XUL will be made available and XUL will not
> be removed until 3.3
>
> Yes, if the core developers vote not to proceed with XUL removal, it would
be delayed until the next release cycle (3.3).

Just to offer some perspective, from the dev side it's not just a question
of how many web staff blockers remain, but how much work is required to
resolve each, who can sign up to fix them, how many sites they likely
affect, how much developer time will be siphoned away from fixing these
issues trying to maintain XUL in 3.2 (!), the fact the XUL is already a
little bit broken in 3.2 based on the agreement it would it would be
removed, etc, etc.

Thanks,

-b

[OPEN-ILS-GENERAL] 3.2 feature freeze and more

[Bill Erickson]

Hi All,

We have a busy few weeks ahead.  This Friday is our feature freeze
deadline.   All new non-bug features need to be merged by this time if they
are to be included in 3.2.  Note, however, I will not be paying very close
attention to the code until after the Sept 3rd (US) holiday.  So, there's
some breathing room with the deadline.

I ask all, especially patch developers, to review the list of pending
features and make sure there are no pending questions or issues that need
resolving:  https://bit.ly/2MyHShH

Web Staff Client Blockers and XUL Client Removal

Blockers: https://bit.ly/2PaEg2n

As I said in the last IRC meeting, if we're going to remove the XUL client
for 3.2 the removal patch needs to be merged before we cut the 3.2 Beta
(Sep 5th).  At the meeting we discussed basing this decision on whether we
have resolved enough of the web staff blocker bugs.   To that end, I
propose we have a formal vote this week on whether to remove the XUL
client.  I'll send a separate email requesting feedback and votes.  (Feel
free to respond here, though, for any discussion in the meantime).

Angular6 Client

Like the XUL removal, if we merge the Angular6 code, it must be merged
before the Beta release.  Pending issues:

1. No web service yet for translators.  We have approval from some
translators to proceed, applying translations directly to the XML files,
pending a web service similar to Launchpad's PO editor service, but for
XLIFF files.  I'd like to hear from other sites the support multiple
languages.  Is editing XML files directly acceptable?  For now, the
translators will only need to edit the browser client navigation menu and
any Ang6 UI's we agree to use (more below).

2. Final decision on list of UI's whose Angular6 version will be used in
the client.  I propose we use the Angular6 client for the Acquisitions
Admin UI's (Under Administration -> Acquisitions Administration), since
it's a fairly small self-contained list.

When users choose this menu item, it will direct them to the Ang6 page
(which looks just like the AngularJS page).  Links to some pages (e.g.
Funds) will point back to the AngularJS versions, because they are
non-trivial interfaces -- more than a simple grid.  Other links (e.g.
currency types) will link to the Ang6 versions, since they are simple CRUD
grid interfaces.  (Note for some of these, I need to add workstation
setting types).

I think we need a formal vote on this one, too, so I'll send a separate
email for that.

Scheduling

Last but not least, I have so far not extended the release schedule.
However, there's a lot yet to do!  I am happy to entertain suggestions of
extending the timeline, particularly for XUL removal and Angular6 merging,
since they are special projects that might need a little more review and
buy-in.

Questions and comments appreciated.

Thanks,

-b

[OPEN-ILS-GENERAL] 3.2 Feature slush date moved

[Bill Erickson]

Hi All,

As discussed in the IRC developer meeting this week, I'm pushing the 3.2
feature slush date back from Friday Aug 17th to Wednesday Aug 22nd, since
I'll be traveling during that time and will be generally unavailable to
participate in the festivities.

As a reminder this is the date where new features need to have a viable
code branch with a pull request tagged.

As always this does not affect bug fixes, which can be merged at any time.

This may result in pushing the 3.2 feature freeze date back as well,
depending on how many features are tagged at the last minute.  I'll keep
you posted.

Thanks,

-b

Re: [OPEN-ILS-GENERAL] standalone interface

[Bill Erickson]

On Mon, Aug 6, 2018 at 3:00 PM Terran McCanna 
wrote:

> We're using it with PINES. Our local instructions are here:
>
> https://pines.georgialibraries.org/dokuwiki/doku.php?id=circ:circulation:offline
>
> We disabled the button to download the offline patron list because it
> would not work, so we're missing the old functionality of being able to
> check for accounts with bad statuses,
>

And as a heads up, this bug should help with the block list issues (among
other things):

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

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] 3.2 Notes on browser client settings moving to server

[Bill Erickson]

On Fri, Aug 3, 2018 at 3:13 PM Kathy Lussier  wrote:

> Hi Bill,
>
> 2. A workstation setting can be turned into a user setting by creating a
>> matching user setting type (same setting name) and removing the workstation
>> setting type.  Such settings will follow the logged user account instead of
>> the workstation.
>
>
> Can we assume the opposite is true too? While testing, I was thinking that
> some sites may prefer the copy templates to be a workstation setting
> instead of a user setting.
>

Yes, with minor code changes.

The code that's loading the copy templates is specifically requesting user
setting values.  If that code were changed to use the new
user-or-workstation-or-yaous API, the existing user setting could be
migrated to a workstation setting.  Ditto the code that applies the values.

Generally speaking, we now have:

1. API to set and get user setting values
2. API to get and get org unit setting values
3. NEW API to get org-or-user-or-workstation setting values, depending on
configuration, context, and available data.
4. NEW API to set user-or-workstation setting values,  depending on
configuration.

I generally refer to the new stuff (#3 and #4) as Cascade Settings.  Any
existing user or org unit setting can be used as a Cascade Setting, if the
caller simply uses the new APIs to manage the code.  (Though, only user and
workstation settings can have values applied via the new API).

-b

[OPEN-ILS-GENERAL] 3.2 Notes on browser client settings moving to server

[Bill Erickson]

Hi All,

With special thanks to Kathy Lussier (and Chris Sharp),
https://bugs.launchpad.net/evergreen/+bug/1750894 was merged to master
today.  This change moves persistent browser client preferences / settings
out of the browser (localStorage / Hatch) to the server.  With this,
preferences and settings will persist across browser sessions and be
shareable across multiple browsers.  Clearing localStorage will no longer
delete preference values.

This code will impact administration and development of new features.  I
wanted to review some of those here since it might impact active
development.

Developers

1. New browser client settings/preferences that should persist across
browser sessions require a DB upgrade script to add the needed rows to
config.worksation_setting_type.

2. Settings that should only be stored locally (e.g. last retrieved patron)
should be stored using hatch.setLocalItem / getLocalItem or the key prefix
should be added to the list of special prefixes in hatch.js =>
service.browserOnlyPrefixes.

3. Beware that storing preferences on the server means more API calls are
needed to load the data.  Whenever possible, make use of the
hatch.getItemBatch call to condense lookups into fewer API calls.

Admins

1. Migration from browser storage to server storage should happen
seamlessly as each setting is accessed using the new code.

2. A workstation setting can be turned into a user setting by creating a
matching user setting type (same setting name) and removing the workstation
setting type.  Such settings will follow the logged user account instead of
the workstation.

3. No setting can be both a workstation and user setting.  They are
mutually exclusive.

4. Org settings with the same name as a user/workstation setting act as a
fall-through value.

5. Org setting types that match a browser preference/setting where no
user/workstation setting type exists (or has been deleted) act as a
read-only configuration for the setting.  This can be useful, for example,
for applying a grid display configuration that cannot be changed by staff.

There are more UI improvements to make for this feature, especially for
managing org unit settings, but I wanted everyone to be aware the pieces
are in place to do these things on the back-end.

-b

[OPEN-ILS-GENERAL] 3.2 July Report

[Bill Erickson]

Hi All,

We're entering the final few weeks of feature development for Evergreen
3.2, so I thought I'd send a round up of what's been going on.  It's a
large info dump, so here's the...

* Executive Summary

At the current rate, I suspect we'll have quite a few last-minute feature
merges.  Anything we can do to get some of that code merged sooner than
later is greatly appreciated.  I'll be on the lookout for features I can
review and merge over the next few weeks.

Many bug fixes have been merged (to 3.0 and up) over the past few weeks.
Many doc updates as well.  Thanks to all for these fixes!  We still have a
nice pile of web staff blocker bugs, though.  These are top priority.

And now for more details.  Let me know if I've neglected anything.
==

* 3.2 Features Merged

https://bugs.launchpad.net/evergreen/+bug/1766716 - Emergency Close Dates
(yay!)

* 3.2 Features Needing Feedback / Testing / Merging

https://bugs.launchpad.net/evergreen/+bug/1750894 - Webstaff settings at
server

https://bugs.launchpad.net/evergreen/+bug/1775466 - Angular 6 Base App
 -- Though this is targeted for 3.2, I believe we have wiggle room on
whether it's merged by then or by 3.3.  If it's not merged by 3.2, I'd like
to see it merged to master soon thereafter.

* 3.2 Features Pending Development

These will each be addressed when/if pullrequests become available before
the August 17th 3.2 feature slush deadline.

https://bugs.launchpad.net/evergreen/+bug/1777675 - Inventory Date
https://bugs.launchpad.net/evergreen/+bug/1774277 - Patron Acq Req.
Improvements
https://bugs.launchpad.net/evergreen/+bug/1777677 - Test Email Notification
https://bugs.launchpad.net/evergreen/+bug/1776020 - Patron Preferred Name
https://bugs.launchpad.net/evergreen/+bug/1779920 - Auto Renew
https://bugs.launchpad.net/evergreen/+bug/1745623 - Alert for previous
checkouts
https://bugs.launchpad.net/evergreen/+bug/1712854 - View record holds
sorting
https://bugs.launchpad.net/evergreen/+bug/1721575 - Batch search results
actions
https://bugs.launchpad.net/evergreen/+bug/1642344 - Report cloning fixes

* 3.2 and OpenSRF

The fix to bug 1775719 (Auth Proxy Logins) (Opensrf bug 1776510) will
require an opensrf update, though since it's a bug fix, it doesn't
necessarily require we cut a new major version of OpenSRF.

I do however prefer we cut a new version of OpenSRF before (or concurrent
with) 3.2 for https://bugs.launchpad.net/opensrf/+bug/1777180 (Websocketd
support).

I believe there were a few other OpenSRF bugs we wanted merged by 3.2. as
well...

* Web Staff Client Blockers

Quite a few blockers have been added over the past ~2 months.  Here's the
current list:

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

A number of these of have pullrequests and just need final testing,
sign-off's, and merging:

https://bugs.launchpad.net/evergreen/+bug/1732761
https://bugs.launchpad.net/evergreen/+bug/1739460
https://bugs.launchpad.net/evergreen/+bug/1755258
-- note opensrf requirement
https://bugs.launchpad.net/evergreen/+bug/1770973
https://bugs.launchpad.net/evergreen/+bug/1775719
-- note relation to https://bugs.launchpad.net/evergreen/+bug/1768947

* Buildmasters

Calling on buildmasters to add their names to the list for 3.2 release
building:

https://docs.google.com/spreadsheets/d/1gZayHfF7qK0zwLMEAXt-PbKBMiAM_F6EZguqzIYceBY/edit#gid=0

I've added a 3.2.beta1 build target to the doc.

Thanks!

-b

Re: [OPEN-ILS-GENERAL] Keeping similar hatch settings for multiple windows users

[Bill Erickson]

Hi Jane,

There should be a file called hatch.properties in the Hatch installation
directory.  The file contains a single property called data.directory which
is used for specifying where the Hatch data should be stored.  (It defaults
to the users's home folder).  If you set the value to a shared directory,
one where all users have read/write access, it should share the data
between them.  You may first want to copy the data from one of the users'
home directories to the new shared directory to create a base data set.

Also note https://bugs.launchpad.net/evergreen/+bug/1750894 will resolve
this by storing the settings for each workstation on the server.

-b


On Thu, Jun 7, 2018 at 11:52 AM Jane Sandberg 
wrote:

> Hi Evergreen friends,
>
> At our branch, there is one staff computer, and many staff members use
> their Windows log ins to sign in to that particular computer.
>
> Is there a way to enable hatch for all of them, and for certain hatch
> settings to apply to all of them?  We don't want to have folks to have
> to spend all that time messing with hatch when we know what
> configuration we want.
>
> Thanks!
>
>  -Jane
>
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> sand...@linnbenton.edu / 541-917-4655
> Pronouns: she/her/hers
>

Re: [OPEN-ILS-GENERAL] Final Day of Bug Squashing Week!

[Bill Erickson]

Wow, that's a lot of people.  Thanks everyone, thanks Terran!

On Fri, May 25, 2018 at 11:36 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Hello everyone!
>
> I'll keep up the tracking chart through the end of today, but this has
> already been the most successful Bug Squashing Week ever! Thank you and
> kudos to all of you who have participated, Evergreen continues to grow and
> improve because of all of you!
>
> The tracking chart is at:
> https://docs.google.com/spreadsheets/d/1pKdrHjwWpuQY-
> F0wGrIew5I65tAM4NxOZJfpJL33vDk/edit?usp=sharing
>
> I'm especially excited this time to see so many people on the chart this
> year that haven't participated before. I hope you've had a good experience
> and that this will encourage you all to continue to be involved. After all,
> thanks to all of the dedicated developers and testers, bug squashing
> happens every day, not just during Bug Squashing Week :)
>
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> 
> Atlanta, GA 30345
> 
> 404
> -235-7138
>
> tmcca...@georgialibraries.org
>
>

Re: [OPEN-ILS-GENERAL] AngularJS to Angular Transition

[Bill Erickson]

Ooops, message sent mid-typing...   I think I made my points, though.

-b

On Wed, May 16, 2018 at 2:34 PM, Bill Erickson <beric...@gmail.com> wrote:

> Hi All,
>
> I have created an AngularJS to Angular migration summary page on the wiki:
>
> https://wiki.evergreen-ils.org/doku.php?id=dev:browser_
> staff:angjs_to_ang_migration
>
> The high-level summary of the transition is we have ~3 years to make the
> move, we can do it in chunks over time, and the process should be as
> transparent as possible to staff.
>
> Included in the page are my own proposals for how we execute the
> transition.  These are meant to be a starting point for discussion.  As
> they evolve here on the list and IRC dev meetings, I will update the wiki
> page to match.
>
> One detail I'd like to highlight here, since it resulted in a lot of IRCis
> the plan to avoid using Template Toolkit in the new Angular application.
> This primarily impacts the ability to have org-unit specific template
> overlays for local customization.  This type of overlay is mainly used in
> the TPAC today, though it's also supported in the AngularJS interfaces.
>
> I appreciate any and all feedback and questions.
>
> Thanks,
>
> -b
>

[OPEN-ILS-GENERAL] AngularJS to Angular Transition

[Bill Erickson]

Hi All,

I have created an AngularJS to Angular migration summary page on the wiki:

https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:angjs_to_ang_migration

The high-level summary of the transition is we have ~3 years to make the
move, we can do it in chunks over time, and the process should be as
transparent as possible to staff.

Included in the page are my own proposals for how we execute the
transition.  These are meant to be a starting point for discussion.  As
they evolve here on the list and IRC dev meetings, I will update the wiki
page to match.

One detail I'd like to highlight here, since it resulted in a lot of IRCis
the plan to avoid using Template Toolkit in the new Angular application.
This primarily impacts the ability to have org-unit specific template
overlays for local customization.  This type of overlay is mainly used in
the TPAC today, though it's also supported in the AngularJS interfaces.

I appreciate any and all feedback and questions.

Thanks,

-b

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

[Bill Erickson]

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] Conference slides and handouts page

[Bill Erickson]

Hi Terran,

Here are the links to the HTML versions of my slides:

Angular slides:
http://git.evergreen-ils.org/?p=working/random.git;a=blob_plain;f=ang2-preso.html;hb=collab/berick/eg2018#(1)

Hatch slides:
http://git.evergreen-ils.org/?p=working/random.git;a=blob_plain;f=hatch-summary.html;hb=collab/berick/eg2018#title-slide

-b


On Tue, May 8, 2018 at 12:41 PM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Thank you!
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> 
> Atlanta, GA 30345
> 
> 404-235-7138
> tmcca...@georgialibraries.org
>
>
> On Tue, May 8, 2018 at 11:55 AM, Lynn Floyd 
> wrote:
>
>> Here is the links to my slides.
>>
>> Asciidoc: http://bit.ly/2KxXuNV
>> Documentation: http://bit.ly/2rgHXtW
>>
>>
>> *Lynn Floyd*
>> Anderson County Library
>> Anderson, SC
>> lfl...@andersonlibrary.org
>>
>>
>> -Original Message-
>> From: Terran McCanna 
>> To: "Group, Evergreen" 
>> Date: Wed, 2 May 2018 21:20:10 -0500
>> Subject: [OPEN-ILS-GENERAL] Conference slides and handouts page
>>
>> I've started posting the slides and handouts from this year's Evergreen
>> International Conference here:
>>
>> https://evergreen-ils.org/conference/2018-evergreen-internat
>> ional-conference/2018-conference-presentation-slides-and-files/
>>
>> Thank you to everyone who has already sent me their slides and handouts!
>> If you presented but haven't sent me your slides yet, please email them
>> (either files or links) to me and I'll get them added to this page.
>>
>> Thank you!
>>
>> Terran McCanna
>> PINES Program Manager
>> Georgia Public Library Service
>> 1800 Century Place, Suite 150
>> 
>> Atlanta, GA 30345
>> 404-235-7138
>> tmcca...@georgialibraries.org
>>
>>
>>
>> Lynn Floyd
>> Head of Information Technology
>> Anderson County Library
>> Anderson, SC
>> lfl...@andersonlibrary.org
>>
>
>

[OPEN-ILS-GENERAL] Evergreen 3.2 Schedule and Call for Roadmap Entries

[Bill Erickson]

Hi,



I have added the following dates to the Evergreen community calendar [1]
for the 3.2 release schedule:


Aug 17: Feature slush

Aug 31: Feature freeze / string slush

Sep 5:  Beta release

Sep 19: RC release / string freeze

Sep 25: General release



Later I'll post a poll for selecting a week for the Feedback Fest.  I'm
thinking July-ish.


==



At this time I also ask anyone developing/funding significant changes to
Evergreen that are expected to be ready by the Fall 3.2 release please add
an entry to the roadmap wiki page:


https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.2

I expect this list will shuffle some during next week's conference, so
let's plan to have all of the major entries noted by the following week,
May 11.


Thanks,



-b



[1] https://evergreen-ils.org/communicate/calendar/

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Call for Release Manager nominations - Evergreen 3.2

[Bill Erickson]

Hi,

I'd like to toss my hat in the ring as the Evergreen 3.2 release manager.
I have served as release manager in the past for Evergreen 2.8.  It's been
a little while and the process has evolved, but I look forward to the
challenge.

Evergreen 3.0 and 3.1 marked the transition period from the XUL client to
the browser client.  For 3.2, we'll be saying farewell to the XUL client
[1].  As release manager, my primary goal will be to define the process for
retiring the XUL client and helping to see that process through.  That
will, of course, include confirming that the browser client is fully up to
the task of replacing the XUL client.

Another goal of mine is to solidify a plan for upgrading our version of
AnguarJS to Angular.  This project will span multiple release cycles.  For
3.2, I hope to reach consensus on the upgrade strategy, define a project
time line, and maybe make headway on some of the code changes.

And finally, I would like to do another Feedback Fest this summer.  This is
where everyone, core committers in particular, are asked to review
outstanding pull requests and help nudge them along in a variety of ways.
I found last year's fests [2][3] to be a great way to score a lot of small
victories -- and they add up.

As far as scheduling goes, I would follow examples from releases past, with
a September release, preceded by the various slushes, freezes, betas, and
release candidates.

I'm happy to answer questions.

Thanks,

-b

[1] http://libmail.georgialibraries.org/pipermail/open-ils-d
ev/2017-August/010400.html
[2] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1
[3] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_2

On Thu, Apr 5, 2018 at 3:07 PM, Galen Charlton 
wrote:

> Hi,
>
> It's now time to decide who will be Release Manager for the autumn
> 2018 release of Evergreen, Evergreen 3.2.
>
> The Release Manager does not have to be a core committer, but does
> need to be familiar with Git and have already contributed
> substantially to the Evergreen project whether it be code or
> documentation.
>
> Nominations (including self-nominations) are due by 11:59 PM EDT on
> Friday, 20 April 2018. Nominations should be made by email to
> open-ils-...@list.georgialibraries.org with a Cc: to
> open-ils-general@list.georgialibraries.org. Replying to all on this
> email will also work.
>
> Nominees should send an email to both of the above mailing lists a
> statement about their relationship to the Evergreen community and
> their goals for the next release. The elected release manager will be
> expected to adhere to the established schedule for the release
> milestones.
>
> If more than one candidate is nominated, an election will be held in
> the #evergreen IRC channel on freenode.net on 25 April at 15:00 EDT /
> 12:00 PDT.
>
> Everyone is invited to participate in the voting. Evergreen core
> committers who cannot make the meeting may submit their vote via email
> to the open-ils-dev mailing list.
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Infrastructure and Added Services Manager
> Equinox Open Library Initiative
> phone:  1-877-OPEN-ILS (673-6457)
> email:  g...@equinoxinitiative.org
> web:  https://equinoxInitiative.org
> direct: +1 770-709-5581
> cell:   +1 404-984-4366
>

Re: [OPEN-ILS-GENERAL] metabib.browse_entry unused cleanup?

[Bill Erickson]

Hi Josh,

I don't have a yearly checklist.  I'll check the browse entries if it seems
like it's been a while or if I just did a full re-ingest.  It's low
priority.

Most of the cleanup these days is nightly, and it's the usual suspects,
circ/holds aging, auditor data, and action trigger data are the biggies.
Incidentally, the initial copy auditor and action/trigger cleanup resulted
in deleting about 1/3 of the database (by disk usage).

I still want to implement a form of bib record deletion that removes most
of the ingested data.  (I could say goodbye to 44M unused rows in
metabib.real_full_rec, for example).  That will require discussion, though,
since not everyone will want to get rid of everything (e.g. you may want to
report on deleted dibs).  This has come up in IRC a few times as well.  LP
pending.

-b



On Tue, Apr 3, 2018 at 8:44 AM, Josh Stompro <stomp...@exchange.larl.org>
wrote:

> Thanks Bill, is there any chance you have your checklist/script for what
> you cleanup shared anywhere?  I would love to see what else you target when
> you clean things up once a year.
>
>
>
> Josh Stompro - LARL IT Director
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Bill Erickson
> *Sent:* Monday, April 02, 2018 3:31 PM
> *To:* Evergreen Discussion Group <open-ils-general@list.
> georgialibraries.org>
> *Subject:* Re: [OPEN-ILS-GENERAL] metabib.browse_entry unused cleanup?
>
>
>
> Hi Josh,
>
>
>
> I clean these up about once a year.  It's never been a problem, though.  I
> just like cleaning things.
>
>
>
> -b
>
>
>
> On Mon, Apr 2, 2018 at 4:10 PM, Josh Stompro <stomp...@exchange.larl.org>
> wrote:
>
> Hello, I’ve been changing around some indexing rules and applied the fix
> to the full stop/rda relator code normalization issue and now just noticed
> that all the no longer used browse entries are sticking around in
> metabib.browse_entry.
>
>
>
> There are 175K entries out of 950K that are no longer used according to
> metabib.browse_entry_def_map and metabib.browse_entry_simple_heading_map.
>
>
>
> Has anyone found this to be an issue and removed those unused entries?  I
> don’t think this is causing any issues, it just seems strange to hold on to
> that data.  Any typo that was ever entered in a browse field and corrected
> is recorded there.
>
>
>
> Thanks
>
> Josh
>
>
>
> Lake Agassiz Regional Library - Moorhead MN larl.org
>
> Josh Stompro | Office 218.233.3757 EXT-139 <(218)%20233-3757>
>
> LARL IT Director | Cell 218.790.2110 <(218)%20790-2110>
>
>
>
>
>

Re: [OPEN-ILS-GENERAL] metabib.browse_entry unused cleanup?

[Bill Erickson]

Hi Josh,

I clean these up about once a year.  It's never been a problem, though.  I
just like cleaning things.

-b

On Mon, Apr 2, 2018 at 4:10 PM, Josh Stompro 
wrote:

> Hello, I’ve been changing around some indexing rules and applied the fix
> to the full stop/rda relator code normalization issue and now just noticed
> that all the no longer used browse entries are sticking around in
> metabib.browse_entry.
>
>
>
> There are 175K entries out of 950K that are no longer used according to
> metabib.browse_entry_def_map and metabib.browse_entry_simple_heading_map.
>
>
>
> Has anyone found this to be an issue and removed those unused entries?  I
> don’t think this is causing any issues, it just seems strange to hold on to
> that data.  Any typo that was ever entered in a browse field and corrected
> is recorded there.
>
>
>
> Thanks
>
> Josh
>
>
>
> Lake Agassiz Regional Library - Moorhead MN larl.org
>
> Josh Stompro | Office 218.233.3757 EXT-139 <(218)%20233-3757>
>
> LARL IT Director | Cell 218.790.2110 <(218)%20790-2110>
>
>
>

Re: [OPEN-ILS-GENERAL] Proposed Change to LP Bug Tracking

[Bill Erickson]

I like it, Dan.  Thanks for the proposal.

-b

On Fri, Mar 30, 2018 at 10:08 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> I think that's an excellent plan.
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> 
> Atlanta, GA 30345
> 
> 404-235-7138 <(404)%20235-7138>
> tmcca...@georgialibraries.org
>
>
> On Fri, Mar 30, 2018 at 10:00 AM, Daniel Wells  wrote:
>
>> Hello all,
>>
>> Our current practice is to only allow bugs to be targeted to a release
>> only if there is code ready for testing.  This change was made several
>> years back to help focus community efforts on testing of existing fixes,
>> and also to avoid a lot of extra work in constantly moving huge numbers of
>> bugs from milestone to milestone when no effort was being made to actually
>> address them.  Overall, this change has worked as intended, and has greatly
>> helped cases where branches would previously sit for months (or years)
>> without inclusion into the shared codebase, or at least feedback.
>>
>> Unfortunately, this practice has also left a hole where some of our worst
>> bugs are not getting the attention they deserve.  While we met our goal of
>> satisfying all the "High" priority bugs targeted at 3.1 before final
>> release, we currently have 25 other "High" priority bugs not targeted at
>> any 3.1 milestone at all.  I am not sure how others work, but at least for
>> me, as a release approaches, I am focused almost exclusively on the
>> activity for bugs within the next release milestone, and it is therefore
>> easy to lose track of important bugs where no branch has been offered (as
>> those bugs, by current standards, remain untargeted).
>>
>> The natural solution, of course, is to target important bugs even before
>> any solution exists.  (This does happen in some cases already.)  The
>> challenge, then is to do this without again causing the issues we've faced
>> in the past.  As stated, we currently have 25 such bugs, so it seems we
>> aren't in imminent danger of a sudden deluge.  Still, I think we should
>> have some modest standards to keep the bug flow reasonable and usable.
>> With that in mind, here is a proposed starting point to work from:
>>
>> 1. Any bug with a status of "High" or "Critical" can be targeted to a
>> milestone by the release manager/maintainer at any time.
>> 2. Any High/Critical bug with at least 3 "affects me too" votes can be
>> targeted to a milestone at any time by anyone.
>> 3. A targeted High/Critical bug with no pullrequest is not a guarantee of
>> inclusion the next release.  Timely releases are required for getting
>> existing committed fixes to end users, so any delay for a High/Critical bug
>> with no pullrequest will remain at the discretion of the release
>> manager/maintainer.
>>
>> Overall, this is a very minor change, but given the cooperative nature of
>> our community, there is little which can be done to actually force action
>> on these bugs.  The goal, instead, is to make sure those responsible for
>> releases are well aware of community needs, and also requiring us to at
>> least confront any such bugs at each release time.
>>
>> Feedback is welcome!
>>
>> Sincerely,
>> Dan
>>
>
>

Re: [OPEN-ILS-GENERAL] Hatch installer can't detect java

[Bill Erickson]

Hi,

I have copied the latest Hatch Windows installer (the same as the
Mobius link) to
/var/www/open-ils.org/downloads/Hatch-Installer-0.1.3.exe on
evergreen-ils.org.

https://evergreen-ils.org/downloads/Hatch-Installer-0.1.3.exe

If someone could please update the downloads page to use this new
version, I'd appreciate it.  The new version should be used by all
versions of Evergreen.

-b



On Wed, Jan 3, 2018 at 2:28 PM, Jane Sandberg  wrote:
> Update: this installer from the Mobius Consortium worked for me:
> https://dropbox.mobiusconsortium.org/pickup/Hatch-Installer-0.1.3.exe
>
> But the one from the official Evergreen Web site did not:
> https://evergreen-ils.org/downloads/previews/Hatch_Windows_Installer.0.0.3.exe
>
> On Wed, Jan 3, 2018 at 10:41 AM, Marcelo Lorca  
> wrote:
>> The version of Java is correct for you evergreen?.
>>
>> 2018-01-03 15:27 GMT-03:00 Jane Sandberg :
>>>
>>> Hi Evergreeners,
>>>
>>> When I try to run the hatch installer on a Windows 7 machine, I get
>>> the following error message: "Java not detected. Setup will now exit."
>>>
>>> However, the JRE is totally installed, and no other program that
>>> relies on java is complaining.  When I run `java -version` in the
>>> command prompt, I get the following output:
>>>
>>> java version "1.8.0_151"
>>> Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
>>> Java HotSpot(TM) Client VM (build 25.151-b12, mixed mode)
>>>
>>> Any suggestions for what I should try next?
>>>
>>> Thanks!
>>>
>>>   -Jane
>>>
>>> --
>>> Jane Sandberg
>>> Electronic Resources Librarian
>>> Linn-Benton Community College
>>> sand...@linnbenton.edu / 541-917-4655
>>> Pronouns: she/her/hers or they/them/theirs
>>
>>
>>
>>
>> --
>> *
>> Marcelo Lorca González
>> Bibliotecario Documentalista
>> Programador Computacional
>>
>
>
>
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> sand...@linnbenton.edu / 541-917-4655
> Pronouns: she/her/hers or they/them/theirs

Re: [OPEN-ILS-GENERAL] Paypal Link

[Bill Erickson]

Hi Scott,

We're using PayPal's "Hosted Pages":
https://developer.paypal.com/docs/classic/payflow/gs_ppa_hosted_pages/

PP has a dizzying array of options, so I don't know if it's similar to
Payflow Link.  The gist is the patron is sent to a PayPal page to enter
their credit card info.  This of course keeps the card data away from EG.

The code is sharable if there's interest, but it would require some cleanup
to get it working with stock EG, particularly with respect to TPAC template
integration.

-b


On Fri, Sep 1, 2017 at 10:27 AM, Dawn Dale <dd...@georgialibraries.org>
wrote:

> Hi Scott,
>
> I would be very interested in knowing this as well. We tried to work with
> Paypal but were not able to do so without a gateway that was an additional
> monthly fee at that time. I would also be interested to know if the patrons
> credit card information passes through the Evergreen server.  Bill Erikson
> sent this out regarding PCI compliance in May of this year.
>
> "PayPal (including PayFlowPro) and Authorize.net both require CC data to
> pass through the EG server network, before getting relayed to the
> PayPal/Authorize.net API server.  The card data may not be stored in
> Evergreen's database, but traversing the network alone is enough to require
> a hefty amount of PCI compliance work.  Stripe is the only option where the
> data never touches the EG server network."
>
> Bill Erickson
>
> 5:29 PM
>
> to Evergreen
>
> On Tue, May 9, 2017 at 5:14 PM
>
>
> Thanks,
>
> Dawn Dale
> Helpdesk Manager
> Georgia Public Library Service
> 1800 Century Place Suite 150
> Atlanta, GA 30345
> 404-235-7136 <(404)%20235-7136>
> dd...@georgialibraries.org
>
>
> On Fri, Sep 1, 2017 at 8:40 AM, scott.tho...@sparkpa.org <
> scott.tho...@sparkpa.org> wrote:
>
>> Hi,
>>
>>It appears a library can use Paypal, PayflowPro, Stripe, and
>> Authorize.net for credit card payments via the OPAC, but does anyone know
>> if it will work with Payflow Link
>> <https://www.paypal.com/us/webapps/mpp/payflow-payment-gateway>?
>>
>>
>>
>> Thank you,
>>
>> Scott
>>
>>
>>
>>
>>
>> Scott Thomas
>>
>> Executive Director
>>
>> *PaILS / SPARK*
>>
>> (717) 873-9461
>>
>> scott.tho...@sparkpa.org
>>
>> Stay informed! Join the SPARK-User Email List:
>>
>> https://mail.palibrary.org/mailman/listinfo/spark-users
>>
>> [image: Description: Description: Training | SPARK – Pennsylvania's
>> Statewide Library System] <http://www.palibrary.org/pails/>
>>
>>
>>
>
>

Re: [OPEN-ILS-GENERAL] Evergreen Self-Check and locking media cases

[Bill Erickson]

I'm late to the thread, but wanted to chime in that we at KCLS make heavy
use of the self checkout interface.   It's heavily modified, primarily for
look and feel, but we are also testing a locally coded version of bug
#1512171 (My OPAC-style renewals).  Unfortunately the code is not easily
shared, since it's built atop years of customization, but we hope to
eventually rebase to the community code, so having it be part of stock EG
is something I'm interested in.

Also, when the time comes for major overhaul, I started a proof-of-concept
branch to port self checkout to Angular.  It's bare bones, but mostly
works, minus a lot of edge case handling.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/angular-selfcheck-exp-wip

I'll open a bug for this...

-b



On Thu, Jul 27, 2017 at 9:30 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Yes, me too. I tweaked a few little things on ours with the layout, but
> nothing major.
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138 <(404)%20235-7138>
> tmcca...@georgialibraries.org
>
>
> On Wed, Jul 26, 2017 at 5:18 PM, Yamil Suarez  wrote:
>
>> Josh,
>>
>> I would like to also see customizations you made made to Self-Check code,
>> so I can get ideas. I had been meaning to ask you when I saw this thread.
>>
>> Thanks in advance,
>> Yamil
>>
>>
>>
>>
>>
>> 
>>
>> Yamil Suarez, MCS
>> Associate Director of Library Systems & Web Development
>>
>> Stan Getz Library
>> Berklee College of Music
>> 1140 Boylston St
>> Boston, MA 02215
>>
>> ysua...@berklee.edu
>> 617-747-2617 <(617)%20747-2617>
>>
>> On Wed, Jul 26, 2017 at 3:49 PM, Josh Stompro > > wrote:
>>
>>> Joe, I have a fix for keeping the cursor focus always on the scan box.
>>> We also use touch screens for our self checks and we were having trouble
>>> with the fact that it was easy to move the focus, which would cause the
>>> next scan to silently fail, and sometimes switch screens.
>>>
>>> I have a bug report on it, but haven’t actually posted the code there
>>> yet.  I’ll try and do that soon.
>>>
>>> https://bugs.launchpad.net/evergreen/+bug/1560601
>>>
>>>
>>>
>>> We have also had trouble with the print list button that exists on the
>>> checkout screen.  Some significant portion of users would press that when
>>> they were done, get a printout and then walk away.  I guess they thought
>>> that was the logout and print a receipt button.  Then the next users would
>>> walk up and sometime check out items on the first person’s account.
>>>
>>> https://bugs.launchpad.net/evergreen/+bug/1555791
>>>
>>>
>>>
>>> I would love to collaborate with you on making the self check more touch
>>> screen friendly.  I can share the css changes I’ve made just to enlarge
>>> everything to make it easier to see and to make the buttons easier to press.
>>>
>>>
>>>
>>> Josh Stompro - LARL IT Director
>>>
>>>
>>>
>>> *From:* Open-ils-general [mailto:open-ils-general-bounc
>>> e...@list.georgialibraries.org] *On Behalf Of *Joe Knueven
>>> *Sent:* Wednesday, July 26, 2017 10:58 AM
>>> *To:* Evergreen Discussion Group
>>>
>>> *Subject:* Re: [OPEN-ILS-GENERAL] Evergreen Self-Check and locking
>>> media cases
>>>
>>>
>>>
>>> While we’re on the subject of user-friendliness of the built in
>>> self-checkout, does anyone have any .tt2 modifications that they are
>>> pleased with and would be willing to share?
>>>
>>>
>>>
>>> I’ve had tweaking the scripting to make the navigation links more button
>>> like (ie touch screen friendly) on my to-do list, but it’s taken me an
>>> especially long time to get around to the first step of teaching myself a
>>> basic amount of tt2 scripting.
>>>
>>>
>>>
>>> Have a good day.
>>>
>>>
>>>
>>> Joe
>>>
>>>
>>>
>>>
>>>
>>> Joseph Knueven, Director
>>>
>>> Germantown Public Library
>>>
>>> 51 North Plum Street
>>>
>>> Germantown, OH 45327
>>>
>>> 937-855-4001 <(937)%20855-4001>
>>>
>>>
>>>
>>> *From:* Open-ils-general [mailto:open-ils-general-bounc
>>> e...@list.georgialibraries.org
>>> ] *On Behalf Of *Terran
>>> McCanna
>>> *Sent:* Wednesday, July 26, 2017 11:16 AM
>>> *To:* Evergreen Discussion Group >> libraries.org>
>>> *Subject:* Re: [OPEN-ILS-GENERAL] Evergreen Self-Check and locking
>>> media cases
>>>
>>>
>>>
>>> >>Renewal seems to work fine.  You just scan an item that's
>>> already checked out and it figures out that a renewal is in order and
>>> available.<<
>>>
>>> Interesting. There's nothing in the interface that tells the patron that
>>> they can do that, or that tells them how. Patrons typically don't have
>>> books in hand when they wish to renew, so they'd need to understand that
>>> they could go to the Items out screen and copy and paste the barcodes.
>>> Online instructions 

[OPEN-ILS-GENERAL] Heads up & feedback for LP #1635737 (circ duration calculation changes)

[Bill Erickson]

Hi All,

I wanted to give bug #1635737 [1] some publicity, since it could lead to
unexpected results once merged.  The bug started as a way to ensure that
time changes were taken into account when calculating due dates for
circulations.  The end result, apart from fixing the bug, is an interesting
new feature that might cause confusion if you're not expecting it.

In short, circulation durations will be dynamic and context sensitive.

For example...

In Evergreen today, a circulation duration of "1 month" always means 30
days (plus a few hours which are essentially ignored).  With the new code,
"1 month" will have a different length depending on when it's calculated.

An item checked out Jan 5 will be due Feb. 5, after 31 days.  An item
checked out Feb. 5 will be due March 5, 28 days later.  The length of the
month does not matter.  And... this will now be called the "28 days later"
feature.

To have a duration that's always 30 days, then a duration value of "30
days" will behave as expected (with the added benefit of correctly handling
time changes).

Since circulation durations in EG are typically based on days and not
months (or years), I don't expect this change to have a huge impact.  It's
good to be aware of it, though.

Thanks,

-b

[1] https://bugs.launchpad.net/evergreen/+bug/1635737

Re: [OPEN-ILS-GENERAL] Credit Card - Stripe Vs Paypal & PCI

[Bill Erickson]

On Tue, May 9, 2017 at 5:14 PM, Jason Stephenson  wrote:

> Josh,
>
> Using PayPal is similar to Stripe, since the transaction is completed
> via PayPal and the CC data is not stored in Evergreen.
>

PayPal (including PayFlowPro) and Authorize.net both require CC data to
pass through the EG server network, before getting relayed to the
PayPal/Authorize.net API server.  The card data may not be stored in
Evergreen's database, but traversing the network alone is enough to require
a hefty amount of PCI compliance work.  Stripe is the only option where the
data never touches the EG server network.

-b



>
> We disabled the staff client credit card interface by commenting out the
> relevant menuitem in Open-ILS/xul/staff_client/server/patron/bill2.xul.
> (IANM, that relevant menuitem is on line 107.) We have not made a
> similar change to the web staff client because we are not using it, yet.
>
> HtH,
> Jason
>
> On 05/09/2017 04:48 PM, Josh Stompro wrote:
> > Hello, we are currently using payflow pro, which I think means that our
> > evergreen server handles the CC data and puts it in PCI scope.  From
> > what I’m reading, if we switched over to using Stripe, which uses a
> > javascript library client side to submit the payment, then it would take
> > our server out of scope.  Does the Paypal code work the same way?
> >
> >
> >
> > It looks like the tpac supports Stripe, but the web based self check
> > does not.  How about the staff client/web staff client payment
> > interface.  Does that support Stripe?
> >
> >
> >
> > Along the same lines, is there a way to disable the staff client credit
> > card interface.  We don’t want staff handling credit cards with that
> > interface, since they have to type in the code and info, which I believe
> > isn’t PCI compliant, but I haven’t found a setting to disable that but
> > allow tpac payments.
> >
> >
> >
> > Thanks
> >
> > Josh
> >
> >
> >
> >
> >
> > Lake Agassiz Regional Library - Moorhead MN larl.org
> >
> > Josh Stompro | Office 218.233.3757 EXT-139
> >
> > LARL IT Director | Cell 218.790.2110
> >
> >
> >
>

Re: [OPEN-ILS-GENERAL] What does the "Holds Expire Alert Interval" library setting do?

[Bill Erickson]

On Thu, May 4, 2017 at 11:57 AM, Diane Disbro 
wrote:

> Good morning -
>
> This is interesting. Patrons at my branch usually pick up holds before
> they expire but I know that isn't true everywhere. An email or text
> reminder would be helpful.
>
>
Hi Diane,

I believe the setting in question relates to holds that were never
captured.  There is an email notification in EG called "Hold Expires from
Shelf Soon" that alerts patrons when their captured holds have been sitting
on the shelf too long.

-b




> Thank you.
>
> Diane Disbro
> Circulation Coordinator/Branch Manager
> Union Branch
> Scenic Regional Library
> 308 Hawthorne Drive
> Union, MO 63084
> 636-583-3224
> ddis...@scenicregional.org
> www.scenicregional.org
>
>
> -Original Message-
> From: Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] On Behalf Of Galen Charlton
> Sent: Thursday, May 04, 2017 9:47 AM
> To: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] What does the "Holds Expire Alert
> Interval" library setting do?
>
> Hi,
>
> On Thu, May 4, 2017 at 9:52 AM, Morgan, Michele 
> wrote:
> > But I can't see that the circ.hold_expire_alert_interval ou setting is
> > actually used anywhere. Maybe someone with better eyes than mine can
> > shed some light?
>
> I did some digging, and that setting is indeed not currently used.
> However, it was used back in the JSPac days, where it specified at what
> point in time to apply a CSS style to the My Account holds list to
> highlight hold requests that are about to expire. It wasn't carried over
> into TPAC.
>
> I'll leave it to others to file a bug in LP to either remove the setting
> or to reimplement it in TPAC.
>
> As a side note, I tracked this down by using the following Git command to
> identify commits that included the setting's code:
>
>   git log -S "circ.hold_expire_alert_interval" --source
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Infrastructure and Added Services Manager Equinox Open Library Initiative
> phone:  1-877-OPEN-ILS (673-6457)
> email:  g...@equinoxinitiative.org
> web:  https://equinoxInitiative.org
> direct: +1 770-709-5581
> cell:   +1 404-984-4366
>
>

Re: [OPEN-ILS-GENERAL] Notes from Wait Wait Do Tell Me conference session

[Bill Erickson]

Hi Jennifer,

Yes, the Action/Trigger event definitions have an "owner" field that limits
the scope of the generated events.  For overdues/predues, the owner would
limit to circulations that occurred at (or below) the specified owner.

If you wanted to limited by patron home library instead, you could add a
"home_ou":[1,2,3,...] filter next to (or in place of) the "profile" filter
from my example.  These would be org unit ID (actor.org_unit.id) values.

-b


On Mon, Apr 10, 2017 at 3:10 PM, Walz, Jennifer <jlw...@asbury.edu> wrote:

> Bill,
>
>
>
> Thanks!   That is so very helpful!
>
>
>
>   Can this be done to set certain notice action triggers for different
> OU?
>
>
>
> Jennifer
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Bill Erickson
> *Sent:* Monday, April 10, 2017 2:44 PM
> *To:* Evergreen Discussion Group
> *Subject:* Re: [OPEN-ILS-GENERAL] Notes from Wait Wait Do Tell Me
> conference session
>
>
>
> Hi,
>
>
>
> As promised at the session, here's a quick rundown of limiting notices to
> specific profile groups.
>
>
>
> 1. Create a custom filter file with a profile limiter.  Here's an example
> overdue notice filter limited to users with profile ID (
> permission.grp_tree.id) values 35, 1002, or 1003.  The "-exists" block is
> where the magic happens.
>
>
>
> {
>
> "checkout.due" : {
>
> "context_org" : "circ_lib",
>
> "filter" : {
>
> "checkin_time" : null,
>
> "-or" : [
>
> { "stop_fines" : ["MAXFINES"] },
>
> { "stop_fines" : null }
>
> ],
>
> "-exists" : {
>
> "select" : {"au" : ["id"]},
>
> "from"   : "au",
>
> "where"  : {
>
> "profile" : [35, 1002, 1003],
>
> "id" : { "=" : {"+circ" : "usr"} }
>
> }
>
> }
>
> }
>
> }
>
> }
>
>
>
> 2. Give the notice in question a unique granularity value in the admin
> interface.
>
>
>
> 3. Tell action trigger to use the custom filter file when generating
> notices for the unique granularity:
>
>
>
> perl action_trigger_runner.pl --granularity-only --granularity
> my-unique-granularity --custom-filters /path/to/my-custom-filter.json
>  [...other parameters]
>
>
>
> Hope this helps.
>
>
>
> -b
>
>
>
>
>
>
>
>
>
> On Fri, Apr 7, 2017 at 3:05 PM, Kathy Lussier <kluss...@masslnc.org>
> wrote:
>
> Hi all,
>
> I have created a Google doc with the questions and answers at today's Wait
> Wait Do Tell Me Conference sessions.
>
> Questions that are answered in the Doc:
>
> Why does my new item not capture existing holds when I check it in?
>
> When are patron buckets coming?
>
> How can you create different types of notifications for different user
> groups?
>
> Will there be an offline mode in the web client?
>
> Learn the answer to these questions and more in the Google doc at
> https://docs.google.com/document/d/1F_84CHvUcCkdMdXd-
> iTxdHF14bsh1QTPMIwge9IrFrU/edit?usp=sharing
>
> Kathy Lussier
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>
>

Re: [OPEN-ILS-GENERAL] Notes from Wait Wait Do Tell Me conference session

[Bill Erickson]

Hi,

As promised at the session, here's a quick rundown of limiting notices to
specific profile groups.

1. Create a custom filter file with a profile limiter.  Here's an example
overdue notice filter limited to users with profile ID (
permission.grp_tree.id) values 35, 1002, or 1003.  The "-exists" block is
where the magic happens.

{
"checkout.due" : {
"context_org" : "circ_lib",
"filter" : {
"checkin_time" : null,
"-or" : [
{ "stop_fines" : ["MAXFINES"] },
{ "stop_fines" : null }
],
"-exists" : {
"select" : {"au" : ["id"]},
"from"   : "au",
"where"  : {
"profile" : [35, 1002, 1003],
"id" : { "=" : {"+circ" : "usr"} }
}
}
}
}
}

2. Give the notice in question a unique granularity value in the admin
interface.

3. Tell action trigger to use the custom filter file when generating
notices for the unique granularity:

perl action_trigger_runner.pl --granularity-only --granularity
my-unique-granularity --custom-filters /path/to/my-custom-filter.json
 [...other parameters]

Hope this helps.

-b




On Fri, Apr 7, 2017 at 3:05 PM, Kathy Lussier  wrote:

> Hi all,
>
> I have created a Google doc with the questions and answers at today's Wait
> Wait Do Tell Me Conference sessions.
>
> Questions that are answered in the Doc:
>
> Why does my new item not capture existing holds when I check it in?
>
> When are patron buckets coming?
>
> How can you create different types of notifications for different user
> groups?
>
> Will there be an offline mode in the web client?
>
> Learn the answer to these questions and more in the Google doc at
> https://docs.google.com/document/d/1F_84CHvUcCkdMdXd-iTxdHF1
> 4bsh1QTPMIwge9IrFrU/edit?usp=sharing
>
> Kathy Lussier
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

Re: [OPEN-ILS-GENERAL] WEbby Staff Client

[Bill Erickson]

Hi Stuart,

When you say "not even an error message", do you mean in the interface or
the JavaScript console?

What happens when you go to https://webby.evergreencatalog.com:7682/ ?  You
should (quickly) get a "Not Found" page.  If the browser hangs, the
WebSockets port may be blocked by your firewall.

-b

On Fri, Mar 24, 2017 at 2:11 PM, Forrest, Stuart  wrote:

> Nope, nothing not a jot. Done cache clearing and in fact this is a freshly
> installed PC. Think about it I’ve only managed to connect once before a
> long time ago.
>
>
>
> Stuart
>
>
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Rogan Hamby
> *Sent:* Friday, March 24, 2017 2:08 PM
>
> *To:* Evergreen Discussion Group
> *Subject:* Re: [OPEN-ILS-GENERAL] WEbby Staff Client
>
>
>
> You don't get a 'please register a workstation' screen either?
>
>
>
>
> Rogan Hamby
>
> Data and Project Analyst
>
> Equinox Open Library Initiative
>
> phone:  1-877-OPEN-ILS (673-6457)
>
> email:  ro...@equinoxinitiative.org
>
> web:  http://EquinoxInitiative.org
>
>
>
> On Fri, Mar 24, 2017 at 8:32 AM, Forrest, Stuart 
> wrote:
>
> Hi Mike
>
> Sorry still no luck. I enter the Username admin and password demo123 then
> when I click the Sign In button nothing happens at all, not even a page
> refresh it just sits there.
>
> Stuart
>
> 
> 
> Stuart Forrest PhD
> Library Systems Specialist
> Beaufort County Library System
> 843 255 6450
> sforr...@bcgov.net
>
> http://www.beaufortcountylibrary.org
>
> For Leisure, For Learning, For Life
>
>
>
> -Original Message-
> From: Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] On Behalf Of Mike Rylander
> Sent: Friday, March 24, 2017 8:15 AM
> To: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] WEbby Staff Client
>
> Stuart,
>
> From time to time we deploy new code on webby as we fix bugs and add
> features.  I think you just caught it during a refresh, as it seems to be
> working fine now, but let us know if you continue to have issues.
>
> Thanks,
>
> --
> Mike Rylander
>  | President
>  | Equinox Open Library Initiative
>  | phone:  1-877-OPEN-ILS (673-6457)
>  | email:  mi...@equinoxinitiative.org
>  | web:  http://equinoxinitiative.org
>
>
> On Thu, Mar 23, 2017 at 1:13 PM, Forrest, Stuart 
> wrote:
> > Hi
> >
> >
> >
> > I am having trouble logging into the demo web staff client at
> > https://webby.evergreencatalog.com/eg/staff/login?route_to=%2Feg%2Fsta
> > ff%2F with the username admin and password demo123. Tried this in
>
> > Chrome and Firefox.
> >
> >
> >
> > When I click the Sign In button nothing happens, not even an error
> message.
> > I have tried clearing my cache to no avail.
> >
> >
> >
> > Any advice would be appreciated.
> >
> >
> >
> > Stuart
> >
> >
> >
> > ==
> > ==
> >
> > Stuart Forrest PhD
> >
> > Library Systems Specialist
> >
> > Beaufort County Library System
> >
> > 843 255 6450
> >
> > sforr...@bcgov.net
> >
> >
> >
> > http://www.beaufortcountylibrary.org
> >
> >
> >
> > For Leisure, For Learning, For Life
> >
> >
> >
> >
>
>
>

Re: [OPEN-ILS-GENERAL] Web-Client

[Bill Erickson]

Also beware the web browser needs to access the server on (nonstandard)
port 7682.  If you are behind a firewall, it may be blocking the port.

FYI work is under way to avoid the requirement for using a nonstandard
port:  https://bugs.launchpad.net/opensrf/+bug/1638651

-b


On Wed, Nov 16, 2016 at 1:51 PM, Rogan Hamby  wrote:

> I just tried on Chrome with no issues.  What browser are you using?
>
> On Wed, Nov 16, 2016 at 12:12 PM, Forrest, Stuart 
> wrote:
>
>> HI
>>
>>
>>
>>
>>
>> I am trying to access the web client to see how it is looking. The
>> address I am using is https://webby.evergreencatalog
>> .com/eg/staff/login?route_to=%2Feg%2Fstaff%2F with admin and demo123 as
>> UN and PW.
>>
>>
>>
>> When I click login nothing happens, any ideas?
>>
>>
>>
>> Thanks
>>
>> Stuart
>>
>>
>>
>>
>>
>> 
>> 
>>
>> Stuart Forrest PhD
>>
>> Library Systems Specialist
>>
>> Beaufort County Library
>>
>> 843 255 6450
>>
>> sforr...@bcgov.net
>>
>>
>>
>> http://www.beaufortcountylibrary.org
>>
>>
>>
>> For Leisure, For Learning, For Life
>>
>>
>>
>>
>>
>
>
>
> --
> --
> Rogan R. Hamby, Data and Project Analyst
> Equinox - Open Your Library
> ro...@esilibrary.com
> 1-877-OPEN-ILS | www.esilibrary.com
>
>

Re: [OPEN-ILS-GENERAL] Staff Client - TypeError: document.getElementById("commonStrings") is null

[Bill Erickson]

Hi Dan,

In my experience, this error can occur for all manner of reasons, which
generally have nothing to do with the specific code mentioned in the
error.  I think this code just happens to be among the first to fail when
the staff client is unable to load.  (It may as well say "Uh oh, something
went wrong").  My first step when this happens is to make sure all of the
XUL client files are in the right place on the server (e.g. check Apache
access logs) and make sure API calls are succeeding (Evergreen activity/ACT
logs).

Hope this helps,

-b



On Fri, Sep 23, 2016 at 4:13 PM, Dan Strauss  wrote:

> Hey all,
>
> I’ve spent the last couple days installing the Evergreen server software
> and its required components and made it to the end of the instructions
> where I logged in via srfsh and got a success response back.
>
> Now, I’m trying to connect to the server using the Staff Client on
> Windows. The server status check passes, but when I try to login I get a
> dialog box with the message in the subject line - TypeError:
> document.getElementById("commonStrings") is null.
>
> I know it’s not much to go off of, but could anyone tell me where I could
> start to figure out what the issue could be? The logs aren’t too helpful as
> far as I can tell, and “document.getElementById("commonStrings”)” is
> referenced in a few dozen places in the code, so I can’t be sure where it’s
> originating at the moment.
>
> Thanks in advance!
>
> Dan Strauss
> Development Engineer
> Datalogics, Inc.
>
>

Re: [OPEN-ILS-GENERAL] Error when upgrading from 2.9.3 to 2.10.0

[Bill Erickson]

Hi Linda,

On Sat, Apr 30, 2016 at 2:41 PM, Linda Jansova  wrote:


> This time we experienced the same error (but involving a different copy of
> the same serial):
>
> psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or
> update on table "usr_circ_history" violates foreign key constraint
> "usr_circ_history_target_copy_fkey"
> DETAIL:  Key (target_copy)=(57113) is not present in table "copy".
>
> Could it be related to the bug fixed in 2.10.2 as described at
> https://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_10.html#_evergreen_2_10_2
> (Fixes a bug where serials checkouts failed for users that track
> circulation history.)?
>

That's the one.  See more here:
https://bugs.launchpad.net/evergreen/+bug/1564079


> If so, what should we do to get rid of the error in our case when 2.10.2
> has not been reached yet (in the upgrade process)?
>

The 2.10.2 fix includes a patch to the 2.9.3-2.10.0 upgrade script.  You'll
want to get the 2.10.2 code and use it to perform your 2.10.0 upgrade (and
ideally continue on to 2.10.2 to pick up more bug fixes).

Hope this helps,

--bill

[OPEN-ILS-GENERAL] opensrf.xml changes required for master and (pending) 2.10

[Bill Erickson]

Hi All,

Just a heads up that next time you update your code to master, you'll need
to add a new "open-ils.auth_internal" service to your opensrf.xml file.
Without this, no one will be able to log in.

This is related to https://bugs.launchpad.net/evergreen/+bug/1468422

This service adopts some of the configs from open-ils.auth.  Here's the
diff from the sample file:

http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=722338616034d1be24603ef193cc775fbbe08307#patch1

See the full versions of the modified open-ils.auth and
open-ils.auth_internal stanzas here:

http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/examples/opensrf.xml.example;h=59f737a921cc77a2ab39bf82e9f03283c483a007;hb=722338616034d1be24603ef193cc775fbbe08307#l412

-b

Bill Erickson

Re: [OPEN-ILS-GENERAL] Self-Registration and Immediate Access to Services

[Bill Erickson]

KCLS is interested in this as well.  I haven't given it much thought yet
beyond, "wouldn't it be nice if...".

-b

On Thu, Jan 28, 2016 at 12:25 PM, McCanna, Terran <
tmcca...@georgialibraries.org> wrote:

> I would also be interested in hearing if anyone else has done something
> like this. We have our self-registration set to remove a pending
> registration after two weeks if the patron has not come into the library to
> complete the process, so that could potentially add another layer of
> complexity even if a temporary barcode number and password were assigned,
> and even if SIP2 could authenticate it.
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138
> tmcca...@georgialibraries.org
> - Original Message -
> From: "Dawn Dale" 
> To: "Evergreen Discussion Group" <
> open-ils-general@list.georgialibraries.org>
> Sent: Thursday, January 28, 2016 12:16:20 PM
> Subject: Re: [OPEN-ILS-GENERAL] Self-Registration and Immediate Access
> to  Services
>
> I would be interested in knowing how others are handling these issues as
> well.
>
> Dawn Dale
> GPLS Helpdesk Manager
> Georgia Public Library Service
> 1800 Century Place
> Suite 150
> Atlanta, GA 30345
> 404-235-7136
> dd...@georgialibraries.org
>
> - Original Message -
> From: "scott thomas" 
> To: open-ils-general@list.georgialibraries.org
> Sent: Thursday, January 28, 2016 9:21:51 AM
> Subject: [OPEN-ILS-GENERAL] Self-Registration and Immediate Access to
>  Services
>
> Hi,
>   Have any libraries done any work on allowing patrons who have
> self-registered to get immediate access to digital services? The problem
> appears to be twofold:
>
> 1. Many databases authenticate using the prefix of the patron barcode,
> and, at least in our system, patrons are not assigned a library card number
> during the self-registration process.
>
> 2. For services like Overdrive that use SIP2, pending patrons are not
> truly registered and are therefore not visible via SIP2.
>
> Has anyone found a way around these problems?
>
> While many of our libraries are quick when it comes to processing pending
> patrons, immediate access to digital services is great customer service.
>
> Thank you,
> Scott
>
> Scott Thomas
> Executive Director
> Pennsylvania Integrated Library System
> 717-873-9461
> scott.tho...@sparkpa.org
>

Re: [OPEN-ILS-GENERAL] Self-Registration and Immediate Access to Services

[Bill Erickson]

On Fri, Jan 29, 2016 at 2:51 PM, Justin Hopkins  <
jus...@mobiusconsortium.org> wrote:

> To go off on a bit of a tangent (it's related, I promise) there is also
> the issue of Evergreen offering a way to validate users without them being
> physically present at the library.
>
> As more and more of our resources are electronic, it makes sense to have a
> form of electronic patron validation as well. It may be a good solution to
> both of these issues if our self-registration form had the ability to use a
> webcam to take a picture of a person and their ID with valid address.
>

+1 to this.  And if I can convince Amazon to sell me wine, surely there's a
way to validate patrons without requiring them to come to the library.

-b

Re: [OPEN-ILS-GENERAL] Acquisitions Funds question

[Bill Erickson]

Hi Janet,

When a fund's "active" field is set to false, the fund will no longer
appear in these lists.  This is typically done in batch via the fiscal /
year-end rollover process (in the funds admin interface), but you can also
mark individual funds as inactive by editing each fund directly (also in
the funds admin interface).

Hope this helps,

-b



On Mon, Jan 4, 2016 at 1:30 PM, Janet Brown  wrote:

> We are beginning our third year using the Acquisitions module of Evergreen
> and are learning more about it each year.
>
>
>
> That being said, we do have a question regarding the Funds list.  Wherever
> there is the option to look at the list of funds (like in a purchase
> order), all of the 2014 funds and all of the 2015 funds show up – not
> necessarily in any discernable order. Since we can’t roll over any of the
> monies to the new year we have been creating new funding sources, but the
> list is getting to be too long.  Does anyone know how to filter or hide the
> old funds so they don’t show up as options anymore?  If need be, we could
> even delete the 2014 funds and just keep the 2015 funds as needed.  As time
> goes by, I see a huge, unmanageable list if we aren’t able to fix this soon.
>
>
>
> Maybe others deal with the funds in a different way. We would be happy to
> hear about how that works too.
>
>
>
> Thank you for any help!
>
>
>
>
>
> Janet Brown
>
> SysAdmin/Circ Supervisor
>
>
>
> Burlington Public Library
>
> 820 E Washington Ave
>
> Burlington WA  98233
>
> 360-755-0760
>
> jan...@burlingtonwa.gov
>
>
>

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Hack-A-Way 2016 Selection

[Bill Erickson]

Ditto Ben's comments.  I see no reason they (or anyone) can't bid every
year, assuming we go through the usual selection process to choose the best
site.  If we agree (and I think we do) that moving the site each year is a
good thing, we could stipulate up front that a site gets bonus points for
being different than the previous year's site and make that part of the
selection process.

-b


On Mon, Oct 12, 2015 at 12:40 PM, Ben Shum  wrote:

> Hi Rogan,
>
> First, yay Evergreen Indiana, thanks for hosting a Hack-A-Way!
>
> Next, I do not have any strong opinion on the proposal.  For myself, I
> do not mind if we want to consider Indiana for two years in a row as
> hosting site.  While it's nice to have it move around and see
> different places, I think it is also equally nice to know that we will
> definitely have a place to meet up and hack on Evergreen.
>
> So, for my two cents, I say please proceed and with thanks to all
> those involved.
>
> -- Ben
>
> On Wed, Oct 7, 2015 at 3:49 PM, Rogan Hamby 
> wrote:
> > I have two sections to this email - first to announce the selected site
> for
> > the Hack-A-Way in 2016 and secondly to bring up a question to the
> community
> > about the 2017 selection process.
> >
> >
> > First, the good news!  Evergreen Indiana will be hosting the Hack-A-Way
> in
> > 2016!  As everyone knows, Indiana is home to some wonderful community
> > members and they are excited to be hosts.  They did a wonderful job with
> the
> > conference a few years ago so I know we will be in excellent hands.
> >
> >
> > The host location is Indianapolis, which is central to the US (and fairly
> > north for our Canadian brethren).  They have three international airports
> > within a few hours drive and is a popular conference city with budget
> > friendly options for our participants (an ongoing goal is to keep the
> event
> > relatively cheap).
> >
> >
> > Evergreen Indiana will fully sponsor the site and two meals plus snack
> each
> > day of the event for all participants and work with negotiating hotel
> > discounts.  They will also arrange for shuttles to and from travel hubs
> and
> > help coordinate some evening events.
> >
> >
> > Yay!  So, what comes next?  As usual we  need to arrange dates, hotel
> plans,
> > etc... but the extended time line allows for a more deliberat pace.
> >
> >
> > And that leads us into talking a bit about the 2017 process.  We changed
> the
> > process this year for selection to provide for a longer time line.  The
> > feedback I'd had from potential hosts and participants who reached out
> to me
> > was that they wanted more time for making decisions than the old
> (admittedly
> > very low key) process allowed.  This is something that we will continue
> to
> > follow in the years that follow, 2017 and beyond.
> >
> >
> > Specfically in regard to 2017, however, Indiana would like to have thier
> bid
> > considered for 2017 as well as 2016 and host it for two years.  I want to
> > continue moving the Hack-A-Way around for the same purposes that we move
> the
> > conference but I also appreciate all the effort they have put into their
> > proposal and there would be some definite virtue to this.  I don't mind
> the
> > idea of doing the Hack-A-Way in Indiana for two years but a) don't want
> it
> > considred a precendent that it will always be in the same places for two
> > years at a time and b) want to put it up to the developers for feedback
> as
> > this event is to facilitate thier activity.
> >
> >
> > Thoughts?
> >
> >
> >
> > --
> >
> > Rogan Hamby, MLS, CCNP, MIA
> > Managers Headquarters Library and Reference Services,
> > York County Library System
> >
> > “You can never get a cup of tea large enough or a book long enough to
> suit
> > me.”
> > ― C.S. Lewis
>
>
>
> --
> Benjamin Shum
> Evergreen Systems Manager
> Bibliomation, Inc.
> 24 Wooster Ave.
> Waterbury, CT 06708
> 203-577-4070, ext. 113
>

Re: [OPEN-ILS-GENERAL] Upgraded to 2.8.3 - Book covers no longer loading

[Bill Erickson]

Jesse,

Beware there is no added content module for Novelist, at least not in the
same sense as the OpenLibrary, ContentCafe, and Syndetic modules.  Novelist
is only used within the templates and in the Apache configuration.

If you have Novelist set as your added content provider in opensrf.xml it
could produce the kind of error you are seeing.

Hope this helps,

-b


On Tue, Aug 25, 2015 at 11:13 AM, Michael Peters mpet...@emeralddata.net
wrote:

 Jesse,



 Would you be able to post a copy of your opensrf and opensrf_core XML
 files (please remove any sensitive information) so we can check for syntax
 errors?  No changes to the AddedContent.pm were made in 2.8.3, and there
 haven’t been any since 2014.



 Michael Peters
 Senior Systems Analyst
 Emerald Data Networks, Inc.
 Phone: 678.302.3000 x1013
 Help Desk: 678.302.3000 x1500
 www.emeralddata.net

 *From:* Open-ils-general [mailto:
 open-ils-general-boun...@list.georgialibraries.org] *On Behalf Of *Michael
 Peters
 *Sent:* Tuesday, August 25, 2015 11:04 AM
 *To:* Evergreen Discussion Group 
 open-ils-general@list.georgialibraries.org
 *Subject:* Re: [OPEN-ILS-GENERAL] Upgraded to 2.8.3 - Book covers no
 longer loading



 Jesse,



 You might be able to take a 2.8.2 version of AddedContent.pm and put it in
 place of this one.  Have you filed a bug on
 https://bugs.launchpad.net/evergreen/+filebug – this is very important to
 get fixed.



 Michael Peters
 Senior Systems Analyst
 Emerald Data Networks, Inc.
 Phone: 678.302.3000 x1013
 Help Desk: 678.302.3000 x1500
 www.emeralddata.net

 *From:* Open-ils-general [
 mailto:open-ils-general-boun...@list.georgialibraries.org
 open-ils-general-boun...@list.georgialibraries.org] *On Behalf Of *Jesse
 McCarty
 *Sent:* Monday, August 24, 2015 7:14 PM
 *To:* open-ils-general@list.georgialibraries.org
 *Subject:* [OPEN-ILS-GENERAL] Upgraded to 2.8.3 - Book covers no longer
 loading



 Hello Everyone,



 I just recently upgraded our test server (slated for promotion to
 Production once the kinks are worked out) from 2.8.1 to 2.8.3 and now none
 of the book cover images are loading. Has anyone run into this or know what
 I need to change to get them back? I copied over our Novelist SetEnv
 information from the old configuration file and this appears to be the only
 thing that broke with the 2.8.3 upgrade.



 Only clue I can see so far in the logs is the following line:



 Evergreen gateway: [perl:error] [pid 30041] [172.xx.xx.xxx:54675] Can't
 call method use on unblessed reference at
 /usr/local/share/perl/5.18.2/OpenILS/WWW/AddedContent.pm line 67



 Thanks in advance.



 Jesse McCarty

 City of Burlington

 IT Technical Assistant

[OPEN-ILS-GENERAL] Deleting (partial) credit card data

[Bill Erickson]

Hi All,

I've opened Launchpad bug for preventing Evergreen from storing credit card
data when credit card payments are made via the TPAC.  Similarly, I'm
proposing that all existing credit card information be deleted as well.
Storing this data is a bad idea for various reasons.  However, since we're
talking about deleting data from the database, I wanted to bring this to
everyone's attention.

The data we want to delete is the partial credit card number, expire date,
credit card type, and first/last name on the card.  Evergreen does not
directly use this data in any way.  The concern is only that existing
reports using this data will no longer function.  Our hope is that no one
is reporting on this data, since it is sensitive, and since you can
generally get the same (or better) data directly from the CC provider, but
we wanted to give everyone a chance to comment.

Here's the bug: https://bugs.launchpad.net/evergreen/+bug/1474051

Does anyone out there in EG land need this data to stay in Evergreen?

-b

Re: [OPEN-ILS-GENERAL] presentations

[Bill Erickson]

Oh CRUD, My API Has a Flesh Wound:

HTML Page: http://goo.gl/NmKlWv

Asciidoc: http://goo.gl/B1pPb7

-b

On Sat, May 16, 2015 at 12:28 PM, Grace Dunbar gdun...@esilibrary.com
wrote:

 Slides from my talk Badges? We don't need no stinking badges!  or
 Encouraging participation in Evergreen.

 http://slides.com/graced/deck

 Grace

 On Sat, May 16, 2015 at 8:34 AM, Chris Sharp csh...@georgialibraries.org
 wrote:

 My presentations:

 Making the Most of Evergreen Reports

 Slides:
 https://docs.google.com/presentation/d/1D_viNoFH86yIjbR7s6mjPD3OQPc4WUKGJxn4gJe_v78/edit?usp=sharing
 Handout:
 https://docs.google.com/document/d/1tcyf50CLpUr5VzKf7UkRGcBxqwzadAse8R8vpBZd48E/edit?usp=sharing

 Troubleshooting With Evergreen Logs

 Handout:
 https://docs.google.com/document/d/1BJ7kSr5LfPkxXRhcrYjNyPlbT9PlNFHg6zL-tyetnKA/edit?usp=sharing


 - Original Message -
  From: Geoff Sams gs...@roanoketexas.com
  To: Evergreen Discussion Group 
 open-ils-general@list.georgialibraries.org
  Sent: Saturday, May 16, 2015 8:17:08 AM
  Subject: Re: [OPEN-ILS-GENERAL] presentations
 
  Thanks for working to make these resources available to the community
  everyone.  I know I greatly appreciate it, and those of my consortium
 that
  couldn't attend will appreciate it just as much!
 
  Thanks,
  Geoff Sams
  North Texas Library Consortium
 
  -Original Message-
  From: Open-ils-general
  [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf
 Of
  Galen Charlton
  Sent: Friday, May 15, 2015 9:01 PM
  To: Evergreen Discussion Group
  Subject: Re: [OPEN-ILS-GENERAL] presentations
 
  Hi,
 
  Thanks, Rogan, for starting this thread; I'll update the program
 schedule
  page with links to the slides that the presenters choose to share.
 Also, if
  your presentation is in the form of a PDF file or some other
 presentation
  file and you wish to share it, please send it to me and I'll can put it
 up
  on the Evergreen website.
 
  Regards,
 
  Galen
 
  On Fri, May 15, 2015 at 5:07 PM, Kathy Lussier kluss...@masslnc.org
 wrote:
   Thanks Rogan! Here are my slides:
  
   State of Evergreen Initiatives and Outreach -
   http://slides.com/kathylussier/state-eg
  
   Getting What You Want in Your Next Development Project -
   http://slides.com/kathylussier/development-projects
  
   Evergreen Search Tune-Up -
   http://slides.com/kathylussier/evergreen-search
  
   Kathy
  
  
   On 05/15/2015 04:23 PM, Rogan Hamby wrote:
  
   In the interest of sharing presentations (that weren't done before the
   conference):
  
   http://www.slideshare.net/roganhamby/welcome-to-the-community
  
   and
  
  
 http://www.slideshare.net/roganhamby/adding-data-sources-to-the-report
   er
  
   There were quite a few from other folks that I wasn't able to attend
   so I hope everyone sends out their presentations!
  
   --
  
   Rogan Hamby, MLS, CCNP, MIA
   Managers Headquarters Library and Reference Services, York County
   Library System
  
   “You can never get a cup of tea large enough or a book long enough to
   suit me.”
   ― C.S. Lewis
  
  
   --
   Kathy Lussier
   Project Coordinator
   Massachusetts Library Network Cooperative
   (508) 343-0128
   kluss...@masslnc.org
   Twitter: http://www.twitter.com/kmlussier
 
 
 
  --
  Galen Charlton
  Infrastructure and Added Services Manager Equinox Software, Inc. / The
 Open
  Source Experts
  email:  g...@esilibrary.com
  direct: +1 770-709-5581
  cell:   +1 404-984-4366
  skype:  gmcharlt
  web:http://www.esilibrary.com/
  Supporting Koha and Evergreen: http://koha-community.org 
  http://evergreen-ils.org
 

 --
 Chris Sharp
 PINES System Administrator
 Georgia Public Library Service
 1800 Century Place, Suite 150
 Atlanta, Georgia 30345
 (404) 235-7147
 csh...@georgialibraries.org
 http://pines.georgialibraries.org/




 --
 Grace Dunbar, Vice President
 Equinox Software, Inc.  -  The Open Source Experts
 gdun...@esilibrary.com
 1-877-OPEN-ILSwww.esilibrary.com

Re: [OPEN-ILS-GENERAL] Resetting karma in IRC

[Bill Erickson]

+1

On Sat, May 16, 2015 at 1:18 PM, Galen Charlton g...@esilibrary.com wrote:

 Hi,

 On Sat, May 16, 2015 at 8:45 AM, Kathy Lussier kluss...@masslnc.org
 wrote:
  I would like to suggest that we reset the karma points in the #evergreen
  channel by the end of next week (to give adequate time for any
 dissension).
  For future conferences, I would like to suggest that the karma points are
  reset on the Monday after the conference ends.

 +1. It's a good practice for #code4lib, and I think it's a good idea
 for #evergreen.

 Regards,

 Galen
 --
 Galen Charlton
 Infrastructure and Added Services Manager
 Equinox Software, Inc. / The Open Source Experts
 email:  g...@esilibrary.com
 direct: +1 770-709-5581
 cell:   +1 404-984-4366
 skype:  gmcharlt
 web:http://www.esilibrary.com/
 Supporting Koha and Evergreen: http://koha-community.org 
 http://evergreen-ils.org

[OPEN-ILS-GENERAL] Evergreen 2.8.1, 2.7.5, and 2.6.8 Released

[Bill Erickson]

Hi All,

On behalf of the Evergreen contributors, the 2.8 release manager (Bill
Erickson),
the 2.7 release maintainer (Ben Shum) and the 2.6 release maintainer
(Dan Wells), we are pleased to announce the release of Evergreen
2.8.1, 2.7.5, and 2.6.8.

The new releases can be downloaded from:

http://evergreen-ils.org/egdownloads/

Special note: For early adopters of Apache version 2.4, this release
contains
security updates.  At this time, no known sites are affected by this issue,
but any sites running Apache 2.4 are encouraged to upgrade as soon as
possible.

More information can be found here:
http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_8.html#_important_security_information

Thanks to all who contributed!

-b

Re: [OPEN-ILS-GENERAL] Action Trigger Opt-In Settings

[Bill Erickson]

On Mon, Apr 27, 2015 at 3:13 PM, Josh Stompro stomp...@exchange.larl.org
wrote:

  Hello, I’m working on updating the action trigger documentation to make
 sure it covers everything, and I want to make sure I understand the Opt-In
 settings.



 Please tell me if I have this correct or not.



 If I wanted to modify the Courtesy Notices (pre overdue) so that they were
 Opt-out.  Something that has been requested by our customers in the past
 since some people get such a high volume of Courtesy Notices so they get to
 be meaningless to those customers.



 I would create a User Setting Type to hold the opt-in/out choice. I just
 used sms settings group since I’m not sure how to define a new one of those
 yet or what the group setting does.



The group is there for sorting and organizing, so feel free to use whatever
group makes sense to you.





 Then the new user settings somehow magically becomes active in the staff
 client new user registration and catalog notification settings (Still
 trying to figure out how this happens.)


The happens because of the next step.

Note that setting the OPAC/Patron Visible field to True means the
setting will also appear in the OPAC.




 Next I modify the Trigger Event Definitions for the “3 Day Courtesy
 Notice” and set the Opt-In Setting Type to the name I specified above and
 the Opt-In User Field to “True”, to match what it should be to be enabled?


Yes and No.  You will set the opt-in-setting type to the setting you
created from the setting name selector.  The Opt-In User Field specifies
the field on the core object which refers to the user object.  (This is how
the system knows how to find the user related to each notice, then look up
that users's settings).  In the case of courtesy notices, the core object
is the circulation (based on the event def hook).  The
action.circulation.usr field refers to the user.  So, the Opt-In User Field
will be usr (no quotes).





 I’m guessing I should also go through and set the value to True for all
 existing users also?


Yes, to opt in all users, you will have to set the value for setting
'opac.default_courtesy_enabled' to true for all patrons.

Hope this helps,

-b

[OPEN-ILS-GENERAL] Evergreen 2.8.RC1 posted

[Bill Erickson]

Hi,

2.8.RC1 files have been pushed to evergreen-ils.org:

http://evergreen-ils.org/downloads/previews/ChangeLog-2.7.4-2.8.0

http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_8.html

http://evergreen-ils.org/documentation/install/README_2_8.html

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.8.rc1.tar.gz

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.8.rc1.tar.gz.md5

http://evergreen-ils.org/downloads/previews/evergreen-setup-2.8.rc1.exe

http://evergreen-ils.org/downloads/previews/evergreen-setup-2.8.rc1.exe.md5

http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.rc1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.rc1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.rc1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.rc1_x86_64.tar.bz2.md5

Note that RC1 uses 2.7.4 as the previous release point for building the
database upgrade, unlike beta, which used 2.7.3.  This means the DB upgrade
is different and requires an upgrade to 2.7.4 before it can be applied.

The only other changes to this release vs. the beta are a number
documentation commits.  If there are no issues, I'd like to consider
releasing 2.8.0 next week.

Thanks, everyone.

-b

[OPEN-ILS-GENERAL] 2.8.beta Released

[Bill Erickson]

Hi Everyone,

I've uploaded the 2.8.beta release files to evergreen-ils.org:

http://evergreen-ils.org/downloads/previews/ChangeLog-2.7.3-2.8.beta
http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_8.html
http://evergreen-ils.org/documentation/install/README_2_8.html
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.8.beta.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.8.beta.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.8.beta.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.8.beta.exe.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.beta_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.beta_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.beta_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.8.beta_x86_64.tar.bz2.md5

Note that the release was built yesterday before 2.7.4 existed, so the DB
upgrade script applies to a 2.7.3 database.  To apply to a 2.7.4 database,
remove updates 0908, 0913, and 0914 from the upgrade file, retaining the
final commit.  The final 2.8.0 DB upgrade script will be built from 2.7.4
instead.

Thanks to all who contributed, thanks to those who test, and special thanks
to the security team for storming the beaches yesterday.

-b

[OPEN-ILS-GENERAL] 2.8 beta pending security releases

[Bill Erickson]

Hi All,

I wanted to give everyone a heads up that the 2.8 beta release will be cut
after a batch of security releases are cut.  2.8 will contain the fixes, so
I'd like to wait until the usual security announcements are wrapped up
before publishing the code.

We hope to have the new versions cut shortly.  We'll keep you posted.

Thanks,

-b

Re: [OPEN-ILS-GENERAL] Holding Subfields

[Bill Erickson]

Hi Leslie,

Purchase order IDs and lineitem IDs are included in EDI messages by
default.  That's the primary mechanism for synchronizing data between
Evergreen and the vendor.  Item (copy) IDs are not included by default, but
can be with a change to the EDI template.

What problem are you trying to solve, exactly?

-b



On Tue, Jan 27, 2015 at 12:30 PM, St. John, Leslie 
lstj...@georgialibraries.org wrote:

 Although Acquisitions related questions tend to not get answered, I'm
 putting this out here anyway in hope of hooking someone.

 On the advice of several Acquisitions users to include line item id's
 and/or purchase order id's in EDI communications with vendors we created a
 consortial standard for our Holdings Subfields and now need to add a couple
 more fields to the holdings subfields list of name values that is used to
 set up this information in the Provider record.  It seems as if this is
 turning into an project that shouldn't be so complicated. If you are using
 Acquisitions, how are you transmitting the line item id or PO id back and
 forth between the library and vendor?  and if you had to add this to the
 holdings subfields mapping how did you do it?  Please and thanks to anyone
 willing to take the time to answer.

 Leslie

 --
 Leslie St. John
 PINES http://gapines.org Consultant
 http://www.georgialibraries.org/public/pines.php
 Georgia Public Library Service http://www.georgialibraries.org/
 A Unit of the University System of Georgia
 1800 Century Place, Suite 150
 Atlanta, GA 30345-4304
 lstj...@georgialibraries.org

Re: [OPEN-ILS-GENERAL] 2.8 release scheduling

[Bill Erickson]

On Thu, Dec 18, 2014 at 2:20 PM, Mike Rylander mrylan...@gmail.com wrote:

 On Thu, Dec 18, 2014 at 12:11 PM, Bill Erickson beric...@gmail.com
 wrote:


 On Thu, Dec 18, 2014 at 8:29 AM, Mike Rylander mrylan...@gmail.com
 wrote:

 Bill,

 First, thanks for putting out a timeline.

 I am a little concerned about the pre-beta feature freeze.  In the past,
 the merge deadline for features has always been whatever makes it into the
 beta release, and I don't see cutting that back by a week helping things
 to get done faster -- we just end up with a week less features in 2.8, and
 that last week is often (us being humans, and whatnot) the critical push
 time for things that are almost there.  Do you have something in mind that
 I'm not seeing for the change there?


 The feature freeze basically is the beta.  (I recall now this was called
 the beta cut-off during the 2.6 cycle.  I'll use this terminology going
 forward).  The interval between the cut-off and beta release cutting is our
 chance to let the dust settle after the merge rush so we're not cutting a
 buggy beta.  If Feb 18th is too soon, we can certainly push the beta back.


 I won't fight you hard on the week between cut-off and beta wrapping, but
 IMO it doesn't serve much purpose. Believe me, I know better than most that
 betas often don't get the attention they deserve, and because of that it
 feels (again, to me and maybe not to anyone else) like a week of doldrums.
 But if you feel that week will help you shake things out as RM, I'll
 mentally s/25/18/ the beta date


I didn't really explain my expectations of the cut-off interval very well.
It's definitely helpful for the RM (finalizing the DB upgrade, compiling
release notes, misc. cleanup, etc.), but to me it's more about developers
testing this shiny new thing that we're about to call the Beta,
particularly since it's the first time some of the features will be living
together.  A group sniff test, if you will.  (e).

I see your point about the doldrums, though.  A week is probably too long.
Let's push the beta cut-off up to the 20th?

-b

[OPEN-ILS-GENERAL] 2.8 release scheduling

[Bill Erickson]

Hi All,

I'm attempting to sketch out the release schedule for Evergreen 2.8, so I'd
like to run some dates/thoughts by everyone.

For starters, unless someone requests it, I'm not planning to cut an Alpha
release.  I've never seen anyone install one :).  I'm happy to cut one if
desired, though.

Proposed schedule:

* Jan 14 2015: Feature Target Deadline

This is the date where all features we expect to get into 2.8 are
documented in LP and targeted to 2.8.  They do not have to be coded or
tagged as pull requests by this date.  They just need to be documented.  As
before, this is a strong recommendation, but not a hard deadline.

Feb 18 2015: Feature Freeze

From this date forward, only bug fixes may be committed to master.  Any
un-merged features will be booted to 2.9.

Feb 25 2015: 2.8.beta1 Release

March 9 2015: 2.8.rc1 Release

March 18 2015: 2.8.0 Release

Comments/suggestions welcome.

Note that in the future I'll avoid cross-posting to both -general and -dev
lists and just send 2.8 updates to -general to cut down on noise.

Thanks, everyone.

-b

Re: [OPEN-ILS-GENERAL] Acq - Copy location UI scoped to registered workstation

[Bill Erickson]

This is probably a limitation within AutoFieldWidget.  It has a special
handler for copy locations to avoid loading all perm-visible locations,
which can be many thousands in some consortia.  This seems like a good
candidate for a typeahead box -- openils.widget.PCrudAutocompleteBox in
this context.

-b


On Fri, Dec 12, 2014 at 10:38 AM, Blake Henderson 
bl...@mobiusconsortium.org wrote:

  Mike,

 We do have the working locations setup (checked) on each of the branches
 in the system for the user in question. We only see the copy locations
 populated for the branch that the workstation is registered.

 -Blake-
 Conducting Magic
 MOBIUS573-234-4513877-312-3517

 On 12/12/2014 9:23 AM, Mike Rylander wrote:

 Blake,

  I didn't see if this was already asked and answered elsewhere and I
 don't know if it will help in the ACQ interfaces, but, did you give the
 user in question multiple working locations via the user permission editor?

  HTH,


   --
 Mike Rylander
  | President
  | Equinox Software, Inc. / The Open Source Experts
  | phone:  1-877-OPEN-ILS (673-6457)
  | email:  mi...@esilibrary.com
  | web:  http://www.esilibrary.com


 On Thu, Dec 11, 2014 at 11:19 AM, Blake Henderson 
 bl...@mobiusconsortium.org wrote:

 Hello all,

 I apologize for the duplicate email, I sent this to the dev list and it
 was suggested that I send it to the general list:

  I couldn't find a bug on this. We are using acq for the first time and I
 don't want to jump to any conclusions. When creating a PO and assigning
 the copies to their branches and copy locations, we noticed that the UI
 only shows the copy locations for the branch that you happen to be
 registered to. We have a scenario where a single branch is doing all of
 the PO's for all of the sibling branches. Are we doing something wrong?
 During some experimenting, I found that if you register the user to the
 system level instead of the branch level, it will show all of the copy
 locations for each branch. That, of course, is not a good idea for other
 reasons. We ruled permissions out by assigning the EVERYTHING^consortium
 to the user.

 It seems like if the software allows the copies to be assigned to
 different branches, it should also allow copies to get assigned to the
 respective shelving location in that branch.

 --
 -Blake-
 Conducting Magic
 MOBIUS

Re: [OPEN-ILS-GENERAL] Acq - Copy location UI scoped to registered workstation

[Bill Erickson]

On Fri, Dec 12, 2014 at 12:00 PM, Blake Henderson 
bl...@mobiusconsortium.org wrote:

  Bill,

 This is the same conclusion that I was coming to. As I was saying before,
 I didn't want to jump to a launchpad bug because it seemed odd that
 something this fundamental wasn't already fleshed out and incorporated.
 Shall I create a bug?


+1

-b

Re: [OPEN-ILS-GENERAL] 2.8 release manager planning

[Bill Erickson]

On Thu, Nov 13, 2014 at 11:12 PM, Jayaraj JR jaya...@iisertvm.ac.in wrote:

 Hello,

 It would be a nice feature if can add the patron image in the coming
 version of Evergreen ILS. This provision may be incorporated while
 registering the patron. When opening the patron account it should be
 visible in both staff client and OPAC.

 It would be very useful as part of many of the library services and
 activities to provide a more friendly and homely interface for the patron.


Hi Jayaraj,

Thanks for the suggestion.  To help ensure feature-specific requests are
not lost, I recommend adding your thoughts to
https://bugs.launchpad.net/evergreen/+bug/1183872 as well.

-b

[OPEN-ILS-GENERAL] 2.8 release manager planning

[Bill Erickson]

Hi All,

At Wednesday's developer meeting I volunteered and was elected the
(provisionally named) Evergreen 2.8 release manager.  I'd like to discuss
my goals for this release and open the floor to others who may wish to
offer suggestions and feedback.

Areas of interest for me personally:

* Solidify support for Debian Jessie and Ubuntu 14.04.
* Continued testing, implementation, and improving the (developer) install
process for the browser staff client
* Continued improvement of the installation process in general, as
discussed in IRC.
* Finalize deprecation of script-based circ (and spidermonkey)
* As always, working through our Launchpad backlog.

Are there any other big picture items we should focus on for this release?

We will, of course, continue the March/Sept. release cycle, so we should
expect a beta release around mid February and a final 2.8.0 release in mid
March.  I'll announce specific dates to the list soon.

Thanks,

-b

Re: [OPEN-ILS-GENERAL] Web Client (Sprint 1) demo server

[Bill Erickson]

On Tue, Sep 16, 2014 at 2:22 AM, Liam Whalen liam.wha...@bc.libraries.coop
wrote:

snip


 I am getting the following error when I try to login via Firefox on the
 Windows VM:

 webby.evergreencatalog.com:7682 uses an invalid security certificate.

 The certificate is not trusted because no issuer chain was provided.

 (Error code: sec_error_unknown_issuer)

 Firefox can't establish a connection to the server at wss://
 webby.evergreencatalog.com:7682/osrf-websocket-translator.
 evergreen-staff-client.0.0.1.min.js:9
 Error: WebSocket Error [object Event] : undefined
 evergreen-staff-client.0.0.1.min.js:9
 closing websocket evergreen-staff-client.0.0.1.min.js:9
 Synchronous XMLHttpRequest on the main thread is deprecated because of its
 detrimental effects to the end user's experience. For more help
 http://xhr.spec.whatwg.org/ exceptionDialog.js:136
 www.evergreencatalog.com:443 uses an invalid security certificate.

 The certificate is only valid for the following names:
   *.esilibrary.com, esilibrary.com


I can confirm this is a problem in Linux / FF 31 as well.  Firefox is
considerably more rigid in its security restrictions than Chrome.  If I
recall correctly, in previous versions of FF, adding an exception for https
would allow websockets connections to succeed as well.  Apparently not
anymore.  We'll need a valid certificate on the server for Firefox to work.


-b

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Web Client (Sprint 1) demo - initial testing results

[Bill Erickson]

Thanks for testing, Terran.  I've added a couple of comments inline...


On Mon, Aug 25, 2014 at 3:32 PM, McCanna, Terran 
tmcca...@georgialibraries.org wrote:

 Hello Grace and all,

 I have begun testing the work on Sprint 1 and here are my notes so far:


 MAIN SCREEN OF INTERFACE:
 - Register Patron(s) link missing
 - Pull List for Hold Requests link missing
 - Catalog Search field missing
 - Advanced Search link missing
 - Item Status link missing
 - Is the large Equinox banner across the bottom of the screen present
 because it's being hosted on an Equinox server, or is this something you
 have added to the default interface? I notice it is not on the original
 test site.


 MENUS:
 - Search Catalog link missing from Search dropdown menu


 PATRON FUNCTIONS:
 - When creating a new message on an account there is an empty dropdown box
 on the right side of the pop-up window - what is that for? I don't seem to
 be able to do anything with it.


This is where you would select local/custom message (penalty) types, but
there probably aren't any setup yet on the new server.


 - the Message pop-up window is missing the field to record staff initials
 that is in the current staff client


 ITEMS OUT SCREEN - COLUMN PICKER:
 - I didn't go through every option, but there were obvious differences
 between the current staff client and the web client and definitely some
 columns missing that are in the current staff client.
 - Show All Columns and Hide All Columns don't appear to do anything


Hmm, this looks like a new bug, probably the result of my final-stretch
grid changes.  I'll take a look at that.


 - Can the column list be alphabetized like it is in the current staff
 client? It's very difficult to find the column you are looking for.
 - There is an optional column for Due Date/Time - what is that for? (It
 does not display the date and time from the normal Due Date column.)
 - Missing 'Checkout Workstation' column option
 - 'Check Out Date/Time' column is empty when turned on
 - 'Check Out Date/Time' should be 'Checkout Date/Time' to be consistent
 with other terminology
 - 'Check In Date/Time' should be 'Checkin Date/Time' to be consistent with
 other terminology
 - There is also a 'Checkin Scan Date/Time' - is that different from
 'Checkin Date/time' ?
 - Circulation Workstation is missing as a column option


 RENEW ITEM WITH SELECTED DUE DATE:
 - date is off (example: select November 5, 2014 as the new date and it
 records it as November 4, 2014)
 - does it matter what format the date is entered in? is there going to be
 a calendar picker next to date fields like this?


There is a calendar selector in Chrome.  Support for the input
type=date HTML element is pending in Firefox, though.  Hopefully it will
be done soon, but if not, we may have to add a calendar widget.




 SCAN ITEM AS MISSING PIECES:
 - it displays a field called Patron Barcode rather than Item Barcode





 Terran McCanna
 PINES Program Manager
 Georgia Public Library Service
 1800 Century Place, Suite 150
 Atlanta, GA 30345
 404-235-7138
 tmcca...@georgialibraries.org

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] browser client dev update July 18 2014

[Bill Erickson]

On Mon, Jul 21, 2014 at 3:41 PM, McCanna, Terran 
tmcca...@georgialibraries.org wrote:



 Back Button - I'm sorry, I'm confused. I tried out both links you provided
 on Chrome and on Firefox and they both seemed to work fine to me. Back
 button (and forward) appeared and functioned as I would expect. What am I
 missing?


Aha!  IFrame navigation works as desired in Chrome on my Mac, but not in
Chrome on Linux.  Are you by any chance using Windows, Terran?

Thanks for testing,

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] browser client update for July 2 2014

[Bill Erickson]

On Mon, Jul 21, 2014 at 4:58 PM, Lazar, Alexey Vladimirovich 
alexey.la...@mnsu.edu wrote:


 On 2014-07-21, at 09:47 , Bill Erickson ber...@esilibrary.com wrote:

 
  On Fri, Jul 18, 2014 at 4:24 PM, Lazar, Alexey Vladimirovich 
 alexey.la...@mnsu.edu wrote:
 
  On 2014-07-11, at 12:37 , Bill Erickson ber...@esilibrary.com wrote:
 
   In the interest of speed, we're only porting interfaces over without
 modifications for now.  I would suggest opening an Launchpad ticket with
 your feature request.
 
  Ok, thank you.
 
  I tacked on a comment to an existing bug dealing with a closely-related
 need: https://bugs.launchpad.net/evergreen/+bug/752894
 
  Thanks, Aleksey.  I think in this case your request would really benefit
 from having its own LP ticket.  LP 752894 is certainly related, but it's
 ultimately a different feature.

 Thank you, Bill. I filed a wishlist bug for the additional required fields
 feature: https://bugs.launchpad.net/evergreen/+bug/1346577.

 After some more looking around,
 https://bugs.launchpad.net/evergreen/+bug/752894 is a duplicate of
 https://bugs.launchpad.net/evergreen/+bug/1060454 (or the other way
 around, but https://bugs.launchpad.net/evergreen/+bug/1060454 is the one
 that is fix-released.) So, I marked it as a duplicate.


Great, thanks Aleksey.

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] browser client update for July 2 2014

[Bill Erickson]

On Fri, Jul 18, 2014 at 4:24 PM, Lazar, Alexey Vladimirovich 
alexey.la...@mnsu.edu wrote:


 On 2014-07-11, at 12:37 , Bill Erickson ber...@esilibrary.com wrote:

  In the interest of speed, we're only porting interfaces over without
 modifications for now.  I would suggest opening an Launchpad ticket with
 your feature request.

 Ok, thank you.

 I tacked on a comment to an existing bug dealing with a closely-related
 need: https://bugs.launchpad.net/evergreen/+bug/752894


Thanks, Aleksey.  I think in this case your request would really benefit
from having its own LP ticket.  LP 752894 is certainly related, but it's
ultimately a different feature.


 Could it be useful to have a tag for bugs especially targeting the browser
 client, as opposed to the existing staff client?


Absolutely.  I've now added a browserclient official bug tag.

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

[OPEN-ILS-GENERAL] browser client dev update July 18 2014

[Bill Erickson]

Hi All,

Today's topic is integrating existing HTML interfaces:

http://evergreen-ils.org/dokuwiki/doku.php?id=dev:browser_staff:dev_notes#section20140718

Cheers,

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] browser client update for July 2 2014

[Bill Erickson]

Hi Aleksey,

In the interest of speed, we're only porting interfaces over without
modifications for now.  I would suggest opening an Launchpad ticket with
your feature request.

-b



On Fri, Jul 11, 2014 at 12:58 PM, Lazar, Alexey Vladimirovich 
alexey.la...@mnsu.edu wrote:


 On 2014-07-08, at 15:01 , Bill Erickson ber...@esilibrary.com wrote:

  That's correct.  The patron edit UI will be practically unchanged.  The
 only changes we're making for this project are to integrate it with the new
 browser interface, which will not have any material affect on its behavior.
  I would really like to see the existing Dojo UIs ported to the new
 structure, but that's a later project.

 Hello, Bill.

 When the patron edit/registration form does get ported to the new
 structure, can you add the ability to optionally define required fields in
 addition to the ones required by default? For example, if a library wants
 to require hold pickup locations preference to always be set explicitly.

 Aleksey Lazar
 IS Developer and Integrator - PALS
 http://www.mnpals.org/




-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

[OPEN-ILS-GENERAL] browser client update for July 2 2014

[Bill Erickson]

Hi All,

It's been a while.  I've been waist deep in circulation and lived to tell
the tale.  In the end, it's not much of a tale, but there's other stuff in
here too

http://evergreen-ils.org/dokuwiki/doku.php?id=dev:browser_staff:dev_notes#section20140702

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] Simple self check

[Bill Erickson]

On Thu, Jun 19, 2014 at 9:58 AM, Tony Bandy to...@ohionet.org wrote:

 Hi Michele, folks,

 I apologize for not responding sooner on this, and please pardon any
 duplication with my responses below.  We were also having issues similar to
 you in that receipts wouldn't work as they should.  We're (COOL,
 cool-cat.org) are running a bit earlier version than you (2.4.2), but
 here's what we did to get things working:



[snip]



 5.  Using the Chrome 'inspect element' option on the self-check interface,
 I also noticed on our system some 404 errors about missing JS scripts.
  This may or may not be relevant, but is something I noticed.


If any of these have /nls/ in the path (e.g.
/js/dojo/openils/widget/nls/en-us/AutoFieldWidget.js), they can safely be
ignored.  These are translation files which Dojo automatically looks for.



 6.  Finally, working with ESI, we upgraded our version of OpenSRF.  This
 last point seemed to really help.


For reference : https://bugs.launchpad.net/opensrf/+bug/1198983



 --

 After all these steps, our self-check seems to be working good at this
 point in Chrome and Firefox.  IE support continues to be an issue, but
 looking through earlier threads, the interface was originally designed with
 Firefox, etc. in mind...I know developing for IE can be troublesome.  Ben
 Shum also helped me track down some errors, but if you search the mailing
 lists (maybe you've done this already), they were helpful to me as well.  I
 also am looking at Ben and Buzzy's discussion here as well:
 http://list.georgialibraries.org/pipermail/open-ils-general/2014-January/009481.html
 .


Indeed, it was developed specifically for Firefox.  The fact that it works
in Chrome is a happy accident.

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] Acquisitions: dealing with cancelled/backordered line items

[Bill Erickson]

On Thu, Jun 5, 2014 at 7:47 PM, Kathy Lussier kluss...@masslnc.org wrote:

  Hi Jane,

 My recollection is that in 2.4.4, you can't change the status of a line
 item in the staff client once it is cancelled. In 2.4.7, you will be able
 to change it to received (
 https://bugs.launchpad.net/evergreen/+bug/1115599), but you still can't
 cancel it a second time. I believe our acq people handle this by changing
 the cancel reason directly in the database.


Just to be clear, for items that are already canceled, changing the cancel
reason will not remove the encumbrances.



 It won't help you now, but Equinox is doing some development for us that
 will allow you to change the cancel reason. We hope the development will
 make it into 2.7. You can read the specs at
 http://yeti.esilibrary.com/dev/pub/techspecs/acq-cancel-reason-display.html
 .


And now we have some code:
https://bugs.launchpad.net/evergreen/+bug/1270289

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] Interface Ideas Mockup

[Bill Erickson]

 within the column header label.  However, what
we can't easily represent in the column header is the link action, so
that's a big plus for the Column Action Bar.



 A second visibility improvement in this mockup can be found in the List
 bar.  Some common actions are displayed without any user intervention, and
 the highlight tells (and reminds) the user of the default double-click
 action for the list.  While the highlight concept itself is not inherently
 knowable and must be learned, once known, it can potentially be applied
 universally throughout the client.  Consequently, no list behavior will
 remain a mystery regardless of familiarity with any particular interface.


I like the space savings of moving the List nav/control bar to the bottom,
but that means users will have to scroll down to control the list when
their page size exceeds the vertical space of the monitor.  Is that
acceptable?



 There are still innumerable variations we might consider, such as
 different use of colors, configuration level, or even using the venerable
 downward-pointing triangle instead of the menu icon.  If anyone feels a
 particular additional detail is critical to consider at this point, please
 do bring it up.  Otherwise, what do we think of this proposal?  Is it
 flexible enough to be applied broadly to every interface?  If not, how can
 we improve it further?  Does it solve more problems than it causes?  And,
 perhaps the biggest question of all, is it worth the necessary effort?


I'm really liking these so far and the mockup helps a lot.  Thanks, Dan!

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

[Bill Erickson]

Hi Joan,

On Fri, May 23, 2014 at 9:40 AM, Joan Kranich jkran...@cwmars.org wrote:

  Bill,



 If the display of the patron summary was horizontal would the displayed
 fields be basically what we see now in the horizontal display in the client
 (stock client, not C/W MARS client)?


As it stands, the summary is vertical, but the search is horizontal, so
it's a hybrid.  The patron summary information matches what we see in the
vertical patron display from the XUL client.  I still need to integrate the
group and stat-cat displays from the horizontal display into the web client.

To (I think) answer your question, it's going to look a little different,
but all of the same information should be there.




 Some of the feedback I’m getting from our libraries is that staff do not
 want scroll down to see the patron information and prefer it to be
 horizontal on the top.  Is the plan for an alert message to be a pop up box
 or possibly just display on the top of the screen?


With the vertical patron summary along the left, all of the page-specific
data starts at the top of the page, which limits the amount of vertical
scrolling required.

As it stands, the majority of alerts, confirm, prompts, dialogs, etc.
appear along the top center of the page as pop-up (modal) windows.  For
example, type a string of random characters into the checkin box:
https://bill-dev2.esilibrary.com/eg/staff/circ/checkin/index

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

[Bill Erickson]

 are indistinguishable, i.e. navigating directly to
/eg/staf/patron/123/bills should work even when accessed from an external
site, where no existing state is available.

However, because #1-style links can maintain state, there will invariably
be differences.  For example, we cache patron search results which remain
cached until the user navigates away from the egPatron Angular application.
 (Note, we could perform user searches via URL params, which would allow us
to avoid caching, but that approach won't be reasonable for every type of
state maintenance).  In this case, there is a noticeable difference between
clicking on another tab in the patron UI and clicking on the barcode link
in the grid, which takes the user out of the egPatron app and into the
egItemStatus app.  Once in the egItemStatus app, clicking the back button
will return the user to the egPatron app, but the previously cached search
results will be gone.

3. Links which perform some action within the current page but do not
affect the URL.  These have an empty href value and are driven by onclick
(ng-click, etc.) handlers.  These links perform nonsense actions when
ctrll-clicked, etc., since empty URLs default to the global base path,
which takes the user to the home splash page.

We have previously discussed indicating links of type #3 by always making
them appear as buttons instead of bare text links.  This is done in many
cases, but not all, as you've pointed out, Dan.  However, the column
sorting links, for example, would probably look... odd as buttons.  Maybe
they should be a different color, different font, etc.?

[Column headers get even more interesting when we consider that some
columns will support server-side sorting and some won't, so they may need
an additional layer of differentiation].

4.  Links to external sites.  These will be rare and I think it's
reasonable to open them in a new tab by default.

Assuming that #3-type links can't always be rendered as buttons, do we need
4 different ways of indicating link behavior when the behavior is not
obvious?  (BTW, i consider the behavior of navbar links, tab links, column
headers, and generally any standard, repeated navigation or UI control link
to be obvious, but there may be some room for debate there.  Button's fall
into this group as well if we all agree that buttons mean do-not-navigate).


How shall we differentiate?  Styling is an obvious choice.  We could
alternatively (or also) append small glyphicon (
http://getbootstrap.com/components/#glyphicons) to each text link as a way
to indicate link behavior.  For example, see the barcode links in the grid
at https://bill-dev2.esilibrary.com/eg/staff/circ/patron/7/items_out  (I
think the use of the Random glyphicon is somehow apropos ;)  The
squiggles in this example say, ctrl-click this link if you want to retain
your work in progress, otherwise click as usual.

Thanks for all your thoughts and input, Dan.  Making the behavior obvious
will be a huge usability win.

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

[Bill Erickson]

On Wed, May 21, 2014 at 5:47 PM, McCanna, Terran 
tmcca...@georgialibraries.org wrote:

 UI Planning:

 I looked through the items listed in Sprint #1 and the only interfaces I
 noticed missing were:

 Patron - Surveys (Will this not be added until the Local Admin sprint?)


Right, practically everything under the Local and Server Admin menus will
come with the Admin sprint.  Workstation Admin items will be added as the
relevant features are added (e.g. we already have the initial print config
interface).


 Patron - Acquisition Requests (Will this not be added until the Acq
 sprint?)


Yes, I left this for the ACQ sprint.  I added a note to the Acq sprint
about ensuring the link from the patron account UI was added.



 I've asked some of our staff that are more familiar with the other
 interfaces to take a look at what you have detailed so far for the other
 sprints.


Thanks!

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

[Bill Erickson]

On Tue, May 20, 2014 at 10:20 AM, Jason Etheridge ja...@esilibrary.comwrote:

  I have feedback requests for patron horizontal vs. vertical display and
 link (a) behavior.

 Bill, just to be clear, and I think is what you mean, you're
 advocating leaving the special click behavior for normal looking
 links up to the web browser?

 So folks can use whatever they're used to in the environment they're
 used to, whether it's using context menus or keyboard shortcuts.


Yes, exactly, no custom context menus or hard-coded target=_blank
attributes.  They're just links.

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

[OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

[Bill Erickson]

http://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:dev_notes#section20140519

I have feedback requests for patron horizontal vs. vertical display and
link (a) behavior.

Thanks,

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

[OPEN-ILS-GENERAL] browser client update 2014-05-09 / UI lists for sprint 1; packaging, etc.

[Bill Erickson]

Hi All,

I don't have any specific feedback requests this time, but feedback is of
course always welcome / appreciated.

http://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:dev_notes

-b

-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] browser client update 2014-05-01 / feedback requested on catalog integration

[Bill Erickson]

Hi Stuart,

I applied some patches over the weekend to get Firefox working, so if you
were using Firefox, please try again.

-b


On Fri, May 2, 2014 at 3:36 PM, Forrest, Stuart sforr...@bcgov.net wrote:

  I seem to be having a problem logging in to the browser client, tried
 admin/demo123, just keeps coming back to the login page.





 Stuart Forrest PhD

 Library Systems Specialist

 Beaufort County Library

 843 255 6450

 sforr...@bcgov.net



 http://www.beaufortcountylibrary.org



 For Liesure, For Learning, For Life







 *From:* open-ils-dev-boun...@list.georgialibraries.org [mailto:
 open-ils-dev-boun...@list.georgialibraries.org] *On Behalf Of *Bill
 Erickson
 *Sent:* Friday, May 02, 2014 10:20 AM

 *To:* Evergreen Discussion Group
 *Cc:* Evergreen Development Discussion List
 *Subject:* Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] browser client update
 2014-05-01 / feedback requested on catalog integration





 On Thu, May 1, 2014 at 4:12 PM, Forrest, Stuart sforr...@bcgov.net
 wrote:

 Hi

 What would be the login to the browser client, I'd like to take a look.
 Probably missed it an email somewhere...



 https://bill-dev2.esilibrary.com/eg/staff/login



 admin / demo123



 This is often my development server as well, so I make no guarantees of
 stability.



 Also, use Chrome for now, pending a resolution to the Firefox issue
 previously noted.



 -b



 --

 Bill Erickson

 | Senior Software Developer

 | phone: 877-OPEN-ILS (673-6457)

 | email: ber...@esilibrary.com

 | web: http://esilibrary.com

 | Equinox Software, Inc. / The Open Source Experts






-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts