- Koha-devel - lists.koha-community.org

Use DateTime::Format::Strptime in Koha::DateUtils
by dcook＠prosentient.com.au 06 Aug '20

06 Aug '20

Hi all, I needed to parse a string into a DateTime object, so I decided to take a look at Koha::DateUtils, and I was surprised to see that we're parsing dates the hard way. We really should look at using DateTime::Format::Strptime instead. I use it in other Perl projects, and it makes life much easier. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1

New 'configurations' table (26129)
by Tomas Cohen Arazi 05 Aug '20

05 Aug '20

TL;DR; This email is for getting some feedback about a new table I'm proposing to add that implements a pattern I'm seeing more and more often as required: global, and per-library, per-item type and per-category settings. It can be easily extended with new constraints as well. Hi all, I wanted to highlight bug 26129 [1] which proposes to add a new table, for storing configuration entries. It differs from the systempreferences table basically on the ability to set values with per-library, per-item type and per-category basis, as well as default catch-all. It is the result of noticing that the smtp_servers table I was going to add on bug 22343 [2], could be easily generalized and could become useful. If someone is willing to do it, we could migrate systempreferences into this new table, but that definitely deserves more thinking. The SMTP configuration page won't live in the sysprefs page, and so a way to differentiate them could be added. One sample use of this configurations table, could be moving z39.50 servers there. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26129 [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 8

--username and --password in process_message_queue.pl
by Tomas Cohen Arazi 03 Aug '20

03 Aug '20

Hi everyone. I'm finishing my work to make SMTP something configurable from the UI with multiple options and per-library configs [1]. I am right now tweaking all the places that send emails so they use this configurations. The only place where things aren't clear regarding what to do, is process_message_queue.pl, which has the following parameters: --username --password They are used to authenticate the SMTP request. The current behaviour is that all email-related stuff points to localhost, and those params are used to authenticate the SMTP connection. Does anyone use them? Is is ok to assume they should supersede the ones defined in the new configuration? Have a great weekend you all [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Koha Community Newsletter: July 2020
by Koha Newsletter 01 Aug '20

01 Aug '20

The Koha Community Newsletter for July 2020 is here: https://koha-community.org/koha-community-newsletter-july-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

ModBiblio function error
by Stephen Graham 31 Jul '20

31 Jul '20

Hi All - I have a script which uses the ModBiblio function (i.e. https://perldoc.koha-community.org/19.11.x/C4/Biblio.html#ModBiblio) I haven't used the script for a while, and we've upgraded to 19.11 since I ran it last. Running the script today and I'm getting the following "error": oAuth error: Database unavailable (109) authorities Bib-1 I'm seeing this 4-5 times for each bibilo I've updated. The update does work. The record looks fine in staff/OPAC, it's findable etc. I've only updated 10 records on our test server, and before I update any more I'm just wondering why I'm getting this message and it will have an adverse effect on our indexing/database if I just ignore and update the reamining 6000+ records? Any advice would be most welcome! Cheers, Stephen -------------------------------------- Stephen Graham Library Technology Consultant Content and Collections Team Library and Computing Services University of Hertfordshire Tel: 01707 286111 Ext: 77751 Email: s.graham4(a)herts.ac.uk<mailto:s.graham4@herts.ac.uk>

5 9

Safari browser and Koha
by dcook＠prosentient.com.au 31 Jul '20

31 Jul '20

Hi all, Does anyone use Safari with Koha? I had someone using it the other day and they weren't able to upload a MARC file to the Staged MARC Management. I just had them use Firefox instead and it was fine though. What's our stance on Safari support? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

5 6

Connecting Koha to OCLC via Z39.50 server
by Monica Benavides 29 Jul '20

29 Jul '20

Our library recently created a z39.50 server (Koha 20.05). We are implementing OCLC Discovery. They can successfully connect to our server, but the connection closes during the attempt to retrieve the data (init 1020 error). How do we allow the connections to stay open in order for OCLC to retrieve our information? Thanks in advance! This XML file does not appear to have any style information associated with it. The document tree is shown below. <zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/"> <zs:version>1.2</zs:version> <zs:echoedSearchRetrieveRequest> <zs:version>1.2</zs:version> <zs:queryType>pqf</zs:queryType> <zs:query>@attr 1=1211 @attr 5=100 471460745</zs:query> <zs:maximumRecords>5</zs:maximumRecords> <zs:recordPacking>xml</zs:recordPacking> <zs:recordSchema>marcxml</zs:recordSchema> <zs:extraRequestData> <zs:target>REDACTED/biblios</zs:target> <zs:max-sockets>60</zs:max-sockets> </zs:extraRequestData> </zs:echoedSearchRetrieveRequest> <zs:diagnostics xmlns:diag="http://www.loc.gov/zing/srw/diagnostic/"> <diag:diagnostioc> <diag:uri>info:srw/diagnostic/l/2</diag:uri> <diag:details> session_shared: target closed connection during init </diag:details> <diag:message>System temporarily unavailable</diag:message> </diag:diagnostic> </zs:diagnostics> </zs:searchRetrieveResponse> -- *Monica Benavides* *Library Assistant/Testing Center Coordinator* –––––––––––––––––––––––––––––––––––––––––––––––––––– *Rocky Mountain University of Health Professions* 122 East 1700 South, Building 3, Provo, Utah 84606 Direct: 385.375.8772 *|* Campus: 801.375.5125 –––––––––––––––––––––––––––––––––––––––––––––––––––– *Stay connected, learn more!* Blog <https://rmuohp.edu/about-the-university/university-news/> | Facebook <https://www.facebook.com/RMUoHP> | Twitter <https://twitter.com/rmuohp> | YouTube <https://www.youtube.com/user/TheRMUoHP> | rm.edu

2 1

Signoff request
by Marcel de Rooy 29 Jul '20

29 Jul '20

Hi all, I submitted patches on bug 20472. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20472 Add digital scan as optional format to Article Requests Please have a look. More work to follow. Marcel

1 0

sample_notices.yml instead of sql
by Marcel de Rooy 28 Jul '20

28 Jul '20

Hi all, What is the current procedure around changing notices and translation? I see that we have an English yml file, but I see sql files in the translated languages. Like de-DE/mandatory/sample_notices.sql We dont have a coding guideline yet about this. Should it be added? If I change an English notice, should I still change the other languages ? Thanks, Marcel

2 1

Autentication LDAP Error Koha 20.05
by Humberto Blanco Castillo 27 Jul '20

27 Jul '20

Hi for all, We are trying to connect koha to LDAP, but appears as credentials its not working, and cant fount what the problem its. this configuration works fine in production environment in version 3.16 Follow are the paras in the /etc/koha/sites/catalogo/koha-conf.xml file <useldapserver>1</useldapserver> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>ldap://ourldapServer:389</hostname> <base>DC=University,DC=EDU</base> <user>CN=ldap_user,OU=Cuenta de servicio,DC=University,DC=EDU</user> <pass>myPassword</pass> <replicate>1</replicate> <update>0</update> <auth_by_bind>1</auth_by_bind> <anonymous_bind>0</anonymous_bind> <update_password>0</update_password> <principal_name>%s(a)urosario.edu.co</principal_name> <mapping> <firstname is="givenName" ></firstname> <surname is="sn" ></surname> <userid is="cn"></userid> <email is="mail"></email> <phone is="telephonenumber"></phone> <cardnumber is="postOfficeBox"></cardnumber> </mapping> </ldapserver> We test the connection from the command line, so: export PERL5LIB=/usr/share/koha/lib/ && export KOHA_CONF=/etc/koha/sites/catalogo/koha-conf.xml && perl /usr/share/koha/opac/cgi-bin/opac/opac-user.pl userid=humberto.blanco password=password_for_humberto.blanco and gets the following error: LDAP bind failed as kohauser humberto.blanco: LDAP error #49: LDAP_INVALID_CREDENTIALS# The wrong password was supplied or the SASL credentials could not be processed Does no matter what kind of information i put on the password field, ever gets the same error. any idea? -- sincerelly, Humberto Blanco

2 1