Re: [OPEN-ILS-GENERAL] Request to have a new company listed at Evergreen dokuwiki

[Vaclav Jansa]

Hi Rogan,
Thank you very much!

Vaclav

On Mon, Mar 11, 2019 at 1:02 PM Rogan Hamby 
wrote:

> Hi Jansa,
>
> This meets all the requirements so I will be glad to go ahead and add it.
>
>
>
> On Mon, Mar 11, 2019 at 5:21 AM Václav Jansa 
> wrote:
>
>> Dear all,
>>
>> We would like to have our non-profit listed at the dokuwiki page with
>> companies providing Evergreen-related services:
>> https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_companies.
>>
>> Based on requirements specified at
>> https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_companies:listing_policy
>> we have gathered the requested information and send it below:
>>
>> ---
>>
>> Name of company/organization:
>> Osvobozená knihovna, z. s.
>>
>> Contact person:
>> Václav Jansa
>>
>> Contact email:
>> i...@osvobozena-knihovna.cz
>>
>> Phone:
>> +420.604.172.718
>>
>> Web site address:
>> https://www.osvobozena-knihovna.cz/
>>
>> Brief description of services:
>> We have been involved in Evergreen promotion and implementation in the
>> Czech Republic since 2008. In 2017 we set up a non-profit organization
>> called Osvobozená knihovna, z. s., which offers a variety of services
>> related to Evergreen. These include consulting, implementation, data
>> migration and cleanup, support, hosting, staff training, and software
>> development to satisfy specific needs of Czech libraries. Any librarian
>> interested in trying Evergreen and/or cataloging his/her personal library
>> is welcome to join our Personal Library (
>> https://osobni.osvobozena-knihovna.cz/eg/opac/home) project for free.
>>
>> ---
>>
>> If there is agreement in the community that we can be listed, you can
>> either put the information up on the dokuwiki on our behalf, or Eva
>> Cerninakova (also a member of our non-profit organization) can add it to
>> the dokuwiki page since she has a dokuwiki account of her own.
>>
>> Thank you in advance for considering our request!
>> Vaclav Jansa
>> chairman of Osvobozena knihovna, z. s.
>>
>

Re: [OPEN-ILS-GENERAL] Problem with upgrade script 2.12.6-3.0.0 on line 6839

[Vaclav Jansa]

gt; transaction is aborted, commands ignored until end of transaction block
> psql:version-upgrade/2.12.6-3.0.0-upgrade-db.sql:6844: ERROR:  current
> transaction is aborted, commands ignored until end of transaction block
> psql:version-upgrade/2.12.6-3.0.0-upgrade-db.sql:6850: ERROR:  current
> transaction is aborted, commands ignored until end of transaction block
>
>
>
> I already try to check authority related scripts, but from my point of
> view, error is somewhere in our authority data in DB.
>
> Anybody else having the same experience? Do you have any idea how to
> find out what is causing the error?
>
> Do you have any tip, how to ad some debugging code into standard code,
> what will help us with finding probably failed data?
>
>
> Thanks for help and all recommendations
>
> Best regards
>
> Vaclav Jansa
>
>

Re: [OPEN-ILS-GENERAL] First beta release of Evergreen 3.0 available for testing

[Vaclav Jansa]

Hi all,
thanks for new EG beta tarbal. What is proposed ETA for OpenSRF 2.5.1
(maybe also in beta) tarball?

We will start ASAP with beta testing of localization.

Thanks and best regards

Vaclav

On Thu, Sep 7, 2017 at 2:23 AM, Galen Charlton 
wrote:

> Hi,
>
> The first beta release of Evergreen 3.0 is now available. For the full
> release announcement, please visit
>
> https://evergreen-ils.org/evergreen-3-0-first-beta-release-available/
>
> At this time, I would like to ask all Evergreen users and admins in a
> position to test the beta release to do so. Evergreen 3.0 is an
> ambitious release; the more bugs we can squash this month, the
> smoother the general release in early October will be.
>
> Many hands have contributed to the development of Evergreen 3.0, but
> for the purpose of this beta release milestone, I would like to
> specifically acknowledge the efforts of buildmasters Dan Wells and
> Blake Henderson, who built the beta tarball this evening.
>
> 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] Linking bibliographic records to non-LoC authorities using a support script

[Vaclav Jansa]

Hi,

We are trying to automatically link bibliographic records to authority
records using the authority_control_fields.pl support script (
http://docs.evergreen-ils.org/2.12/_support_scripts.html). We are currently
on 2.12.

It seems that the script is only aware of the default LoC Control Set as
mentioned in Mike's 2014 presentation (http://evergreen-ils.org/wp-
content/uploads/2014/04/eg14_Authorities-presentation-EGCON-2014.pdf,slide
19).

Is there a way to add custom control sets to the authority_control_fields.pl
script? So far we haven't been able to identify the right part of the
script which would indicate that only LoC Control Set is taken into
account...

Thank you in advance for any hints!

Vaclav

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

[Vaclav Jansa]

Hi Bill,
thanks for confirmation. Our testing environment is currently fully updated
from 2.8.2 to 2.10.2. Overall DB update process is without error.

Best regards

Vaclav Jansa

On Sun, May 1, 2016 at 5:17 PM, Bill Erickson <beric...@gmail.com> wrote:

> Hi Linda,
>
> On Sat, Apr 30, 2016 at 2:41 PM, Linda Jansova <skolk...@chello.cz> wrote:
> 
>
>> This time we experienced the same error (but involving a different copy
>> of the same serial):
>>
>> psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or
>> update on table "usr_circ_history" violates foreign key constraint
>> "usr_circ_history_target_copy_fkey"
>> DETAIL:  Key (target_copy)=(57113) is not present in table "copy".
>>
>> Could it be related to the bug fixed in 2.10.2 as described at
>> https://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_10.html#_evergreen_2_10_2
>> (Fixes a bug where serials checkouts failed for users that track
>> circulation history.)?
>>
>
> That's the one.  See more here:
> https://bugs.launchpad.net/evergreen/+bug/1564079
>
>
>> If so, what should we do to get rid of the error in our case when 2.10.2
>> has not been reached yet (in the upgrade process)?
>>
>
> The 2.10.2 fix includes a patch to the 2.9.3-2.10.0 upgrade script.
> You'll want to get the 2.10.2 code and use it to perform your 2.10.0
> upgrade (and ideally continue on to 2.10.2 to pick up more bug fixes).
>
> Hope this helps,
>
> --bill
>
>

Re: [OPEN-ILS-GENERAL] Problem registering new patron

[Vaclav Jansa]

Hi Dawn,
in original state is our EG set with shorter org tree. Cons - Branch. No
editable fields in registration form are visible.
After changing org tree to classic layout cons-sys-branch everything work's
fine.

Best regards
Vaclav
On May 12, 2014 3:23 PM, Dale, Dawn dd...@georgialibraries.org wrote:

 Hi Eva,

 Your staff member needs a working location set.  At the top of the
 permissions screen you should have a list of working locations.  Choose at
 least one of those for your staff member, preferably the location where the
 staff member is working. That should fix the problem.  They may need to log
 out and back in for it to take affect.

 Dawn Dale
 PINES Helpdesk Manager
 Georgia Public Library Service
 1800 Century Place
 Suite 150
 Atlanta, GA 30345
 404-235-7136
 dd...@georgialibraries.org

 - Original Message -
 From: Cerninakova Eva cer...@jabok.cz
 To: Evergreen Discussion Group 
 open-ils-general@list.georgialibraries.org
 Sent: Sunday, May 11, 2014 9:12:51 AM
 Subject: [OPEN-ILS-GENERAL] Problem registering new patron



 In a new Evergreen system we have a problem registering
 patrons. Staff (except admin account) is not able to register new patron or
 edit patron account information - only some fields are displayed, see
 http://knihovna.jabok.cz/Evergreen/snapshots/edit_patron.jpg or or
 http://knihovna.jabok.cz/Evergreen/snapshots/register_patron.jpg .

 Staff permission groups have following configurations:
 Editing permission: group_application.user.patron or
 group_application.user.staff
 Parent group: Staff

 Group permissions:
 CREATE_USER
 CREATE_USER_GROUP_LINK
 DELETE_USER
 UPDATE_USER
 VIEW_USER
 group_application.user
 group_application.user.patron
 group_application.user.staff

 We don´t know what does the USER_BTYPE mean, but we also tried adding:
 CREATE_USER_BTYPE
 DELETE_USER_BTYPE
 UPDATE_USER_BTYPE
 VIEW_USER_BTYPE

 Permission mentioned above are granted to staff accounts both on the
 permission group level and for individual user (via user permission editor).

 Staff accounts have assigned appropriate working location too.

 Registering new patron is impossible even for the local system
 administrator account, that have all above mentioned permissions granted
 for the consortium depth (and can also grant them) and has the 'EVERYTHING'
 permission granted on the branch level.

 Is there anything else that should be set up to enable staff to edit or
 register new user?

 Thanks for any ideas

 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
 IČO: 45769621, DIČ: CZ45769621
 Č. ú. 1993 04/5500 - Raiffeisenbank