- Koha - lists.katipo.co.nz

Staff interface requests multiple logins
by Elaine Bradtke 10 Jun '21

10 Jun '21

We're running 20.11.06 on our test site. In the staff interface searching, and editing a found record work fine. The problem occurs when I try to use authorities (any step of the process from searching, to looking at one, to editing one, or any method used to create a new biblio. authorities/authorities-home.pl authorities/ authorities-home.pl?op=do_search&type=intranet&authtypecode=&marclist=mainmainentry&and_or=and&excluding=&operator=contains&value=harmonica&orderby=HeadingAsc authorities/authorities.pl?authid=11041 cataloguing/addbooks.pl cataloguing/z3950_search.pl?biblionumber=&frameworkcode=Default cataloguing/addbiblio.pl?frameworkcode=BKS We can't find anything suspicious in the log files. It happens on chrome and firefox (running windows). I don't know if this makes a difference, but the test site is http not https. Any ideas what we should look for? Elaine Bradtke VWML <https://www.vwml.org> English Folk Dance and Song Society <https://www.efdss.org> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999

1 0

limits on canned OPAC searches
by Carlos Lopez 10 Jun '21

10 Jun '21

Hi everyone We have a little drop-down option on our OPAC that we call "New Titles" - it basically brings up a reverse-chronological listing of books or ebooks on the catalogue: <form name="searchform" method="get" action="/cgi-bin/koha/opac-search.pl"> <input name="idx" value="kw" type="hidden"> <input name="sort_by" value="acqdate_dsc" type="hidden"> <input name="do" value="OK" type="hidden"> <select name="limit" onchange="this.form.submit()"> <option>-- Display new titles to the collection --</option> <option value="mc-itype:BOOK">New books</option> <option value="mc-itype:EBK">New ebook</option> </select> </form> Is there a way we could improve this by limiting results to a time range (preferably "last 6 months" or something like that)? And excluding material that is "Ordered"? With kind regards from the Dalton McCaughey Library Team Carlos Lopez Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA 3052 Ph: 03 9340 8888 ext.1 | library(a)dml.vic.edu.au<mailto:library@dml.vic.edu.au> | library.dmlibrary.org.au

1 0

Re: [Koha] Identifying Records with Non-Roman Characters
by Randy Wright 09 Jun '21

09 Jun '21

You may get some useful suggestions from the MarcEdit list: https://listserv.gmu.edu/cgi-bin/wa?A0=marcedit-l Randy Wright Information Resource Steward Santa Barbara Botanic Garden Blaksley Library 1212 Mission Canyon Road Santa Barbara CA 93105 805-682-4726 x107 www.sbbg.org www.sbbgphotos.org ---------------------------------------------------------------------- Message: 1 Date: Mon, 7 Jun 2021 09:53:24 +0900 From: Charles Kelley <cmkelleymls(a)gmail.com> To: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Identifying Records with Non-Roman Characters Message-ID: <CAM8F7wqwMav=yuhDjPM7r8ZDZKjzHWONtY397AxEc-TWw-Mb5w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hello, all! Our catalog has 8766 records that lack the 880 field for non-Roman titles. Examples: =245 10$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков =246 11$a Velikaia otechestvennaia voina 1941-1945 =245 10$a英汉常用物理学小词典 /$cYing Li, Lian Wei =246 11$aYing-Han changyong wulixue xiaocidian Of those, a significant portion is in Cyrillic, CJK, Greek, etc. Is there a way in either Koha or MarcEdit to isolate said records? The problem is to turn the 245 into 880, turn the 246 into 245 fields and then pair the resulting 880 and the new 245 into something like =880 10$6245-45/(N$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков. =245 10$6880-45$aVelikaia otechestvennaia voina, 1941-1945. =880 10$6245-45/[dollar]1$a英汉常用物理学小词典 /$cYing Li, Lian Wei. =245 10$6880-45$aYing-Han changyong wulixue xiaocidian. The indicators are easy to fix after the 245 and 880 fields are reconstructed. The 245 $c subfield can be copied from the 880 $c subfield. I'm just trying to automate the process as much as possible and thereby avoid the painstaking manual corrections if they can be avoided. This is an interim step. Eventually the catalog will have to be recataloged from scratch, I think. Many thanks, all! -- 気を付けて。 /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. ------------------------------

1 0

Opac display
by c.dumontet＠btinternet.com 09 Jun '21

09 Jun '21

I'm new to Koha and I would be grateful for some help. The name in the "Label for opac" in the MARC framework does not correspond to the actual label on the opac. For example: In the Admin module one of our frameworks has the following labels for 246: "Label for Lib" = Variant title ; "Label for Opac" = Variant title. But in the Opac display the label in fact reads: "Other title". In which part of the Admin module do I tweak with these labels? Why the discrepancy? Is there any video online where this topic is covered? (I could not find any). Many thanks for your help. Carlo

2 1

Re: [Koha] Identifying Records with Non-Roman Characters
by dcook＠prosentient.com.au 09 Jun '21

09 Jun '21

Hi Charles, I'm not 100% sure what you're asking here. Are you asking to find all records where there is a 245 title that isn't Romanized? You could try something like this: SELECT * FROM biblio WHERE title <> CONVERT(title USING latin1); I've tried that out on one of my multilingual libraries and it had some decent results. However, it's worth noting that it isn't a perfect solution. There are certain characters (I've noticed a particular hyphen) that won't have a latin1 equivalent, but they'd still be "Roman" (like hyphen which is made of the hexadecimal bytes E2 80 90, but is not to be confused with hyphen-minus which is ASCII and represented by the byte 2D). Other examples are emoji and other symbols like ↔️. You could then tweak the query or do a visual scan through to filter out any results that are irrelevant. Anyway, I hope that helps you advance your work. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Date: Mon, 7 Jun 2021 09:53:24 +0900 From: Charles Kelley <cmkelleymls(a)gmail.com> To: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Identifying Records with Non-Roman Characters Message-ID: <CAM8F7wqwMav=yuhDjPM7r8ZDZKjzHWONtY397AxEc-TWw-Mb5w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hello, all! Our catalog has 8766 records that lack the 880 field for non-Roman titles. Examples: =245 10$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков =246 11$a Velikaia otechestvennaia voina 1941-1945 =245 10$a英汉常用物理学小词典 /$cYing Li, Lian Wei =246 11$aYing-Han changyong wulixue xiaocidian Of those, a significant portion is in Cyrillic, CJK, Greek, etc. Is there a way in either Koha or MarcEdit to isolate said records? The problem is to turn the 245 into 880, turn the 246 into 245 fields and then pair the resulting 880 and the new 245 into something like =880 10$6245-45/(N$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков. =245 10$6880-45$aVelikaia otechestvennaia voina, 1941-1945. =880 10$6245-45/[dollar]1$a英汉常用物理学小词典 /$cYing Li, Lian Wei. =245 10$6880-45$aYing-Han changyong wulixue xiaocidian. The indicators are easy to fix after the 245 and 880 fields are reconstructed. The 245 $c subfield can be copied from the 880 $c subfield. I'm just trying to automate the process as much as possible and thereby avoid the painstaking manual corrections if they can be avoided. This is an interim step. Eventually the catalog will have to be recataloged from scratch, I think. Many thanks, all! -- 気を付けて。 /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

koha-US General Meeting reminder: Wednesday, June 9, 2021
by Jason Robb 08 Jun '21

08 Jun '21

The next koha-US general meeting is *tomorrow, *Wednesday, June 9, 2021. When: 8:30a PT / 11:30a ET / 16:30 UTC (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+June+gene…> ) Where: https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 Agenda: https://docs.google.com/document/d/1pLb2UrM49aetTlYpHS3zTQ29i0gr6VNvSqSHiVF… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 These meetings are always free and open to any and all. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Bar code not reading by scanner
by Nalisha Tamang 08 Jun '21

08 Jun '21

dear all, please help me out. Barcode scanner is not reading the barcodes. We have recently changed our systems and after that I tried generating barcodes and the barcode numbers are strange, especially '0' comes with dots. I can't figure out the problem. Please help me asap. I have attached the barcode sheet as well. thank you with regards, Nalisha Tamang Rai

2 2

Identifying Records with Non-Roman Characters
by Charles Kelley 07 Jun '21

07 Jun '21

Hello, all! Our catalog has 8766 records that lack the 880 field for non-Roman titles. Examples: =245 10$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков =246 11$a Velikaia otechestvennaia voina 1941-1945 =245 10$a英汉常用物理学小词典 /$cYing Li, Lian Wei =246 11$aYing-Han changyong wulixue xiaocidian Of those, a significant portion is in Cyrillic, CJK, Greek, etc. Is there a way in either Koha or MarcEdit to isolate said records? The problem is to turn the 245 into 880, turn the 246 into 245 fields and then pair the resulting 880 and the new 245 into something like =880 10$6245-45/(N$aВеликая отецественная война 1941-1945 /$cВ. И. Чуйков. =245 10$6880-45$aVelikaia otechestvennaia voina, 1941-1945. =880 10$6245-45/[dollar]1$a英汉常用物理学小词典 /$cYing Li, Lian Wei. =245 10$6880-45$aYing-Han changyong wulixue xiaocidian. The indicators are easy to fix after the 245 and 880 fields are reconstructed. The 245 $c subfield can be copied from the 880 $c subfield. I'm just trying to automate the process as much as possible and thereby avoid the painstaking manual corrections if they can be avoided. This is an interim step. Eventually the catalog will have to be recataloged from scratch, I think. Many thanks, all! -- 気を付けて。 /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.

1 0

"Return to the last advanced search" exclude keywords if more than 3
by Claes Eriksson 04 Jun '21

04 Jun '21

Hi! After performing an advanced search with more than 3 keywords<https://kohaopac.alingsas.se/cgi-bin/koha/opac-search.pl?advsearch=1&idx=kw…> I use the option "Return to the last advanced search" on the result page. However, now there are only 3 keywords. I can perform the search again but then use the browsers "go back one page" and in my example all the 5 keywords are there. I do not know which version they use. In our own 20.11 OPAC i repeat the example searching with 4 keywords<https://bibliotek.vti.se/cgi-bin/koha/opac-search.pl?advsearch=1&idx=kw&q=p…>. The option "Return to the last advanced search" gives the same result: only 3 keywords. However, using the "go back one page" also results in the disappointing only 3 keywords left. Same result for FF and Chrome (latest versions). Is this a bug or a feature? Kind regards Claes ----------------------------- Claes Eriksson Systems librarian Department of Communication, Marketing and Library (KOMBI) Swedish National Road and Transport Research Institute (VTI) VTI, SE-581 95 Linkoeping, Sweden Tel: +46-13-20 40 00 Direct: +46-13-20 41 99 E-mail: claes.eriksson(a)vti.se<mailto:claes.eriksson@vti.se> ----------------------------------

2 2

Koha 21.05.00 released
by Jonathan Druart 04 Jun '21

04 Jun '21

Hello everybody, It is with great pleasure that the Koha community announces the release of Koha 21.05, a major release of the Koha open source integrated library system. Read the full release notes here: https://koha-community.org/koha-21-05-released/ The Debian packages for this new version will be available soon. Stay tuned! Cheers, Jonathan

4 3