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

[Dan Wells]

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

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.

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 :)

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


On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson 
mailto:beric...@gmail.com>> wrote:
Hi Scott,

On Mon, Aug 27, 2018 at 5:24 PM 
scott.tho...@sparkpa.org 
mailto: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 

Re: [OPEN-ILS-GENERAL] Order your conference t-shirts by the end of the month!

[Dan Wells]

Not sure if I will order a shirt, but just a shout-out to whoever made the 
conference logo this year.  The overlay of the four branch logos is simple, 
brilliant, and beautiful.

Sincerely,
Dan


From: Open-ils-general  on 
behalf of Kathy Lussier 
Sent: Wednesday, March 7, 2018 4:48:42 PM
To: 'Evergreen Discussion Group'
Subject: [OPEN-ILS-GENERAL] Order your conference t-shirts by the end of the
month!

Hi all,

I'm sending out a reminder that the community is selling conference
t-shirts that feature the 2018 conference logo for the very low price of
$15 per t-shirt.
https://urldefense.proofpoint.com/v2/url?u=https-3A__evergreen-2Dils.org_merchandise_conference-2Dt-2Dshirt_=DwICaQ=4rZ6NPIETe-LE5i2KBR4rw=LAgsHjAkdLiSDjEY2jDUJg=Bq8hP0Jq1DVMQC0zl87RJK_ptD4NC_Mx1DTxYEG7VyA=lrE3oXAO6-gNixMoCmJhqEtE8MJfRzcoMT4ob2VpYP0=
 . They come in
Small, Medium, Large, Extra Large, and Extra Extra Large.

Because we need time to get the t-shirts made and shipped to the venue,
they must be pre-ordered by Friday, March 30. The t-shirts will be
available for pickup at the Evergreen merchandise table.

Don't miss out on this opportunity! I'll be wearing mine!

Kathy

--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_kmlussier=DwICaQ=4rZ6NPIETe-LE5i2KBR4rw=LAgsHjAkdLiSDjEY2jDUJg=Bq8hP0Jq1DVMQC0zl87RJK_ptD4NC_Mx1DTxYEG7VyA=EeFnmSf05_Rm9aYWMJM657VnHfHd5kh5hMM-qpARNLU=

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Call for nominations for release manager — Evergreen 3.0

[Dan Wells]

Dear Evergreen Community,

I am writing to offer myself as release manager for the upcoming 3.0 release.

Our library is an independent academic installation, and having recently 
celebrated 7 years on Evergreen, a fairly early adopter.  I served as release 
manager for 2.5 and 2.6, release cycles distinguished by virtual "medals" 
(which, if I am elected, will certainly be making a comeback), and stirring 
lyrical ballads about "2.next" (which certainly will not be).  I was also the 
buildmaster and am current release maintainer for 2.11.

If elected, my primary focus will be full support for our express goal of a 
fully-featured web client for 3.0.  A particular emphasis will be a 
continuation of Kathy's efforts to push for greater consistency of the user 
experience while still being ever mindful of the particularities of any given 
feature.

My secondary point of emphasis will be on non-functional yet valuable changes 
to the codebase, and this falls into two main areas.  First, I would like to 
spearhead an effort to trim away dead (or dying) and deprecated code.  I 
greatly appreciate recent efforts in this area, but there is more to be done, 
and not just the XUL client.  While some things can be removed outright, 
another useful strategy will be simply increasing log messages (e.g. "XYZ is 
deprecated, consider using ABC instead."), or even more simple than that, at 
least adding code comments when a method (or entire file) has been superceded.  
This last idea leads directly to the second piece of this emphasis, and that is 
a general increase in code comments.  In particular, I will seek volunteers to 
work through the service code in particular and add, at a minimum, a header 
explaining broadly what the contained code is for.

These goals are being informed and inspired by ongoing work here at Calvin to 
document and holistically understand Evergreen in preparation for our 
conference presentation and beyond.  External and internal documentation are 
two separate goals which ultimately will work better when working together.

I know from experience that an RM has limited ability to spur actual new 
developments.  We each must work to scratch our own itches and those of our 
institutions, so I will briefly mention here a few areas where I intend to 
focus my own development efforts in the next cycle.  First, for too long I've 
let a few of our local billing improvements languish, so I will double my 
efforts to produce branches for community review.  Second, as one of the 
original contributors to the serials module, I intend to offer whatever help I 
can in smoothing the transition of those interfaces into the web staff client.

Thank you for your consideration.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] REL 2.10 and export non-imported records

[Dan Wells]

Hello Janet,

It appears a late change to that feature did not get fully implemented.  It 
originally exported as MARC-XML, but was changed to export as MARC21 instead.  
However, the dialog box still includes the ".xml" extension by default.

If you manually change the extension to something more MARC-like (e.g. ".mrc"), 
it may behave more reliably.  Ultimately, though, it depends on what software 
you want to use to edit the file, and how that software will interpret the 
contents of the file.  If you have the option, tell the software that the file 
is in MARC21 format.

In any case, I will open a bug about the ".xml" default, since giving a non-XML 
file an ".xml" extension is never going to be a good idea.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
Remington Steed
Sent: Tuesday, August 09, 2016 8:38 AM
To: Evergreen Discussion Group 
Subject: Re: [OPEN-ILS-GENERAL] REL 2.10 and export non-imported records

Hi Janet,

You aren't doing anything wrong.  This feature exports a MARCXML file, which is 
suitable for importing via the same MARC Batch Import interface.  You can 
simply save the file and reimport it (with different settings, or after editing 
the records if you wish).

Feel free to reply if you have more questions.

Remington

--
Remington Steed
Electronic Resources Specialist
Hekman Library, Calvin College
http://library.calvin.edu/

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Janet 
Schrader
Sent: Monday, August 08, 2016 5:45 PM
To: 
open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] REL 2.10 and export non-imported records

Hi,

I'm testing REL 2.10:
8.3.2. Quickly export non-imported records
When inspecting a queue in MARC Batch Import/Export, there is now a link to 
download to MARC file any records in the queue that were not imported into the 
catalog. This allows catalogers to quickly manipulate the records that failed 
to import using an external tool, then attempt to import them again.

How does this work? The file extension seems to be for XML.
[cid:image001.png@01D1F254.9F94D180]

I'm saving to my desktop where the icon appears to be MARC to MODS mapping??
[cid:image002.png@01D1F254.9F94D180][cid:image003.png@01D1F254.9F94D180]

I have been waiting for this development for four years, two months, and one 
week (but who's counting). I really appreciate any help on what I'm doing wrong.



Thanks!
Janet

Janet Schrader
Bibliographic Services Supervisor
C/W MARS Inc.
67 Millbrook Street, Suite 201
Worcester, MA 01606
Tel: 508-755-3323 ext. 325
Fax: 508-757-7801
jschra...@cwmars.org

Re: [OPEN-ILS-GENERAL] Shiny new EG server, shiny new 500 error

[Dan Wells]

Hello Justin,

Those ‘file not found’ errors are normal, and should be harmless.  For example, 
the ‘nls’ lookups are for translation, and since the fallback files are already 
English, there is no need to provide English translation files.  They certainly 
aren’t related to your 500 error.

That 500 error should be showing up in your Apache error log, wherever that is. 
 Recent setups default to syslog, but it might be elsewhere, e.g. 
/var/log/apache2/.  Your Apache config should lead you in the right direction 
there.  Find that error and please post back if it doesn’t lead you anywhere 
fruiful.  There are also *probably* errors in /openils/var/log/  (e.g. grep for 
“ERR”).  Feel free to post those, too.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Justin 
P Degenaars
Sent: Thursday, April 14, 2016 2:43 PM
To: open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] Shiny new EG server, shiny new 500 error

Hi,
We recently fired up a EG server, finally, and at first it was beautiful! That 
is until I tried linking it to AD...
So following the steps outlined in documentation, I shutdown EG and apache, 
made the change to opensrf.xml to match my enviroment hit save, turned on 
apache, turned on EG, fired up my client, and things went down hill quickly. I 
tried to create a user, to test the AD link, and when I went to hit save, I got 
an error, which I can't replicate now. So troubleshooting I logged off, and 
tried to test the connection, which returned a 500 error. So I went to the 
website to see if I would see a 500 error, which I did. So, I shut everything 
down and back on, with no luck. Digging deeper, I look to the apache logs which 
returns errors like:

File does not exist /openils/var/web/js/dojo/fieldmapper/OrgLasso.js

and a few more like it, including this one:

File does not exist: /openils/var/web/js/dojo/openils/User/nls/en-us/User.js

Which I checked and the entire "en-us" folder is gone. Along with a few other 
stuff from various folders and such.

So what is the best way to resolve this, and why oh why did this happen? (I 
understand the second part could because a polar bear sneezed, just want to 
make sure that something I did didn't wipe it out)

Thank you in advance,

Justin Degenaars



Please email all technology and copy requests, questions, and problems to 
bush...@vcu.edu.

Justin P. Degenaars
System administrator\Supervisor

Virginia Commonwealth University
School of Business--Technology Services
301 West Main Street--Room B2131F
PO BOX 844000
Richmond, Virginia 23284-4000
804.828.7177 (D) 804.828.8884 (F) 804.828.4059 (Help Desk)



Don't be a phishing victim - VCU and other reputable organizations will never 
use e-mail to request that you reply with your password, Social Security 
Number, or confidential personal information.

Re: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding with Void overdue fines when items are marked lost org unit setting on 2.9

[Dan Wells]

Hello Brent,

Ah, sorry about that.  You are right.  We have that note due to a local patch 
for a different (related) bug.

I’ll get it sorted and post a link to the bug(s) with branch(es).

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Brent 
Mills
Sent: Wednesday, January 27, 2016 7:34 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Indication of what caused fine 
forgiveness/voiding with Void overdue fines when items are marked lost org unit 
setting on 2.9

Hi Dan,

Thanks for the quick reply. I should have included the Note field from the 
column picker in the (present) screen shot. But there is nothing in that field 
for any of the account_adjust payments for "System: VOIDED OVERDUE FOR LOST". A 
check in the database for entries in money.account_adjustment only shows note 
entries for "System: OVERDUE REVERSED FOR CLAIMS-RETURNED" right now.

-Brent
On 1/27/16 3:06 PM, Dan Wells wrote:
Hello Brent,

Those adjustments should already have a note, but it looks like your note 
column is not displaying.  Try adding it from the column picker in the upper 
right corner of that box.  The note should say “System: VOIDED OVERDUE FOR 
LOST”.  (Certainly not the best note as far as wording goes, but I think it was 
just taken wholesale from the old note applied to the billing.)

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Brent 
Mills
Sent: Wednesday, January 27, 2016 4:30 PM
To: Evergreen Discussion Group 
<open-ils-general@list.georgialibraries.org><mailto:open-ils-general@list.georgialibraries.org>
Subject: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding 
with Void overdue fines when items are marked lost org unit setting on 2.9

Hello,

We recently upgraded to 2.9.1 from 2.7.5 and the negative balance fixes have 
changed what some libraries -- with the Void overdue fines when items are 
marked lost library setting enabled -- were used to seeing in the patron bills 
tab.

Example:
Patron with overdue book has it marked lost. Library Setting for "Void overdue 
fines when items are marked lost" is enabled for the the library where this 
occurred.

Previously, the fines were voided as normal and the display gave a little more 
information about what caused the voiding in the Note field.

Now, the overdue forgiveness has moved to the payment section which I 
understand is correct from the conditional negative balance documentation for 
2.9 at http://docs.evergreen-ils.org/2.9/_circulation_2.html


The account adjustment payment type will also be used for all libraries, 
regardless of the state of negative balance settings, in cases where overdue 
fines are adjusted when an overdue item is marked lost.

I was wondering if there was a way to indicate what those payments are for to 
the staff members? The account_adjustment payment type helps, but it would be 
nice if there was a note field entry for "Overdue Forgiveness Payments" or 
something like that.

Just curious how/if other libraries are handling this situation (or if it's 
even an issue for most).

Thanks!



--

Brent Mills

Systems Librarian | Sage Library System

email: br...@hoodriverlibrary.org<mailto:br...@hoodriverlibrary.org>

tickets: sagelib.org/support



--

Brent Mills

Systems Librarian | Sage Library System

email: br...@hoodriverlibrary.org<mailto:br...@hoodriverlibrary.org>

tickets: sagelib.org/support

desk/mobile: 541.387.5063 / 541.610.8384

Re: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding with Void overdue fines when items are marked lost org unit setting on 2.9

[Dan Wells]

Okay, it turns out I had actually posted the fix before the holidays, but it 
hasn’t been reviewed or committed yet.  I have now force pushed a couple small 
tweaks, and you can see it all here:

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

It’s a very small set of changes.  One thing holding it back is a lack of 
automated testing, and I’m still not too sure how to meet that need.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Thursday, January 28, 2016 1:59 PM
To: Evergreen Discussion Group <open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] Indication of what caused fine 
forgiveness/voiding with Void overdue fines when items are marked lost org unit 
setting on 2.9

Hello Brent,

Ah, sorry about that.  You are right.  We have that note due to a local patch 
for a different (related) bug.

I’ll get it sorted and post a link to the bug(s) with branch(es).

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Brent 
Mills
Sent: Wednesday, January 27, 2016 7:34 PM
To: 
open-ils-general@list.georgialibraries.org<mailto:open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] Indication of what caused fine 
forgiveness/voiding with Void overdue fines when items are marked lost org unit 
setting on 2.9

Hi Dan,

Thanks for the quick reply. I should have included the Note field from the 
column picker in the (present) screen shot. But there is nothing in that field 
for any of the account_adjust payments for "System: VOIDED OVERDUE FOR LOST". A 
check in the database for entries in money.account_adjustment only shows note 
entries for "System: OVERDUE REVERSED FOR CLAIMS-RETURNED" right now.

-Brent
On 1/27/16 3:06 PM, Dan Wells wrote:
Hello Brent,

Those adjustments should already have a note, but it looks like your note 
column is not displaying.  Try adding it from the column picker in the upper 
right corner of that box.  The note should say “System: VOIDED OVERDUE FOR 
LOST”.  (Certainly not the best note as far as wording goes, but I think it was 
just taken wholesale from the old note applied to the billing.)

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Brent 
Mills
Sent: Wednesday, January 27, 2016 4:30 PM
To: Evergreen Discussion Group 
<open-ils-general@list.georgialibraries.org><mailto:open-ils-general@list.georgialibraries.org>
Subject: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding 
with Void overdue fines when items are marked lost org unit setting on 2.9

Hello,

We recently upgraded to 2.9.1 from 2.7.5 and the negative balance fixes have 
changed what some libraries -- with the Void overdue fines when items are 
marked lost library setting enabled -- were used to seeing in the patron bills 
tab.

Example:
Patron with overdue book has it marked lost. Library Setting for "Void overdue 
fines when items are marked lost" is enabled for the the library where this 
occurred.

Previously, the fines were voided as normal and the display gave a little more 
information about what caused the voiding in the Note field.

Now, the overdue forgiveness has moved to the payment section which I 
understand is correct from the conditional negative balance documentation for 
2.9 at http://docs.evergreen-ils.org/2.9/_circulation_2.html

The account adjustment payment type will also be used for all libraries, 
regardless of the state of negative balance settings, in cases where overdue 
fines are adjusted when an overdue item is marked lost.

I was wondering if there was a way to indicate what those payments are for to 
the staff members? The account_adjustment payment type helps, but it would be 
nice if there was a note field entry for "Overdue Forgiveness Payments" or 
something like that.

Just curious how/if other libraries are handling this situation (or if it's 
even an issue for most).

Thanks!


--

Brent Mills

Systems Librarian | Sage Library System

email: br...@hoodriverlibrary.org<mailto:br...@hoodriverlibrary.org>

tickets: sagelib.org/support


--

Brent Mills

Systems Librarian | Sage Library System

email: br...@hoodriverlibrary.org<mailto:br...@hoodriverlibrary.org>

tickets: sagelib.org/support

desk/mobile: 541.387.5063 / 541.610.8384

Re: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding with Void overdue fines when items are marked lost org unit setting on 2.9

[Dan Wells]

Hello Brent,

Those adjustments should already have a note, but it looks like your note 
column is not displaying.  Try adding it from the column picker in the upper 
right corner of that box.  The note should say “System: VOIDED OVERDUE FOR 
LOST”.  (Certainly not the best note as far as wording goes, but I think it was 
just taken wholesale from the old note applied to the billing.)

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Brent 
Mills
Sent: Wednesday, January 27, 2016 4:30 PM
To: Evergreen Discussion Group 
Subject: [OPEN-ILS-GENERAL] Indication of what caused fine forgiveness/voiding 
with Void overdue fines when items are marked lost org unit setting on 2.9

Hello,

We recently upgraded to 2.9.1 from 2.7.5 and the negative balance fixes have 
changed what some libraries -- with the Void overdue fines when items are 
marked lost library setting enabled -- were used to seeing in the patron bills 
tab.

Example:
Patron with overdue book has it marked lost. Library Setting for "Void overdue 
fines when items are marked lost" is enabled for the the library where this 
occurred.

Previously, the fines were voided as normal and the display gave a little more 
information about what caused the voiding in the Note field.

Now, the overdue forgiveness has moved to the payment section which I 
understand is correct from the conditional negative balance documentation for 
2.9 at http://docs.evergreen-ils.org/2.9/_circulation_2.html

The account adjustment payment type will also be used for all libraries, 
regardless of the state of negative balance settings, in cases where overdue 
fines are adjusted when an overdue item is marked lost.

I was wondering if there was a way to indicate what those payments are for to 
the staff members? The account_adjustment payment type helps, but it would be 
nice if there was a note field entry for "Overdue Forgiveness Payments" or 
something like that.

Just curious how/if other libraries are handling this situation (or if it's 
even an issue for most).

Thanks!


--

Brent Mills

Systems Librarian | Sage Library System

email: br...@hoodriverlibrary.org

tickets: sagelib.org/support

Re: [OPEN-ILS-GENERAL] Patrons can't place holds on Parts

[Dan Wells]

Michele, thanks for bringing this up.  There are two related but functionality 
distinct options for blocking holds on available items, and they each work at 
different levels.

ctx.holds_block.enabled is a setting in the TPAC config.tt2 file.  If this is 
true, the “Place Hold” link is hidden whenever there are available copies.  
This is the option which is not yet (I don’t think) parts aware, and it may be 
difficult to work out a good way to do it seamlessly.

There is also, as Michele points out, an org unit level setting called “Has 
Local Copy Block”.  This does not control when the “Place Hold” link appears 
(it will always be visible in this scenario), but it does block the actual 
request if a local copy is available.  If one can educate users that the 
appearance of the “Place Hold” link does not indicate that a hold can actually 
be placed, then this is a workable alternative.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
Morgan, Michele
Sent: Monday, January 11, 2016 3:00 PM
To: Evergreen Discussion Group <open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] Patrons can't place holds on Parts

Hi,

Placing part holds on checked out items is working fine on our 2.9 system. The 
Place Hold button is visible and we are able to place a part level hold on a 
checked out item without a problem. The library in question has the setting 
"Has Local Copy Block" set to True.

If we attempt a part level hold where the copy is available, the hold fails 
with this message:
Hold was not successfully placed
There is already a copy available at your local library.

If we attempt a part level hold where the copy is checked out, the hold is 
placed successfully.
Could something else be causing the Place Hold link on the record not to show?

Hope this is helpful,
Michele
--
Michele M. Morgan, Technical Assistant
North of Boston Library Exchange, Danvers Massachusetts
mmor...@noblenet.org<mailto:mmor...@noblenet.org>


On Mon, Jan 11, 2016 at 9:27 AM, Dan Wells 
<d...@calvin.edu<mailto:d...@calvin.edu>> wrote:
Hello Rosie,

I think you are right in that this scenario (block holds when available, allow 
holds for unavailable parts) is not supported by the current code.  
Unfortunately, I think getting it supported also won’t be especially simple, 
especially from the UI side.

It’s simple to check if every copy is out, but in this case we’d need to know 
if any particular part is totally out, so that’s the first hurdle.  Maybe some 
of those pieces are in place, I didn’t check.  After that, you would then need 
to decide how to present the place hold links / screen.  How do you make it 
clear (along with the underlying reasons) that the patron can only place a hold 
on a certain part?  It seems inherently confusing for a holds screen to be 
partially offered, so we’d need to be careful there.

I do think this is missing functionality we should ultimately support, so 
please just take this as some thoughts about what you might be up against.  
Please open up a bug (if there isn’t one), and if you do tackle this, please 
share back what you did to get it where you needed it to be.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org<mailto:open-ils-general-boun...@list.georgialibraries.org>]
 On Behalf Of Rosemary Le Faive
Sent: Friday, January 08, 2016 12:45 PM
To: 
open-ils-general@list.georgialibraries.org<mailto:open-ils-general@list.georgialibraries.org>
Subject: [OPEN-ILS-GENERAL] Patrons can't place holds on Parts

Hi,

We're trying to implement Monograph Parts so that patrons can place holds on 
specific volumes that are out.  But the "Place hold" link isn't showing up! I'm 
wondering if I'm missing something in the configuration, or if I need to 
customize the template.

The case in question: of four volumes/parts in a record, two are available and 
two are checked out. All are in a holdable location.

If I set ctx.holds_block.enabled = 'false' then the Place Hold link shows up, 
and holds can be placed on the checked-out parts. But then the Place Hold link 
shows up even where it shouldn't (since we don't allow holds on available 
copies!)

I'm afraid i have to hack the template here [1].

Has anyone else faced this issue?

Thanks!

-Rosie

[1] 
https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/templates/opac/parts/record/summary.tt2#L45-L48


--

Rosemary Le Faive
Digital Infrastructure and Discovery Librarian
Robertson Library
University of Prince Edward Island
550 University Ave, Charlottetown PE C1A 4P3
Canada
tel: 902-566-0533 | fax: 902-628-4305 | 
email: rlefa...@upei.ca<mailto:rlefa...@upei.ca>

Re: [OPEN-ILS-GENERAL] Patrons can't place holds on Parts

[Dan Wells]

Hello Rosie,

I think you are right in that this scenario (block holds when available, allow 
holds for unavailable parts) is not supported by the current code.  
Unfortunately, I think getting it supported also won’t be especially simple, 
especially from the UI side.

It’s simple to check if every copy is out, but in this case we’d need to know 
if any particular part is totally out, so that’s the first hurdle.  Maybe some 
of those pieces are in place, I didn’t check.  After that, you would then need 
to decide how to present the place hold links / screen.  How do you make it 
clear (along with the underlying reasons) that the patron can only place a hold 
on a certain part?  It seems inherently confusing for a holds screen to be 
partially offered, so we’d need to be careful there.

I do think this is missing functionality we should ultimately support, so 
please just take this as some thoughts about what you might be up against.  
Please open up a bug (if there isn’t one), and if you do tackle this, please 
share back what you did to get it where you needed it to be.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
Rosemary Le Faive
Sent: Friday, January 08, 2016 12:45 PM
To: open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] Patrons can't place holds on Parts

Hi,

We're trying to implement Monograph Parts so that patrons can place holds on 
specific volumes that are out.  But the "Place hold" link isn't showing up! I'm 
wondering if I'm missing something in the configuration, or if I need to 
customize the template.

The case in question: of four volumes/parts in a record, two are available and 
two are checked out. All are in a holdable location.

If I set ctx.holds_block.enabled = 'false' then the Place Hold link shows up, 
and holds can be placed on the checked-out parts. But then the Place Hold link 
shows up even where it shouldn't (since we don't allow holds on available 
copies!)

I'm afraid i have to hack the template here [1].

Has anyone else faced this issue?

Thanks!

-Rosie

[1] 
https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/templates/opac/parts/record/summary.tt2#L45-L48


--

Rosemary Le Faive
Digital Infrastructure and Discovery Librarian
Robertson Library
University of Prince Edward Island
550 University Ave, Charlottetown PE C1A 4P3
Canada
tel: 902-566-0533 | fax: 902-628-4305 | email: 
rlefa...@upei.ca

Re: [OPEN-ILS-GENERAL] Who's Using Syrup?

[Dan Wells]

Hello Jim,

We’re using Syrup here at Calvin.  We just started our second semester using 
it, so we’re still relatively green.  Our install is also somewhat customized 
for local needs.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of James 
Keenan
Sent: Tuesday, September 22, 2015 1:10 PM
To: Evergreen Discussion Group 
Subject: [OPEN-ILS-GENERAL] Who's Using Syrup?

Hi All,

We’re trying to get a sense of who in the Evergreen Community is using the 
course reserves software, Syrup, for their academic libraries. We know our 
MassLNC partner, NOBLE, is but we don’t have a sense of who else in the world 
may be.

Is anyone using a different software package for course reserves for their 
academic libraries?

Jim

Jim Keenan
Library Applications Supervisor
jkee...@cwmars.org
508-755-3323 x23

C/W MARS
67 Millbrook St., Suite 201
Worcester, MA 01606

P   Save a tree! Please don't print this e-mail unless it's really necessary.
Currently reading Swansong 1945  by Walter Kempowski.

Re: [OPEN-ILS-GENERAL] Auto-generated Barcodes

[Dan Wells]

Hello Lezlie,

Again, it isn't quite the same as how it works in Vandelay, but there is 
another built-in method for autogenerating barcodes which can work almost 
anywhere in Evergreen.  If you try to create (or edit) an item and you use a 
barcode starting with '@@', the system will automatically set the barcode to 
'@@[item id]', which by its nature is guaranteed to be unique.  At our library 
(and in the serials code) we use @@AUTO when we want to auto-generate, but 
@@ANYTHINGYOUWANT will work  :)

Good luck!
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason 
Etheridge
Sent: Wednesday, September 09, 2015 11:13 PM
To: Evergreen Discussion Group 
Subject: Re: [OPEN-ILS-GENERAL] Auto-generated Barcodes

> From the Holdings Maintenance screen I opt to create a volume.  In the 
> bottom left corner of the screen is the [Auto-Generate Barcode?] button.
> The cursor is in the Barcode/Item Part box.  It seems like clicking 
> the barcode button would put a system generated barcode In the box, 
> but that isn’t happening.

Hi Lezlie, it's not the same concept as what exists in acquisitions and 
vandelay.  This function is intended to help with adding multiple items in one 
shot, for example, when using pre-printed barcodes.
Let's say you were to specify 10 for the number of new items to create, and for 
the first item you scan in the first barcode from the printed sheet.  The 
Auto-Generate button would then assign the remaining barcodes in sequence using 
the first barcode as a seed value.  If the Strict Barcode checkbox is checked, 
these generated barcodes will also contain the correct check digit.

Let me know if that makes sense.

--
Jason Etheridge
| Community and Migration Manager
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: ja...@esilibrary.com
| web: http://www.esilibrary.com

Re: [OPEN-ILS-GENERAL] Inventory Item

[Dan Wells]

We also do more or less exactly what Jennifer and others have outlined in more 
detail.  When the scanning is done, we generally pull our missing list directly 
from the DB, with a query something like the one listed below (adjust to suit), 
which we then import into Excel for staff/student searching of items.

Dan

---

COPY (
SELECT
oils_xpath_string('//*[@tag=245]/*[@code=a]', bre.marc) || ' ' || 
COALESCE(oils_xpath_string('//*[@tag=245]/*[@code=b]', bre.marc), '') as 
title,
oils_xpath_string('//*[@tag=100]/*[@code=a]', bre.marc) as author,
acn.label,
acp.copy_number,
acp.barcode,
ccs.name,
bre.id,
acp.create_date,
acp.edit_date,
acp.id,
acn.label_sortkey
FROM asset.copy acp
JOIN asset.call_number acn ON acn.id = acp.call_number
JOIN biblio.record_entry bre ON bre.id = acn.record
JOIN config.copy_status ccs ON ccs.id = acp.status
WHERE
NOT bre.deleted
AND NOT acn.deleted
AND NOT acp.deleted
AND acp.location = 103 -- this run was only for the 4th Floor
AND acn.label LIKE 'BS%' -- this run was for BS call numbers
AND acp.edit_date  '2014-05-07' -- date inventory started
AND acp.status NOT IN (1,102) -- checked out, legacy lost
AND circ_modifier  'PERIODICAL' -- these don't have barcodes, so they 
don't get scanned
AND barcode NOT LIKE '@@%' -- items with auto-barcodes can't be scanned
) TO '/tmp/BS_inventory_report.csv' WITH CSV;


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
Jennifer Pringle (Project Sitka)
Sent: Wednesday, July 29, 2015 1:19 PM
To: Evergreen Discussion Group open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Inventory Item

Several of our libraries have run inventory using the procedure we came up 
with:  
http://docs.sitka.bclibraries.ca/Sitka/current/html/inventory.html

I can send more details about the report templates we have set up if anyone is 
interested.

Jennifer


Quoting Hardy, Elaine eha...@georgialibraries.org:

 PINES a number of years ago explored development of an inventory 
 function in Evergreen; however, our development funding was cut so 
 that we were unable to pursue it. We have not revisited the requirements.



 We did develop a now dated document on using existing functionality to 
 inventory. I have attached the pdf. I have not reviewed it in a few years.



 Elaine



 J. Elaine Hardy
 PINES  Collaborative Projects Manager Georgia Public Library Service
 1800 Century Place, Ste 150
 Atlanta, Ga. 30345-4304



 404.235.7128
 404.235.7201, fax
 eha...@georgialibraries.org
 www.georgialibraries.org
 www.georgialibraries.org/pines



 From: Open-ils-general
 [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of
 Scott Thomas
 Sent: Wednesday, July 29, 2015 12:35 PM
 To: open-ils-general@list.georgialibraries.org
 Subject: [OPEN-ILS-GENERAL] Inventory Item



 We have been with EG for four months, and this is the first time this has
 come up: there does not appear to be an Inventory Item function (at least
 in 2.6.3). I am not finding a Date Inventoried field in the item record
 nor can I locate a way to inventory an item. Am I missing something
 obvious? If not, how do Evergreen libraries inventory their collections?



 Thank you,
 Scott





 Scott  Thomas, MLS

 Head of Information Technologies and Technical Services

 Scranton Public Library

 Lackawanna County Library System

 2006 N. Main Ave.

 Scranton, PA 18508

 Ph: 570-207-2379

 Fx: 570-348-3020

 Email:  mailto:sc...@albright.org sc...@albright.org


-- 
Jennifer Pringle
Co-op Support
BC Libraries Cooperative
Tel: 1-888-848-9250
Email:jprin...@sitka.bclibraries.ca
Website: http://bc.libraries.coop

Re: [OPEN-ILS-GENERAL] Marc Export Script Error

[Dan Wells]

Jesse,

Getting back to what you are trying to accomplish, is there a particular reason 
you are exporting your MARC records?  If you're just migrating the whole 
database to a new server, I'd say exporting and reimporting the MARC isn't 
something you'd need (or want) to do.  It's also possible you're actually 
talking about a data dump and restore, and I am just misunderstanding.

It might still be worth looking over those records to see if you can spot the 
problem, but honestly, a database with only three records with shoddy MARC 
isn't bad at all :)

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jesse 
McCarty
Sent: Tuesday, July 28, 2015 12:30 PM
To: open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] Marc Export Script Error

Hi Everyone,

I am working on a new Evergreen Server to deploy in the fall (Ubuntu 14.04, 
Postgres 9.3 - Current system is Ubuntu 12.04, Postgres 9.2) and am running 
into an error with the marc_extract script. The script works with no issue on 
the production system running Postgres 9.2, but after I import the current 
production data into a test server (identical to the current production server, 
with older DB data) and upgrade Postgres to 9.3 it stops working with the 
following error:

Error in bibliographic record 168171
Substr outside of string at /usr/share/perl5/MARC/Record.pm line 573

There are two other bibliographic records that have the error as well (168498  
172482).

The new database seems to be working otherwise (attached is a screen shot of 
the output of the pg_upgradecluster results) even though the upgrade showed 
some errors.

Any help is greatly appreciated. Thanks!

Jesse McCarty
City of Burlington
IT Technical Assistant

[OPEN-ILS-GENERAL] Web Client Design - Fixed Page Elements?

[Dan Wells]

Hello all,

This came up in Kathy's recent thread asking about the patron editor, and 
rather than hijack that thread, I'd like to broaden the conversation a little, 
because the same usability issues will affect many areas of the staff client.

To cut straight to the point, I strongly believe that using fixed position for 
large portions of the staff client interface will have a major positive effect 
on usability.  This has been applied and proven in desktop applications for 
decades, and is now being rediscovered within the browser environment as web 
pages become applications.  There is plenty of evidence out there to support 
this stance, but here is a quick read which highlights the point well: 
http://www.smashingmagazine.com/2012/09/11/sticky-menus-are-quicker-to-navigate/

If we consider the mockups from our design internship a few months back, in the 
screenshot Kathy referenced, the entire top area (and, in this case, the right 
sidebar) would ideally be fixed position.  The only scrolling area should be 
the actual form.  For any who attended my talk on design at the conference, 
this is exactly the concern of rule of thumb #3: Scroll the data, not the 
interface, with data broadly including all information and workspaces which 
are not the program.  (Here is Kathy's screenshot link again for reference: 
http://media.tumblr.com/69beec7802a938b889bdfa80c7e0d54b/tumblr_inline_nkn0okinXl1t572gy.png
 )

The main complaint driven at fixed screen elements is that they take up too 
much space.  They do take up space, obviously, but with the amount of use these 
elements get on a moment by moment basis, the space is well worth taking.  In 
cases where more workspace is truly of benefit, we are better off using fixed 
position with a hide option (auto or manual) than we would be with using 
scroll, as we can retain the clear benefits of persistent availability and 
predictability.  (Expert users might also choose to do without some toolbars 
and rely on keyboard shortcuts, but that sort of use will never be feasible for 
many staff client users and scenarios.)

As the Smashing Magazine article points out, the easiest way to understand the 
situation is to simply imagine other software working with fully-scrolling 
interfaces.  In this imaginary scenario, when you are using a word processor, a 
spreadsheet application, or even a browser itself, all of your menus, toolbars, 
tabs, etc., would simply scroll off the screen as soon as you tried to scroll 
down to see additional content.  It's likely that some ancient desktop software 
did exactly that, but if they did, they are now extinct, and not without good 
reason.

Another valid concern sometimes raised is the effect a rich, fixed interface 
might have on a small screen appliance, like a phone.  This topic should be 
addressed, but I believe it is best kept separate from the problems at hand, 
which are already large enough.  My personal stance would be that a full, 
first-class staff client interface on a small screen device is not a realistic 
concern for a community of our size, needs, and capabilities.  Our bar for 
using the full client on phones should be not impossible, and then we can 
re-dedicate a portion of our energy to creating limited, purpose-built 
interfaces for functions of known value on small devices (e.g. inventory 
scanning), and which are also likely to best include some fixed top and/or 
bottom elements.

I also want to emphasize that none if this is meant to disparage the work which 
has been done so far.  It is much harder to make something out of nothing than 
to take something and make it better.  I also acknowledge that, while I have 
spent large amounts of time studying the web client, I have found zero time to 
contribute to the actual web client code.  That said, if we can help establish 
consensus around where we want to end up, I know I would feel more comfortable 
jumping in, and I suspect others might as well.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Hack-A-Way

[Dan Wells]

Hello Rogan,

One question: since the conference this year is later than it has typically 
been, do we still want to aim for 6 months out (which would put us in 
November), or stick to a Sept./Oct. event?  It would of course be nice to know 
the 2016 conference dates to help decide, but I’m not sure how far along that 
process is yet (I suspect not very).

Just curious,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Rogan 
Hamby
Sent: Monday, March 30, 2015 5:58 PM
To: Evergreen Discussion Group
Subject: [OPEN-ILS-GENERAL] Hack-A-Way

While thinking about it I wanted to inject a thought into the streams as we 
approach the conference.  About six months after the conference each year we 
have a Hack-A-Way, an opprotunity to host Evergreen developers in a low key 
environment away from the general activities of the conference where they can 
just talk about development and work.

The threshold is much lower than a conference with about 10 - 20 participants.  
For those curious please read our WIKI page:

http://evergreen-ils.org/dokuwiki/doku.php?id=hack-a-way

And if anyone would like to host please contact me.  Thanks!

--

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. Lewishttp://www.goodreads.com/author/show/1069006.C_S_Lewis

[OPEN-ILS-GENERAL] Evergreen 2.6.6 Released

[Dan Wells]

The Evergreen 2.6.6 maintenance release is now available.

Quick Links
*   Download Page - http://evergreen-ils.org/egdownloads/
*   List of Bugs Fixed - https://launchpad.net/evergreen/+milestone/2.6.6
*   Changelog - http://evergreen-ils.org/downloads/ChangeLog-2.6.5-2.6.6

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen OPW Style Guide Group: Help Wanted!

[Dan Wells]

Hello all,

This email is an open invitation to join the #opw-evergreen channel, 
particularly from 9am-noon eastern on Wednesdays and Fridays (our regular OPW 
group meeting times).  Given the duration of these events, we're opting to keep 
using the separate channel for now and see how things go.

Overall, we're still in the early stages labeling and understanding the staff 
client layout, with the goal of unifying (where it makes sense) the different 
screen flavors within the client.  We're also dabbling in different colors, 
icons, and fonts.  Though you may see some mockups exploring all of this, I 
want to emphasize that nothing is decided and everything will be subject to 
the normal level of community input and review.  The mockups at this point are 
primarily to give points of reference for discussion, as it is very difficult 
to discuss style and design without having something to actually look at!

Please reply if you have any questions, and we hope to see you there!

On behalf of the OPW team,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Patron Batch Functions

[Dan Wells]

Hello all,

We currently sync to two different student information systems, one for the 
college and one for the seminary.  Evergreen does have a possible way to 
classify identifiers (i.e. record their sources) via the 
config.identification_type table as linked to the actor.usr.ident_type field.  
In our system, we have a 'College' identifier_type and a 'Seminary' 
identifier_type, and our load overlays based on a combination of ident_type and 
ident_value.  You can of course have as many types as you have ID sources, and 
this method also assumes you are not already using ident_type for some broader 
purpose.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Tina 
Ji (Project Sitka)
Sent: Tuesday, December 09, 2014 12:31 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Patron Batch Functions

Our academic libraries use the unique identifiers from the student information 
system as ident_value. We have only a few academic libraries, but some use the 
same student information system (same software, runs separately). We 
encountered the duplicate ident_value issue, and had to pad it.

We also have another working scenario. Some libraries want to sync between 
Evergreen and the student information system on every patron load. They send us 
a complete current students file. We delete all student records based on patron 
profile, such as Student and Postgrad Student, and then undelete and update 
matching records and load nonmatching records.

Tina Ji
Support Specialist
BC Libraries Coop


Quoting Martha Driscoll drisc...@noblenet.org:

 Rogan,
 Thanks for mentioning the unique identifier problem.  I did intent to 
 associate ident_value with the unique identifier coming from the 
 campus system.  Having non-unique identifiers from multiple campus 
 systems is definitely a possibility.  Our libraries are told to append 
 the org_unit shortname to the university id.  That mostly works well 
 except in cases where a student was entered by hand prior to a data 
 load and the library staff person did not enter the ID or entered it 
 without the shortname appended.  We will see barcode collisions in 
 that case which will halt the load until resolved.

 Martha Driscoll
 Systems Manager
 North of Boston Library Exchange
 Danvers, Massachusetts
 www.noblenet.org

 On 12/9/2014 9:12 AM, Rogan Hamby wrote:
 I think the syncing between Evergreen and the student information 
 system will be critical part and I think the workflow you mentioned 
 Tim is fairly typical.  I noticed that the wiki write up already 
 mentions an ident_value.  Is that intended to be a unique identifier 
 from the origin student information system?  If so, can we imagine a 
 scenario where we might have multiple origin student systems, such as 
 a consortium with multiple schools?  We might need a table to 
 identify those external sources.


Tina Ji
1-888-848-9250
Support Specialist
BC Libraries Cooperative/Sitka

[OPEN-ILS-GENERAL] Maintenance Releases for 2.5 and 2.6

[Dan Wells]

Hello all,

With apologies for the general state of limbo for maintenance releases for 2.5 
and 2.6, I just want to quickly note that the next releases are now scheduled 
for next Wednesday, 11/5.  I also want to mention that this will be the *last* 
bugfix release for 2.5.  (Security fixes for 2.5 will continue for up to 6 
months.)

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6.3 and 2.5.7 Uploaded

[Dan Wells]

Hello all,

Maintenance releases 2.6.3 and 2.5.7 are now available for preview testing:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.3.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.3.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.3_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.3_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.3_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.3_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.3.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.3.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.6.2-2.6.3

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.7.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.7.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.7_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.7_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.7_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.7_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.7.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.7.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.6-2.5.7

Please check out the changelogs for more details.

As always, feedback is appreciated.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6.2 and 2.5.6 Uploaded

[Dan Wells]

Hello all,

With apologies for the delays, maintenance releases 2.6.2 and 2.5.6 are now 
available for preview testing:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.2.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.2.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.2_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.2_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.2_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.2_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.2.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.2.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.6.1-2.6.2

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.6.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.6.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.6_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.6_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.6_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.6_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.6.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.6.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.5-2.5.6

These are fairly small releases; please check out the changelogs for more 
details.

Also, due to it already being 7/7, I am also planning to delay the next 
maintenance releases until Friday the following week (new target of 7/25).

As always, feedback is appreciated.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Maintenance Releases Delayed

[Dan Wells]

Hello all,

Just a quick note for anyone waiting, the maintenance releases for 2.5 and 2.6 
are currently delayed.  Please plan on these releases next week instead.

Thank you,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Evergreen 2.6.1 and 2.5.5 Uploaded

[Dan Wells]

Hello Jesse,

Thanks for bringing this up again.  I have been thinking about it since your 
earlier issues, and rather than start that thread here, I am going to respond 
in a new thread on the dev list, as this is going to need input from the other 
developers.

Thanks again,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jesse 
McCarty
Sent: Friday, May 30, 2014 12:48 PM
To: 'Evergreen Discussion Group'
Subject: Re: [OPEN-ILS-GENERAL] Evergreen 2.6.1 and 2.5.5 Uploaded

Here is a question: What is the official supported upgrade path from one 
version (2.4.x - 2.5.x, 2.5.x-2.6.x etc..) to the next? Looking through the DB 
upgrade scripts I see 2.4.3-2.5.0 upgrade script and a 2.5.3-2.6.0 upgrade 
script. Will any upgrade past a 2.x.3 (such as the 2.4.4-2.5.4 upgrade I have 
been trying to complete) run into headaches and issues? If we are looking to 
jump into a newer version (versus staying on a particular branch for an 
extended period of time) would we be wise to avoid going higher than a 2.x.3 
release (say, upgrade to 2.5.3 with the plans to upgrade to either 2.6.x or 
2.7.x at a later date and again going no higher than a 2.x.3 release)?

Currently with our Evergreen system we have scheduled 3 in house upgrades per 
year, with the initial plan being two point release upgrades and one major 
version upgrade per year (though, with the improvements to Acquisitions in 
2.5.x we are re-evaluating the only one major release upgrade plan). I am 
trying to plan out the upgrade path to eliminate as many issues as possible 
when upgrading.

Thanks,

Jesse McCarty
City of Burlington
IT Technical Assistant

From: 
open-ils-general-boun...@list.georgialibraries.orgmailto:open-ils-general-boun...@list.georgialibraries.org
 [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Thursday, May 29, 2014 9:08 AM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] Evergreen 2.6.1 and 2.5.5 Uploaded

Hello all,

Maintenance releases 2.6.1 and 2.5.5 are now available for preview testing:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.6.0-2.6.1

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.5.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.5.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.5.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.5.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.4-2.5.5

As always, feedback is appreciated.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6.1 and 2.5.5 Uploaded

[Dan Wells]

Hello all,

Maintenance releases 2.6.1 and 2.5.5 are now available for preview testing:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.6.0-2.6.1

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.5.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.5.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.5_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.5.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.5.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.4-2.5.5

As always, feedback is appreciated.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

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

[Dan Wells]

Hello Bill,

Thanks for the update.  I have some thoughts about both of your questions, but 
will focus on the link issue for now.

I’m not quite sure how to answer because I feel like we’re not asking the right 
question.  Rather than ask how links should behave, we might instead ask, what 
should be a link?  And also perhaps the inverse; in our interface, what should 
a link be?

As an experiment, I tried to look very critically at a familiar and popular 
interface: Gmail.  In the parts I would consider to be the everyday interface, 
you’d be hard-pressed to identify anything as a link.  In fact, the only things 
I could find which actually are links are the main sidebar options (Inbox, 
Starred, etc.), and even those don’t present themselves as links.

On the other hand (and recognizing the current code is a work in progress), 
consider our use of links in the patron search.  We have links both for column 
sorting, and also a link on the row numbers.  Neither of these currently do 
anything useful when right-clicking and opening in a new tab.  The row number 
links could, I imagine, but the column header links make little sense in that 
context.

The simplest argument, then, is that those shouldn’t be links, but that gets to 
the heart of what I am trying to say.  We are taking something which is 
fundamentally a website concept (a link between pages) and applying it to an 
application, and we need to very careful that we don’t misapply a web-centric 
mindset to any areas where that thinking isn’t appropriate.

Back to Gmail, in my experience, every link *within* an email opens in a new 
tab.  This prevents you from losing your Gmail context.  I think this is a very 
sensible behavior, and would even say it is the correct behavior for external 
links.  In my opinion, we should do the same, at least by default.

My sense, though, is that you were not really asking about external links which 
might exist in our content, but rather “internal” links (which I will define as 
a link to a new context in the staff client).  These are trickier.  To help our 
thinking, I wish to posit that on any given screen, we have both a context and 
a state.  The URL always captures the context, and sometimes some aspects of 
the state, but we cannot expect it to always capture every aspect of the 
current state.  Because of this fact, every time you switch contexts, you risk 
losing some state.  Therefore, we should be very careful to offer any interface 
element, link or otherwise, which switches context without a clear indication 
to the user of that intention.

To help illustrate the idea, I don’t feel the linked barcode in the “Items Out” 
table passes this test.  It isn’t clear that that link is going to change my 
current context.  It might not matter much in the patron context, since there 
isn’t much state to lose, but that won’t always be the case in every context.  
Also, why link on barcode?  What is the analog in, say, a list of serial items 
attached to a unit?

Instead of thinking of things as “links” and then trying to make one rule for a 
bunch of disparate things, I’d propose that we should have distinctive 
interface elements for which we can then define usage appropriate behaviors.  
Doing so would create a tremendous opportunity for improving the overall 
usability of the staff client as a whole.

I could say more, but I’ve said a lot already.  I’d love to hear reactions to 
what I’ve said so far (which I know is very uneven given the time and space 
limitations).  Am I way off-base?  Or is this the beginning of something we can 
work with?

Thanks,
Dan

P.S.  Bill, I think you are doing an outstanding job, and we couldn’t even have 
this conversation without all the work you have done to pave the way.  Please 
don’t take anything above as being critical of the hundreds of decisions you’ve 
had to make to get to where we are today.  Again, thank you!


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Bill 
Erickson
Sent: Monday, May 19, 2014 5:01 PM
To: Evergreen Discussion Group
Subject: [OPEN-ILS-GENERAL] staff client dev 2014-05-19 / feedback requests

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.commailto:ber...@esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts

Re: [OPEN-ILS-GENERAL] Report Generation

[Dan Wells]

One thing I'm not sure you can do in the reporter is group filters.  For 
example, I don't think you could pull 650a and 911b.  Instead, you effectively 
end up with the cross product of 650ab and 911ab.  Sometimes this limitation 
matters, sometimes it doesn't.

Also, if I'm mistaken, I'd love to know about it.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
Chauncey Montgomery
Sent: Tuesday, May 06, 2014 9:04 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Report Generation

  Jayaraj,
On your filters for tags and subfields, change the operator to in list. When 
you build your report, you'll have empty text boxes to enter the information 
you want to filter on.  You can enter more than one element into that filter. 
For example, with the tag, I can enter 600 in the box and click add, then 650 
and click add again, and now the report should filter on both.  See the 
attached screenshot for the example.  I hope that makes sense. Good luck and 
keep us posted on the outcome.
CM
--
Chauncey G. Montgomery, MLIS
Director/Fiscal Officer | Community Library
44 Burrer Drive | Sunbury, OH 43074
740-965-3901 | http://community.lib.oh.us


On 05/06/2014 12:31 AM, Jayaraj JR wrote:
 Hello,

 The recent developments discussed about Report Generation is very 
 interesting and useful. Special Thanks and Congrats to Chauncey 
 Montgomery !.

 We have a requirement to generate a report which can display the 
 values contained in the sub fields and tags.ie http://tags.ie

 Instead of displaying 650 a, we require the value entered in the field
 650 a.

 and 911 a b c. What modification need to be done below for such a report.

 Filters:
 Item :: Shelving Location - Location ID Item :: Call Number/Volume - 
 Owning Library Item :: Call Number/Volume - Is Deleted Item - Call 
 Number/Volume - Bibliographic Record :: Flattened MARC Fields - Tag 
 Item - Call Number/Volume - Bibliographic Record :: Flattened MARC 
 Fields - Subfield

 Display:
 Item - Call Number/Volume - Bibliographic Record :: Simple Record 
 Extracts - Title Proper (normalized) Item - Call Number/Volume - 
 Bibliographic Record :: Flattened MARC Fields - Tag Item - Call 
 Number/Volume - Bibliographic Record :: Flattened MARC Fields - 
 Subfield


 --
 Jayaraj J R
 Central Library
 IISER Thiruvananthapuram
 goog_1668144428
 http://www.iisertvm.ac.in

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] browser client update for 2014-04-23

[Dan Wells]

So why bother with a web based client?  I only had to write a very small
HTML5 app to realize it is a nightmarish moving target of pain.  Raise your 
hand if you would willingly use
HTML/CSS/DOM/JS for anything if it wasn't the lowest common demoninator that 
everything reads in an almost but
not quite incompatible way.  But it looks like most of those odd platforms 
just got dropped from consideration as hosts
for the new staff client, leaving only those that support the JRE.  Basically, 
newish Windows, OS X and Linux or the
same as Xulrunner and the current client.

Two points.  First, the Java shim (aka hatch) will ideally not be required 
for staff client use, but only for certain special features (like printing) 
which are not well supported natively by the browser environment.  Second, 
since we are already communicating via a network protocol, there have been 
discussions of allowing the Java shim to run on a different machine on your 
local network to allow for hybrid use (e.g. taking inventory on a tablet but 
then printing from that tablet to a machine at the circ desk).

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

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

[Dan Wells]

Hello Bill,

Thanks for the update.

I know others feel differently, but I don’t think we should rule out using 
iframes for catalog integration.  Iframes are actually pretty close in many 
respects to the way the catalog “integrates” into the current (XUL) staff 
client.  The usual problems with iframes are bookmarking (not really a concern 
the way we would use it), SEO (not a concern here at all), and cross-site 
scripting issues (we should have the same origin, which solves the biggest 
headaches).  If we want to keep things close to the current design, especially 
for phase one, iframes could be our shortest path there.

That said, I believe we could rework some bits of the TPAC (and it might not 
take much at all) to essentially use the same templates to dynamically fetch a 
frameless TPAC “core” for displaying inline in the staff client.

I do also like the idea of having (more or less) a grid-based OPAC (call it the 
gridPAC, of course) for use within staff client interfaces.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Bill 
Erickson
Sent: Thursday, May 01, 2014 10:40 AM
To: Evergreen Discussion Group; Evergreen Development Discussion List
Subject: [OPEN-ILS-GENERAL] browser client update 2014-05-01 / feedback 
requested on catalog integration

Hi All,

Here's another mixed bag of updates:

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

Feedback on catalog integration appreciated.

Thanks!

-b

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

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

[Dan Wells]

Struggling with some connectivity issues and lost part of my message.  This:

That said, I believe we could rework some bits of the TPAC (and it might not 
take much at all) to essentially use
the same templates to dynamically fetch a frameless TPAC “core” for displaying 
inline in the staff client.

Should end with:

Of course, remapping the action elements (buttons, forms, links) within the 
included TPAC core would be challenging.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Non-unique Dewey call numbers with spaces rather than periods

[Dan Wells]

Hello Linda,

I don't fully understand how you built your holdings, but it looks like you 
found something that worked for you.

Your update is failing on a record which already has both versions of the call 
number (correct with '.' and incorrect with 'space').  See here:

http://lib.etspraha.cz/eg/opac/record/4465?query=evangelical;qtype=keyword

If you manually merge those copies onto either call number, there is a chance 
your listed SQL query can succeed.  If not, you will need to determine how many 
records you have which already have a correct call number listed:

SELECT record,label FROM asset.call_number WHERE label LIKE '%.%';

That doesn't tell the whole story (i.e whether you have *both* types of call 
numbers on that record), but it's a quick way to see what you are up against.  
If it's just a few, I'd merge them manually.  Otherwise, I'd next do a JOIN to 
see how many actually have both types of call number.  If it is still a lot, 
working up a little script or even a more complex query to do the merging would 
be your best bet.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Linda 
Jansova
Sent: Monday, April 28, 2014 1:56 AM
To: Evergreen Discussion Group
Subject: [OPEN-ILS-GENERAL] Non-unique Dewey call numbers with spaces rather 
than periods

Hi all,

We have imported bibliographic and holdings data of the Evangelical Theological 
Seminary library to Evergreen 2.5.3!

Yet, we have encountered the following problem (maybe a bit related to a recent 
discussion on Dewey normalization: 
http://comments.gmane.org/gmane.education.libraries.open-ils.general/9661):

The library uses Dewey decimals as call numbers but these call numbers are not 
unique (no cutters are applied). In the OPAC, these data can be found as 
correctly imported in subfield a of the the 082 field (which means the data 
in MARCXML have been well preserved). But during the import, they were 
normalized in metabib.full_rec and call numbers are created from these data. 
There is no problem with padding zeroes as these have not been added but 
periods within the Dewey number have been overrided by spaces, e.g., 
http://lib.etspraha.cz/eg/opac/results?query=evangelical;qtype=keyword.

Therefore we have - unsuccessfully - tried to add the periods back but then the 
call numbers are expected to be unique which is not our case. 
So an error has occured:

evergreen=# UPDATE asset.call_number SET label = replace(label, ' ', '.');
ERROR:  duplicate key value violates unique constraint 
asset_call_number_label_once_per_lib
DETAIL:  Key (record, owning_lib, label, prefix, suffix)=(4465, 4, 274.3708, 
-1, -1) already exists.

Is there anything we can do about it (get the periods back to call numbers and 
have the call numbers that are not unique)?

Any ideas are very welcome :-)!

Linda and Vaclav Jansovi

Re: [OPEN-ILS-GENERAL] dewey call number normalization

[Dan Wells]

Hello Paul,

You've pretty much nailed your problem as being the extra decimals before your 
Cutters.  While that's normal for an LC call number, I've looked around and 
found nothing to make me believe that's common or accepted practice for DDC.

That said, as far as I can tell, the standard format for Dewey is:

[Dewey Decimal Number] [Whatever else you want to make it unique]

In my experience, the second part is *usually* the first few letters of the 
author's last name, or a cutter-ized version of the same.  Can anyone point to 
an authoritative source on how to build the non-DDC part of the call number?  
It would be a great help if we could at least reference something and say this 
is what our normalizer supports.

Naturally, if we can cook up a normalizer that works 100% with our agreed upon 
form (whatever that might be), yet also make it flexible enough to accommodate 
variances, we absolutely should do that.  I also think the code you included 
here is on the right track for being more flexible.  Still, our first step must 
be to establish a canonical support format before we consider any code to 
handle exceptions.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Paul 
Hoffman
Sent: Friday, April 25, 2014 4:45 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] dewey call number normalization

On Thu, Apr 24, 2014 at 05:15:35PM -0400, Ben Shum wrote:
 This will be a slightly more technical answer that may require some 
 direct database access to ascertain more details.
 
 You mention that the call numbers are identified as DDC.  So that's 
 label_class of 2, I believe.  We are using Dewey (DDC) for all of our 
 materials by default as well in our consortium.
 
 I'd be curious to know what the label_sortkey values were for those 
 call numbers you mention.  That field is what actually drives the 
 sorting values for a given set.

Here's what our DB shows (Adam and I work together):

SELECT   label_class, label, label_sortkey
FROM asset.call_number
WHERElabel_sortkey like '720%'
ORDER BY label_sortkey;

 label_class |  label  | label_sortkey 
-+-+---
   1 | 720 H47 1979| 720 H47 1979
   2 | 720 a   | 720_000_A
   2 | 720 .H47| 720_000__H47
   2 | 720.1 H74 1979  | 720_100_H74_1979
   2 | 720.1 .H47 1980 | 720_100__H47_1980
   2 | 720.1 .H74 1979 | 720_100__H74_1979
   2 | 720 H74 1979| 720_H74_1979000
   2 | 720 .H47 1980   | 720__H47_198
   2 | 720 .H47 1980   | 720__H47_198
   2 | 720 .H74 1979   | 720__H74_1979000
(10 rows)

So the problem appears to be caused by the periods that sometimes occur before 
the Cutter number.  I don't know if that's kosher or not, but I can see that it 
occurs plenty in our (Voyager) catalog.

Looking at the function asset.label_normalizer_dewey it seems to me that it can 
be done much more simply and efficiently if you leverage the fact that space 
(ASCII 32) and tilde (ASCII 126) come before and after (respectively) anything 
else meaningful that might be found in a call number.  Except periods, which 
complicate things.  Anyhow, here's a first stab at it:

use strict;
use warnings;
sub ddcnorm {
local $_ = uc shift;
# Strip leading or trailing space and any slashes or apostrophes
s/^\s+|\s+$|[\/']//g;
# Insert a space at digit/non-digit boundaries
s/(?=[0-9])(?=[^0-9])|(?=[^0-9])(?=[0-9])/ /g;
# Replace some punctuation with a space
tr/-/ /;  # XXX What else?
# Strip extra junk -- XXX make this work on non-ASCII call numbers
tr/A-Za-z0-9. //cd;
s/ \. /~/g;
s/ \.|\. / /g;
tr/ //s;
return $_;
}

When I run our Deweys in the 720s through this, I get what seems to be the 
right order:

   2 | 720 a   | 720 A
   2 | 720 .H47| 720 H 47
   2 | 720 .H47 1980   | 720 H 47 1980
   2 | 720 .H47 1980   | 720 H 47 1980
   2 | 720 .H74 1979   | 720 H 74 1979
   2 | 720 H74 1979| 720 H 74 1979
   2 | 720.1 .H47 1980 | 720~1 H 47 1980
   2 | 720.1 .H74 1979 | 720~1 H 74 1979
   2 | 720.1 H74 1979  | 720~1 H 74 1979

If there's any interest, I'll run our entire set of Deweys through it and see 
if I can make sense of the results.  Hmm... should prefixes like j or C
(juvenile or Canadian) be ignored?

Paul.

 On Thu, Apr 24, 2014 at 3:32 PM, Adam Shire a...@flo.org wrote:
 
  Hi Everyone,
 
  We are testing in evergreen 2.5.2
 
  I'm noticing what I think looks like incorrect behavior when using 
  the call number browse feature.
 

Re: [OPEN-ILS-GENERAL] dewey call number normalization

[Dan Wells]

Okay, looking more carefully at the sortkey Ben pointed out, you really do have 
two different problems affecting your sort.  Sorry for focusing on the smaller 
one!

Everything I advocated earlier still stands, but in the meantime, we do need to 
fix the misplaced padding in the 'no decimal but we have a year' case.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Friday, April 25, 2014 10:15 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] dewey call number normalization

Hello Paul,

You've pretty much nailed your problem as being the extra decimals before your 
Cutters.  While that's normal for an LC call number, I've looked around and 
found nothing to make me believe that's common or accepted practice for DDC.

That said, as far as I can tell, the standard format for Dewey is:

[Dewey Decimal Number] [Whatever else you want to make it unique]

In my experience, the second part is *usually* the first few letters of the 
author's last name, or a cutter-ized version of the same.  Can anyone point to 
an authoritative source on how to build the non-DDC part of the call number?  
It would be a great help if we could at least reference something and say this 
is what our normalizer supports.

Naturally, if we can cook up a normalizer that works 100% with our agreed upon 
form (whatever that might be), yet also make it flexible enough to accommodate 
variances, we absolutely should do that.  I also think the code you included 
here is on the right track for being more flexible.  Still, our first step must 
be to establish a canonical support format before we consider any code to 
handle exceptions.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Paul 
Hoffman
Sent: Friday, April 25, 2014 4:45 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] dewey call number normalization

On Thu, Apr 24, 2014 at 05:15:35PM -0400, Ben Shum wrote:
 This will be a slightly more technical answer that may require some 
 direct database access to ascertain more details.
 
 You mention that the call numbers are identified as DDC.  So that's 
 label_class of 2, I believe.  We are using Dewey (DDC) for all of our 
 materials by default as well in our consortium.
 
 I'd be curious to know what the label_sortkey values were for those 
 call numbers you mention.  That field is what actually drives the 
 sorting values for a given set.

Here's what our DB shows (Adam and I work together):

SELECT   label_class, label, label_sortkey
FROM asset.call_number
WHERElabel_sortkey like '720%'
ORDER BY label_sortkey;

 label_class |  label  | label_sortkey 
-+-+---
   1 | 720 H47 1979| 720 H47 1979
   2 | 720 a   | 720_000_A
   2 | 720 .H47| 720_000__H47
   2 | 720.1 H74 1979  | 720_100_H74_1979
   2 | 720.1 .H47 1980 | 720_100__H47_1980
   2 | 720.1 .H74 1979 | 720_100__H74_1979
   2 | 720 H74 1979| 720_H74_1979000
   2 | 720 .H47 1980   | 720__H47_198
   2 | 720 .H47 1980   | 720__H47_198
   2 | 720 .H74 1979   | 720__H74_1979000
(10 rows)

So the problem appears to be caused by the periods that sometimes occur before 
the Cutter number.  I don't know if that's kosher or not, but I can see that it 
occurs plenty in our (Voyager) catalog.

Looking at the function asset.label_normalizer_dewey it seems to me that it can 
be done much more simply and efficiently if you leverage the fact that space 
(ASCII 32) and tilde (ASCII 126) come before and after (respectively) anything 
else meaningful that might be found in a call number.  Except periods, which 
complicate things.  Anyhow, here's a first stab at it:

use strict;
use warnings;
sub ddcnorm {
local $_ = uc shift;
# Strip leading or trailing space and any slashes or apostrophes
s/^\s+|\s+$|[\/']//g;
# Insert a space at digit/non-digit boundaries
s/(?=[0-9])(?=[^0-9])|(?=[^0-9])(?=[0-9])/ /g;
# Replace some punctuation with a space
tr/-/ /;  # XXX What else?
# Strip extra junk -- XXX make this work on non-ASCII call numbers
tr/A-Za-z0-9. //cd;
s/ \. /~/g;
s/ \.|\. / /g;
tr/ //s;
return $_;
}

When I run our Deweys in the 720s through this, I get what seems to be the 
right order:

   2 | 720 a   | 720 A
   2 | 720 .H47| 720 H 47
   2 | 720 .H47 1980   | 720 H 47

[OPEN-ILS-GENERAL] 2.6 Wrap Up and Awards [RM2.6]

[Dan Wells]

Hello all,

With 2.6.0 cut 10 days ago, it is high time for me to give one final update 
before I pass the torch.  I haven't given a formal email progress summary since 
the beta (though a verbal update was given at the conference), so we'll be 
looking back at both the RC and the 2.6 final contribution periods.

With 23 tickets committed for the RC and 15 for 2.6.0, the grand total for the 
2.6 cycle comes to exactly 100 improvements committed.  You can see the latest 
two rounds of fixes here:

https://launchpad.net/evergreen/2.6/2.6.0-rc1

and here:

https://launchpad.net/evergreen/2.6/2.6.0

While Launchpad gives us a nuts and bolts view of things, with a final release 
comes a better way to look more broadly at the changes: release notes!  You can 
read the release notes for 2.6 here:

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

Of course, the beat goes on, and a few important fixes have already been 
committed for what will be 2.6.1.  I encourage anyone looking at 2.6.0 to read 
up on these recent commits and decide whether they might affect your local use:

https://bugs.launchpad.net/evergreen/+milestone/2.6.1

My expectation is still that 2.6.1 will be cut relatively early (within the 
next week or two), and that normal monthly updates will begin with 2.6.2.


Overall, I am proud of all that we have been able to accomplish these past two 
cycles.  With that in mind, I'd like to take another moment to recognize those 
who put forth the necessary effort to make 2.6 a reality.  Of course this means 
medals, and for this round, you will notice that the medals are now rimmed in 
maroon.  This is meant not only to distinguish these final medals from the 
rest, but also as a modest gesture to my employer Calvin College, without whom 
I would not be involved with Evergreen, and without whose support I could not 
have managed these last two releases.

Here are the recipients of the final Evergreen Medals of Honour for the 2.6 
release (RC and 2.6.0 combined):

A. HANCOCK Medal of Fortitude (for reviewing and signing off on another 
community member's code)
  1. GOLD Recipients (granted for signing off on at least 6 branches)

http://www.calvin.edu/library/images/eg_medals/Hancock_Medal_2_6_Final_Gold.png
Ben Shum
Galen Charlton
Remington Steed
  2. SILVER Recipients (at least 2 signoffs)

http://www.calvin.edu/library/images/eg_medals/Hancock_Medal_2_6_Final_Silver.png
Bill Erickson
  3. BRONZE Recipients (at least 1 signoff)

http://www.calvin.edu/library/images/eg_medals/Hancock_Medal_2_6_Final_Bronze.png
Doug Kyle
Jason Stephenson
Jeff Godin
Kathy Lussier
Mike Rylander

B. BARTON Medal of Steadfastness (for contributing in general to the code 
review process)
  1. GOLD Recipients (granted for contributing to at least 7 bug reviews)

http://www.calvin.edu/library/images/eg_medals/Barton_Medal_2_6_Final_Gold.png
Ben Shum
Bill Erickson
Galen Charlton
Mike Rylander
  2. SILVER Recipients (at least 3 bugs)

http://www.calvin.edu/library/images/eg_medals/Barton_Medal_2_6_Final_Silver.png
Chris Sharp
Dan Scott
Grace Dunbar
Jason Etheridge
Jason Stephenson
Kathy Lussier
Lebbeous Fogle-Weekley
Remington Steed
  3. BRONZE Recipients (at least 1 bug)

http://www.calvin.edu/library/images/eg_medals/Barton_Medal_2_6_Final_Bronze.png
Christine Morgan
Doug Kyle
Elaine Hardy
Elliot Voris
Erica Rohlfs
Holly Brennan
Jeff Godin
Jennifer Pringle
Mark Cooper
Michael Peters
Michele Morgan
Pasi Kallinen
Rogan Hamby
Sarah Childs
Srey Seng
Steve Callender
Tim Spindler
Tina Ji
Tony Bandy
Warren Layton
Yamil Suarez

C. ARMSTRONG Medal of Courage (for installing and testing a release tarball, 
and reporting back)
  1. GOLD Recipients (granted for simply doing this!)

http://www.calvin.edu/library/images/eg_medals/Armstrong_Medal_2_6_Final_Gold.png
Remington Steed

As always, please contact me if I made any mistakes, as I want everyone to get 
the recognition they deserve!

Along those lines, and in addition to the recognition given above, I'd like to 
give one more medal under the banner of ask and you shall receive.  Mike 
Rylander single-handedly wrote code to fix a majority of the release blockers 
for 2.6, and mentioned in IRC the possibility of an extra medal as a source of 
motiviation.  Who am I to deny such a dream?  Here it is, with thanks!

D. HAAS Medal of Expeditiousness (for dedication to fixing release blockers)

http://www.calvin.edu/library/images/eg_medals/Haas_Medal_2_6_Final_Gold.png
Mike Rylander

I really can't say it enough, so thanks again to everyone who made Evergreen 

Re: [OPEN-ILS-GENERAL] separating tabs in staff client

[Dan Wells]

Hello Holly,

The browser-based client will be a normal website from the perspective of your 
browser, so you'll be able to do any sort of window/tab management supported by 
the browser.  So, yes, you'll be able to do what you're asking about.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Holly 
Brennan
Sent: Thursday, April 24, 2014 2:12 PM
To: Evergreen Discussion Group (open-ils-general@list.georgialibraries.org)
Subject: [OPEN-ILS-GENERAL] separating tabs in staff client

Yesterday I had the desire to view 2 or 3 tabbed pages in the staff client at 
one time. I tried to pull the tabs apart, as I often do in Chrome or Firefox, 
so they were in their own windows - thus viewable at the same time. But sadly 
they wouldn't budge.

Will the new browser staff client be able to function this way, with tabs 
acting more like individual web pages? Or will they be stuck within one 
window as they are now?

I appreciate being able to shuffle the order of tabs currently, but the added 
flexibility to create separate windows would be awesome.

Since I have no knowledge of the development requirements for this, I'm just 
throwing the idea out there. It may be extremely difficult, or impossible, or 
just scary. Thanks in advance for any feedback!

-Holly




Holly Brennan
Library Technology Specialist
Homer Public Library
907-235-3180 (main)
907-435-3154 (direct)
hbren...@cityofhomer-ak.govmailto:hbren...@cityofhomer-ak.gov

Re: [OPEN-ILS-GENERAL] Call for vote: Release Manager 2.7

[Dan Wells]

 Shall we accept Ben Shum's proposal to be Release Manager for Evergreen 2.7?

+1

Re: [OPEN-ILS-GENERAL] 2.6.0 Available for Testing [RM2.6]

[Dan Wells]

Hello again all,

The 'preview' tag has been dropped, so 2.6.0 is now fully released and linked 
from the main Evergreen downloads page.  I'll send a more thorough release 
summary as time allows (very likely within the week).

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Wednesday, April 16, 2014 12:57 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] 2.6.0 Available for Testing [RM2.6]

Hello all,

I am happy to announce that a build of 2.6.0 is now available in the preview 
area:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.0.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.0.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.3-2.6.0

You can also preview the release notes here:

http://evergreen-ils.org/downloads/previews/RELEASE_NOTES_2_6.html

As I noted in the RC email, while all testing and feedback is appreciated, I am 
particularly interested in anyone able to test the upgrade script, especially 
on a production-like DB.

Thanks,
Dan




Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.5.4 Uploaded

[Dan Wells]

Hello all,

Continuing the theme of new releases, 2.5.4 is now also available for preview 
testing:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.4.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.4.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.4_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.4_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.4_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.4_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.4.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.4.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.3-2.5.4

As always, feedback is appreciated!

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.6.0 Available for Testing [RM2.6]

[Dan Wells]

Hello all,

I am happy to announce that a build of 2.6.0 is now available in the preview 
area:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6.0_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.0.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6.0.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.3-2.6.0

You can also preview the release notes here:

http://evergreen-ils.org/downloads/previews/RELEASE_NOTES_2_6.html

As I noted in the RC email, while all testing and feedback is appreciated, I am 
particularly interested in anyone able to test the upgrade script, especially 
on a production-like DB.

Thanks,
Dan




Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] browser staff feedback request / integration

[Dan Wells]

I'm fine with the decision and consensus, but want to add one thing.  I've met 
a fair number of users who have a difficult time managing multiple windows in 
an ongoing way (call them the closers).  We obviously don't have any such 
folks responding to this thread, but I think we should be open to such feedback 
(should it come) and possibly reconsider this decision if necessary.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-dev-boun...@list.georgialibraries.org 
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Bill 
Erickson
Sent: Monday, April 07, 2014 1:20 PM
To: Evergreen Discussion Group
Cc: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] browser staff feedback request / 
integration


Agreed on fleshing out modules on a workflow-by-workflow basis as much as 
possible.  This is one area where user testing early in the process can really 
pay off.

So, I think it's safe to say we have a consensus on avoiding the XUL/mixed 
integration path entirely.  From a development perspective, this is certainly a 
relief.

-b

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

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] browser staff feedback request / integration

[Dan Wells]

Galen, I was deliberately vague in my earlier email, and hope you will 
understand if I continue to be :)

I think it is fine to proceed with a separation mindset and see how it turns 
out.

Thanks,
Dan

Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-Original Message-
From: open-ils-dev-boun...@list.georgialibraries.org 
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Galen 
Charlton
Sent: Monday, April 07, 2014 5:52 PM
To: Evergreen Development Discussion List
Cc: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] browser staff feedback request / 
integration


To clarify, are you talking about computer users in general, or folks you've 
met who are already using the Evergreen staff client but who you believe would 
not be able to adapt to switching contexts at all?

Regards,

Galen

[OPEN-ILS-GENERAL] 2.6 RC Available for Testing [RM2.6]

[Dan Wells]

Hello all,

I am happy to announce that a build of the 2.6 release candidate is now 
available in the preview area:

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-rc1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-rc1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-rc1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-rc1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-rc1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-rc1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-rc1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-rc1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.3-2.6-rc1

You can also preview the release notes build here:

http://evergreen-ils.org/downloads/previews/RELEASE_NOTES_2_6.html

While all testing and feedback is appreciated, I am particularly interested in 
anyone able to test the upgrade script, especially on a production-like DB.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Quick Update on 2.6 RC [RM2.6]

[Dan Wells]

Hello all,

The 2.6 release candidate has not yet been cut.  Two of the blockers are still 
in need of final review:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker

Actually, though, the bigger reason we are waiting is that there are reports of 
search issues on a production data set, and since an RC should be 
production-ready, I am trying to give as much time as possible to see if we can 
ferret out the source of these problems.

I am committed to moving forward with a release of some sort before the 
conference kicks off on Wednesday.  If we get a handle on this issue before 
then, I will likely go ahead with the RC, but if we cannot, I intend to package 
up the code as a 2.6-beta2 release instead.

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Hackfest 2014 Ideas Page [Cf. Browser client dev log update / feedback request on grids]

[Dan Wells]

Hello Bill,

Thanks for bringing this up!  I think this is absolutely the linchpin for 
getting the web staff client rolling.

Since this code is still so fresh, it seems ripe for hacking, so I've created a 
conference Hackfest page and added this there.

http://evergreen-ils.org/dokuwiki/doku.php?id=dev:hackfest:eg2014

If anyone else has ideas, please post them!

Thanks again,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-dev-boun...@list.georgialibraries.org 
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Bill 
Erickson
Sent: Thursday, March 13, 2014 3:09 PM
To: Evergreen Development Discussion List; Evergreen Discussion Group
Subject: [OPEN-ILS-DEV] Browser client dev log update / feedback request on 
grids

Hi,

I just posted a wordy update to the browser client dev log with a call for 
input on how we build our UI grids (tables, lists, etc.).  See the first 
section titled User Interface Grids / Tables.  This particular component will 
be used heavily, so I want to make sure we explore all options before we pick a 
path.

There are a few other miscellaneous updates in there, as well.

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

Thanks,

-b

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

[OPEN-ILS-GENERAL] 2.6 RC Goal Today [RM2.6]

[Dan Wells]

Hello all,

Just a quick reminder that if we want 2.6 to stay on target, today is the goal 
date for getting things reviewed and committed.  We are to the point that we 
certainly won't push forward until things are ready, so depending on how today 
goes, I'll try to better define what ready means in regards to the RC vs. 2.6 
final.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Push Time for 2.6 RC1 [RM2.6]

[Dan Wells]

Hello all,

Friday was the last day to assign bugs to RC1, and now it's time for what we 
hope will be the last big push for getting 2.6 polished up and out the door.  
The goal is to have things squared up by end-of-day on Wednesday, March 12, as 
that should give us plenty of time to get things packaged up before the big 
event next week.

The current blockers are, naturally, top priority.  You can see those here:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker

Every branch there (so far) has a pullrequest, so it comes down to testing.  
While the fixes for some of these are not particularly complex, they do tend to 
be fairly deep, so we want as much testing and feedback as we can get.  This 
applies especially to the Postgresql bugs, since we need to verify things still 
work across multiple known version differences.

I will take some time today to scan through the other targeted bugs and see if 
anything else seems like a blocker.  Please feel free to weigh in on this 
matter if there is a bug report you feel strongly about.  You can see the list 
of 2.6-RC bugs with pullrequests here:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=64164field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-importancestart=0

Thanks for your help!

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] A Song of Hope

[Dan Wells]

Hello all,

Anyone who knows me knows that I take this project and my duties to it very 
seriously.  I even (literally) lose sleep over it from time to time, and a few 
nights ago, my tossing and turning was not for naught, as the following lyric 
came to me, so I hope you can grant me a moment of levity.  Perhaps a 
sing-along could lift a few spirits around here :)

2.next (2-Point-Next)
by Dan Wells
(tune: Tomorrow from Annie)

This code will come out
2-point-next!
Bet your bottom dollar by 2-point-next
this will run.
Just thinkin' about
2-point-next,
Clears away my anger towards the RM
till there's none!

When I'm stuck with a branch,
not done,
and buggy,
I just load up my Vim,
and grin,
and say,
2-point-next! 2-point-next!
I love you, 2-point-next!
You're only six months away!

2-point-next! 2-point-next!
I love you, 2-point-next!
You're only six months away!


Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.6 RC Schedule [RM2.6]

[Dan Wells]

Hello all,

I am working on a separate wrap up email for the 2.6 beta which was cut last 
Tuesday, but since time is mercilessly marching on, I decided I should 
highlight the planned schedule for the 2.6 RC which is nearly upon us.  This 
Friday, March 7, is the last day for targeting medium and lower bugs for 
inclusion in the release candidate (high and critical bugs are always welcome). 
 You can see the current list here:

https://launchpad.net/evergreen/+milestone/2.6.0-rc1

The list is already pretty extensive, so I am hoping we won't find too much to 
add.  That said, the current list of blockers for the RC is rather short:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker

The list currently stands at four items, three of which are problems related to 
newer versions of PostgreSQL.  Those three bugs are going to require a fair 
amount of testing and eyes, so please contribute in any way you can!  Also, 
please let me know if there is another bug you feel should be added to the list 
of blockers.

I am setting a goal of Wednesday, March 12, as the last day to commit branches 
for inclusion in the RC.  I know this is a fairly aggressive timeline, but it 
is important that we accomplish as much as we can before turn our collective 
attention toward the conference the following week.

As always, please let me know if you have any questions or concerns about the 
release process.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6 Beta Preview Uploaded [RM2.6]

[Dan Wells]

Hello all,

A more thorough beta summary email is pending, but this preview build is now 
available for download and testing.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-beta1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-beta1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-beta1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-beta1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-beta1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-beta1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-beta1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-beta1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.3-2.6-beta1

Please note the upgrades assume you are coming from *2.5.3*, which was uploaded 
yesterday, and will soon be linked from the downloads page.  And remember, 
here's your chance to go for the gold (so to speak)!

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.5.3 Release Candidate Uploaded

[Dan Wells]

Hello all,

The release candidate for Evergreen 2.5.3 is now available for download and 
testing.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.3.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.3.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.3_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.3_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.3_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.3_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.3.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.3.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.2-2.5.3

Feedback is appreciated!

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Beta Review Period Extended [RM2.6]

[Dan Wells]

Hello all,

We've collectively made a great deal of progress on the beta-targeted bugs, and 
I've been really happy to see all the extra review effort.  It looks like a 
couple of the feature branches could use a few more minutes of baking, so I am 
going to delay cutting the beta until Friday.  This effectively means we now 
have until end-of-day on Thursday to work things out in a more orderly fashion.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Beta Review, Beta Blockers [RM2.6]

[Dan Wells]

Hello all,

As most should be aware, the beta review period is scheduled to run through end 
of day tomorrow.  I've gone through the list of targeted bugs and marked 6 (so 
far) which I consider to be blockers for getting the beta released:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-beta-blocker

These are not necessarily the most important bugs, but since beta represents 
the last chance to get features in, I think it is worth blocking for features 
which we don't want to wait another 6 months for.  If there are other features 
which you think deserve beta-blocker status, please let me know!

(Note: we agreed at the dev meeting to make sure the 2.6 release includes 
proper support for PG9.3, but I consider those bugs to be release-blockers 
rather than beta-blockers, just to be clear.)

Of course, any other bug fixes which made the targeting deadline are encouraged 
for review and inclusion in the beta.  You can see those here:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=63762field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-importancestart=0

If we can together manage reviewing another 10+ from this list before beta, I 
think we could feel pretty good about where we stand.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] 2.6 Beta Schedule and Bug List [RM2.6]

[Dan Wells]

Hello all,

Just a quick and final reminder that the last call for targeting branches for 
inclusion in 2.6.0-beta1 is *today at noon EST*.  This is most important for 
feature branches, since there will be no feature inclusion beyond the beta.  
Even if your feature pullrequest isn't quite ready, if you have a high degree 
of confidence that it will be ready with enough time for review before next 
Tuesday, please do target it.

Thanks!
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Wednesday, February 05, 2014 5:42 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] 2.6 Beta Schedule and Bug List [RM2.6]

Hello all,

Based on the feedback I have received, the cutoff for targeting bugs at 
2.6.0-beta1 will be *Tuesday, February 11 at noon EST*.  At that time, I will 
create both an RC milestone (for new bugs) and an Evergreen-next milestone (for 
new features not getting into 2.6).  Please do not assign any bugs to the beta1 
milestone after noon on Tuesday.

After the cutoff on the 11th, the community will have until *end-of-day on 
Tuesday, February 18* to review and commit the beta-targeted bugs.  The 
following day I will begin (and hopefully finish) the process of cutting a 
2.6.0 beta release.

On a related topic, earlier today I went through all the unfinished bugs for 
2.6.0-alpha1.  Most were moved to 2.6.0-beta1, but a few were not.  If a bug 
had no pullrequest, and no signs of life, I likely set it back to being 
untargeted.  Please look over the list of bugs before the February 11 cutoff 
and make sure bugs you want included in 2.6 are targeted.  The current list can 
be seen here:

https://bugs.launchpad.net/evergreen/+milestone/2.6.0-beta1

As always, questions, comments, and concerns about the release process are 
welcome.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6 Alpha - Summary and Awards [RM2.6]

[Dan Wells]

Hello all,

The 2.6 alpha is several weeks old, and we are already in the thick of the beta 
process.  But, as a friend of mine once said, better late than sorry, so here 
is a quick summary of what we accomplished during the 2.6 alpha period, and 
also some much deserved recognition for those who made it happen.

First, here is a list of everything which made it into the alpha:

https://launchpad.net/evergreen/+milestone/2.6.0-alpha1

It amounted to 27 branches committed, and considering only 49 total branches 
were ready for review, cutting the number by more than half is certainly a 
respectable result.

At this point, I usually make some sort of blanket statement like thanks to 
everyone who helped, but it was suggested at the Hack-a-way that some might be 
inspired by a more direct form of encouragement.  So, without further ado, I am 
proud to present the first ever round of Evergreen Medals of Honour.

First up, we have the HANCOCK Medal of Fortitude (for reviewing and signing off 
on another community member's code).  This award for the 2.6 alpha goes to (in 
alphabetical order by first name):

Ben Shum
Bill Erickson
Dan Scott
Jeff Godin
Lebbeous Fogle-Weekley
Mike Rylander
Remington Steed
Srey Seng

And, these awards aren't just empty words, they also include a graphical 
representation of your achievement, suitable for general boasting on social 
media, desktop wallpaper, etc.  
http://www.calvin.edu/library/images/Hancock_Medal_2_6_Alpha.png

Second, we have the BARTON Medal of Steadfastness (for contributing in general 
to the code review process).  This medal is awarded to:

Ben Shum
Bill Erickson
Dan Scott
Elizabeth Thomsen
Elliot Voris
Erica Rohlfs
Galen Charlton
Jason Boyer
Jason Etheridge
Jason Stephenson
Jeff Godin
Joe Atzberger
Kathy Lussier
Kyle Tomita
Lebbeous Fogle-Weekley
Michael Peters
Mieke Stroo
Mike Rylander
Pasi Kallinen
Sarah Childs
Srey Seng
Steve Callender
Tim Spindler
Yamil Suarez

Some of you might not even recall contributing, since the bugs were rather old, 
but I am happy that at last your contribution is being recognized.  I am sorry 
it took so long, and here is your award!  
http://www.calvin.edu/library/images/Barton_Medal_2_6_Alpha.png

And finally, we honour those who went the extra mile and earned the ARMSTRONG 
Medal of Courage (for installing and testing a release tarball, and reporting 
back):

NOBODY

Yeah, maybe next time this can be yours.  
http://www.calvin.edu/library/images/Armstrong_Medal_2_6_Alpha.png

So, thanks again to all of our award recipients.  I am very sorry if I 
legitimately left anybody out, but if you are only feeling left out, there is 
still ample time to contribute and earn the beta medals, though all should be 
aware that selection criteria is subject to change without notice!

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.6 Beta Schedule and Bug List [RM2.6]

[Dan Wells]

Hello all,

Based on the feedback I have received, the cutoff for targeting bugs at 
2.6.0-beta1 will be *Tuesday, February 11 at noon EST*.  At that time, I will 
create both an RC milestone (for new bugs) and an Evergreen-next milestone (for 
new features not getting into 2.6).  Please do not assign any bugs to the beta1 
milestone after noon on Tuesday.

After the cutoff on the 11th, the community will have until *end-of-day on 
Tuesday, February 18* to review and commit the beta-targeted bugs.  The 
following day I will begin (and hopefully finish) the process of cutting a 
2.6.0 beta release.

On a related topic, earlier today I went through all the unfinished bugs for 
2.6.0-alpha1.  Most were moved to 2.6.0-beta1, but a few were not.  If a bug 
had no pullrequest, and no signs of life, I likely set it back to being 
untargeted.  Please look over the list of bugs before the February 11 cutoff 
and make sure bugs you want included in 2.6 are targeted.  The current list can 
be seen here:

https://bugs.launchpad.net/evergreen/+milestone/2.6.0-beta1

As always, questions, comments, and concerns about the release process are 
welcome.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Quick Note: 2.6 Beta Deadline Extended [RM2.6]

[Dan Wells]

Hello all,

The initially proposed 2.6 timeline called for a beta bug assignment deadline 
of tomorrow, 2/4.  That deadline is being extended.  Right now it is 
tentatively set for Friday, but may be pushed back a few days more pending 
additional developer feedback.

I hope and expect to have things firmed up no later than this Wednesday.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.6-alpha1 Available for Testing [RM2.6]

[Dan Wells]

Hello all,

The first packaged release of Evergreen 2.6, alpha1, is now available for 
download and testing.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-alpha1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-alpha1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-alpha1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-alpha1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-alpha1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.6-alpha1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-alpha1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.6-alpha1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.2-2.6-alpha1

We are still early in the release process, so these downloads are offered 
primarily as a convenience to would-be testers, and also as an opportunity to 
continue to refine the release process itself.

I hope to send out a more complete update on the progress made in alpha1 within 
the next day or two.

Thanks,
Dan




Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Evergreen 2.5.2 Release Candidate Uploaded

[Dan Wells]

Hello all,

Just a quick note to say that Evergreen 2.5.2 is now released, and has been 
moved from the preview location into the normal download space.  Thanks again 
to those who tested the release candidate.

Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan 
Wells
Sent: Thursday, January 16, 2014 4:39 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] Evergreen 2.5.2 Release Candidate Uploaded

Hello all,

The release candidate for Evergreen 2.5.2 is now available for download and 
testing.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.2.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.2.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.1-2.5.2

Feedback is appreciated!

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Please Contribute to 2.6.0-alpha Review [RM2.6]

[Dan Wells]

Hello all,

The review period for 2.6.0-alpha1 is underway.  After some bug shuffling over 
the last few days, it looks like we now have 38 bugs which are ready for 
inclusion in the alpha (not counting 'Incompletes').  As sent in the previous 
email, you can see the list here:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=62053field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

The original timeline from a few weeks ago said alpha cut - Jan. 21.  I am 
going to change (or clarify) that slightly and say that you have until the end 
of the day on Jan. 21 to push things into master for inclusion in the alpha.  
The alpha will be rolled into a release package on Wednesday, Jan. 22.

I know we still have quite a few bugs incoming, so I'd really like to see us at 
*least* get this number into the 20s.  As added incentive, those who 
participate will get recognition in a future email, and who knows, maybe 
something more at a later date... :)  Remember, participation can come in many 
forms, e.g.:
-   Reviewing and leaving comment
-   Reviewing and creating a sign-off branch
-   Reviewing and pushing to master
-   Reviewing and marking Incomplete with comment
In short, everyone can help!

I know we only have a couple days allotted here.  If anyone is sure they could 
do more with an extra day or two, please don't hesitate to ask.  Without 
feedback, it is impossible to know how these plans fit with our many schedules. 
 As always, questions and comment are welcome!

Sincerely,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Reminder: Deadline is TODAY for 2.6 alpha targeting [RM2.6]

[Dan Wells]

Hello all,

Just a quick reminder that today is the last day to target bugs for inclusion 
in 2.6 alpha.  As in past releases, new features will still be permitted until 
beta, which is scheduled for early February.  That said, the sooner something 
is ready and targeted, the more likely it will be reviewed and included in 2.6, 
so please don't miss this opportunity to get some attention for your branch.

Here is the current list of bug reports in the 2.6.0-alpha1 milestone which 
also have pullrequest tags:
https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=62053field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

This is the list which I am asking reviewers focus on over the next few days, 
but as you can see, the list is relatively small.  In contrast, here is a list 
of *all* un-committed pullrequests:
https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-milestonememo=75start=0direction=backwards

I couldn't figure out a way to exclude the items already targeted at 2.6 (the 
first list), but I was able to sort them to the bottom.  As you can see, we (at 
the time of this writing) have 70+ pullrequests which are either targeted only 
at old branches or not targeted at all.  Many of these are stale and should 
probably be invalidated, but many others should rightly be targeted at 2.6.  If 
you are able, please take some time today to review the second list, and apply 
the 2.6.0-alpha1 milestone (or invalidate) as you deem appropriate.

As always, please reply to this thread if you have any questions or concerns.

Thank you,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Reminder: Deadline is TODAY for 2.6 alpha targeting [RM2.6]

[Dan Wells]

Hello Liam,

It is never too early to create a Launchpad bug.  That said, we generally do 
not add a milestone target until a pullrequest branch is ready, as this limits 
distraction and prevents a lot of milestone churn.  Occasionally exceptions are 
made in cases where there is high confidence that a branch will be ready in 
time for the milestone, so the milestone is added early to indicate intention.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Liam 
Whalen
Sent: Thursday, January 16, 2014 1:08 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Reminder: Deadline is TODAY for 2.6 alpha 
targeting [RM2.6]

Hi Dan,

I have a few improvements to the staff client that I am still testing 
internally, but I plan to push them into 2.6 at some point.  Would it be best 
to create launchpad bugs for them now?

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coopmailto:liam.wha...@bc.libraries.coop



On Jan 16, 2014, at 9:31 AM, Dan Wells 
d...@calvin.edumailto:d...@calvin.edu wrote:


Hello all,

Just a quick reminder that today is the last day to target bugs for inclusion 
in 2.6 alpha.  As in past releases, new features will still be permitted until 
beta, which is scheduled for early February.  That said, the sooner something 
is ready and targeted, the more likely it will be reviewed and included in 2.6, 
so please don't miss this opportunity to get some attention for your branch.

Here is the current list of bug reports in the 2.6.0-alpha1 milestone which 
also have pullrequest tags:
https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=62053field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

This is the list which I am asking reviewers focus on over the next few days, 
but as you can see, the list is relatively small.  In contrast, here is a list 
of *all* un-committed pullrequests:
https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-milestonememo=75start=0direction=backwards

I couldn't figure out a way to exclude the items already targeted at 2.6 (the 
first list), but I was able to sort them to the bottom.  As you can see, we (at 
the time of this writing) have 70+ pullrequests which are either targeted only 
at old branches or not targeted at all.  Many of these are stale and should 
probably be invalidated, but many others should rightly be targeted at 2.6.  If 
you are able, please take some time today to review the second list, and apply 
the 2.6.0-alpha1 milestone (or invalidate) as you deem appropriate.

As always, please reply to this thread if you have any questions or concerns.

Thank you,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.5.2 Release Candidate Uploaded

[Dan Wells]

Hello all,

The release candidate for Evergreen 2.5.2 is now available for download and 
testing.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.2_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.2.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.2.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.1-2.5.2

Feedback is appreciated!

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Timetable for Evergreen 2.6 [RM2.6]

[Dan Wells]

Hello all,

First, thank you to everyone for the show of support in keeping me on for 2.6.  
A few people did express concern that I might be over-burdened as I continue as 
the maintainer for 2.5.  I think that concern is valid, but I think we can also 
take a wait-and-see approach to the issue.  My brief experience with 
maintaining 2.5 leads me to believe that packaging a release is more about 
achieving the necessary focus than about the actual time involved, so it's my 
hope that handling two releases will give me some economies of scale, so to 
speak.  We shall see, and I won't hesitate to ask for help if needed.

Second, I want to solicit feedback on a preliminary timeline for 2.6.  As 
stated before, I think we will be best served to have an abbreviated release 
which gets us back on our March/September timeline.  With that in mind, here is 
what I am thinking:

alpha (bugs targetted) - Jan. 16
alpha cut - Jan. 21
beta (bugs targetted) - Feb. 4
beta cut - Feb. 11
RC (bugs targetted) - Mar. 4
RC - Mar. 6

Of these dates, the most meaningful is of course the beta cutoff, which would 
effectively be Feb. 4.  I am also scheduling the longest review/commit period 
for the beta release, since I expect there to be the usual bulge of 
pullrequests.

So, do we collectively think this is doable?  If not, what adjustments should 
we consider?

Thanks for your thoughts,
Dan

Re: [OPEN-ILS-GENERAL] opensrf - cannot authenticate user

[Dan Wells]

Hello Matthias,

The only usable user account credentials on a default Evergreen install are 
those which you specify when using the --admin-user and  --admin-pass 
option to  eg_db_config.  Does that help?

Also, please note that installing Evergreen requires installing both OpenSRF 
and Evergreen itself.  Have you done both installs?  If so, what installation 
instructions are you using, and what versions are you trying to install?

Thanks,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

From: open-ils-general-boun...@list.georgialibraries.org 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of mart 
steinholz
Sent: Monday, December 02, 2013 2:52 PM
To: open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] opensrf - cannot authenticate user

Hello,
I must have missed something during the opensrf setup, but I cannot launch 
evergreen or login to the opensrf webadmin page with any of the users I have. 
I'm currently using a local install as a test install. My UID and pwd are the 
same, and I've edited the .conf files listed in the server install instructions 
but for the life of me can't find what username/password to use in either the 
.conf files or the webadmin page.

I would very much appreciate  some help with this!

Sincerely,
Matthias

[OPEN-ILS-GENERAL] Evergreen 2.5.1 release candidate uploaded

[Dan Wells]

Hello all,

The release candidate for Evergreen 2.5.1 is now available for download.

http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.1.tar.gz.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.1_i686.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.1_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.1_x86_64.tar.bz2
http://evergreen-ils.org/downloads/previews/evergreen-client-2.5.1_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.1.exe
http://evergreen-ils.org/downloads/previews/evergreen-setup-2.5.1.exe.md5
http://evergreen-ils.org/downloads/previews/ChangeLog-2.5.0-2.5.1

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.5.0 Released [RM2.5]

[Dan Wells]

Hello all,

I am happy and relieved to announce the first general release of Evergreen 2.5, 
version 2.5.0.  As usual for full releases, you may check out the Changelog, 
read the release notes, or download the installation files here:

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

I also want to publicly thank both Melissa Ceraso and Steve Callender for 
testing the final release tarball, which enabled us to proceed with the release 
with some extra confidence.

Please note that the 2.5.0 release is also the first step in ending support for 
the 2.3 release line.  Evergreen end-of-life policy states that 2.3 will 
receive three months of only security updates following the release of 2.5.  I 
expect more details about the final planned version of 2.3 will be announced 
soon, so this is just an advance notice.

Looking over changes made since the release candidate was cut, we were able to 
make good use of the three weeks of 2.5-rc.  We identified and fixed a handful 
of high to critical issues, along with a few smaller fixes and tweaks.  You can 
see more details of those fixes here:

https://launchpad.net/evergreen/2.5/2.5.0

I also want to highlight an open bug which did not get integrated into 2.5.0, 
but which may affect users on newer Linux distributions:

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

If you have a very recent version of Encode.pm, this issue will affect you, and 
will be very obvious, as you will (at a minimum) not be able to add or save any 
bib records.  There is a working branch on that bug, so please check it out and 
give feedback if you are able.  The changes touch some fundamental functions, 
so I think it makes sense to be deliberate when evaluating these possible 
fixes, but we also want to get ahead of the Encode.pm updates as they filter 
into the mainstream.

Finally, thanks again to everyone who contributed and tested the ideas and code 
which make up Evergreen 2.5.  It has been exciting to see it all come together.

Sincerely,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.5 Release Update [RM2.5]

[Dan Wells]

Hello all,

It's been two weeks since 2.5 RC1, and while testing and feedback for the RC 
has been scant, I am eager to cut 2.5.0 as soon as possible.  My primary source 
of confidence is the fact that my library has been running 2.5 in production 
since 10/13, but that enthusiasm is tempered by the fact that there are major 
functions (particular authority related) which our installation does not 
currently exercise.

Looking at the tracker, there are currently 4 bugs for 2.5.0 (at time of 
writing) which I think are release-blockers.  All have pullrequests, so it is 
just a matter of review.  You can see them here:

https://launchpad.net/evergreen/+milestone/2.5.0

While I would still much prefer to hear from more testers, we also can't afford 
to delay the release indefinitely.  For that reason, it is my intention to 
branch rel_2_5 and begin preparing the release as soon as the bugs highlighted 
above are committed (provided no new 'high' or 'critical' bugs pop up in the 
interim).  In other words, if anyone has any other reason why 2.5.0 should be 
further delayed, speak now, or hold your peace until 2.5.1 ;)

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.5-rc1 Released [RM2.5]

[Dan Wells]

Hello all,

I am pleased to announce that Evergreen 2.5-rc1 is now available for download.  
Once again, thank you to the many folks who put in some extra time to help us 
get to this point!  You can grab RC1 from the downloads page here:

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

Given the relatively short timeframe, the RC period was a bit busier than 
expected.  In all, 22 bugs were committed in the (roughly) two weeks since 
beta1, which you can see here:

https://launchpad.net/evergreen/+milestone/2.5.0-rc

My site installed an early cut of the RC upgrade on Friday, and after a few 
hiccups (which have since been fixed), things are going smoothly.

So, now that RC1 has landed, how do we get from here to a final 2.5.0?  Until 
now, I have been setting fairly arbitrary deadlines for milestones, but as the 
needs of these last few milestones have become less fluid, selecting target 
dates has become a little more futile.  For 2.5.0, I'd like to try something a 
bit different.  Basically, I am proposing that we use a checklist of specific 
goals, and when we meet every goal, then 2.5.0 final will be cut.  Here are the 
goals I have in mind:

1)  At least two sites do a clean install of 2.5-rc1 from the release 
tarball
2)  At least one site upgrades a production database (or exact clone) to 
2.5-rc1 using the release tarball upgrade script
3)  At least one additional site upgrades to 2.5-rc1 (code and DB, 
production or testing) from the release tarball
4)  At least one site managed by a non-committer either installs or 
upgrades to 2.5-rc1

The reason these goals specify using the release tarball is because we want to 
validate not only the code, but the release process.  I should also note that 
it's possible that the event which satisfies goal 4 will at least partially 
satisfy one of the first three.  Overall, what do we think about these goals as 
a benchmark for release?  Too much?  Not enough?  Please reply if you have any 
feedback on this idea!

Finally, as far as bug management, I have created two new milestones, both 
2.5.0 and 2.5.1.  Since the ideal situation for release will be to make as few 
changes as possible for 2.5.0, I have moved all but one bug to 2.5.1.  If you 
think there are things in the 2.5.1 list which are critical for 2.5.0, please 
do make a case for them, but also please keep in mind that if too many changes 
get applied to 2.5.0, we may need to release it as RC2 and try the process 
again.

As always, feedback is welcome.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.5-beta1 Released [RM2.5]

[Dan Wells]

Hello all,

Friday marked the first beta release of Evergreen 2.5.  You can download it 
here:

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

As noted in my previous email, we are a bit behind schedule, and looking back, 
I think vacation season ending, plus Hack-a-Way activity, plus general 
procrastination in a few areas, all conspired together to create a brief but 
intense whirlwind over the last week or two.  We ended up with 49 total 
bugs/features committed for the beta phase, so considering the other phases all 
had 30-40, it wasn't a huge rush by comparison, but it was noticeable.  You can 
see all the work done specifically as part of the beta here:

https://launchpad.net/evergreen/+milestone/2.5.0-beta1

Thanks again to everyone who wrote and tested all the code and documentation 
changes committed since 2.4, particularly those who gave some extra effort to 
add meaningful strength to the additional milestones throughout the cycle.  I 
am still hopeful that some of the more methodical activity we accomplished over 
the summer will result in a better overall release.

At this point, the main thing which stands between us and 2.5.0 gold is 
enough people putting the beta through its paces.  Please test if you are able, 
and please open (or comment on) a Launchpad ticket if you find anything you 
feel must be fixed before a final release, i.e. show-stoppers.  Also, I would 
very much appreciate any kind of feedback on the upgrade script, since that is 
something least likely to be realistically tested by the Evergreen developer 
community.

Sincerely,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] 2.5 Release Update [RM2.5]

[Dan Wells]

Hello all,

[NOTE: This message was sent yesterday, but I am told that list problems 
prevented it from getting through, so this is a resend.]

The purpose of this email is to announce the official delay of the 2.5 release, 
and to establish a new timeline for release.  A number of factors are 
contributing to this delay, including some exciting development targeted at 
making the TPAC work better on mobile devices.  In talking with many community 
members, the consensus opinion was that the benefits of delaying and including 
the to-be-reviewed work outweighed the costs, but several also cautioned that 
we must emphasize these costs (loss of release predictability, increased chance 
of instability).  How the community wants to balance similar tradeoffs in the 
future will need to be discussed more thoroughly at a later date.

Here is the new timeline:

9/26, noon - feature freeze for master (beta cutoff)
9/26, end-of-day - packaged beta release
10/4 -2.5 RC1 release
10/14 - 2.5 final release

In addition to the mobile TPAC branch (which Lebbeous and I have both offered 
to review), there are still 4 outstanding branches (well, more like 3.25) on 
the original beta-blockers list which I would like to include if possible.  I 
know this recent burst in development activity has spread everyone a little 
thin, but any help in reviewing these would be much appreciated:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.5-beta-blocker

Thanks as always,
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Beta-blockers Tagged and Ready [RM2.5]

[Dan Wells]

Hello all,

The beta-blockers for 2.5 are all tagged and ready for review.  You can see 
them here:

https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.5-beta-blocker

I lowered the count from the 35 planned to 30 because a) this email is a day 
late, and b) I wanted to leave room for any I left out which others might feel 
strongly about.  You can see all the 2.5 reviewable bugs here:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=61110field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

Remember, the goal is to release the beta next Tuesday, so we want these 30 
reviewed by the end of the day on Monday.  I know it's a stretch goal, but as I 
have said before, if every core committer does one a day, we will make it.

Go forth and unblock!

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Today is last day for 2.5 features [RM2.5]

[Dan Wells]

Hello all,

This is just a quick reminder that today, 9/10, is the last day to target 
features for inclusion in 2.5.  This is not a guarantee that your feature will 
get in if targeted today, but it has a pretty good chance.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Last day for alpha1 targeting is tomorrow, 8/2 [RM2.5]

[Dan Wells]

Hello folks,

Hard to believe, but we'll soon be at the end of the 2.5 alpha1 targeting 
phase.  Please continue targeting bugs at '2.5.0-alpha1' in Launchpad through 
the end of the day tomorrow.

So far, the list to tackle looks like:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=59486field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-importancestart=0

One thing you might notice is that the list is no longer sorted simply by age, 
but first by importance, then age.  I know importance often doesn't mean a 
whole lot, but since this will be the first packaged release, I think it is 
time to put a little more focus on reviewing and committing the more serious 
outstanding issues.

Finally, while this isn't the final call for features, I would very much 
appreciate if everyone doing feature work could, at a minimum, open a bug for 
your feature.  It doesn't need a branch or a pullrequest, just go ahead and 
target it at 2.5-alpha1.  These tickets will help us figure out how aggressive 
to be with the beta schedule, or even perhaps if we will need a second alpha 
phase.

Thanks!
Dan



Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

[OPEN-ILS-GENERAL] m2 is Finished, On to alpha1 [RM2.5]

[Dan Wells]

Hello all,

First, thanks again to everyone who put in some extra time to make commits for 
the m2 phase of Evergreen 2.5.  It didn't live up to the drama of m1, but that 
is  a good thing.  We entered Friday needing only 5 more commits, and we 
exceeded that goal.  When all was said and done, our needing-review list had 
dwindled from 62 branches to 29.  If you include a few commits done earlier in 
the m2 period, we pushed a total of 40 branches, and you can see all of that 
work here:

https://launchpad.net/evergreen/2.5/2.5.0-m2

While the amount is great in itself, I also want to highlight a couple other 
positive facts.  First, we cut our pool of year-old+ review bugs from 11 to 4.  
At this rate, I see no reason that cannot be 0 by the 2.5 release.  Second, of 
the 40 bugs committed, 14 were classified as 'wishlist', up from 9 for m1.  
When I see wishlist bugs getting attention, I see more evidence of a maturing 
project.  Once again, great job, everybody!

Looking ahead, we are now past the m's and moving quickly to alpha1.  Here are 
a few things to keep in mind:

1.  While not a hard feature cutoff (that comes at the beta), please make 
every attempt to have new features ready in some form for the alpha1 milestone. 
 If you won't have a pullrequest ready, you should at least have a bug open 
and/or a mention on the roadmap.  That way, there won't be any surprises for 
the beta period.
2.  This will be the first milestone where we will package a release 
tarball.  Potential testers, take note!
3.  The bug target cutoff date will be Aug. 2, and the commit cutoff will 
be Aug. 9.

As always, please reply with any comments, questions, or concerns.

Thanks again,
Dan

[OPEN-ILS-GENERAL] Today is Last Day for m2 Commits [RM2.5]

[Dan Wells]

Hello everyone,

First, thank you to everyone who has contributed to the m2 commit push.  Today 
is the last day, and the goal is well in range!  In four days, we have gone 
from 62 ready m2 pullrequests to 36 still needing review; just 6 more to reach 
our target.  Keep pushing!

Again, here is the list:

https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=59485field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

(I am continuing to list 'Incomplete' bugs, but they are (by the previously 
given definition) not in the 'ready' count.)

Thanks again,
Dan

[OPEN-ILS-GENERAL] M2 Targeting Deadline TODAY[-ish] [RM2.5]

[Dan Wells]

Hello all,

As usual, the summer is cruising by at a rapid pace.  Already we find ourselves 
at the first of July, the suggested last day for targeting bugs at M2.  If you 
have something you feel is ready for review, but haven't pushed your branch 
yet, now is the time!  Also, since Monday deadlines are sneaky, and this 
message is coming pretty late in the day, feel free to continue targeting until 
noon tomorrow EDT.  At that point we'll take a count of what is out there and 
see where things stand.

Thanks all,
Dan

Re: [OPEN-ILS-GENERAL] Error receiving serial issuances

[Dan Wells]

Hello Beth,

In this case, your problem is being caused by the 'x, 01' in your pattern.  
This subfield is for a calendar change meaning the volume should increment at 
a certain month (or day, or season), but your serial is not a monthly, and has 
no month in the caption.  If you remove the 'x, 01', you should be able to 
receive as expected (with (I think) no need to delete and recreate any of the 
issuances).

So, the caption/pattern has a minor problem, but this is one (of many) cases 
where the code should be more forgiving, especially since I only see one 
sensible way to interpret the caption/pattern in this case.  Please do file a 
bug for this case (or add a 'me too' if a bug exists for this already).  Also, 
if you used the caption/pattern wizard to create this caption, mention that in 
the bug report, since we need to be especially careful to avoid generating bad 
caption/patterns whenever we can.

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 6/13/2013 at 11:09 AM, Beth Willis wil...@noblenet.org wrote:

 For some time, some of our libraries have reported sporadic errors when 
 receiving serial issuances.   In the past, I often was able to eliminate 
 the errors by editing faulty holding codes.  But, in the most recent 
 cases, I don't see any problem with the holding codes.
 
 For example, I have a report from a library of two titles that they 
 cannot receive.  Both are annual publications.  I created a test 
 subscription for one of the titles using the same caption and pattern 
 code that the library used.  I then generated 6 expected issuances. 
 When I tried to receive an issuance, I  got the same database error as 
 reported by the library.
 
 We use the Serial Control View for receiving.  As of today, we are on 
 v.2.3.7.
 
 Subscription details:
 
 Caption/Pattern:
 
 [2,0,8,1,a,Vol.,i,(year),w,a,x,01]
 
 Generated 6 expected issances as follows:
 
 Holding Codes:
 [4,1,8,1.2,a,63,i,2012,x,AUTOGEN]
 [4,1,8,1.3,a,64,i,2013,x,AUTOGEN]
 [4,1,8,1.4,a,65,i,2014,x,AUTOGEN]
 [4,1,8,1.5,a,66,i,2015,x,AUTOGEN]
 [4,1,8,1.6,a,67,i,2016,x,AUTOGEN]
 [4,1,8,1.7,a,68,i,2017,x,AUTOGEN]
 
 
 ERROR MESSAGES:
 
 I received this error today (v.2.3.7)
 
 FIXME:  If you encounter this alert, please inform your IT/ILS helpdesk 
 staff or your friendly Evergreen developers.
 
 Thu Jun 13 2013 11:01:07 GMT-0400 (Eastern Daylight Time)
 
 cmd_receive_items failed!
 
 BAD_PARAMS
 Invalid parameters were encountered in a method
 
 
 I received the following error last week while we were still on v.2.2.8:
 
 
 Network or server failure.  Please check your Internet connection to 
 evergreen.noblenet.org and choose Retry Network.  If you need to enter 
 Offline Mode, choose Ignore Errors in this and subsequent dialogs.  If 
 you believe this error is due to a bug in Evergreen and not network 
 problems, please contact your help desk or friendly Evergreen 
 administrators, and give them this information:
 method=open-ils.serial.receive_items
 params=[0091d3e98ea1fd83ae651ddad3f4bd9c,[{__c:sitem,__p:[113706,{_
 _c:au,__p:[null,null,null,null,null,null,null,null,null,null,null,t,nu
 ll,f,null,1,0,0,2012-05-14T15:46:39-0400,0.00,null,1979-01-22T00:00:00-0500
 ,null,null,2015-05-14T15:46:39-0400,System 
 Account,Administrator,1,1,1,null,identification,null,none,null,t,1,
 null,8cbb514d32e37b43ef310752c90b5cb3,null,null,1,null,1,null,t,1,noble
 ,null,f,2012-05-15T10:13:34-0400,null,f]},{__c:au,__p:[null,null,nul
 l,null,null,null,null,null,null,null,null,t,null,f,null,1,0,0,2012-05-14T1
 5:46:39-0400,0.00,null,1979-01-22T00:00:00-0500,null,null,2015-05-14T15:46:39-
 0400,System 
 Account,Administrator,1,1,1,null,identification,null,none,null,t,1,
 null,8cbb514d32e37b43ef310752c90b5cb3,null,null,1,null,1,null,t,1,noble
 ,null,f,2012-05-15T10:13:34-0400,null,f]},2013-06-04T11:28:35-0400,2013-06-0
 4T11:28:35-0400,{__c:siss,__p:[120364,{__c:au,__p:[null,null,null
 ,null,null,null,null,null,null,null,null,t,null,f,null,1,0,0,2012-05-14T15
 :46:39-0400,0.00,null,1979-01-22T00:00:00-0500,null,null,2015-05-14T15:46:39-0
 400,System 
 Account,Administrator,1,1,1,null,identification,null,none,null,t,1,
 null,8cbb514d32e37b43ef310752c90b5cb3,null,null,1,null,1,null,t,1,noble
 ,null,f,2012-05-15T10:13:34-0400,null,f]},{__c:au,__p:[null,null,nul
 l,null,null,null,null,null,null,null,null,t,null,f,null,1,0,0,2012-05-14T1
 5:46:39-0400,0.00,null,1979-01-22T00:00:00-0500,null,null,2015-05-14T15:46:39-
 0400,System 
 Account,Administrator,1,1,1,null,identification,null,none,null,t,1,
 null,8cbb514d32e37b43ef310752c90b5cb3,null,null,1,null,1,null,t,1,noble
 ,null,f,2012-05-15T10:13:34-0400,null,f]},2013-06-04T11:28:35-0400,2013-06-0
 4T11:28:35-0400,{__c:ssub,__p:[3836,37,2012-01-01T00:00:00-0500,null,209
 0279,null]},6748,Vol.63(2012),2012-01-01T00:00:00-0500,[\4\,\1\,\8\,\
 

[OPEN-ILS-GENERAL] Milestone 1 Wrap-up [RM2.5]

[Dan Wells]

Hello all,

Milestone 1 (aka m1), the first phase of the 2.5 development process, came to a 
close on Friday.  We entered the commit phase with 63 bug reports needing 
review, many of them being part of a bug backlog which built up over time.  
With the number so high, the challenge given to the dev community was to cut 
that number in half during this first round.  With my last, bleary-eyed check 
of the count late Friday, the number needing review (by the same criteria) had 
fallen to 31!  By the mere width of half a bug, we had made our goal.  THANK 
YOU to everyone who pitched in; even if you only dealt with one bug, this 
success simply wouldn't have happened without you.

So, what made it into m1?  Rather than highlight some contributions and leave 
out others, please check out the whole list:

https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=field.status%3Alist=FIXCOMMITTEDfield.milestone%3Alist=58847search=Searchorderby=id

On thing I will point out is that thirteen of the listed issues were created 
more than six months ago, so that's good evidence that we were able to take 
care of a significant portion of the lingering issues rather than focus 
entirely on new features, and this gives me confidence that Evergreen is truly 
a maturing product.

With m1 now in the past, let's turn our attention to m2.  We are behind a 
little from the original schedule (which is fine and not unexpected), plus we 
need to account at least somewhat for 4th of July absences.  So, my suggestion 
is that July 1 is the last day to target bugs at m2, and July 12 will be the 
last day of the commit push (it may have just been chance, but we did much 
better with the Friday deadline than the Tuesday one, so we'll try the same 
thing again).  Speaking of bugs, I'll be spending some time shortly retargeting 
the left-over m1 pull requests at m2.

Important Dates:
7/1 - Suggested last day for targetting bugs/features at m2
7/2-7/12 - Suggested period to focus energy on reviewing/committing m2 
bugs/features

Once again, thanks again to everyone who helped in the m1 push.  With a few 
repeat performances, I am confident Evergreen 2.5 can be the best release yet.

As always, please feel free to voice any comments or concerns you have about 
the release process.  One question I have for everyone: is there demand for an 
m1 tarball (aka packaged release)?  The primary goal of the early milestones 
was more organizational, since this is still pre-alpha code, but if there is 
demand, we can make it happen.  (Plus, it would probably be good practice for 
me to learn more about the packaging process).

Sincerely,
Dan

[OPEN-ILS-GENERAL] m1 Update, Reprieve [RM2.5]

[Dan Wells]

Hello all,

Today was targeted as the last day for getting commits into m1.  According to 
my count [1], we have gone from 63 branches ready to merge to... 54 (after 
removing Incomplete tickets).

I have to admit, this is a little disappointing.  Maybe people just forgot.  
Maybe I didn't communicate the goal well enough.  Maybe the law of averages 
took the week off, and by virtue of that, everyone else did, too.

Whatever the case, I think we can do better.  So, I am pushing the deadline out 
just a little farther, and setting the bar a little lower.  The m1 commit 
period will now end on Friday at 3:00pm (EDT), and I want every committer to 
make an effort to commit just *one* pullrequest from the given list [1] between 
now and then.

I was holding out hope that there would be a rush of activity today, but it 
never came.  Hopefully we can make something out of this second chance.  At 
this point, I haven't gotten any feedback on these deadlines, but I would 
certainly appreciate any suggestions you all might have.  Also, if you can't 
participate for whatever reason, I would appreciate at least hearing from you, 
so I can know we are on the same page.

Thanks,
Dan

[1] 
https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=58847field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0

[OPEN-ILS-GENERAL] Milestone 1 - Deadline TODAY, More Details [RM2.5]

[Dan Wells]

Hello everyone,

In my last communication, I indicated that 5/27 would be the suggested cutoff 
date for targeting bugs in Launchpad at Milestone 1 (2.5.0-m1).  When I wrote 
that, I wasn't thinking about the fact that it was a U.S. holiday.  So, 
everyone gets a one day extension, and today is the suggested cutoff for m1 
targeted bugs.  After today, please target any new 2.5 bugs/features at 
2.5.0-m2.  (One exception to this recommendation would be bugs deemed High or 
Critical.  Those should go in ASAP regardless of this process).

The reason for having this cutoff is that tomorrow begins the first commit push 
for 2.5 (and it can be demoralizing to try to tear down a mountain which is 
still building!).  At current count we, have 63 tickets which have pullrequest 
tags and are apparently ready for merge.  Since I am extending the assignment 
cutoff, we are also going to add a day to the commit period, which pushes the 
m1 commit cutoff to June 4 (end of day).  If every committer handles one 
pullrequest ticket per day between now and then, we could almost clear out this 
entire backlog.  I know that isn't realistic, but can we do at least half that? 
 Two thirds, even?  I think we can!  Add in valuable sign-offs from 
non-committers, and our chances are that much better.

To help in this endeavor, I am going to make two suggestions.  First, I am 
going to recommend the judicious use of the Incomplete status.  Some 
pullrequests sit around and rot because the provided code is a little funky, or 
the solution/feature is controversial, or the code simply doesn't seem to work. 
 If anyone reviews a pullrequest, but doesn't commit (or sign off) on these 
sorts of grounds, please mark the bug as incomplete and leave a comment 
explaining why.  While the window would still be open to address the concerns 
and get it committed before m1 arrives, any tickets marked Incomplete will be 
considered done for this round when assessing our goal completion rate.

Second, and especially for committers who tend to be more conservative in the 
review process (you know who you are), I think we should temporarily and 
collectively lower the review bar to pretty good.  Try to consider the nature 
of the code change, such as how much and what parts of the system, and make 
your level of testing in line with the character of the changes, rather than 
attempting perfection.  This temporary attitude adjustment means two things:  
you will not be shamed for any bad commits done in the next week, and anyone 
running from master might want to put any pulls on hiatus for the next week or 
two until the dust settles.  I think some level of planned instability is our 
best hope at keeping things on track, and is far better than the most likely 
alternative: unplanned instability (a.k.a. the mad rush).

Important Dates:
5/28 (was 5/27) - (suggested) last day to target bugs/features for m1
6/4 (was 6/3) - goal date for having all m1 bugs/features committed to master

As always, additional thoughts and concerns are welcome!

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133

[OPEN-ILS-GENERAL] Evergreen 2.5 - Introduction and Milestone 1 Details [RM2.5]

[Dan Wells]

Hello everyone,

After a couple weeks of suspense and anguish, you are now at last reading my 
first official communication as release manager [RM] for 2.5.  In the interest 
of general efficiency, and to encourage dialog over unnecessary detail, I will 
try to be succinct.

Announcements:
1) Hello world - For any who do not know, I am the release manager for 
Evergreen 2.5.  Unless you were at the dev meeting, you probably don't know, 
because I haven't (publicly) done anything yet.

2) Mailing list intentions - Rather than double-post everything for the next 4 
months, future official 2.5 RM communications will typically be on the 
*general* list only.  Every developer should be on the general list, and my 
primary goal will be to keep everybody in the loop, not just the developers.  
If you are a dev and are not on the general list (and you care about these 
messages, or Evergreen in general), please subscribe.

3) Mailing list tag - I'll be tagging any RM-specific emails with [RM2.5] 
in the subject line.  I don't know if this will be useful, but it seems like it 
might be helpful to me at least.

4) Concerning milestones
4a) Changing of alpha milestone - As implied by my original proposal, the 
current 2.5-alpha1 milestone is going to be renamed to 2.5-M1.  If you have 
anything in Launchpad tagged alpha1 which you actually want to put off until 
then, you will need to move it to the new alpha1 milestone (see next).
4b) Creating planning milestones - After alpha1 is renamed, I will 
immediately create an M2 milestone and a new alpha1 milestone.  These are meant 
to provide a way to set expectations for feature branch completion goals.  You 
are encouraged to post your feature descriptions as early as possible.
4c) Setting milestones based on the roadmap [1] - Any current feature tickets 
on the roadmap with a 'pullrequest' tag but no milestone will be set to M1.  
Any without a 'pullrequest' tag will be initially set to M2.  If you are 
heading up development of any features, please feel free to adjust the goal 
milestones as appropriate.

5) Whitespace fix (revised plans) - There was concern at the dev meeting about 
my initial plan to split up the mass whitespace fix into three passes.  After 
further consideration and process testing, I now feel more confident that doing 
the fix all at once is both doable and preferable.  Sometime in the next week 
or so, I will make a first pass at creating some process instructions/tips and 
post them to the wiki.  The current intention is that the mass whitespace fix 
will happen immediately after the M1 phase.


Important Dates:
5/27 - (suggested) last day to target bugs/features for M1
6/3 - goal date for having all M1 bugs/features committed to master


So, developers, testers, and other contributors, the first big push for 2.5 
commits will start 1.5 weeks from now and continue for 1 week.  I fully 
understand that there will be personal conflicts which prevent participation in 
this push, but with a little focus (and perhaps some poking and prodding), I am 
confident we can make it happen.

As always, questions, comments, concerns, and suggestions are welcome.

Sincerely,
Dan

[1] http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap:2.5

Re: [OPEN-ILS-GENERAL] What should be done during unexpected library closings?

[Dan Wells]

The idea of newly added closed dates pushing back current checkouts due on that 
date sounds like a good wishlist request to me, if anyone is so inclined to 
create one:

https://bugs.launchpad.net/evergreen

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 4/24/2013 at 11:59 AM, Aaron Zsembery azsemb...@pls-net.org wrote:
 We also backdate. Adding closed dates for weather closings will not effect 
 the actual due date in the system as that is computed at the time of 
 checkout. It might help with fines, but using a backdated check-in works just 
 as well.
 
 Aaron Z
 Jr. Systems Administrator
 
 Pioneer Library System
 2557 State Rt. 21
 Canandaigua, New York  14424
 Phone: (585) 394-8260

Re: [OPEN-ILS-GENERAL] What should be done during unexpected library closings?

[Dan Wells]

This isn't especially relevant to the conversation, but last I checked, 
Evergreen actually post dates fines to the end of the fine period in which 
they occur.  In other words, daily fines are all dated with a timestamp of 
23:59 regardless of what time the fine generator runs.  This made the fine 
logic a little simpler to calculate, but it is also a source of general 
confusion for users, as fines appear to happen in the future if you look 
closely.  Perhaps someday someone will find the tuits to fix this, but for now, 
it works.

All that said, maybe you really do run your fine generator at 23:59, but that 
seems a little like living on the edge to me, and I wouldn't base any opinions 
on the billing timestamps :)

Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 4/24/2013 at 3:25 PM, Aaron Zsembery azsemb...@pls-net.org wrote:
 On Wednesday, April 24, 2013 3:21:05 PM chtrot...@ocrl.org wrote:
 I am not sure  if the closed date can be entered the same day and fines
 not accrue.
 IIRC, in our install the fine generator runs at 23:59 to generate daily 
 fines, so as long as the entry gets in, it should theoretically work. I 
 haven't tried that though.
 
 Aaron Z
 Jr. Systems Administrator
 
 Pioneer Library System
 2557 State Rt. 21
 Canandaigua, New York  14424
 Phone: (585) 394-8260

Re: [OPEN-ILS-GENERAL] OPAC- serial holding summary display

[Dan Wells]

Hello Eva,

This seems likely to be a bug.  If you haven't already, could you report this
at https://bugs.launchpad.net/evergreen ?  That will at least reduce the
likelihood of this issue getting lost.

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 2/19/2013 at 8:33 AM, Cerninakova Eva cer...@jabok.cz wrote:
 We came across  a problem of  serials holding display for a particular
 serial in library  OPAC .
 I  think the problem could have something to do with the fact that  in this
 case the numbering  increments continuously (we newer had a problem
 displaying serials holdings in OPAC when issuance numbering restarts at
 unit completion).
  We received serial issues no. 42 and 43, but in the serial holding summary
 no information about no. 43 is  displayed in OPAC (however call numbers are
 displayed), see

http://www.jabok.cuni.cz/opac/en-US/skin/default/xml/rdetail.xml?r=10801d=0h

 c=1adv=10801rt=tcn
 
 When creating pattern code and  issuance I entered following data:
 
 1) Pattern code wizard:
 Page 1 - Use enumeration: filed checked
 Enumerating caption :
 First level: Vol.
 Second level: No., Number: 2, Increments continuously
 
 Page 2 - Use calendar changes: filed checked.
 Used calendar change „At start of a month“ „January“
 
 Page 3 - Use chronology caption: field unchecked
 
 Page 4
 Compressibility and Expandability: Cannot compress or expand
 Caption Evaluation: Caption unverified, all levels may not be present
Frequency: Semiannual
 
 2) I created New Issuance with following: Date published:12/15/2011
  then I entered data to Issuance wizard (Vol :2011, no 41) and compiled
 the holding code.
 
 3) I generated prediction for vol. 2012 and 2013 (numbers 42 - 43/2012 and
 44 - 45/2013).
 
 I am quite new in holding data formats so I think I might have done
 something wrong when generating pattern code or making  prediction (however
 I cannot exclude possibility of existing bug).
 
 Have you any idea?
 Thanks a lot.
 
 Eva
 
 
 
 
 -- 
 Mgr. Eva Cerniňáková
 cer...@jabok.cz 
 
 Knihovna Jabok
 http:/knihovna.jabok.cz
 Tel.: +420 224 990 157
 
 Jabok - Vyšší odborná škola sociálně pedagogická a teologická
 Salmovská 8, 120 00 Praha 2

Re: [OPEN-ILS-GENERAL] Proposal to change Evergreen versioning scheme

[Dan Wells]

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
 On 1/4/2013 at 3:52 PM, Dan Scott d...@coffeecode.net wrote:
 In the end, I'd really like to not have this discussion come up on a
 regular basis. There's code and docs and tests and websites to be worked
 on, and a product that is solid and reliable and easy to understand and
 use is going to succeed no matter how much the version numbers diverge
 from the scheme documented on a wiki page. And if the current problem
 can be rectified by striking out two clauses from the wiki page, why
 don't we just do that so we can focus on everything else we have to work
 on?

+1!  And bravo to Jason S. for taking the initiative to go ahead and change the 
wiki page to reflect this current reality.

Dan

P.S. (and apologizes for flippancy, I mean no offense)
Or, in honor of the new year, I'd like to suggest we bump the version to 10.0 
and start working our way down to 0.0.  This plan has the following advantages:

- we would probably get the project 15 minutes of fame on Slashdot or something
- it meets Galen's monotonicity requirement, so we know he's on board
- people would find it really confusing, or maybe exciting
- when we reach 0.0, then Evergreen is over and we get to do something else 
with our lives

Who's with me?

Re: [OPEN-ILS-GENERAL] TPAC question: getting ebooks as an option in formats

[Dan Wells]

Hello all,

This is a pretty complex subject, and anyone interested in diving in full on 
should probably start here:

http://www.loc.gov/marc/ldr06guide.html

In all, there are at least five major factors which all relate to describe the 
type of an item.  They are:

Leader/06 - Type of record
Leader/07 - Bibliographic level
Field 008 - Fixed-Length Data Elements
Field 006 (repeatable) - Fixed-Length Data Elements - Additional Material 
Characteristics
Field 007 (repeatable) - Physical Description Fixed Field

Notice that I listed 008 before 006.  This is not an accident, as despite their 
numbering, 006 is subsequent to 008.  It actually contains the same data as 
positions 18-34, which is the material specific portion of the 008, and was 
added later to make up for the fact that 008 is not repeatable.

There is an interplay between these fields such that the meaning changes 
depending on the content of the more primary fields.

To get more to the point, my understanding is that setting Leader/06 to 'm' for 
cataloging is a last resort for records which cannot be better described at a 
different level, which means that ebooks are supposed to use 'a' (as yours do), 
and changing them to 'm' would be considered (by some, anyway) to not follow 
best practices.  As Dan Scott points out, there are other places (008/006) 
where the cataloger can indicate the electronic-ness of the thing, so Leader/06 
is more about the essence of the thing.

I think! :)

It would probably be wise to work with the catalogers here and create a unified 
cheat sheet which would be representative of an official Evergreen 
understanding of best practices for the most common types of items.  Without 
something we can agree on, the developers cannot have a unified target, and we 
will either end up with something excessively complex (by simply exposing these 
innards), something watered-down (by simply hiding these innards), or an 
endless tug-of-war as we write code which reflects local practices or (worse) 
our own understanding.

Dan

 On 8/3/2012 at 11:19 AM, Soulliere, Robert
robert.soulli...@mohawkcollege.ca wrote:
 Hi Justin,
 
 Exactly right about that. If this method is OK, we will be investigating 
 extending the usefulness of format by extracting and differentiating some of 
 those computer file formats into unique format codes. I am worried about 
 how far we can get into creative cataloguing before we are  considered 
 rogue librarians or mangle our system. ;-)
 
 Technically, Evergreen gives us the power, but should we use it?
 
 Regards,
 Robert
 
 
 Robert Soulliere, BA (Hons), MLIS
 Systems Librarian
 Mohawk College Library
 robert.soulli...@mohawkcollege.ca 
 Telephone: 905 575 1212 x3936
 Fax: 905 575 2011
 
 From: open-ils-general-boun...@list.georgialibraries.org 
 [open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Justin 
 Hopkins [jus...@mobiusconsortium.org] 
 Sent: August 3, 2012 11:05 AM
 To: Evergreen Discussion Group
 Subject: Re: [OPEN-ILS-GENERAL] TPAC question: getting ebooks as an option  
  
  in formats
 
 Just chiming in to say that I'm also interested in this topic. The LOC marc 
 standard would seem to indicate that 'm' for computer file (I believe the 
 label in EG is electronic resource) is the right code, but that doesn't 
 seem specific enough to be useful.
 
 
 On Aug 3, 2012, at 9:17 AM, Soulliere, Robert wrote:
 
 Hi all,

 We are investigating a method to get ebooks as a format option in our TPAC 
 and I wonder if I could get some feedback on whether this is a good way to do 
 this. Here is the method we are investigating:

 1. Add a unique type entry using the MARC Code Value Map in the staff 
 client.

 2. Edit the Leader field of our electronic books to indicate that they are 
 in the new ebook type. Currently most use a to indicate a book.

 I had a few question about this method:

 1. Is there a better way to add the ebook as a format search option?

 2. Are there potential dangers for us using this method? e.g. issues with 
 future upgrades.

 3. Is this kosher from a cataloguing perspective?

 This works technically, but want to see if this is the best way.

 Thanks,
 Robert









 Robert Soulliere, BA (Hons), MLIS
 Systems Librarian
 Mohawk College Library
 robert.soulli...@mohawkcollege.ca 
 Telephone: 905 575 1212 x3936
 Fax: 905 575 2011

 This E-mail contains privileged and confidential information intended
 only for the individual or entity named in the message.  If the reader
 of this message is not the intended recipient, or the agent responsible
 to deliver it to the intended recipient, you are hereby notified that
 any review, dissemination, distribution or copying of this communication
 is prohibited.  If this communication was received in error, please
 notify the sender by reply E-mail immediately, and delete and destroy
 the original message.
 
 
 This E-mail contains privileged and confidential information 

Re: [OPEN-ILS-GENERAL] conversion of overdue items to lost -- very basic

[Dan Wells]

Hello Sheila,

Lost marking in Evergreen is handled by a flexible (but somewhat complex) 
Action Trigger system.  The event definition for lost marking in a stock 
install can only be easily configured for number of days overdue, not for 
individual circ modifiers, so any checkout which is, for instance, 90 days 
overdue will be marked as lost.  I should also note that this event is disabled 
in a stock install.

Before the action (in this case, marking the item lost) happens, though, it 
must pass a validation step.  The stock event simply verifies that the circ 
is overdue, but I would think it is possible to write a validator which would 
check for certain circ modifiers.  If you did that, you could then define 
multiple triggers with different overdue requirements and different validators 
to achieve the effect you are after.  Creating a new validator involves 
writing some Perl code, if I remember correctly.  While not easy, this type 
of code isn't terribly intense, and many people here or in IRC could provide 
guidance if you or someone on your staff with some basic Perl understanding 
wanted to take a crack at it.

It's been quite a while since I worked with setting up out Action Triggers, but 
I expect others will chime in if I am too far off.

Hope this helps,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 7/23/2012 at 10:23 AM, Kearns, Sheila sheila.kea...@state.vt.us 
 wrote:
 Looking for some quick guidance and hoping the terminology is correct.
 
 Is there a single point at which all items (regardless of circ modifier) are 
 converted to lost or can that be different for different circ. modifiers?
 
 ---
 Sheila M. Kearns
 Vermont Dept. of Libraries
 109 State St.
 Montpelier, VT 05609
 802-828-6952
 sheila.kea...@state.vt.us 
 ---

Re: [OPEN-ILS-GENERAL] Evergreen 2.2 sites

[Dan Wells]

Hello Janet,

We are on 2.2 but still using JSPAC for our primary catalog.  Our TPAC is still 
a work-in-progress, but if you want a sneak peek:

http://ulysses.calvin.edu/eg/opac/home 

Dan


-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 7/31/2012 at 12:59 PM, Janet Royer jan...@ci.burlington.wa.us wrote:
 Our library will be updating to Evergreen 2.2 near the end of August and
 we would like to know which other sites have already migrated so we can
 take a peek at your catalog.
 
  
 
 Thanks so much!
 
  
 
 Janet Royer
 
 SysAdmin/Circ Supervisor
 
  
 
 Burlington Public Library
 
 820 E Washington Ave
 
 Burlington WA  98233
 
 360-755-0760
 
 jan...@ci.burlington.wa.us mailto:jan...@ci.burlington.wa.us 
 

[OPEN-ILS-GENERAL] Job posting [still open] - Electronic Services and Emerging Technologies Librarian

[Dan Wells]

Calvin College is seeking an Electronic Services  Emerging Technologies 
Librarian (ESET).  This position is responsible for introducing, designing, 
developing, and maintaining the technologies used by the library staff and the 
community of library users with the goal of providing an exceptional user 
experience. The ESET Librarian is adept at collaborating with a broad range of 
constituencies, possesses outstanding relational, communication, and project 
skills, and is skilled in motivating and inspiring others to embrace change. 
The ESET Librarian also teaches, assists students and researchers in a 
one-on-one environment, and collaborates with professors in assigned academic 
departments.

ESSENTIAL DUTIES AND RESPONSIBILITIES include the following. Other duties may 
be assigned.

1. Maintains, enhances, and evaluates the library's existing technologies, and 
manages the technical aspects of the library's instance of Ex Libris' SFX
2. Provides leadership for the identification, assessment, and implementation 
of emerging technologies that further the library's mission and increase and 
enhance access to library resources and services
3. Provides efficient and effective management and leadership of the library's 
programmers
4. Leads the Electronic Services Team in incorporating appropriate design 
principles, information architectures, coding standards, and emerging 
technologies into the library's services to the community of users
5. Communicates with service or technology providers regarding agreements, 
contracts, or support
6. Ensures appropriate hardware, software, facilities, training and support are 
provided for library staff and clients
7. Gathers data about how Library users employ technology to access information
8. Collaborates with the library's Marketing Team to ensure that the Hekman 
Library's web site offers an accurate, intuitive, and user-friendly experience
9. Teaches research fluency skills in an introductory English course and in 
advanced courses in liaison areas
10. Staffs the research assistance desk occasionally during regular business 
hours, evenings, and weekends
11. Collaborates with professors in assigned academic departments
12. Performs administrative duties by attending library meetings and 
contributing to team efforts so the library can deliver high quality services
13. Participates in professional activities by attending national and regional 
conferences, by serving on college committees and by playing a visible role in 
the Calvin community and the broader library community to ensure professional 
growth

For additional information, or to apply, please see http://jobs.calvin.edu 



-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] Questions about serials

[Dan Wells]

Hello Kathy,

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 5/17/2012 at 10:44 AM, Kathy Lussier kluss...@masslnc.org wrote:

 
 1. After setting up a subscription, creating a caption/prediction, 
 pattern, etc., we've noticed that when return to the OPAC view of the 
 record, select Actions for this Record  MFHD Holdings  Edit MFHD 
 record, there is now a MFHD record that appears to be editable (see 
 attached screenshot.)
 
...
 
 My question is whether I am suppose to be able to edit this 
 automatically-generated MFHD statement. If so, I can file a bug report, 
 but I just didn't know what the intended behavior is here.

Lebbeous is correct, you are not supposed to be able to edit the generated data 
directly, so the bug here is that the menu entry is added.  This same bug was 
found and fixed at one point (in JSPAC at least), and should be fairly simple 
to fix again.

 
 2. My understanding is that special issues can only be created via the 
 alternate serials control view. Is that still the case?
 

Special issues are still problematic for a number of reasons.  Creating them 
manually is cumbersome and error prone, especially if you have a lot of 
distributions and streams, and they frequently cause havoc when generating 
summaries.  The ability to create them was removed from the Serial Control View 
sometime during 2.0 alpha with the intention of making sure they worked 
properly top-to-bottom before including them, but we are going on two years of 
intending, so maybe pulling what we had at that time (despite its danger) 
was a little optimistic.

At any rate, we are surviving at my library with a workaround.  It doesn't 
solve the bigger underlying issues, but it is pretty easy and helps ensure good 
data, so I recommend it at this point regardless of which interface you are 
using.  Here are the steps:

1. Make sure you have at least *2* unreceived issuances generated which are 
chronologically after your special issue.
2. Carefully hijack your *last* predicted issuance, editing it to reflect the 
special issue data, paying particular attention to the date published.
3. (optional) Edit the 'Date expected' on the individual items attached to the 
issuance (which generally only matters if you are not receiving it right away). 
 If you use the Serial Control Items tab, you can edit them all at once.

That's it.  All of your distributions/streams are populated and everything is 
linked together properly.  The prediction code always predicts from the last 
issuance based on *date published*, so as long as you follow these steps, the 
issuance you hijacked will be recreated the next time you predict issues, 
because your current last issuance was (and will be) the one right before it. 
 Hopefully this makes at least some sense!

 
 4. This last question will probably turn into a bug report, but I just 
 want to understand the expected behavior before filing the bug. We have 
 libraries that prefer using something like most recent 5 years as the 
 textual holdings statement. I've been playing with the summary method 
 and have found that I can successfully do so by setting the summary 
 method to Use record entry only.
 
 However, I found that the remaining three options (add to record 
 entry, merge with record entry and do not use record entry) 
 generate the same display in tpac. It displays the holdings statement 
 automatically generated by Evergreen followed by the record entry. I'm 
 assuming that do not use record entry should not be displaying the 
 record entry at all. What is merge with record entry supposed to do?
 

To add to what Lebbeous said, in cases where the generated holdings are a 
direct continuation of the MFHD holdings, the merge setting is meant to 
detect that and therefore not display the break (that is, to use simple number 
ranges for example purposes, you should see 1-5 instead of 1-3,4-5).

Thanks for the questions and the (coming) bug reports!
Dan

Re: [OPEN-ILS-GENERAL] Active Directory

[Dan Wells]

Hello Tim,

You can generally communicate with Active Directory via the LDAP protocol.  If 
that is the case for your installation, there is a feature in 2.2 which allows 
for basic authentication using LDAP user bind.  To answer your listed concern, 
it is possible to limit this feature to a single org unit.  You can read a 
description here:

http://www.open-ils.org/documentation/release/RELEASE_NOTES_2_2.html#_authentication_proxy

Alternative methods of LDAP authentication (anonymous or admin bind) are not 
currently supported.  Also, this feature has not been ported to TPAC, but I 
intend to do so before our migration to 2.2 in a few weeks.  TPAC integration 
will then very likely be part of 2.3.

Please let us know if you have any other questions.

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 5/16/2012 at 6:38 AM, Tim Spindler tspind...@cwmars.org wrote:
 We have a question if a library could connect to active directory for
 authentication. Is this possible and has someone done this?  We are of
 course in consortium environment so it would only be one library among 150
 if it was even possible.

Re: [OPEN-ILS-GENERAL] Prediction pattern for annual serial

[Dan Wells]

Hello,

I am also unfortunately not able to reproduce this problem on 2.2.  If anyone 
can reproduce this, could you please post both your pattern code and also the 
holding code of your starter, along with your exact Evergreen version?

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 5/3/2012 at 10:05 AM, Erhan Tuskan e...@iisg.nl wrote:
 Which version do you use? I tried both patterns of you in version 2_0_3 and 
 they work without any problem, giving the same predictions.
 
 At the IISH we have the following pattern for an incrementing annual, using 
 number instead of volume:
 [2,0,8,1,a,no.,u,1,i,(year),w,a,x,01]
 
 And the calendar changes have indeed no influence.
 
 Erhan Tuskan
 IISH
 
 -Original Message-
 From: open-ils-general-boun...@list.georgialibraries.org 
 [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
 David Fiander
 Sent: donderdag 3 mei 2012 3:29
 To: Evergreen Discussion Group
 Subject: Re: [OPEN-ILS-GENERAL] Prediction pattern for annual serial
 
 It's probably an odd boundary condition. Because every issue arrives in 
 January, the month never actually changes.
 
 - David
 
 On Thu, May 3, 2012 at 9:15 AM, Kathy Lussier kluss...@masslnc.org wrote:
 Hi all,

 I have a question about a serials prediction pattern that seems like 
 it should have been fairly straightforward, but took some time to get 
 the volumes to increment correctly.

 The prediction pattern is for an annual serial where the volume should 
 be incrementing every year. The example I was using was for the 
 Journal of Hellenic Studies. When I was first setting up the 
 prediction pattern through the alternate serial control view, I did the 
 following:

 *I added a first level enumeration for v.
 *I selected the option to use calendar changes and identified the 
 start of January as the time when the first-level enumeration should change.
 * I selected year for the caption
 * I selected annual as the frequency

 The resulting prediction pattern was:
 [2,0,8,1,a,v.,i,(year),w,a,x,01]

 I then set up my first issuance with a volume number of 10, but when I 
 generated the predictions, the volumes didn't increment.

 We ultimately were able to get the volumes to increment correctly by 
 de-selecting the option to use calendar changes, which resulted in the 
 following prediction pattern:

 [2,0,8,1,a,v.,i,(year),w,a]

 I'm happy we got this pattern working correctly, but I'm still curious 
 as to why the calendar change option does not work in this situation.

 Thanks for any insight you can provide!

 Kathy



 --
 Kathy Lussier
 Project Coordinator
 Massachusetts Library Network Cooperative
 (508) 756-0172
 (508) 755-3721 (fax)
 kluss...@masslnc.org 
 Twitter: http://www.twitter.com/kmlussier

[OPEN-ILS-GENERAL] Job posting - Electronic Services and Emerging Technologies Librarian

[Dan Wells]

Calvin College is seeking an Electronic Services  Emerging Technologies 
Librarian (ESET).  This position is responsible for introducing, designing, 
developing, and maintaining the technologies used by the library staff and the 
community of library users with the goal of providing an exceptional user 
experience. The ESET Librarian is adept at collaborating with a broad range of 
constituencies, possesses outstanding relational, communication, and project 
skills, and is skilled in motivating and inspiring others to embrace change. 
The ESET Librarian also teaches, assists students and researchers in a 
one-on-one environment, and collaborates with professors in assigned academic 
departments.

ESSENTIAL DUTIES AND RESPONSIBILITIES include the following. Other duties may 
be assigned.

1. Maintains, enhances, and evaluates the library's existing technologies, and 
manages the technical aspects of the library's instance of Ex Libris' SFX
2. Provides leadership for the identification, assessment, and implementation 
of emerging technologies that further the library's mission and increase and 
enhance access to library resources and services
3. Provides efficient and effective management and leadership of the library's 
programmers
4. Leads the Electronic Services Team in incorporating appropriate design 
principles, information architectures, coding standards, and emerging 
technologies into the library's services to the community of users
5. Communicates with service or technology providers regarding agreements, 
contracts, or support
6. Ensures appropriate hardware, software, facilities, training and support are 
provided for library staff and clients
7. Gathers data about how Library users employ technology to access information
8. Collaborates with the library's Marketing Team to ensure that the Hekman 
Library's web site offers an accurate, intuitive, and user-friendly experience
9. Teaches research fluency skills in an introductory English course and in 
advanced courses in liaison areas
10. Staffs the research assistance desk occasionally during regular business 
hours, evenings, and weekends
11. Collaborates with professors in assigned academic departments
12. Performs administrative duties by attending library meetings and 
contributing to team efforts so the library can deliver high quality services
13. Participates in professional activities by attending national and regional 
conferences, by serving on college committees and by playing a visible role in 
the Calvin community and the broader library community to ensure professional 
growth

For additional information, or to apply, please see http://jobs.calvin.edu 


-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133

Re: [OPEN-ILS-GENERAL] ***SPAM*** Another serials question

[Dan Wells]

Hello Mary,

Sorry for the delayed reply.  What you are saying is correct in 2.0.  The 
original thinking was that we wanted a unit for every item, as one eventual 
goal is to be able to generate shelving location based holdings summaries.  
Without units, the serial items have no shelving location.  In 2.0, if one 
doesn't want to see received items in the OPAC, one might use a 
non-opac-visible location, status, or flag in their receive template to 
accomplish that, but that is more or less a workaround.

There is clearly demand for unit-less receiving, and the support already 
present in the Batch Receive interface has been extended to the Serial Control 
receiving interface as of 2.1.  To do so, select No Unit from the Set 
Current Unit selector when receiving.

Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 11/11/2011 at 12:17 PM, Mary Llewellyn mllew...@biblio.org wrote:
 Hi all,
 
 When you want to receive an issue without creating a unit/item, it appears
 to me that you have to use Serials Batch Receive, and cannot do it in the
 Serials Control View. Is this correct? If I try to receive an issue there,
 and it has no assigned Receive Unit Template, I get an error message:
 
 FIXME:  If you encounter this alert, please inform your IT/ILS helpdesk
 staff or your friendly Evergreen developers.
 
 Fri Nov 11 2011 12:13:02 GMT-0500 (Eastern Standard Time)
 
 cmd_receive_items failed!
 
 SERIAL_DISTRIBUTION_HAS_NO_COPY_TEMPLATE
 Units cannot be created for the given item because its associated
 distribution does not have a copy template.
 
 And if I did assign a receive unit template, but don't want items created, I
 don't see an option like that as I do in Serials Batch Receive. I'm kind of
 forced to create an item, even if I don't supply a barcode or call number. 
 
 Bug or feature?
 
 Thanks,
 
 Mary
 
 
 Mary Llewellyn
 Database Manager
 Bibliomation, Inc.
 Middlebury, CT
 mllew...@biblio.org

Re: [OPEN-ILS-GENERAL] Trying to do Overdues.

[Dan Wells]

Hello Liam,

No need to apologize, this is quite the amazing effort!

The only thing I would add at first glance is that there is also a specific
'Overdue Circulation' source.  If you use that one rather than 'Circulation',
it automatically covers the 'due date' and 'checkin time' filters, and also
filters out any items which are 'lost' or 'claims-returned'.

Dan

 On 10/25/2011 at 4:28 PM, Whalen, Liam liam.wha...@nrcan-rncan.gc.ca
wrote:
 Sorry about the horrible spelling. I was running it through the spell 
 checker, but I sent it before the check was complete.
  
 Liam
 
 
 
   From: open-ils-general-boun...@list.georgialibraries.org 
 [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
 Whalen, Liam
   Sent: October 25, 2011 16:12
   To: Evergreen Discussion Group
   Subject: Re: [OPEN-ILS-GENERAL] Trying to do Overdues.
   
   
   This will not send overdue notices to patrons.  It will simple create a

 report that can be emailed to staff, who can then contact patrons about 
 overdue items.

   In the Staff Client, click the 'Admin' link in the upper right corner:

   In 'Admin' click the 'Local Administrators' option.

   In 'Local Administrators' click the 'Reports' option.

   If you do not have a your Reports folders configured you will need to
do so 
 now:



http://docs.sitka.bclibraries.ca/Sitka/draft/html/folder.html#report-folder-cr

 eating

   Once you have your folders created, then you click the arrow beside the

 'Templates' link in the 'My Folders' section.

   From here, click on a folder you have setup to store your report
templates.

   There is a link on the right hand side of the screen that says 'Create
a new 
 Template for this folder', click that link.

   This takes you to the reports section.

   In this section click the 'Sources' drop down menu and choose, the 
 'Circulation' option.

   This will cause 'Circulation' to be displayed in the area below the 
 'Sources' drop down menu.

   Click the arrow besides 'Circulation' in this display area.  This will
show 
 you a list of options that can be included in your report, they are ordered

 alphabetically.

   Click the 'Patron' option, this will display a number of items in the
area 
 to the right of the 'Sources' screen.

   I'm going to choose the items I used in my report, but you can choose
any 
 item you see fit to include in your report.
   When choosing an item for the report, it is important to look at the
'Data 
 Type' column.  If the 'Data Type' is 'link' then you need to look further to

 find the details you want to display.

   For instance, under Patron there is a 'Mailing Address' option with a
'Data 
 Type' of link.  To get to the Mailing Address details you need to click the

 the arrow beside 'Patron', which will open up a subset of options to chose 
 from.  One of those options is 'Mailing Address' if you click 'Mailing 
 Address' you will now see the actually details for the patrons mailing 
 address displayed to the right. Many of these items have a 'Data Type' of 
 text.  Unlike the 'link' data type, the 'text' data type will display useful

 information in your report.  There are other data types that will display 
 useful information.  If I come across any while writing this I will make
note 
 of them.

   Ok, back to the report.

   So, once  you have clicked 'Patron' and have the list of items
displaying to 
 the right of the 'Sources' screen, you can click double click the 'First 
 Name' option which has a data type of 'text'.  This will add 'First Name' to

 your report.  You will see it show up in the 'Display Fields' tab in the 
 bottom section of the screen.  After you have double clicked 'First Name' do

 the same for 'Last Name', 'Daytime Phone', and 'Evening Phone'.  Next, click

 the arrow beside 'Patron', then click the 'Current Library Card' option.  In

 the screen to the right of 'Sources' double click the 'Barcode' option to
add 
 the patron's barcode to your report.  Now, above the 'Patron' option click 
 the arrow besides 'Circulating Item'.  In the items that appear below 
 'Circulating Item', click the 'Call Number/Volume' option.  In the window to

 the right of 'Sources' click 'Call Number Label' to add the call number to 
 your report.  Now, click the 'Circulating Item' link in the 'Sources'
window. 
  In the window to the right of Sources, click 'Barcode' to put the item's 
 barcode in your report.

   There is now a problem with your report.  You have two report items
named 
 Barcode (the user's barcode and the item's barcode).  Click once on the
first 
 Barcode in the 'Display Fields' screen.  This is the patron's barcode.  Then

 click the 'Alter Display Header' button.  

Re: [OPEN-ILS-GENERAL] Default state setting in patron driver's license field

[Dan Wells]

Hello Jesse,

On 1.6 you need to edit '/openils/var/web/xul/server/patron/ue_config.js'.  
Near the top you will find a 'defaultState' variable set to 'GA'.

Dan

 On 9/9/2011 at 6:54 AM, Jesse Ephraim jephr...@roanoketexas.com wrote:
 Does anyone know where to reset the default GA- that appears in the 
 driver's 
 license field when adding a new patron?  We would like to replace it with 
 TX- as the default.  We are on version 1.6.1.8.
 
 Thanks!
 
 Jesse Ephraim
 
 Director, Roanoke Public Library
 308 S. Walnut
 Roanoke, Texas 76262
 (817) 491-2691
 jephr...@roanoketexas.com

Re: [OPEN-ILS-GENERAL] Evergreen and LDAP

[Dan Wells]

Hello Lori,

There may be other cases where Patch Available would make sense, but at
least for this case, I think Under Development is our best bet (if such a
category already exists).  The patch which is available is quite old, and is
really more of a starting point than something which can simply be applied and
run without some additional tinkering.

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 7/27/2011 at 11:53 AM, Lori Bowen Ayre lori.a...@galecia.com wrote:
 Maybe we need to create new category called Patch Available or something
 like that?
 
 Lori
 
 On Wed, Jul 27, 2011 at 8:51 AM, Anoop Atre anoop.a...@mnsu.edu wrote:
 
 As a middle ground I'd say it's Under Development and once accepted into
 the core (or should it be when available in a release version) we set it
to
 Supported.

 Cheers


 On 07/27/2011 10:41 AM, Dan Scott wrote:

 On Wed, Jul 27, 2011 at 11:28 AM, Lori Bowen Ayrelori.a...@galecia.com
  wrote:

 Yes, thanks for the clarification Dan.  So, based on what you've said,
 I'm
 updating the Evergreen feature summary some of us are working on to
LDAP
 supported.   I've added it as feature SA537 (System Admin 537) in case
 anyone wants to review it.


 I'd say no, LDAP isn't supported, because Dan Wells' patch is not part
 of the core Evergreen code.



 --

 Anoop Atre
 IS Developer  Integrator, MnPALS
 PH: 507.389.5060
 OF: 3022 Memorial Library (Office-ML 3022)
 --
 Mit der Dummheit kämpfen Götter selbst vergebens
  ~ Johann Christoph Friedrich von Schiller

Re: [OPEN-ILS-GENERAL] Evergreen and LDAP

[Dan Wells]

Hello Lori,

I have moved the technical aspects of this discussion over to the Dev list.  I 
fully expect we will be able to make this happen for 2.2.  If you are not on 
the Dev list, you can follow the discussion here:

http://list.georgialibraries.org/pipermail/open-ils-dev/2011-July/007411.html

Thanks for pushing this forward!

Dan

 On 7/27/2011 at 5:12 PM, Lori Bowen Ayre lori.a...@galecia.com wrote:
 I support this idea as well.   How could we move the idea forward enough
 that I could shop the project around for other developers to help us with
 it?
 
 Lori
 
 
 On Wed, Jul 27, 2011 at 11:57 AM, David Fiander da...@fiander.info wrote:
 
 I would definitely support a pluggable authentication system, since
 different communities may use different authentication systems.


 On Wed, Jul 27, 2011 at 13:59, Galen Charlton g...@esilibrary.com wrote:

 Hi,


 On 07/27/2011 12:27 PM, Dan Wells wrote:

 There may be other cases where Patch Available would make sense, but at
 least for this case, I think Under Development is our best bet (if such
 a
 category already exists).  The patch which is available is quite old, and
 is
 really more of a starting point than something which can simply be
 applied and
 run without some additional tinkering.


 And mining the open-ils-dev archive more deeply, Dan's patch inspired Mike
 Rylander to do some brainstorming in late 2009 about adding a pluggable
 authentication system to Evergreen. [1]

 If folks are interesting in working on it, I'd love to see that discussion
 picked up again, as something like what Mike is proposing would mean much
 more than just LDAP support in core (though that would of course be a big
 win in and of itself).

 [1] http://list.georgialibraries.**org/pipermail/open-ils-dev/** 
 
 2009-December/005481.htmlhttp://list.georgialibraries.org/pipermail/open-ils-dev
  
 /2009-December/005481.html

 Regards,

 Galen
 --
 Galen Charlton
 Director of Support and Implementation

 Equinox Software, Inc. / Your Library's Guide to Open Source
 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 

Re: [OPEN-ILS-GENERAL] Evergreen and LDAP

[Dan Wells]

Hello Gordana,

We are currently using LDAP to authenticate.  I may be mistaken, but I believe 
the code attached to the following message is still our current version, with 
the one exception of an |= which is supposed to be an ||=.

http://list.georgialibraries.org/pipermail/open-ils-dev/2009-October/005293.html
 

There are a few different methods for using LDAP to authenticate, but in 
general it is not especially difficult.  This code uses one common method, but 
could be altered fairly easily to support others if the need exists.

The larger issue, as I see it, is working out the scaffolding (as Mike called 
it in the previous thread).  Since this has been lurking on my todo list for 
more than a year, I guess no time like the present.  I'll try to organize my 
thoughts within the next few days and post to the dev list, then return to this 
thread when something more concrete comes of it.

Thanks,
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 7/26/2011 at 3:39 PM, Gordana Vitez gvi...@niagaracollege.ca wrote:
 Hi there,
  
 Lori, thanks for the search suggestion. I should have mentioned in my email 
 that I did do the search but didn't find mention of anyone actually using it. 
 
  
 Jason, thanks for letting me know it's a no right now.
  
 Is this something other libraries might benefit from? Would this be more 
 trouble than it's worth to develop? or would there be interest in the 
 community to pursue LDAP for Evergreen?
  
 Thanks!
 Gordana
 
 Jason Etheridge ja...@esilibrary.com 7/26/2011 2:46 PM 
 If you go to the main Evergreen site (http://evergreen-ils.org) and use the
 Search Box in the right hand corner, you can search for LDAP and get a few
 hits from 2009.
 
 But to summarize here (since this thread is now also going to show up
 in such searches:)
 
 No, no LDAP support for Evergreen currently.
 
 However, there are folks that import/overlay patron data on a regular
 basis, including their foreign system passwords.
 
 It's also possible for other systems to authenticate against Evergreen
 (using SIP, ezproxy, etc.)

Re: [OPEN-ILS-GENERAL] apostrophe in title search causing problems (Bug #744513)

[Dan Wells]

Hello Gordana,

This was a skin level fix, so since you are using a custom skin ('nc'), it must 
be applied manually to your skin after upgrading.  Since the fix is simply 
deleting a single line, it should be pretty simple to take care of.  See here 
to view the actual change needed:

http://git.evergreen-ils.org/?p=Evergreen.git;a=blobdiff;f=Open-ILS/web/opac/skin/default/js/adv_global.js;h=897b1ea057cac0fc7b1c022c34e654ce2efe9dcf;hp=a6311b7ccdb76a85232a8f006eea08ff6971b21a;hb=04a9a2aaf7d17ce84a78ddf132fdb20486aa4218;hpb=f466fd7c66570af8f80e8ee085ff9c945aee8ffd

Note, though, that there may be other skin fixes between 2.0.2 and 2.0.7, so 
you may want to be more systematic about looking at all the 'default' skin 
changes from 2.0.2 to 2.0.7 and applying them to your custom skin.

Good luck!
Dan

-- 
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


 On 7/19/2011 at 12:16 PM, Gordana Vitez gvi...@niagaracollege.ca wrote:
 Hi everyone,
 
 We recently upgraded to 2.0.7 and noticed that a search using an apostrophe 
 in the staff client or the advanced search screen returns no results. For 
 example: searching cops don't cry in Niagara College's catalogue returns 
 the following results:
 
 http://niagaracollege.niagaraevergreen.ca/opac/en-CA/skin/nc/xml/rresult.xml? 
 if=it=bl=lf=a=la=cl=d=1l=2s=relsd=ascadt=mltp=t=keyword%3A%20cops%20don%20t%2
 0cryav=rt=multiol=2
 
 You'll notice that there is a space where the apostrophe should be. 
 
 I did find the following Bug #744513 that shows a fix was committed for 
 2.0.6. Is it possible that the fix wasn't committed to 2.0.7 or wasn't 
 included in upgrade instructions? Our upgrade was from 2.0.2 to 2.0.7.
 
 Thanks!
 Gordana
 
 Gordana Vitez
 Library Services  Systems Coordinator
 NC Libraries and Learning Commons
 Niagara College
 300 Woodlawn Rd
 Welland Ontario
 L3C 7L3
 Phone: (905) 735 2211 ext 7404
 Fax: (905) 736 6021
 gvi...@niagaracollege.ca