- Koha - lists.katipo.co.nz

Education meeting date poll
by Caroline Cyr-La-Rose 05 Jun '19

05 Jun '19

Hello everyone! During this morning's General meeting (https://wiki.koha-community.org/wiki/General_IRC_meeting_5_June_2019) a meeting for educators/trainers to exchange ideas, best practices, materials and other experiences was proposed. This meeting would be for all community members who have a hand in training new Koha users, or in continuing education for current Koha users, and who are interested in sharing experiences with colleagues. (Note that this is not a training meeting, but a meeting for educators.) If you would like to attend the very first meeting, please fill in the date poll available here : https://framadate.org/Y2p9c5PVIXuOP8Kg The meeting will be held by video conference. So far, NEKLS and ByWater Solutions have both offered to host the first meeting using Zoom. George and Donna, can you insert your room's availability as a "person" in the poll? I will make sure one of the rooms can attend when deciding the date :) The poll closes on June 12. So answer as soon as possible. I will send the details and agenda on the list when a date is picked. Thank you everyone! -- Caroline Cyr La Rose, M.L.I.S. Librarian | Product Manager Phone: 1-833-465-4276, ext. 221 Caroline.Cyr-La-Rose(a)inLibro.com <mailto:caroline.cyr-la-rose@inLibro.com> INLiBRO | Document Technologies Specialists | www.inLibro.com <http://www.inLibro.com>

1 0

Re: [Koha] Cannot find records created in KoHa
by Michael Kuhn 04 Jun '19

04 Jun '19

Hi Patric >> Reading your original e-mail again: "I just created my first record >> with some items. Among other things I filled in the field "Number >> (ISBN)” with 100.100. >> >> Using the advanced catalog search I’m trying to find my record, but >> nothing is found: >> >> No results match your search for 'nb: 100.100'." >> >> Can you search (and find) something else than "nb: 100.100" and you >> will find the record or won't you find it at all, not even if you >> search for author name, for example? > > No, this didn’t work neither. It seems like you don't have an index that you could search. You should probably build one. >> If you don't find anything at all: Did you ever successfully create >> the Zebra index? Maybe you got some user permissions problem - test >> it with: >> >> # INSTANZ=yourKohaInstance >> # ls -al /var/lib/koha/$INSTANZ/{authorities,biblios}/* >> # ls -al /var/lock/koha/$INSTANZ/{authorities,biblios,rebuild} >> >> All these directories and files need to be owned by Linux user >> "$INSTANZ-koha" and "$INSTANZ-koha”. > > These rights seem to be correct, same user and group as the daemons. As I see in your last post you only have three processes running: 1445 ? S 0:00 daemon --name=ausleihe-test-koha-zebra --pidfiles=/var/run/koha/ausleihe-test/ --errlog=/var/log/koha/ausleihe-test/zebra-error.log --output=/var/log/koha/ausleihe-test/zebra-output.log --verbose=1 --respawn --delay=30 --user=ausleihe-test-koha.ausleihe-test-koha -- /usr/bin/zebrasrv -v none,fatal,warn -k 1024 -f /etc/koha/sites/ausleihe-test/koha-conf.xml 1447 ? S 0:00 \_ /usr/bin/zebrasrv -v none,fatal,warn -k 1024 -f /etc/koha/sites/ausleihe-test/koha-conf.xml 1688 ? S 0:00 daemon --name=ausleihe-test-koha-indexer --errlog=/var/log/koha/ausleihe-test/indexer-error.log --stdout=/var/log/koha/ausleihe-test/indexer.log --output=/var/log/koha/ausleihe-test/indexer-output.log --pidfiles=/var/run/koha/ausleihe-test/ --verbose=1 --respawn --delay=30 --user=ausleihe-test-koha.ausleihe-test-koha -- /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5 I don't know the command you got these lines from, but however "ps -ef | grep zebra" gives the following in my Koha demo installation: sandkas+ 651 1 0 Jun01 ? 00:00:00 daemon --name=sandkasten-koha-zebra --pidfiles=/var/run/koha/sandkasten/ --errlog=/var/log/koha/sandkasten/zebra-error.log --output=/var/log/koha/sandkasten/zebra-output.log --verbose=1 --respawn --delay=30 --user=sandkasten-koha.sandkasten-koha -- /usr/bin/zebrasrv -v none,fatal,warn -f /etc/koha/sites/sandkasten/koha-conf.xml sandkas+ 653 651 0 Jun01 ? 00:00:01 /usr/bin/zebrasrv -v none,fatal,warn -f /etc/koha/sites/sandkasten/koha-conf.xml sandkas+ 1205 1 0 Jun01 ? 00:00:00 daemon --name=sandkasten-koha-indexer --errlog=/var/log/koha/sandkasten/indexer-error.log --stdout=/var/log/koha/sandkasten/indexer.log --output=/var/log/koha/sandkasten/indexer-output.log --pidfiles=/var/run/koha/sandkasten/ --verbose=1 --respawn --delay=30 --user=sandkasten-koha.sandkasten-koha -- /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5 sandkas+ 1206 1205 0 Jun01 ? 00:00:45 /usr/bin/perl /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5 sandkas+ 16720 653 0 18:51 ? 00:00:00 /usr/bin/zebrasrv -v none,fatal,warn -f /etc/koha/sites/sandkasten/koha-conf.xml As you see there are two processes more than in your installation. Maybe you should just restart Zebra or if you don't know how, restart all of Koha (including Zebra), or restart your host with everything (including Koha, Zebra and the rest). > I just saw that somebody introduced some frameworks that do not > include the field "000 - Record Label”. This field is needed to > create a correct record in koha, right? The following MARC fields are "mandatory" by default: LEADER ("000" in the Koha framework) 003 008 040$c 245$a 942$c - in the framework they are marked with a very small red asterisk. Whatever "mandatory" means: I tried to destroy a framework like you have one - exporting the standard framework, importing it as a new framework TEST, then deleting the MARC LEADER ("000"). In Koha menu "Administration > MARC Bibliographic framework test" it still says for this mutilated framework: "Configuration OK, you don't have errors in your MARC parameters table". This seems like some kind of higher nonsense to me. Interestingly enough even without the "mandatory" MARC LEADER ("000") in the framework a test record can be saved - it will then just insert some default values (as can be seen in the "MARC view"). However, as said, such a record can be saved and also be searched. See http://koha.adminkuhn.ch/cgi-bin/koha/opac-MARCdetail.pl?biblionumber=469 (but only until about 04:00 AM tomorrow) So the mutilated framework is probably not the initial reason for your problem. Still, I wouldn't ever advise to delete the MARC LEADER in any framework. As I wrote above, I assume you don't have a (correct) Zebra index at all. Hope this helps. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

Data migration from SOUL 1 to Koha
by Dixson Rodriges 04 Jun '19

04 Jun '19

Hi, Is there any option to export the data from SOUL 1 to Koha ? How to export bulk CCF format data from soul 1. Regards, Dixson

3 3

Re: [Koha] Koha Digest, Vol 164, Issue 3
by Charles Kelley 03 Jun '19

03 Jun '19

Hello, Katrin! Yes, it helped immensely! It installed the missing sudo command. Koha is now installing its little heart away, as it were. What a relief it is that it wasn't operator error for a change. Many thanks! In our latest exchange, on June 3, 2019, at 9:01 AM, you wrote through the Koha Discussion List: Message: 6 > Date: Sun, 2 Jun 2019 16:43:03 +0200 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Installation Failure > Message-ID: <4a0d9bf4-a2a9-9e38-ade1-e3be695b49cd(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Charles, > > it appears that under some circumstances the sudo command is not > available on a fresh Debian installation. I found this blog post that > might be helpful in solving this: > > https://chewett.co.uk/blog/477/sudo-command-not-found-debian-fixed/ > > I've also found this, which might explain the situation a bit more: > > "As of DebianSqueeze <https://wiki.debian.org/DebianSqueeze>, if you > give root an empty password during installation, sudo will be installed > and the first user will be able to use it to gain root access > (currently, the user will be added to the *sudo* group). The system will > also configure gksu and aptitude to use sudo. You should still verify > group membership > <https://wiki.debian.org/sudo#Verifying_sudo_membership> after logging > in as the installed user." (https://wiki.debian.org/sudo) > > Hope it helps, > > Katrin > > On 02.06.19 15:41, Charles Kelley wrote: > > Hello, all > > > > I am new to both Linux and Koha. I readily admit so. After several > > failed attempts to install Debian Linux on VirtualBox for Mac, I finally > > succeeded. Now I have trouble in installing Koha on the Debian > VirtualBox. > > It fails at the first instruction in the Koha-Community instructions. > > > > When I open terminal and type this instruction > > > > $ wget -q -O- https://debian.koha-community.org/koha/gpg.asc | sudo > apt-key > > add - > > > > terminal reports > > > > bash: sudo: command not found > > > > When I type this instruction > > > > $ wget -q -O- http://debian.koha-community.org/koha/gpg.asc | sudo > apt-key > > add - > > > > terminal reports > > > > base: sudo: command not found > > > > I have even tried a variant from Joel Hertel's installation guide > from > > a few years ago, to wit: > > > > $ su > > $ wget -q -O- http://debian.koha-community.org/koha/gpg.asc | apt-key > add - > > > > What am I doing wrong? > > > -- -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 1-301-741-7122 [US cell] 011-81-80-4714-5490 [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

Adding "Identifier-standard" field to Zebra's authority index
by Simon Hohl 03 Jun '19

03 Jun '19

Hi everyone, this Email is a followup on: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22013 I want to apply a record matching rule on my authority data, which checks field 024$9 against existing authority data. So far I tried following these instructions: https://wiki.koha-community.org/wiki/How_to_add_new_zebra_index 1. Added to authority-koha-indexdefs.xml (roughly copied over from the biblio equivalent): >  > <kohaidx:index_subfields tag="024" subfields="abcdefghjklmnopqrstvxyz0123456789"> > <kohaidx:target_index>Identifier-standard:w</kohaidx:target_index> > </kohaidx:index_subfields> 2. Added to etc/zebradb/authorities/etc/bib1.att: > att 1007 Identifier-standard 3. Ran xsltproc on xml to create xsl file 4. Rebuilt Zebra > koha-rebuild-zebra -a -f -v (...) But so far, the error persists: > oAuth error: Unsupported Use attribute (114) Identifier-standard Bib-1 Did I miss something or are there additional steps necessary for adding authority fields compared to the bibliographic index? Kind regards, Simon My system information: > Koha version: 18.11.05.000 > OS version ('uname -a'): Linux (...) 4.9.0-9-amd64 #1 SMP Debian > 4.9.168-1 (2019-04-12) x86_64 > Perl interpreter: /usr/bin/perl > Perl version: 5.024001 > Perl @INC: /usr/share/koha/lib > /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 > /usr/local/share/perl/5.24.1 > /usr/lib/x86_64-linux-gnu/perl5/5.24 > /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.24 > /usr/share/perl/5.24 > /usr/local/lib/site_perl > /usr/lib/x86_64-linux-gnu/perl-base > MySQL version: mysql Ver 15.1 Distrib 10.1.38-MariaDB, for > debian-linux-gnu (x86_64) using readline 5.2 > Apache version: Server version: Apache/2.4.25 (Debian) > Memcached: Servers: 127.0.0.1:11211 | Namespace: (...) | Status: > running. | Config read from: koha-conf.xml > Zebra version: Zebra 2.0.59 (C) 1994-2014,(...) > Date and time: 14/05/2019 10:18 > Time zone: Used: Europe/Berlin | Config: Undefined | Environment > (TZ): Undefined

3 7

June 2019 koha-US meeting dates
by Jason Robb 03 Jun '19

03 Jun '19

*koha-US meetings are open to any and all.* *Board Meeting -* When: Wednesday, June 5th at 10:30 am CDT (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+Board+Mee…> ) Where: https://kslib.zoom.us/j/450230564 Agenda: https://docs.google.com/document/d/14Q91toxcrancNWjtJZkjq5QiI91-1IQBuLlmuhl… *Board meetings* focus on business-related matters and topics that would otherwise slow down general meetings. *General Meeting* - When: Wednesday, June 12th at 10:30 am CDT (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+General+M…> ) Where: https://kslib.zoom.us/j/110290143 *General meetings* put an emphasis on Koha -- bugs, issues, development ideas, workflows -- bring your problems and questions so we can discuss! These meetings also include major organizational decisions and reports from various committees. Meetings are held via Zoom video conferencing. A microphone and camera 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 <https://support.zoom.us/hc/en-us/categories/200101697>* If you have topics for discussion at either meeting, please send them to secretary(a)koha-us.org. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Installation Failure
by Charles Kelley 02 Jun '19

02 Jun '19

Hello, all I am new to both Linux and Koha. I readily admit so. After several failed attempts to install Debian Linux on VirtualBox for Mac, I finally succeeded. Now I have trouble in installing Koha on the Debian VirtualBox. It fails at the first instruction in the Koha-Community instructions. When I open terminal and type this instruction $ wget -q -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - terminal reports bash: sudo: command not found When I type this instruction $ wget -q -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - terminal reports base: sudo: command not found I have even tried a variant from Joel Hertel's installation guide from a few years ago, to wit: $ su $ wget -q -O- http://debian.koha-community.org/koha/gpg.asc | apt-key add - What am I doing wrong? -- -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 1-301-741-7122 [US cell] 011-81-80-4714-5490 [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

Restoring OPAC - Help
by SATISH 02 Jun '19

02 Jun '19

Hi, With Koha 16.11.11 / Package Installation/ Ubuntu 14.04 Desktop with MySQL - mysql Ver 14.14 Distrib 5.5.57 Took mysqldump and moved koha database from server A to server B Did db-schema upgrade, rebuild zebra index But, I am not able to find OPAC pages server B. (Home › Administration › System preferences > Local Use) Is there any specific files to be restored?? Your answers would help me in restoring OPAC. Thank You Satish MV Librarian Govt. Engineering College, Hassan. Karnataka. --

3 6

How to take backup of KOHA 16.04 and 18.05
by Sugandha Bajaj 02 Jun '19

02 Jun '19

Dear All, Can I request you to please provide me inputs on how to take the backup of KOHA 16.04 and 18.05 Kind Regards, Sugandha Bajaj.

2 2

880 field OPAC display
by Archimandrite Gregory 02 Jun '19

02 Jun '19

Hello. I have a dilemma which I am hoping someone can help me solve. I want my patrons to be able to see both non-Latin script as well as the romanized transliteration of an item in the OPAC. I have tried linking several fields to the 880 field, but discovered that it will not display all the fields or subfields I choose. For example, the 245 field will link to the 880 field, but will only display subfield a. Also, the 264 field when linked to the 880 field will not display at all. Do I need to do something to the 880 field? Should I be entering the information into the record differently to achieve my goal? Any advice would be appreciated.

2 1