[OPEN-ILS-GENERAL] z39.50 character set negotiation?

[Jane Sandberg]

Hi all,

OCLC made updates to its z39.50 service on Sunday, and since then,
it's been sending badly encoded characters like nobody's business.
I've been able to find out how to get uncorrupted characters in
yaz-client, but I don't know how to get Evergreen to do the extra
utf-8-setting step detailed below.

Example one: just regular old searching (doesn't work)

$ yaz-client zcat.oclc.org:210/OLUCWorldCat
Z> authentication user/pass
Z> init
Z> find 9786070131356
Z> show 1

100 1  $a Plans, Juan Jose, $e compiler.
245 10 $a Los mejores relatos de terror llevados al cine / $c
seleccion, prologo y notas de Juan Jose Plans.
250$a Segunda edicion
264  1 $a Mexico, D. F. : $b loqueleo, $c 2016.


Example two: specifying utf-8 (which does work)

$ yaz-client zcat.oclc.org:210/OLUCWorldCat
Z> charset utf-8
Z> authentication user/pass
Z> init
Z> find 9786070131356
Z> show 1

100 1  $a Plans, Juan José, $e compiler.
245 10 $a Los mejores relatos de terror llevados al cine / $c
selección, prólogo y notas de Juan José Plans.
250$a Segunda edición
264  1 $a México, D. F. : $b loqueleo, $c 2016.


Is there an Evergreen setting somewhere that would specify a charset
and fix this problem?

Thanks!

  -Jane

-- 
Jane Sandberg
Electronic Resources Librarian
Linn-Benton Community College
sand...@linnbenton.edu / 541-917-4655
Pronouns: she/her/hers or they/them/theirs

[OPEN-ILS-GENERAL] Includes from Library Setting in Webclient

[Lynn Floyd]

I am working on the documentation for formation receipts in the Web client.  I 
know we use the Includes alert_text, event_text, footer_text, header_text, and 
notice_text.  I am trying to get them to work with the web client.  I have 
tried several methods to get them to work, but I have not had any luck.

 

Any suggestions on how to get them to show up in the web client?

 

 

 

Lynn Floyd 
lfl...@andersonlibrary.org 
Anderson County Library 
864-260-4500 x181 
http://www.andersonlibrary.org   
  

 

From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Terran 
McCanna
Sent: Tuesday, March 21, 2017 12:07 PM
To: cerninak...@jabok.cz; Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Evergreen translations DokuWiki page

 

This is excellent, Eva! We will be sure to point people to this page when we do 
our translation session at the Evergreen Conference next month.

Thank you!

Terran




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

 

On Mon, Mar 20, 2017 at 7:06 AM, Cerninakova Eva  wrote:

Hi all,

I have added information  concerning  Evergreen translations  and related 
topics (like translations workflow, useful tips for translators etc.) to 
Evergreen DokuWiki,
see https://wiki.evergreen-ils.org/doku.php?id=eg_translations
The page is intended primarily for translators (but some information might be 
probably useful for others too).

If you have any comments or suggestions for improving, you are welcome to send 
me note or directly edit the DokuWiki page.

Eva






 

---

Mgr. Eva Cerniňáková
cer...@jabok.cz

Tel. +420 211 222 409  

Knihovna Jabok
http:/knihovna.jabok.cz
Tel.  +420 211 222 410  
Jabok - Vyšší odborná škola sociálně pedagogická a teologická
Salmovská 8, 120 00 Praha 2

 



Lynn Floyd
Head of Information Technology
Anderson County Library
Anderson, SC
lfl...@andersonlibrary.org

[OPEN-ILS-GENERAL] Proposal to be release manager for Evergreen 3.0

[Galen Charlton]

Hi,

I am putting my hat in the ring to be release manager for Evergreen
3.0 as the autumn 2017 release of Evergreen. As has been discussed by
the development community, most recently during the Hack-A-Way, 3.0
would represent the first release where the community supports and
recommends the web staff client for full production use. 3.0 would
also mark the deprecation of the XUL staff client.  As release
manager, I would commit to helping the Evergreen developers achieve
that goal.

Specific areas of functionality that I will help provide code and
tests for over the next few months include the web staff serials
interface, offline circulation, and general tidying up of loose ends.

However, the primary role of a release manager is much more about
enabling others to contribute to Evergreen — and to get feedback more
quickly. To that end, as release manager I propose to do the following
to improve the state of the pullrequest queue:

[1] Organize at least one event that, for the purposes of this
proposal, I'll call a "feedback fest", loosely based on PostgreSQL's
commitfests.  This would be an exercise during the course of a week
where every single pull request would be reviewed with the goal of
deciding whether it is still applicable and ready for merging, if it
needs additional work (and then identify what that work is), or if it
should not be merged. During this week, I would be actively pinging
developers and testers who are in a good position to review a given
pull request.

The feedback fest would complement Bug Wrangling week with its goal of
getting eyes on _every_ pull request and with a particular focus on
those pull requests that have been languishing the longest.

I would aim to have the feedback fest occur in the middle of the
release cycle; if it is successful, I would then consider calling a
feedback fest prior to feature freeze as a way of better managing the
typical end-of-cycle merge rush.

[2] Organize the creation of a biweekly email update to the
development list that would summarize recent changes in master,
identify bugs and architectural issues that deserve wide attention,
and acknowledge folks for their contributions.

[3] Organize the creation of a development dashboard for the website.
My vision is that it would serve as a way for folks to find things to
do and see who has been active, similar to what
http://dashboard.koha-community.org/ offers, but with an emphasis on
noting progress of the race towards 3.0.

As far as the release schedule is concerned, I would plan on setting
release for September or possibly October 2017, as per usual practice,
but I would first want to have a brief discussion in open-ils-dev to
decide whether we may need to allow ourselves a bit more time
(measured in weeks, not months) to reach our target of full support of
the web staff client in production.

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Open Library Initiative
phone:  1-877-OPEN-ILS (673-6457)
email:  g...@equinoxinitiative.org
web:  https://equinoxInitiative.org
direct: +1 770-709-5581
cell:   +1 404-984-4366

[OPEN-ILS-GENERAL] SFC Membership Review

[Tim Spindler]

The Evergreen Oversight Board (EOB) has been looking at alternatives to
membership in the Software Freedom Conservancy (SFC).  The SFC currently
provides service that include


   - Bookkeeping and accounting services
   - Access to Eventbrite (event registration software for the annual
   conference)
   - Resources for defending the Evergreen trademark
   - Maintaining liability insurance for the conference

Our needs and the SFC ability to meet these needs are no longer as good a
match as we would like. Therefore, the EOB is exploring additional options.

One of the options we are exploring is for a non-profit within the
Evergreen community to provide these services. We are still in the very
early stages of this research and wondering if there are currently
organizations who are Evergreen users who might be capable and willing to
provide a similar set of services. These services could be done under
contract with a newly formed Evergreen non-profit or contained entirely
within the organization as it currently stands with the SFC. Ideally the
organization would already be able to provide the above services.

If your organization has an interest in providing these types of services
please send me (tspind...@cwmars.org) a message.

This involves no commitment from any organization. Any move forward would
still require a formal process to vet and select the organization to take
on these responsibilities. Our purpose at this time is to determine
interest.

Thanks,

-- 

Tim Spindler | Executive Director

tspind...@cwmars.org | 508-755-3323 x120 <(508)%20755-3323>

C/W MARS | http://www.cwmars.org

67 Millbrook St., Ste. 201

Worcester, MA 01605

-- 
Tim Spindler
tjspind...@gmail.com

*P**   Go Green - **Save a tree! Please don't print this e-mail unless it's
really necessary.*

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] Evergreen translations DokuWiki page

[Terran McCanna]

This is excellent, Eva! We will be sure to point people to this page when
we do our translation session at the Evergreen Conference next month.

Thank you!
Terran


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


On Mon, Mar 20, 2017 at 7:06 AM, Cerninakova Eva  wrote:

> Hi all,
>
> I have added information  concerning  Evergreen translations  and related
> topics (like translations workflow, useful tips for translators etc.) to
> Evergreen DokuWiki,
> see https://wiki.evergreen-ils.org/doku.php?id=eg_translations
> The page is intended primarily for translators (but some information might
> be probably useful for others too).
>
> If you have any comments or suggestions for improving, you are welcome to
> send me note or directly edit the DokuWiki page.
>
> Eva
>
>
>
>
>
> ---
> Mgr. Eva Cerniňáková
> cer...@jabok.cz
> Tel. +420 211 222 409 <+420%20211%20222%20409>
>
> Knihovna Jabok
> http:/knihovna.jabok.cz
> Tel.  +420 211 222 410 <+420%20211%20222%20410>
> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
> Salmovská 8, 120 00 Praha 2
>
>

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

[Daniel Wells]

[I apologize for possible duplication; my calvin.edu email is getting
"greylisted" by the mailing list, so I am sending this a second time from
Gmail.]

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 superseded.  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

Re: [OPEN-ILS-GENERAL] Reports - circulation count by call number

[Trisha Cantwell Keene]

Thank you Beth.
This is great.
Take care.
Trisha

On Tue, Mar 21, 2017 at 11:42 AM, Willis, Beth  wrote:

> Hi Tricia,
>
> We have a report template that filters on owning library, checkout date
> (range) and copy location.  The last filter could easily be dropped if not
> relevant for your library.
>
> I have attached screenshots of our template configuration.
>
> Please let me know if you have any questions.
>
> I hope this helps.
> Beth
>
>
>
> On Wed, Mar 15, 2017 at 3:19 PM, Trisha Cantwell Keene 
> wrote:
>
>> Does anyone a report template for a report filtering by library and check
>> out date and giving a circulation count by item or grouped by call number?
>>
>> I have tried changing circulation count by location to 'by call number'
>> and thought of trying to add circulation count to an inventory report.
>>
>> Any help appreciated! Thank you.
>>
>>
>> --
>> Trisha Cantwell Keene
>> Associate Director
>> Thorndike Library
>> College of the Atlantic
>> 109 Eden St.
>> Bar Harbor, ME  04609
>>
>> (207) 801-5661
>> (207) 288-2328 Fax
>> tcantw...@coa.edu
>>
>> "Google can bring you back a hundred thousand answers. A librarian can
>> bring you back the right one."  The Guardian (London)
>>
>
>
>
> --
> Beth Willis
> Digital & Catalog Librarian
> NOBLE, Inc.
> 26 Cherry Hill Drive
> Danvers, MA 01923
>



-- 
Trisha Cantwell Keene
Associate Director
Thorndike Library
College of the Atlantic
109 Eden St.
Bar Harbor, ME  04609

(207) 801-5661
(207) 288-2328 Fax
tcantw...@coa.edu

"Google can bring you back a hundred thousand answers. A librarian can
bring you back the right one."  The Guardian (London)

Re: [OPEN-ILS-GENERAL] Reports - circulation count by call number

[Willis, Beth]

Hi Tricia,

We have a report template that filters on owning library, checkout date
(range) and copy location.  The last filter could easily be dropped if not
relevant for your library.

I have attached screenshots of our template configuration.

Please let me know if you have any questions.

I hope this helps.
Beth



On Wed, Mar 15, 2017 at 3:19 PM, Trisha Cantwell Keene 
wrote:

> Does anyone a report template for a report filtering by library and check
> out date and giving a circulation count by item or grouped by call number?
>
> I have tried changing circulation count by location to 'by call number'
> and thought of trying to add circulation count to an inventory report.
>
> Any help appreciated! Thank you.
>
>
> --
> Trisha Cantwell Keene
> Associate Director
> Thorndike Library
> College of the Atlantic
> 109 Eden St.
> Bar Harbor, ME  04609
>
> (207) 801-5661
> (207) 288-2328 Fax
> tcantw...@coa.edu
>
> "Google can bring you back a hundred thousand answers. A librarian can
> bring you back the right one."  The Guardian (London)
>



-- 
Beth Willis
Digital & Catalog Librarian
NOBLE, Inc.
26 Cherry Hill Drive
Danvers, MA 01923

[OPEN-ILS-GENERAL] Minimum PostgreSQL requirements for 2.12 and 3.0

[Kathy Lussier]

Hi all,

At the developer's meeting earlier this month, with a follow-up 
discussion on the open-ils-dev list, the developers decided on the 
following requirements for Postgres support in Evergreen:


- For the 2.12 release (scheduled for tomorrow), deprecate Postgres 9.3 
support and recommend use of Postgres 9.4.


- For the 3.0 release (September), make Postgres 9.4 a minimum requirement.

A primary reason for this recommendation is an upcoming search 
development project, expected to be done for the 3.0 release, that will 
require database functions only available in 9.4+. The goal of this work 
is to eliminate two-stage search from Evergreen, leading to a more 
complete set of search results. Early analysis has also shown that we 
will see performance improvements with this work, particularly with more 
selective searches.


Postgres 9.4 has been in release since December 2014 and is already used 
successfully in production at many Evergreen sites. The new requirement 
will not impact any Evergreen releases prior to the 2.12 release. Any 
new features that depend on 9.4 will only make an appearance in 
Evergreen 3.0 or later.


Feel free to let us know if you have any questions!
Kathy

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

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

[Jason Stephenson]

Nawras,

Is the websockets instance of Apache running?

You can check by doing "ps ax | grep websockets" on the server.

If you don't seen any running, you'll need to start per the instructions
in the OpenSRF README.

Good luck,
Jason

On 03/21/2017 07:34 AM, nawras ali wrote:
> Thank you for the reply!
> 
> 
> I have self signed SSL cert. only. I entered the the username and the
> password in the page https://my-ip/eg/staff. But nothing happened. I
> didn't get redirected to any page.
> 
> I also tried to connect through the port 7682 as Eva suggested,
> unfortunately, it did not work for me :(
> 
> I also tried to connect to the web client using the URL:
> http://my-ip/eg/staff, I got a 403 error (Forbidden: You don't have
> permission to access /eg/staff/login on this server.)
> 
> Is there any way to log in to the web client with self-signed cert.??
> 
> Thank you, I appreciate your help!
> 
> 
> Nawras Ali ,
> Learn with Naw 
> Regards*,
> *
> 
> On Mon, Mar 20, 2017 at 2:03 PM, nawras ali  > wrote:
> 
> Hello everyone,
> 
> I installed Evergreen ILS, and everything works properly.
> 
> However, when I try to log in to the web client through the URL:
> https://eg/staff/, nothing happens.
> 
> Is there any special setup I should make in order to log in to the
> web client??! Did I miss any step through the installation process
> (I followed the steps mentioned in the installation guide) ?!
> 
> Thank you!
> 
> Nawras Ali ,
> Learn with Naw 
> Regards*,
> *
> 
> 

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

[nawras ali]

Thank you for the reply!


I have self signed SSL cert. only. I entered the the username and the
password in the page https://my-ip/eg/staff. But nothing happened. I didn't
get redirected to any page.

I also tried to connect through the port 7682 as Eva suggested,
unfortunately, it did not work for me :(

I also tried to connect to the web client using the URL:
http://my-ip/eg/staff, I got a 403 error (Forbidden: You don't have
permission to access /eg/staff/login on this server.)

Is there any way to log in to the web client with self-signed cert.??

Thank you, I appreciate your help!


Nawras Ali ,
Learn with Naw 
Regards
*,*

On Mon, Mar 20, 2017 at 2:03 PM, nawras ali  wrote:

> Hello everyone,
>
> I installed Evergreen ILS, and everything works properly.
>
> However, when I try to log in to the web client through the URL:
> https://eg/staff/, nothing happens.
>
> Is there any special setup I should make in order to log in to the web
> client??! Did I miss any step through the installation process (I followed
> the steps mentioned in the installation guide) ?!
>
> Thank you!
>
> Nawras Ali ,
> Learn with Naw 
> Regards
> *,*
>