- Koha - lists.katipo.co.nz

koha-US June 2021 Events & Meetings
by Jason Robb 01 Jun '21

01 Jun '21

koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. For Google Calendar users, add our events calendar to your list for easy access to meeting times and links: https://calendar.google.com/calendar/u/1?cid=a29oYS11cy5vcmdfZG1xb2pkczE5Zn… *Meetings* Board Meeting - Wednesday, June 2nd @ 8:30a PT / 11:30a ET / 15:30 UTC - Meeting Link - https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 - Agenda - https://docs.google.com/document/d/1chju7Tr3jsM54BRC_gZH8LHTFWF3y-HVQcAz8dW… General Meeting - Wednesday, June 9th @ 8:30a PT / 11:30a ET / 15:30 UTC *Special Interest Groups* Circulation - Tuesday, June 1st (*today!*) @ 10:00a PT / 1:00p ET / 17:00 UTC Cataloging - Thursday, June 3rd @ 8:00a PT / 11:00a ET / 15:00 UTC System Administration - Tuesday, June 8th @ 9:00a PT / 12:00p ET / 16:00 UTC Acquisitions - Tuesday, June 15th @ 9:00a PT / 12:00p ET / 16:00 UTC Web Development - Thursday, June 17th @ 10:00a PT / 1:00p ET / 17:00 UTC Books & Crafts - Wednesday, June 30th @ 5:00p PT / 8:00p ET / 00:00 UTC Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Jason Robb koha-US Secretary secretary(a)koha-us.org

1 0

Automated Way to Construct Field 2 from Field 1
by Charles Kelley 01 Jun '21

01 Jun '21

Hello, all! A bit off topic from Koha, but here goes. Our catalog has quite a few records that have translated title (242) fields. Alas, while the translated titles display in the OPAC and the staff cataloging module, they are not searchable. Through experimentation, I have learned that by reproducing the 242 field into a 740 field, the translated title will indeed be both displayable and searchable. I don't think Koha can help with this, but maybe MarcEdit can. Does anyone remember a video or document (PDF or DOC) about MarcEdit that allows building a field from the elements of another field? Is it the swap utility in MarcEdit Many thanks. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

Update EAN13-label printout
by kamilla.braun＠boenischnet.de 31 May '21

31 May '21

Hello Koha-Mailinglist, in the meanwhile I was tying to find reasons for this strange behavior. First the good news: The Koha-generated EAN13-barcode in itself is correct. However: 1. All QR/barcode-code readers suppress the very first leading zero ONLY, if there is any. This leads to the problem, that sometimes it outputs only 12 instead of 13 digits. 2. All QR/barcode-code readers also print out the last check-digit. This leads to the error, that the Koha search function is not working, as the last digit is a check-digit, it is by the EAN13 definition not part of the payload-data and thus must not be a part of the assigned book/shelf-number. You may easily check this using a free QR-code reader on a smartphone (i.e. Lightning QR). I hope somebody is interested in this, because the labeling and serach functions are essentials parts of a professional library system. Best Regards Kamilla Braun

1 0

Koha Community Newsletter: May 2021
by Koha Newsletter 30 May '21

30 May '21

The Koha Community Newsletter for May 2021 is here: * https://koha-community.org/koha-community-newsletter-may-2021/ Many thanks to everyone who submitted articles and news to last month's newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

How to setup Holds in Koha
by Tadas G 30 May '21

30 May '21

Hello, We have Koha installed in our server for education purposes, everything looks fine, but there are a few issues: 1. We decided to use Hold function to reserve a book for patron. But, i.e., if there is only one book, many patrons are able to reserve a book using Hold function. Is it possible to make a book reservation only for one patron (one book -> one patron reservation; two books -> two patrons reservations; etc.)? 2. Is it possible to create automatic term for holds? I.e. reservation for the book could be made only for three days (and if you won't come to take your holding from library, it returns to library without Hold tag)? How to do it? Thanks for the help

2 1

odd error messages setting up Apache during install
by David Lesniaski 29 May '21

29 May '21

Ok, I'm installing the current version of koha on a debian server. I have a DNS and have pointed it to the IP address. Installed Koha. I think. Ditto Apache. When I get to creating the name of the library: sudo koha-create --create-db libraryname and I create a name for the library, say MYLIB I get this error message: ---------- sudo: unable to resolve host dalkoha: Name or service not known AH00557: apache2: apr_sockaddr_info_get() failed for dalkoha AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message AH00557: apache2: apr_sockaddr_info_get() failed for dalkoha AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message AH00557: apache2: apr_sockaddr_info_get() failed for dalkoha AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message adduser: Please enter a username matching the regular expression configured via the NAME_REGEX configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. ----------- dalkoha is the "internal" name of my server (I'm using Linode to host the server, and I picked "dalkoha" as the name of my server). So why apache is looking for this in the first place I have no idea. I did edit the config file to replace the domain with my actual DNS -- so I am not sure why apache isn't looking for that. the 127 ... stuff is in the config file (I really don't know what it's doing there) but I did not see any instructions during the install that said to change this. So how do I get apache to "find" my actual web address? Should I just ditch all this and do an IP address install? Many thanks for any advice you can give. If this is so basic or obscure that there is no need to clutter the list with a list reply, just reply to me at the email below. -- David Dr. David Lesniaski Associate Professor MLIS Program St. Catherine University 2004 Randolph Ave. #4125 St. Paul, MN 55105 dalesnaski(a)stkate.edu he, him, his

2 1

Install database on different server than Koha?
by Bales (US), Tasha R 28 May '21

28 May '21

Good morning, My team is working on implementing Koha on Oracle Linux and so far it's worked out. We are getting ready to test to see if we can swap out Maria DB with Percona MySQL Server, which seems uncomplicated. I'd like to ask if anyone has set up Koha to operate with a database that is on a separate server (separate virtual machines on the same network), as opposed to embedded with Koha. My first thought is that it should work if Koha and Percona can talk to each other, but how is that achieved? Perhaps it's a matter of updating a couple configuration files, or maybe it's totally impossible. Any ideas? Thanks for your time and consideration! Tasha R. Bales | Business Support Team Information Services | Enterprise Services Enterprise Operations, Finance and Sustainability

2 2

EAN13-label printout incorrect with attachment-link
by kamilla.braun＠boenischnet.de 28 May '21

28 May '21

Hello Koha-Mailinglist, related to a rejected bug-report I found out, that the KOHA-printout of EAN13-lables may be incorrect. My professional-grade USB-barcodereader (Manhattan 177665) is reproducibly reading only 12 digits instead of 13 digits. On some reason the first digit is missing. I've checked it many times also with a plain text-document where the numbers are typed in as if they are coming from a keyboard. Standard ISBN-book-labes (EAN13) are read correctly with all 13 digits. Did anybody came acrosse the same or a similar problem, or is able to reproduce it? Please also refer to my KOHA-printout of EAN13-lables in the attachment-link below. Download-Link: https://wetransfer.com/downloads/ad79c35825961962c0f4726d702710832021052810… Best Regards Kamilla Braun

1 0

EAN13-label printout incorrect
by kamilla.braun＠boenischnet.de 27 May '21

27 May '21

Hello Koha-Mailinglist, related to a rejected bug-report I found out, that the KOHA-printout of EAN13-lables may be incorrect. My professional-grade USB-barcodereader (Manhattan 177665) is reproducibly reading only 12 digits instead of 13 digits. On some reason the first digit is missing. I've checked it many times also with a plain text-document where the numbers are typed in as if they are coming from a keyboard. Standard ISBN-book-labes (EAN13) are read correctly with all 13 digits. Did anybody came acrosse the same or a similar problem, or is able to reproduce it? Please also refer to my KOHA-printout of EAN13-lables in the attachment. (Sorry now with attachment...) Best Regards Kamilla Braun

1 0

Koha - Active Directory LDAP struggles
by Michael BC 27 May '21

27 May '21

I've tried searching the archives and can't seem to find the answer. When we use a correct username/password, the login page generates a Software Error: LDAP search failed to return object : 0000208F: LdapErr: DSID-0C090AC0, comment: Error processing name, data 0, v3839 at /usr/share/koha/lib/C4/Auth_with_ldap.pm line 97. Our conf file is set up like this: <useldapserver>1</useldapserver> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>ldaps://ldap.azag.gov</hostname> <base>"OU=XX,DC=XXXX,DC=XXX"</base> <user>ldapauth</user> <pass>XXXXXX</pass>  <replicate>1</replicate>  <update>1</update>  <auth_by_bind>1</auth_by_bind>  <anonymous_bind>0</anonymous_bind> <principal_name>%s</principal_name> <mapping>  <userid is="sAMAccountName"></userid> <password is="userpassword"></password> <firstname is="givenname"></firstname> <surname is="sn"></surname> <branchcode is="">XXXX</branchcode> <categorycode is="">PT</categorycode> <email is="mail"></email> </mapping> </ldapserver> When logging in, we have to use "username(a)XXXX.XXX" instead of just "username". However, our emails are formatted "firstname.lastname(a)XXXX.XXX". I thought this might be the reason it's generating the error, but I'm not sure how to change the config file to reflect that. Or if I need to change the auth_with_ldap file. Thanks, Michael

2 3