Re: [Koha] Hosting options for Koha installation

[Mark Alexander]

Excerpts from Lennon Mazonde's message of 2017-01-31 12:38:06 +0200:
> I've run Koha using a VPS before, but they are limited in terms of the 
> resources you get. I found i frequently ran out of inodes and space and 
> had too many bandwidth limitations.

I'd like to know more about this, since I'm in the process of
switching our library over to using Koha on a Linode VPS.  Our catalog
is not large (about 24K holdings), and the $10/month plan with 2GB of
RAM and 24 GB SSD seems adequate so far, at least in my admittedly
limited testing.

When would I be likely to see the limitations you mentioned?

Also, if there are other users out there using Linode, I'd like
to hear about their experience with that service.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to check a file's MIME type in KOHA

[Mark Alexander]

Excerpts from Rejeesh K.Nair's message of 2017-02-07 15:49:42 +0530:
> I have checked the MIME information of a specific file using its extension.
> But actually I need details of exact file.

I'm a newbie with the Koha source code.  But I'm wondering if there
is some way you could use the external "file" program from within
Koha to determine the file type.  This program is not fooled by
file name extensions; it examines the file contents to determine
the type.  Here is an example of a test I ran where I renamed a .pdf
file with .jpg extension in an attempt to fool file:

  $ cp koha-notes.pdf junk.jpg
  $ file -i junk.jpg
  junk.jpg: application/pdf; charset=binary
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Checkout limit by household

[Mark Alexander]

Excerpts from Katrin's message of 2017-01-23 00:25:38 +0100:
> If you add relationships between the members of one household (guarantor 
> and guarantees), you should be able to see in the staff client what the 
> other members of the household have checked out when you are in the 
> patron account.

Thanks!  I had already realized that my idea of matching addresses was pretty
bogus. The guarantors idea might work for us.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Mistakes (?) in wiki pages

[Mark Alexander]

What is the standard procedure for reporting possible errors in 
wiki pages?

The reason I ask is that during my attempts to install Koha from (1)
Debian packages, and (2) a git development environment, I have run
into a small number of commands or config file lines in the wiki pages
I used that I had to change.

Some examples:

In https://wiki.koha-community.org/wiki/Debian_Jessie_development_setup,
I had to change the line:



to:



In https://wiki.koha-community.org/wiki/Koha_on_Debian,
I had to change:

sudo xmlstarlet sel -t -v 'yazgfs/config/user' 
/etc/koha/sites/libraryname/koha-conf.xml koha_libraryname 
sudo xmlstarlet sel -t -v 'yazgfs/config/pass' 
/etc/koha/sites/libraryname/koha-conf.xml randompasswordtext

to:

sudo xmlstarlet sel -t -v 'yazgfs/config/user' 
/etc/koha/sites/libraryname/koha-conf.xml
sudo xmlstarlet sel -t -v 'yazgfs/config/pass' 
/etc/koha/sites/libraryname/koha-conf.xml

(i.e., delete the last command line arguments).
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Checkout limit by household

[Mark Alexander]

Our library (running Mandarin currently) has a limit of two DVDs
per household.  Mandarin doesn't enforce this limit; the librarian
knows pretty much everybody in this little town and has the data
in her head.  But we volunteers don't have that brainpower.

I have been working on a Koha upgrade for our library for some months,
and am pretty close to having everything working.  But this household
limit has me a bit stumped.  For one thing, our patron database is a
bit inconsistent, so if we define "household" as being "all borrowers
with the same address", we're in trouble because the same address
might be spelled several different ways.  (For example, Route can be
RT or RTE or Rte. or Rt. or Rt)

But leaving aside the consistency problem, Koha doesn't seem to have
a way to do this kind of check.  I can cobble together some SQL that
looks like this:

  select count(issue_id) from issues
left join borrowers on issues.borrowernumber = borrowers.borrowernumber
left join items on issues.itemnumber = items.itemnumber
where borrowers.address = '123 Main Street'
and city = 'Podunk'
and state = 'VT'
and items.itype = 'DVD';

and then check this result against configurable checkout limits for
particular item types.  This sounds like a fair amount of work in the
Koha codebase itself, so I was wondering if anybody else had looked
into this and had other ideas.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Date Wise List of Checked In Books

[Mark Alexander]

Excerpts from Scott Owen's message of 2017-01-27 08:08:43 -0500:
> SELECT 
> old_issues.returndate,items.barcode,biblio.title,biblio.author,borrowers.firstname,borrowers.surname,borrowers.cardnumber,borrowers.categorycode
> FROM old_issues  LEFT JOIN borrowers ON
> borrowers.borrowernumber=old_issues.borrowernumber LEFT JOIN items ON
> old_issues.itemnumber=items.itemnumber LEFT JOIN biblio ON
> items.biblionumber=biblio.biblionumber WHERE old_issues.returndate
> BETWEEN <> AND < (-mm-dd)|date>>  ORDER BY old_issues.returndate DESC

I tried something like this on my installation, and it worked when
I put the dates in single quotes in the BETWEEN clause:

SELECT 
old_issues.returndate,items.barcode,biblio.title,biblio.author,borrowers.firstname,borrowers.surname,borrowers
 .cardnumber,borrowers.categorycode
FROM old_issues
LEFT JOIN borrowers ON borrowers.borrowernumber=old_issues.borrowernumber
LEFT JOIN items ON old_issues.itemnumber=items.itemnumber
LEFT JOIN biblio ON items.biblionumber=biblio.biblionumber
WHERE old_issues.returndate BETWEEN '2017-01-19' AND '2017-01-22'
ORDER BY old_issues.returndate DESC;
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] cron issue with Koha on Ubuntu

[Mark Alexander]

Excerpts from Steve Nickerson's message of 2017-02-20 23:28:51 -0500:
> Thank you Mark!   As it turns out apparently my issue was that 'cron' was 
> installed but not 'anacron'.   I had those same /etc/cron.d, /etc/cron.daily, 
> etc. files that you provided, but anacron wasn't installed/running, so they 
> weren't being used.   As soon as I added anacron things seem to be working 
> now.  Maybe anacron should be one of the dependencies for the koha-common 
> package???

I'm not sure I understand why anacron was required.  On both of the
installations I'm using, anacron was either not installed (Debian 8 on
Linode) or I had to disable it (Debian 8 in a VM on my laptop).
Anacron caused problems for me (and others) with Zebra being killed
off every morning.

See these discussions:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885
https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] cron issue with Koha on Ubuntu

[Mark Alexander]

I wrote:

> I'm not sure I understand why anacron was required.

Looking at this some more, could it be that your server isn't running
continuously?

The reason I ask is that the file /etc/crontab on Debian 8 looks like this:

17 ** * *   rootcd / && run-parts --report /etc/cron.hourly
25 6* * *   roottest -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
47 6* * 7   roottest -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.weekly )
52 61 * *   roottest -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.monthly )

I believe this means that if your machine isn't running at these
times, and anacron isn't available, the cron jobs won't run.  In
particular, it appears that the daily, weekly, and monthly jobs are
run between 6:25 and 6:52 AM.

Anacron is useful for personal machines that don't run continuously,
but it doesn't play well with Koha, in my experience.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Mandarin conversion scripts

[Mark Alexander]

Over the past few months, I have written some scripts to convert
Mandarin catalog and patron data into formats suitable for importing
into Koha.  I have placed these scripts on github, in case there are
any other Mandarin users who are also going through the conversion
process:

https://github.com/bloovis/marc
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] cron issue with Koha on Ubuntu

[Mark Alexander]

Excerpts from Steve Nickerson's message of 2017-02-23 09:15:26 -0500:

> OK, so I dug further and do indeed find cron running and can see the
> jobs executing via /var/log/syslog.  It appears that everything is
> working EXCEPT that the zebra indexing updates aren't working
> correctly.  I see the line "Uncomment the following line if you do not
> want to use the koha-index-daemon integration" and the line following
> that is commented out...should it be?

My fairly stock installation has that line commented out.

> How do I know if I'm using the koha-index-daemon or not?

Maybe the daemon didn't get started for some reason.  Check using this:

  ps auxfw | egrep zebra

You should see four processes related to the two zebra daemons (one
daemon for the indexer and one for the server).  It's possible that
the daemons didn't get started for some reason; they should have
been started by /etc/init.d/koha-common.  But you could try using
this:

  koha-start-zebra 
  koha-indexer --start 
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] cron issue with Koha on Ubuntu

[Mark Alexander]

Excerpts from Steve Nickerson's message of 2017-02-18 13:38:56 -0500:
> Can someone tell
> me what the crontab(s) should look like and which user they should run
> under, please?   Anyone have a URL with instructions already?

Under my 16.11 installation, I see the following cron files,
all owned by root but not appearing in the crontabs for root
or any other user.  I've copied them below, with the GPL3
notices stripped out for brevity.

$ ls -laF /etc/cron*/koha*
-rwxr-xr-x 1 root root 1674 Sep 22 16:15 /etc/cron.daily/koha-common*
-rw-r--r-- 1 root root  516 Sep 22 16:15 /etc/cron.d/koha-common
-rwxr-xr-x 1 root root  840 Sep 22 16:15 /etc/cron.hourly/koha-common*
-rwxr-xr-x 1 root root  838 Sep 22 16:15 /etc/cron.monthly/koha-common*

$ cat /etc/cron.daily/koha-common
#!/bin/sh
# /etc/cron.daily/koha-common -- Daily housekeeping tasks for all Kohas.
# Copyright 2010  Catalyst IT, Ltd

koha-foreach --enabled /usr/share/koha/bin/cronjobs/automatic_renewals.pl
koha-foreach --enabled /usr/share/koha/bin/cronjobs/fines.pl
koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/overdue_notices.pl 
-t
koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/advance_notices.pl 
-c
koha-foreach --enabled /usr/share/koha/bin/cronjobs/membership_expiry.pl -c
koha-foreach --enabled 
/usr/share/koha/bin/cronjobs/holds/cancel_expired_holds.pl >/dev/null 2>&1
koha-foreach --enabled /usr/share/koha/bin/cronjobs/services_throttle.pl > 
/dev/null 2>&1
koha-foreach --enabled /usr/share/koha/bin/cronjobs/cleanup_database.pl 
--sessions --zebraqueue 10 --list-invites
koha-foreach --enabled --noemail 
/usr/share/koha/bin/cronjobs/cleanup_database.pl --mail
koha-foreach --enabled 
/usr/share/koha/bin/cronjobs/holds/auto_unsuspend_holds.pl > /dev/null 2>&1
koha-run-backups --days 2 --output /var/spool/koha

$ cat /etc/cron.d/koha-common
# /etc/cron.d/koha-common
#
# Call koha-rebuild-zebra for each enabled Koha instance, to make sure the
# Zebra indexes are up to date.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# Uncomment the following line if you do not want to use the koha-index-daemon 
integration
# */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra 
-q $(koha-list --enabled)

*/15 * * * * root koha-foreach --enabled --email 
/usr/share/koha/bin/cronjobs/process_message_queue.pl

$ cat /etc/cron.hourly/koha-common
#!/bin/sh
# /etc/cron.hourly/koha-common -- Hourly housekeeping tasks for all Kohas.
# Copyright 2010  Catalyst IT, Ltd

koha-foreach --enabled /usr/share/koha/bin/cronjobs/holds/build_holds_queue.pl

$ cat /etc/cron.monthly/koha-common
#!/bin/sh
# /etc/cron.monthly/koha-common -- Monthly housekeeping tasks for all Kohas.
# Copyright 2015 Biblibre

koha-foreach --enabled 
/usr/share/koha/bin/cronjobs/share_usage_with_koha_community.pl
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Zebra server is not running

[Mark Alexander]

Excerpts from Luis Moises Rojas's message of 2017-02-13 10:15:24 -0400:
> When i see KOHA ABOUT its says:Zebra service is not running
> 
> But when we try to restart o star using koha-zebra-restart or start: say
> 
> Zebra is already running?
> 
> Where is the problem?
> 
> Is this the cause (maybe) why we have to run the koha-rebuild every morning?

This may be the problem:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

See this for a possible fix:

https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] connecting to zs39

[Mark Alexander]

Excerpts from Solomon mwangi's message of 2017-01-16 06:09:54 -0600:
> question: why does the port need to be greater than 1023?

Ports below 1024 are privileged.  When I tried using port 210 (the usual port
number for Z39.50) I got a "permission denied" error when I restarted Zebra.
The error message was in /var/log/koha//zebra-output.log:

19:03:20-10/01 [fatal] Failed to bind to tcp:@:210 [Permission denied]
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hello from Vermont

[Mark Alexander]

Hi all,

I'm a retired software geek, now living in a small town in Vermont
after many years in Silicon Valley.  I've been using Linux on my own
computers for 20 years, and have hacked on everything from microkernels
in assembly language to web apps in Ruby on Rails.

I also spent a year in NZ as a child and still consider it as my first
home, and miss it very much, though I've not been back since.  It's
cool to see such great open source software originating from my old
homeland.

Our town library currently uses proprietary software from Mandarin,
but I've been investigating what it would take to convert to Koha.
Many libraries here in Vermont are in a consortium that is using Koha
hosted by a commercial vendor.  But the consortium is closed to
new members.

So to see what it would take for us to build our own Koha installation
from scratch, I installed 16.05 (using git) in an Ubuntu 14.04 virtual
machine and have started to play around with it.  I've exported our
catalog (about 22K items) from Mandarin into a MARC dump.  Now I'm
figuring out what I need to do to import these records and correctly
set things like the item call number and item type.  I may ask some
questions later if I get stuck.

--Mark
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Hello from Vermont

[Mark Alexander]

Excerpts from Joy Nelson's message of 2016-08-28 18:23:32 -0500:
> I worked on some mandarin data in the past. Let me know if you have any 
> questions

Thanks, all, for the kind welcome and advice!

Right now I'm working on a couple of things:

1. To set the item call number on import, I think I can use the Koha
cataloging preference "itemcallnumber".  It looks like setting
it to "852khi" would work for our Mandarin records.

2. To set the item type, I think I can use the MARC field 245$h, which
in our Mandarin installation contains things like "[sound recording]",
"[videorecording]", etc.  It looks like the MARC Modification
Templates, with their regular expressions, have enough power this
without my having to write a converter.  (I've already written a
MARC-8 to UTF-8 converter in Ruby, so writing another converter
wouldn't be too hard, but it'd be nice for our librarian to be able to
do imports on her Windows box.)

I should stop fretting and just go ahead and try this out :-) .
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] AdvancedSearchTypes and OPAC

[Mark Alexander]

Hi all,

I'm trying to add tabs for collections (ccode) and shelving locations
(loc) to the advanced search pages for the OPAC client.  I set the
AdvancedSearchTypes preference to "itemtypes|ccode|loc", and this
caused the ccode and loc tabs to appear on the staff client search
page, as expected.  But the OPAC client advanced search page still
shows only the itemtypes tab.  Is there some other preference I need
to set to get the additional search tabs to appear on the OPAC?

Thanks in advance,
Mark
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] AdvancedSearchTypes and OPAC

[Mark Alexander]

Excerpts from Hugo Agud's message of 2016-10-21 15:31:25 +0200:
> depending the version of koha you're using and if you have plack enabled or
> not... you perhaps need to clean memcache and restart plack
> 
> try
> 
> sudo service memcached restart

Thanks, that did it!

> sudo koha-plack --restart *instanceName*

That reminds me -- enabling plack is on my to-do list.

Thanks again!
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Manual locations?

[Mark Alexander]

Hi all,

I'm not able to find the 16.05 (English) manual.  It used to be here:

http://translate.koha-community.org/manual/16.05/en/

I don't see it here either:

http://translate.koha-community.org/manual/

I took a look at the new Sphinx-ified manual, but it doesn't seem quite
ready yet.  (I was looking specifically for the OverDrive paragraphs of
the Enhanced Content section.)

Is there a new location for the older manuals?

Thanks,
Mark
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Can't specify due date/renewal due date in 16.05

[Mark Alexander]

Excerpts from King, Fred's message of 2016-11-18 09:43:33 -0500:
> Yesterday I upgraded Koha from 3.20 to 16.05, on Ubuntu 14.04LTS. Now we 
> can't specify a due date for either checkouts or renewals. When we use the 
> calendar to click on a date nothing happens; when we try to put in a date 
> using the format 2016-12-30 I get an error message "Please enter a valid date 
> (should match -mm-dd)." SpecifyDueDate is set to Allow.
> 
> Any ideas? I've run out of them here.

It sounds like this bug: 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17524
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] logrotate, anacron and bug 16885

[Mark Alexander]

This morning I started up my Koha test VM (Debian 8) and around 7:35
plack stopped working.  I believe this is the logrotate/zebra death issue
mentioned here:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

I am running 16.05.04.01 and verified that the patch shown in the above
bug is present in /usr/sbin/koha-stop-zebra.

In an email to this list a couple of months ago, Radek Siman suggested
disabling anacron as follows:

1) open /etc/cron.d/anacron and add a # to turn off the line starting
with 30 7 * * *  anacron...
2) mv /usr/sbin/anacron /usr/sbin/anacron-temporarily-renamed

I'm going to do this until I find a better solution.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] connecting to zs39

[Mark Alexander]

Excerpts from Solomon Mwangi's message of 2017-01-13 12:55:12 +0300:
> I have Koha running on an Linux server running Ubuntu 12.04
> 
> Koha runs fine - no issues.
> 
> I have been trying to connect to it via ZS39 but unable to connect.
> 
> Yaz client gives me this error = System (lower-layer) error
> 
> Help/ideas would be appreciated.

I assume you're talking about Z39.50?  There is a Wiki page describing
how to troubleshoot problems:

https://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server

But I've found that a few details in that document were slightly wrong
or incomplete for my installation (Koha 16.11 on Debian 8).  Here are
the notes I wrote for myself as I was getting Z39.50 to work on my
installation (all tasks performed while logged in as root):

To enable Z39.50, edit the file `/etc/koha/sites/LIBRARYNAME/koha-conf.xml`,
where LIBRARYNAME is the name you chose when you created your Koha instance.

Near the top of that file is a line that looks like this:

tcp:@:nnn

Uncomment that line by removing the `` lines before and after it.
Then replace `nnn` with an unused port number, preferably something greater
than 1023.  I chose 9998.

Farther down in file, around line 180, is a section starting with a line that
looks like this:



Below that is a line that looks like this:



Remove the start-of-comment line (``) after that line.

Finally, save the file and exit the editor.

Restart Zebra (the program that handles searches in Koha):

koha-restart-zebra rpl

Verify that Zebra is now listening on the port you chose (9998 in the
example above) by doing this:

netstat -pn --tcp --listen | grep 9998

If things are working, you should see a line that looks like this:

tcp0  0 0.0.0.0:99980.0.0.0:*   LISTEN  
6986/zebrasrv   

If things are not working, you won't see any output.

As a final check, you can try making a Z39.50 connection:

yaz-client tcp:127.0.0.1:9998/biblios

If things are working, you should see a few lines of output, including a line
that looks like this:

Connection accepted by v3 target.

and then a prompt line:

Z> 

If things aren't working, you'll see an error message like this:

Connecting...error = System (lower-layer) error: Connection refused

Exit the `yaz-client` program by hitting Ctrl-D or typing `exit` followed by 
Enter.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha zebra indexing stops every day morning.

[Mark Alexander]

Excerpts from Server Room Thane's message of 2016-12-19 13:38:38 +0530:
> I am using Koha 16.05.04.000 version on Ubuntu 16.04.1 LTS. Problem is
> that, each day morning OPAC searching stops. We checked the status of
> Koha-common service. Its active.

I ran into this problem, too.  It might be this bug:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

I am running the latest 16.05, and the problem persisted despite the
update having applied the patch described in the bug to
/usr/sbin/koha-stop-zebra.

To work around this problem, I used the suggestion from Radek Siman
to disable anacron (while logged in as root):

1) open /etc/cron.d/anacron and add a # to turn off the line starting
with 30 7 * * *  anacron...
2) mv /usr/sbin/anacron /usr/sbin/anacron-temporarily-renamed
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Regarding Installation of KOHA in window 1o

[Mark Alexander]

Excerpts from Lalit Thakur's message of 2017-03-27 13:47:13 +0530:
> How can install KOHA Live DVD in window 10. I am trying but I am not
> success. So kindly guide me.

Koha is best installed on Debian 8.  If you really must use Windows,
you could run Debian in a virtual machine; VMware Workstation or
VirtualBox should work for this.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Import staged MARC records with ElasticSearch engine

[Mark Alexander]

Excerpts from Abdulsalam Yousef's message of 2017-04-17 11:04:58 +0300:
> - Importing MARC records into catalog form (Manage staged MARC records) in
> staff client GUI using ElasticSearch engine is very slow and accidentally
> stops after importing some hundreds of records, That we may spend 3 days to
> import about 26000 record only, Is that normal? or there are any other
> configurations should be done first with ElasticSearch engine?
> 
> - We are using Koha 16.11.01.

We're not using Elastic Search on our installation, but I have found
that attempting to import our entire catalog of 24000 MARC records
failed due to Koha running out of memory (our system has 2 GB of RAM).
I was forced to split the MARC file into smaller chunks of 2000
records, and import each chunk separately.  A larger chunk might have
worked but I didn't want to take any chances.

I wrote a Ruby script to do the splitting of the MARC records, but
perhaps other tools can do the job (maybe Marcedit, which I haven't used).
The Ruby script is here:

https://github.com/bloovis/marc/blob/master/splitmarc.rb
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra - item-level_itypes errors

[Mark Alexander]

Excerpts from Tom Hanstra's message of 2017-04-19 12:13:30 -0400:
> item-level_itypes set but no itemtype set for item (item#) at
> /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698

Our installation has item-level_itypes enabled, but all of our item
records (imported from another ILS) have the itype set to a non-NULL
value.  When I manually set the itype of an item to NULL, I see the
above warning in /var/log/koha/INSTANCE/indexer-output.log. 
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] My Zebra keeps dying

[Mark Alexander]

Excerpts from i.pr...@zigzagee.com's message of 2017-03-13 13:16:19 +:
> Sounds like a sad problem I know but on our Koha test server (16.05) Zebra
>   keeps dying.

This sounds familiar, especially if Zebra is dying in morning.  It might be 
this problem:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

See this for a possible fix:

https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] SQL Help - Daily (on Monthly basis) & Monthly (on Yearly basis) Transactions Counts (Circulation)

[Mark Alexander]

Excerpts from Barton Chittenden's message of 2017-03-06 08:08:04 -0500:
> I'll do the 'month, by year'; the 'day by month' one will follow the same
> pattern.
> 
> SELECT
> monthname(datetime),
> SUM( IF(type = 'issue'), 1, 0 ) as issues,
> SUM( IF(type = 'renew'), 1, 0 ) as renewals,
> SUM( IF(type = 'return'), 1, 0 ) as returns
> FROM
> statistics
> WHERE
> YEAR(datetime) = YEAR(current_date)
> AND MONTH(datetime) = MONTH(current_date)
> 
> I haven't actually run this; there may be typos, but it should be pretty
> close.

Pretty close!  Just some misplaced parens:

SELECT
  monthname(datetime),
  SUM( IF(type = 'issue', 1, 0 )) as issues,
  SUM( IF(type = 'renew', 1, 0 )) as renewals,
  SUM( IF(type = 'return', 1, 0 )) as returns
  FROM
  statistics
  WHERE
  YEAR(datetime) = YEAR(current_date)
  AND MONTH(datetime) = MONTH(current_date)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 16.11.04 - Setting a template cache directory

[Mark Alexander]

Excerpts from Craig Butosi's message of 2017-03-02 13:42:07 +:
> >You are missing the  entry in your koha-conf.xml file. 
> >That will bring a performance boost to >enable it.
> 
> Is there an expected, standard, or best directory path to use? The error is 
> clear enough; however, I'd like to define the directory with an appropriate 
> path.

In this bug comment:

  https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17951#c2

it was suggested that we use /var/cache/koha//templates,
so that was what I used, and it seems to work fine.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 16.11.04 - Setting a template cache directory

[Mark Alexander]

Excerpts from Mark Alexander's message of 2017-03-02 15:53:19 -0500:
> In this bug comment:
> 
>   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17951#c2
> 
> it was suggested that we use /var/cache/koha//templates,
> so that was what I used, and it seems to work fine.

I forgot to mention that I also had to use chown to make that directory
owned by the user associated with the instance:

  mkdir -p /var/cache/koha/INSTANCE/templates
  chown INSTANCE-koha:INSTANCE-koha /var/cache/koha/INSTANCE/templates
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Searching capability dies every few days - Zebra problem?

[Mark Alexander]

Excerpts from mpw's message of 2017-07-31 06:24:49 -0700:
> I set up Koha a few months ago and we're still learning the system. One
> thing we've noticed that presumably is not normal is that every few days the
> searching capability dies for some reason or other. My guess is that it has
> something to do with Zebra.

It might be this problem:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

I solved it on my installation using this:

https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to import loans data into Koha?

[Mark Alexander]

Excerpts from Mark Alexander's message of 2017-08-15 19:03:46 -0400:
> Excerpts from Chris Brown's message of 2017-08-15 21:06:52 +0100:
> > [...] but I was wondering if
> > there is a way to import data on current issues (loans)?  All we really
> > need to import is the item ID, the patron ID and the due-back date.
> 
> I did this by writing a script to convert the loan list generated by
> our our old library system (Mandarin) into a KOC file (Koha Offline
> Circulation File), and then importing that. [...]

I forgot to mention that each row in the the KOC file has a date, but
it is the issue date, not the due-back date.  When Koha imports the
file, it will calculate the due-back dates using the circulation rules
that you should have already defined.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to import loans data into Koha?

[Mark Alexander]

Excerpts from Chris Brown's message of 2017-08-15 21:06:52 +0100:
> We are migrating records from a few small community libraries (currently
> held as a fancy spreadsheet) into Koha 17.05. I have figured out how to
> migrate the biblio records, items and patron data but I was wondering if
> there is a way to import data on current issues (loans)?  All we really
> need to import is the item ID, the patron ID and the due-back date.

I did this by writing a script to convert the loan list generated by
our our old library system (Mandarin) into a KOC file (Koha Offline
Circulation File), and then importing that.  The KOC file format is
defined here:

https://wiki.koha-community.org/wiki/Koha_offline_circulation_file_format
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Import holds?

[Mark Alexander]

Excerpts from Katrin Fischer's message of 2017-08-15 12:47:45 +0200:
> holds information is stored differently in every ILS and at the moment 
> there exists no generic tool to import holds into Koha. For a migration 
> you could try to map the data you get out of Mandarin to the columns in 
> Koha's reserves table and then use a script or SQL to fill it. It can be 
> useful to place a few different holds in Koha first to see what data is 
> required/set by Koha itself.

Thank you.  That makes sense, and I was already thinking of doing
something like this.  But there aren't a large number of holds, and it
might be less time-consuming to enter them manually than to study the
database tables and write the script.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Import holds?

[Mark Alexander]

Our little (24K items) library has successfully moved from Mandarin to
Koha as of Tuesday.  I was able to import the catalog, patrons, and
checkouts (issues) from Mandarin by writing scripts to convert
Mandarin-generated data to Koha-compatible data.

The one missing thing is holds (reserves).  I'm still looking for a
way to generate a holds report in Mandarin, but assuming I can
generate such a report, I don't see a way to import hold information
into Koha.  I was able to use KOC files to import issues, but the KOC
file format doesn't support holds.  I was wondering if there is some
other way to import holds programmatically, or if anyone else has had
to deal with this problem when migrating to Koha.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Patron Club feature

[Mark Alexander]

Excerpts from Krishna K's message of 2017-07-30 06:02:15 +:
> We recently upgraded to 17.05.01 from 16.11.05. When we try to use the
> clubs feature by clicking on Tools-> Patron Clubs link, we are getting 404
> error. We dont seem to be having the clubs.pl file. What should we do ?
> Appreciate your inputs.

[Apologies if this is a dupe message; my previous reply seems to
have been rejected by the list server.]

I think there may be problem with the koha-common package.  I don't
see clubs.pl in there:

  % dpkg -L koha-common | egrep clubs
  /usr/share/koha/opac/cgi-bin/opac/clubs
  /usr/share/koha/opac/cgi-bin/opac/clubs/clubs-tab.pl
  /usr/share/koha/opac/cgi-bin/opac/clubs/enroll.pl
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/clubs-tab.tt
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/enroll.tt
  /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/templates-add-modify.tt
  /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/clubs.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/clubs-add-modify.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/patron-enroll.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/patron-clubs-tab.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/club-enrollments.tt

But I do see clubs.pl in the git repository:

  % pwd
  /home/marka/shared/tools/kohaclone
  % ls -laF clubs
  total 36
  drwxr-xr-x  2 marka marka 4096 Jul 19 16:00 ./
  drwxr-xr-x 47 marka marka 4096 Aug  9 11:07 ../
  -rwxr-xr-x  1 marka marka 1267 Jul 19 16:00 club-enrollments.pl*
  -rwxr-xr-x  1 marka marka 3575 Jul 19 16:00 clubs-add-modify.pl*
  -rwxr-xr-x  1 marka marka 1740 Jul 19 16:00 clubs.pl*
  -rwxr-xr-x  1 marka marka 1504 Jul 19 16:00 patron-clubs-tab.pl*
  -rwxr-xr-x  1 marka marka 1358 Jul 19 16:00 patron-enroll.pl*
  -rwxr-xr-x  1 marka marka 5524 Jul 19 16:00 templates-add-modify.pl*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha slowed down by Google indexing?!

[Mark Alexander]

Excerpts from Michael Kuhn's message of 2017-05-03 16:14:55 +0200:
>   # ufw status
>   Status: active
> 
>   To Action  From
>   -- --  
>   22/tcp ALLOW   Anywhere
>   80/tcp ALLOW   Anywhere
>   8080/tcp   ALLOW   Anywhere
>   Anywhere   DENY66.249.64.32
> 
> But however this is possible, still Googlebot is crawling and eating 
> CPU!

I haven't used UFW, but I'm looking at the documentation here:

  https://help.ubuntu.com/community/UFW

and it seems that the order of the rules is important.  Quote:

  Once a rule is matched the others will not be evaluated (see manual
  below) so you must put the specific rules first. As rules change you
  may need to delete old rules to ensure that new rules are put in the
  proper order. 

and from the man page:

  Rule ordering is important and the first match wins. Therefore when
  adding rules, add the more specific rules first with more general
  rules later. 

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Slow Koha OPAC login process

[Mark Alexander]

Excerpts from Michael Kuhn's message of 2017-05-09 19:57:51 +0200:
> With my poor Perl knowledge I have now measured the execution time of 
> the various parts of script "opac-user.pl". As I found out everything is 
> always very fast (using less than 1 second execution time) except the 
> very last function in this script which looks as follows:
> 
> output_with_http_headers $cgi, $cookie, $template->output, $content_type;

I am not familiar with this code, but I took a quick look at it just
now.  If I were trying to debug this problem, I would measure the
execution time of the last statement in output_with_http_headers:

print $query->header($options), $data;

If I understand correctly, this print is going to send a big blob of
HTML (preceded by a header) via Apache to the client.  If Apache is
timing out for some reason, perhaps that would cause a big delay in
this print statement.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Digest, Vol 139, Issue 14

[Mark Alexander]

Excerpts from Ghulam Mustafa Zaman's message of 2017-05-09 07:15:05 -0200:
> i am new koha user and recently i have applied koha software in my college
> library so i need help in few functions like how to create backup of Data .

This should help:

https://wiki.koha-community.org/wiki/Backing_up_Koha

(This is the first hit you get with a Google search for "koha backup").
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Status lost for items

[Mark Alexander]

Excerpts from Søren Hovmand's message of 2017-06-22 14:03:15 +:
> To my question - apologies if it should be obvious: Where do I mark
> an item lost? I can find documentation on where it should be (Item
> Statuses/Edit item) but not find the option anywhere in our test
> installation (version 16.05.05.000)

I found this confusing, too.  If you look at the page source for the
"Edit item" page, the field for setting the "lost" status is
marked as invisible.

Instead, when you are looking at the biblio record, click on the "Items" tab
at the left side of the page.  Then you'll see a form where the "Lost status"
can be changed.  This is described here:

http://manual.koha-community.org/16.05/en/catitems.html#itemquickedit
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha slowed down by Google indexing?!

[Mark Alexander]

> When I searched for who is 66.249.64.32 I saw this IP addresse belongs
> to Google.

This does seem to be the Google indexer:

  % nslookup 66.249.64.32
  ...
  32.64.249.66.in-addr.arpa name = crawl-66-249-64-32.googlebot.com.

I haven't seen this problem (yet), but perhaps that is because I have
a /usr/share/koha/opac/htdocs/robots.txt containing this:

Crawl-delay: 60

User-agent: *
Disallow: /

User-agent: Googlebot
Disallow: /cgi-bin/koha/opac-search.pl
Disallow: /cgi-bin/koha/opac-showmarc.pl
Disallow: /cgi-bin/koha/opac-detailprint.pl
Disallow: /cgi-bin/koha/opac-ISBDdetail.pl
Disallow: /cgi-bin/koha/opac-MARCdetail.pl
Disallow: /cgi-bin/koha/opac-reserve.pl
Disallow: /cgi-bin/koha/opac-export.pl
Disallow: /cgi-bin/koha/opac-detail.pl
Disallow: /cgi-bin/koha/opac-authoritiesdetail.pl
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Data not found

[Mark Alexander]

Excerpts from Luis Moises Rojas's message of 2017-09-15 09:23:17 -0400:
> Everyday in the morning, i have to run this script:
> Koha-rebuild-zebra -f -v -b -r {Koha instance}
> 
> if i do not do this: we can not see any data, not search is found, etc.
> Why?

It could be that the zebra server is not running.  Try this:

https://wiki.koha-community.org/wiki/Koha_on_Debian#Anacron
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Z39.50, ILL, and 952$r

[Mark Alexander]

Our little state (hint: starts with "V") has implemented an
interlibrary loan system that seems to be unable to use Z39.50
correctly to query Koha in order to determine an item's availability.
I'll try to describe the problem and then ask if there's a workaround
in Koha.

The state ILL system, called CLOVER, is able to use Z39.50 to query
our library's Koha installation to determine whether an item is in our
catalog.  We told the state to use the MARC 952$r field returned by
Koha (actually Zebra, if I understand correctly) to determine whether
the item is available.  This field contains the item's due date.  If
it is present and contains a date, the item is NOT available.  If it
is not present, the item IS available.

But apparently, CLOVER is not able to handle a MARC field that is
present sometimes and not at other times.  It requires that the field
be present ALL the time.  That is the explanation given to us by the
state when we asked why CLOVER wasn't working correctly (it keeps
issuing requests for books that it had already requested).  This seems
like a serious bug, because there are at least 80 other Koha
installations in our state.  Unfortunately, CLOVER is closed-source
and proprietary, so there seems to be no way for the state to fix the
problem.

Is there some workaround that I can implement in Koha and/or Zebra to
force the 952$r field to be present in all records returned in
response a Z39.50 query?  I think CLOVER might work if 952$r were
present but blank for items that are available.

Thanks in advance!
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Z39.50, ILL, and 952$r

[Mark Alexander]

Excerpts from Jason Robb's message of 2017-09-21 16:53:16 -0500:
> Along with the other systems that use Koha in Kansas, we have worked with
> ByWater on this. You can see the details here: https://bugs.koha-
> community.org/bugzilla3/show_bug.cgi?id=13937. The basic idea is that
> whenever a z39.50 request is made, Koha will populate a status into a
> singular subfield that can be mapped and read by the external ILL software.

Thanks!  I ran across that bug a few minutes before I saw your reply.
The proposed solution looks good.  Is there a plan to incorporate it
eventually into the official Debian package?
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Z39.50, ILL, and 952$r

[Mark Alexander]

I made a silly mistake in my previous message: I meant 952$q (onloan),
not 952$r (datelastseen).
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Hide MARC View separator

[Mark Alexander]

Excerpts from | dalmeida |'s message of 2017-09-16 18:57:03 +0100:
> Does anyone know how to hide MARC View separator on book Details page? I'd
> like to have only Normal View and ISBD View.

I used the following as a hint:

  
https://wiki.koha-community.org/wiki/JQuery_Library#Hide_Marc_.26_ISBD_view_from_OPAC

which recommended using:

  $(".view a:contains('MARC view')").hide();

But using Firefox's "Inspect Element" feature, I saw that the "MARC view" tab
has an ID of "MARCview".  So I was able to simplify the Javascript in
OPACUserJS preference to the following:

  $(document).ready(function(){
$("#MARCview").hide();
  });

Note: I tested this only on 17.05.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Z39.50, ILL, and 952$r

[Mark Alexander]

Excerpts from Tomas Cohen Arazi's message of 2017-09-21 23:44:56 +:
> Wow. I hadn't noticed that new feature!

I applied the patches to our Koha installation and it does seem to work
when I invoke the server as follows:

  koha-shell 
  cd /usr/share/koha
  perl bin/z3950_responder.pl --add-item-status=k tcp:@:

I realize that patching an installation made from a Debian package is
not recommended, but I'm comfortable with this sort of thing, and I was
in a bit of a hurry to fix the ILL problem.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 4 Perl Modules Not Installed on Koha 17.05.03.000

[Mark Alexander]

Excerpts from Mark Tompsett's message of 2017-09-05 14:10:59 +:
> The major problem with cpan'ing your modules is that if you cpan them, and 
> then a newer version comes out with a fix/enhancement, the search paths used 
> by Perl will more likely find your CPAN'd versions rather than the DEB'd 
> versions. This is why cpan2deb (or the 3rd suggestion) is what I tend to do 
> if the first 2 ways don't work.

Thanks, that helps.  cpan2deb worked for me.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Kitchen sink plugin and GetBranchName

[Mark Alexander]

In order to learn how to write a plugin, I installed the Kitchen sink plugin:

  https://github.com/bywatersolutions/koha-plugin-kitchen-sink

into stock Koha 17.05.  When I ran the plugin's report tool, I got
this error:

  Undefined subroutine 
::Plugin::Com::ByWaterSolutions::KitchenSink::GetBranchName called at 
/var/lib/koha/rpl/plugins/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm line 
372.

The code in question is this:

$template->param(
date_ran => dt_from_string(),
results_loop => \@results,
branch   => GetBranchName($branch),
);

After poking around in the Koha git repository, I saw that GetBranchName
was removed by this commit:

  commit 19a977dc7b779173c4a3e96b6b06dc35db663601
  Author: Jonathan Druart 
  Date:   Tue Feb 2 17:28:30 2016 +

  Bug 15758: Koha::Libraries - Remove GetBranchName

I was able to fix the plugin by replacing the line with the GetBranchName call
with this line:

branch   => Koha::Libraries->find($branch)->branchname,
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 16.11.04 - Setting a template cache directory

[Mark Alexander]

Excerpts from Prof. Lisandro Laura's message of 2017-08-26 11:05:34 -0300:
> Could anyone please point me to a simple step by step instruction to
> set  entry in my koha-conf.xml file?

As I mentioned in my earlier email, I created the cache directory as follows:

  mkdir -p /var/cache/koha/INSTANCE/templates
  chown INSTANCE-koha:INSTANCE-koha /var/cache/koha/INSTANCE/templates

Then I added the following line at the end of the  section
in /etc/koha/sites/INSTANCE/koha-conf.xml:

 /var/cache/koha/INSTANCE/templates

In all of the above instructions, replace INSTANCE with your actual
library instance name.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 4 Perl Modules Not Installed on Koha 17.05.03.000

[Mark Alexander]

Excerpts from Mark Tompsett's message of 2017-09-05 03:57:06 +:
> > WebService::ILS (0.07)
> 
> On newer versions this is the only one that you will probably care about.

Can you explain what this module is used for in Koha?  It was missing
in my installations of 17.05.03, but Koha seemed happy without it.

On my test VM, I installed it using 'cpan -i WebService::ILS'.
Is there any reason why this method isn't mentioned on this page?

https://wiki.koha-community.org/wiki/How_to_install_missing_Perl_modules_on_Debian
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Regexp in MARC modification action

[Mark Alexander]

Excerpts from Jonathan Druart's message of 2017-11-26 16:45:08 +:
> The "ig" in the modifiers input is a placeholder, not the default.
> It is displayed as it to let you know 'i' and/or 'g' are possible modifiers.
> Please try again explicitly specifying "ig" in the input box and it should
> work.

Thanks, that worked.  I was confused by the faint gray "ig" in the input box
because I thought that field wasn't editable.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] OAI-PMH Set Question

[Mark Alexander]

Excerpts from Alphie Garcia's message of 2017-11-22 09:56:03 -1000:
> When I'm in Linux and type:
> 
> perl /usr/share/koha/bin/migration_tools/build_oai_sets.pl
> 
> 
> I get the following error:
> 
> Can't locate C4/Context.pm in @INC (you may need to install the C4::Context
> module) (@INC contains: /etc/perl

Try running this command first:

  koha-shell INSTANCE

where INSTANCE is the name of your Koha instance.  That should set up
the environment so that the build_oai_sets.pl script will run correctly.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Regexp in MARC modification action

[Mark Alexander]

I'm trying to use a MARC modification template to fix the 952$d field
in MARC records we receive from our library supply house.  This field
is supposed to be the acquisition date, but is coming to us in the
format /MM/DD instead of the required -MM-DD.  So I needed to
find a way to replace the slashes with dashes. 

I created a MARC modification template with a simple action that uses
the regular expression s/\//-/ig.  The UI for creating the action in
Koha implies that the "ig" modifiers are always used (though there
doesn't seem to be any way to change them).  My understanding of the
"g" modifier in Perl is that it causes the s// operator to "replace
globally, that is, all occurrences".  (This is a quote from an old
copy of "Programming Perl" by Wall et. al.)

Yet it doesn't seem that the "g" modifier is really being used.  When
I used this template on an imported MARC record, it changed the first
slash in 952$d, but not the second one.  So, for example, 2017/11/06
got changed to 2017-11/06.  I had to add a second action to the
template, identical to the first action, to cause the second slash to be
replaced. 

Am I misunderstanding the use of regular expressions in MARC
modification templates, and in particular the behavior of the "g"
modifier?  Or is this a possible bug?
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] ILS Z39.50 server information where to look for?

[Mark Alexander]

Excerpts from Bustillos, Corina's message of 2017-12-15 19:20:55 +:
> I was wondering if anyone knows where I can find the following information 
> within KOHA.
> IP address of the ILS Z39.50 server
> Port that Ze9.50 searches use
> Database name.

By default the Z39.50 server has the same IP address as your Koha
server, port 9998, database biblios.  The port and database are
defined in /etc/koha/sites/LIBRARY/koha-conf.xml, where LIBRARY is the
Koha instance name. 

You can test this using this:

  yaz-client mylibrary.example.com:9998/biblios

Replace mylibrary.example.com with your actual hostname or IP address.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] koha not sending email notices for Check in, Check out, Overdue etc.

[Mark Alexander]

Excerpts from Javed Sahil's message of 2017-12-01 12:36:37 +0500:
> *# PERL5LIB="/usr/share/koha/lib"#
> KOHA_CONF="/etc/koha/sites/library/koha-conf.xml"# cd
> /usr/share/koha/bin/cronjobs*
> 
> above commands go fine but when i try the following command,
> 
> *# ./*process_message_queue.pl
> 
> it returns
> 
> unable to locate Koha configuration file koha-conf.xml at
> /usr/share/koha/lib/C4/Context.pm line 242.

Try using this command first:

   koha-shell LIBRARY

where LIBRARY is your Koha instance name.  This should set
up the environment correctly to run the various scripts.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Email status changes failed from pending

[Mark Alexander]

Excerpts from Javed Sahil's message of 2017-12-03 16:05:23 +0500:
> 5../process_message_queue.pl
> 
> this error message appears:
> 
> connect to localhost failed (Connection refused)

This sounds to me like a postfix configuration problem.

What happens when you try this?

  telnet localhost 25

This should connect to the postfix SMTP server.

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] SQL help please

[Mark Alexander]

Excerpts from Pedro Amorim's message of 2017-12-11 14:18:08 -0100:
> This should work:
> 
> Select title, author, i.itemcallnumber from biblio b
> Left join biblioitems bi on b.biblionumber=bi.biblionumber
> Left join items i on bi.biblionumber=i.biblionumber
> where i.barcode IN ("BARCODE1", "BARCODE2", "BARCODE3");

This can also be made into an SQL report using multiple entry fields
for the barcodes.  It's a bit of a kludge but seems to work because
the blank fields are treated either as '' or NULL in the generated SQL.

Select title, author, i.itemcallnumber from biblio b
Left join biblioitems bi on b.biblionumber=bi.biblionumber
Left join items i on bi.biblionumber=i.biblionumber
where i.barcode = <>
or i.barcode = <>
or i.barcode = <>
or i.barcode = <>
or i.barcode = <>
or i.barcode = <>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Can't run auth_show_hidden_data.pl script

[Mark Alexander]

Excerpts from Prof. Lisandro Laura's message of 2017-12-06 11:41:57 -0300:
> perl ./usr/share/koha/bin/maintenance/auth_show_hidden_data.pl
> 
> But I get the following error:
> 
> "Can't locate Koha/Authorities.pm in @INC (you may need to install the
> Koha::Authorities module) (@INC contains: /etc/perl

This sounds familiar.  Try running the following command first:

  koha-shell LIBRARY

where LIBRARY is your Koha instance name.  After that, the various
Koha shell scripts should work.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] SQL Report not populating

[Mark Alexander]

I tried your query with the WHERE clause slightly simplified to
give a non-empty result on my test installation of 18.05:

  WHERE (TO_DAYS(curdate())-TO_DAYS(date_due)) >= ''

I was then able to download the CSV file and read it into LibreOffice
Calc with no problems.

So your query looks good; maybe take a look at the CSV file in
an editor to see if there's anything strange about it.  Or perhaps
you have to tell your CSV import tool to use commas, and not semicolons
or other delimiters (LibreOffice has several options for this).
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Migration from Mandarin to Koha

[Mark Alexander]

Excerpts from Mr Mutsikiwa Admire's message of 2018-06-15 16:55:38 +0200:
> I want to migrate bibliographic records from a Mandarin to Koha. 
> Currently, I am guided by the resource 
> http://www.bloovis.com/2017/08/09/mandarin-to-koha.html. I am wondering 
> if there are any generic resources that could aid in the migration 
> process.

I am the author of that guide (which may be slightly out of date,
since I wrote it almost a year ago).  I had to develop my own
Mandarin-to-Koha migration scripts because I couldn't find any existing
tools to do the job.

Are you having problems with the scripts I wrote?  If so, feel free
to write to me privately and I may be able to help.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Fwd: OPAC Page not available and login credentials don't work

[Mark Alexander]

Excerpts from Bedanta Borah's message of 2018-05-28 10:45:54 -0700:
> 2) In case of  koha livedvd, all features were doing fine untill I updated
> the system and the koha-common packages. After the update, my root user and
> password (koha_library & koha123) stopped working. But I can login with
> another patron which I had created before the update was done. Why I loose
> database user access after updating the software?
> 
> Q) How can I regain the database user access?

I'm not sure if the following will help, but I did notice something
that may be related in the release notes for 18.05 here:

  https://koha-community.org/koha-18-05-released/

Here is what they say about this issue:

  No more login with the database user

  It is no longer possible to use the database user to login into Koha.
  You should first create a superlibrarian patron and use it for logging in.
  [...]
  It is no longer possible to use the database user (defined in koha-conf.xml) 
to login into Koha.
  You should first create a superlibrarian patron and use it for logging in.
  See the script misc/devel/create_superlibrarian.pl

This was discussed in this bug:

  https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] ssl for koha login

[Mark Alexander]

Excerpts from Alvaro Cornejo's message of 2018-06-04 21:18:57 -0500:
> I´m trying to setup a ssl connection to Koha  (using letsEncrypt certs ) so
> my users, admin and opac can have a secure connection.
> 
> I´ve folllowed letsEncrypt & certbot instrucctions but neither opac nor
> admin pages work.

I used certbot on Debian 8 to get the OPAC and staff clients to use
SSL.  If I recall correctly, certbot attempted to modify my Apache
config file to add references to the LetsEncrypt certificate files,
but I think it chose the wrong file to modify.  So I hand-modified the
Koha-specific config file to point to the certificates.

Below is the resulting /etc/apache2/sites-available/LIB.conf.  Replace
LIB with the actual Koha instance name, and replace KOHA.MYLIBRARY.COM
with the actual hostname.  Note also that I chose port 81 for the OPAC
and port 82 for the staff client; you will probably need to change
those numbers.

# Koha instance LIB Apache config.

# OPAC

  = 2.4>
   Define instance "LIB"
  
   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-opac-plack.conf
   Include /etc/koha/apache-shared-opac.conf

   ServerName KOHA.MYLIBRARY.COM
   SetEnv KOHA_CONF "/etc/koha/sites/LIB/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
   SetEnv MEMCACHED_NAMESPACE "koha_LIB"
   AssignUserID LIB-koha LIB-koha

   ErrorLog/var/log/koha/LIB/opac-error.log
#  TransferLog /var/log/koha/LIB/opac-access.log
#  RewriteLog  /var/log/koha/LIB/opac-rewrite.log
SSLCertificateFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf


# Intranet

  = 2.4>
   Define instance "LIB"
  
   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
  Include /etc/koha/apache-shared-intranet-plack.conf
   Include /etc/koha/apache-shared-intranet.conf
   
   ServerName KOHA.MYLIBRARY.COM
   SetEnv KOHA_CONF "/etc/koha/sites/LIB/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
   SetEnv MEMCACHED_NAMESPACE "koha_LIB"
   AssignUserID LIB-koha LIB-koha

   ErrorLog/var/log/koha/LIB/intranet-error.log
#  TransferLog /var/log/koha/LIB/intranet-access.log
#  RewriteLog  /var/log/koha/LIB/intranet-rewrite.log
SSLCertificateFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/KOHA.MYLIBRARY.COM/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Can't locate LangInstaller.pm in @INC

[Mark Alexander]

> > root@srv2:/usr/share/koha/misc/translator# perl 
> > -I/usr/share/koha/misc/translator translate install it-IT
> > Can't locate TmplTokenizer.pm in @INC (you may need to install the 
> > TmplTokenizer module) (@INC contains: /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) at 
> > /usr/share/koha/misc/translator/tmpl_process3.pl line 20.
[...]
> sudo koha-shell instancename

This problem comes up so frequently that I wonder if the scripts
could check for it and suggest a fix, along these lines:

if (!defined($ENV{KOHA_CONF}) && !defined($ENV{PERL5LIB})) {
   die("Please run koha-shell first.");
}
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] SQL help

[Mark Alexander]

Excerpts from Elaine Bradtke's message of 2018-01-09 11:06:16 -0800:
> "Unknown column 'place' in 'field list'"
> Here's the report - what field name do I need to replace place?:
> select
>   b.biblionumber, author, title,
>   ExtractValue(metadata, '//datafield[@tag="245"]/subfield[@code="b"]') as
> subtitle,
>   ExtractValue(metadata, '//datafield[@tag="250"]/subfield[@code="a"]') as
> edition,
>   copyrightdate, place, publishercode, isbn
> from
>   items as a
> left join
>   biblio_metadata as b on (a.biblioitemnumber = b.biblioitemnumber)
> left join
>   biblio as c on (b.biblionumber = c.biblionumber)
> where
>   itype = 'BK' and holdingbranch = 'VWML'
> order by author asc

I took a look at the 17.05 schema here: 
http://schema.koha-community.org/17_05/index.html.
It seems that some things have been moved to biblioitems, though I'm not
familiar with the history.

I was able to get your query to work (or at least, not give errors) by
rewriting it as follows:

select
  biblionumber,
  biblio.author,
  biblio.title,
  ExtractValue(biblio_metadata.metadata, 
'//datafield[@tag="245"]/subfield[@code="b"]') as subtitle,
  ExtractValue(biblio_metadata.metadata, 
'//datafield[@tag="250"]/subfield[@code="a"]') as edition,
  biblio.copyrightdate,
  biblioitems.place,
  biblioitems.publishercode,
  biblioitems.isbn
  from items
  left join biblioitems using (biblionumber)
  left join biblio_metadata using (biblionumber)
  left join biblio using (biblionumber)
  where  itype = 'BK' and holdingbranch = 'VWML'
  order by author asc;
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Export from one library, Import to another?

[Mark Alexander]

Excerpts from Alvin W.'s message of 2018-01-15 16:43:12 -0500:
> Basically, I don't care about the content, I just want a verified file that
> I was able to Import correctly, to serve as a baseline for the actual
> collection when I load it, so that if errors occur, it should be easier to
> figure out exactly what went wrong.

I had to go through this process when I converted our library
from Mandarin to Koha.  Mandarin exported its catalog in MARC
format, but I had to do a fair amount of work (using scripts that
I wrote) to modify the holding fields so that Koha would accept them.

A good starting point for understanding the issues is this
document:

https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx)

You'll notice that a number of the fields (such as collection code,
branchcode, shelving location code, and Koha item type) will need to
have values that match values that you have previously set up in Koha.
Collection code and shelving location code must match authorized
values for CCODE and LOC, respectively.  The branchcode must match
codes that you've set up for library branches.  The item type must
match the item types you've set up.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Import of .KOC file into Koha 17.11 hangs

[Mark Alexander]

Excerpts from Chris Brown's message of 2017-12-27 17:03:17 +:
> Using a fresh install of Koha 17.11.00 (from Debian packages) I have
> successfully loaded our patron data, our catalog and our items. However
> when I try to import an offline circulation (.koc) file, nothing happens.
> The progress bar sits at 0% and nothing is imported.

I just tried this with a six-entry .koc file on a test installation of
17.11.00 in a VM and it seemed to work.  The progress bar did stay at
0% for a lengthy period, maybe 15 seconds, which was a little
alarming.  During that time, the VM seemed quite CPU-bound and I
couldn't ssh into it; this might be due to the fact that the VM had
only 1 GB of RAM.  But eventually it did complete and reported that
"your data was processed" along with a list of the processed items.

Here's what my test file looked like, in case that might help.  Note
that there are tabs separating the fields, not spaces.  Note also that
this file was generated by a script I wrote to convert a Mandarin loan
report to .koc, hence the funny looking timestamps.

Version=1.0 Generator=pdf2koc.rbGeneratorVersion=0.1
2017-08-05 12:30:00 0   issue   R7306   RPL24055
2015-07-09 12:30:00 1   issue   R1786   RPL26855
2017-07-25 12:30:00 2   issue   R1786   RPL22690
2017-08-01 12:30:00 3   issue   R1786   RPL24021
2017-08-01 12:30:00 4   issue   R1786   RPL23969
2017-08-01 12:30:00 5   issue   R1786   RPL28030
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Problems adding new members in 17.11

[Mark Alexander]

Excerpts from Tim McMahon's message of 2018-01-02 16:26:39 -0600:
> I'm testing 17.11 (package upgrade from 17.05.02) and when I try to 
> enter a new patron, the Password and Confirm password fields in the 
> OPAC/Staff login section near the bottom of the form will get labeled 
> "This field is required."

I can confirm this behavior on my test VM of 17.11

Curiously, during my test of adding a new patron, the "required"
labels on the Password and Confirm fields didn't appear when I first
loaded the form. They only showed up after I hit the "Save" button,
which failed to save, and presented me with the form again, this time
with the labels added.

I got around the problem by putting the word "junk" in for the
passwords, and leaving the username blank.  Then when I edited that
patron again, I found that Koha had auto-generated a user name
consisting of the first and last names of the patron concatenated with
a "." separator.

In summary, I couldn't find a way to enter blank usernames or passwords
for patrons.  I don't recall that 17.05 exhibited this behavior.

> I also noticed that the primary and secondary email fields aren't 
> validating either.

I didn't see a problem with these fields.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra shutting down - no search

[Mark Alexander]

Excerpts from Scott Owen's message of 2018-06-21 09:16:56 -0400:
> I still seem to be having some issues with logrotate and the zebra service
> starting up
> 
> I have tried both of the options discussed in bug #
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

I was able to solve this problem by disabling anacron, as described here:

https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reservoir records deletion

[Mark Alexander]

Excerpts from Hira Akram's message of 2018-08-09 17:30:07 +0500:
> I want to delete all biblio records from my koha but they are still appearing 
> in reservoir. How to remove them? I have deleted them from catalogue and they 
> are not imported so I cant clean the batch.

This is how I did it:

  koha-shell LIB  # LIB is your Koha instance name
  /usr/share/koha/bin/cronjobs/cleanup_database.pl --import 60 -v

Here is what the --help option says about this:

   --import DAYS  purge records from import tables older than DAYS days.
  Defaults to 60 days if no days specified.

Also see:

  http://koha.1045719.n5.nabble.com/Biblios-in-reservoir-td5965405.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 18.05.01 up gradation login access denied

[Mark Alexander]

Excerpts from Arshad Iqbal's message of 2018-07-16 17:59:22 +0500:
> I have upgraded koha version 16.05 to 18.05.01. After  upgraded i am trying
> to login with master username and password but access denied to login error
> facing.

This is described in the release notes for 18.05:

https://koha-community.org/koha-18-05-released/

Quote:

It is no longer possible to use the database user (defined in
koha-conf.xml) to login into Koha.  You should first create a
superlibrarian patron and use it for logging in.
See the script misc/devel/create_superlibrarian.pl

Also see this bug:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] added new library branch -- lost all collections

[Mark Alexander]

Excerpts from Jack Boulier's message of 2018-04-11 04:25:23 +:
> I have ubuntu xenial and koha 17.11.04. I added a new library to the database 
> and added some books to that library. When I did a search for the text I 
> could not find them as a superuser. The search would always query the 
> original database and not the new branch. In the database I was able to 
> locate the records with an SQL query. I attempted to run the 
> koha-rebuild-zebra library attempting to get the collection updated. Now I 
> have lost the entire collection. However the database is still complete in 
> mariadb.
> Now I can not locate any items in the database.

As an experiment, try using the advanced search in the staff client
(cgi-bin/koha/catalogue/search.pl). Then under the headings
"Location and availability" and "Individual libraries", try selecting
your new library and redoing the search.  Maybe this won't help, but it
would be a data point in the debugging process.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Zebra stops every day

[Mark Alexander]

Excerpts from Javed Sahil's message of 2018-04-04 17:44:23 +:
> I am using Koha17.11, I moved my old DB which was working fine in koha16.11,
> 
> But now my zebra server stops daily or after two or three days,  actually
> i have not noted exact duration.

It might be this problem:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885

If so, this is the solution that worked for me:

https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Importing MARC records with items

[Mark Alexander]

Excerpts from Sean Carte's message of 2018-04-18 10:44:45 +0200:
> I have records that I have exported from SirsiDynix Symphony that I'm
> trying to import into a new instance of Koha. The bib records load, but the
> items are not added.
>[...]
> 952
> 
> *_a*657 GAA V.1

This doesn't look quite right to me.  According to the holdings table
in the wiki:

https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx)

952$a and 952$b should contain the branch codes for owning library
and holding library, respectively.  Your 952$a doesn't look like
a branch code, and I don't see a 952$b.

When I imported our Mandarin catalog to Koha, my script set the following
rather minimal holding fields, and that seemed to be enough:

 942$c - item type
 952$8 - collection code
 952$a - owning library
 952$b - holding library
 952$c - location code
 952$d - acquisition date
 952$o - call number
 952$p - barcode
 952$v - price
 952$y - item type

Note that you need to have previously set up the authorized values for 
collection
codes and location codes for this to work.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Out of memory

[Mark Alexander]

Excerpts from Rubeno Fernández's message of 2018-03-19 07:12:29 +0100:
> How much memory do you need to run Koha?
> I run a database with about 22000 records on a virtual server on Digital 
> Ocean 
> with 1GB memory and very low usage, but the server is crashing very often.

We're running Koha 17.11.02 on Linode (Debian 8) with 2 GB of RAM, and
our library has about 25000 item records.  So far we haven't had any out
of memory problems.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Mark Alexander]

Excerpts from Narcis Garcia's message of 2018-03-20 10:38:26 +0100:
> 1. What is the concrete indicator that Plack is enabled and running or not?

In the "About Koha" page, immediately after the "Apache version:" line, you 
should
see a line that looks like this:

PSGI:   Plack (deployment)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] DDoS attack on memcached

[Mark Alexander]

Apparently, a bug in memcached (which we use in Koha) causes it to be
used an intermediary in a DDoS attack:

https://arstechnica.com/information-technology/2018/02/in-the-wild-ddoses-use-new-way-to-achieve-unthinkable-sizes/

I'm not an expert on this kind of thing by any means, but judging
from this:

  https://github.com/memcached/memcached/wiki/ReleaseNotes156

It seems that we can disable the attack by preventing memcached from
listening on a UDP port.  I was able to do this by adding the
following lines to /etc/memcached.conf:

  # Disable UDP
  -U 0

Then restarted memcached and apache2.

My questions for the experts: Is this the correct approach?  Is it even 
necessary?
Is there more we should do?
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Matric Number and Barcode not Showing on Library Card

[Mark Alexander]

Excerpts from olufunmilayo favour's message of 2018-11-07 08:01:57 +:

> I configured my university's koha library card and it works
> perfectly for the undergraduate students whose matriculation numbers
> are in this format AAA/12345678 and varchar was selected for the type
> at PHPMyAdmin. However, using the same card layout, for the
> postgraduate students whose matriculation numbers are in the format
> BBB/pg/17/, the matriculation numbers (card numbers) and the
> barcode do not come out when the cards are printed. Card numbers are
> supposed to be printed printed as barcode. Our Koha LMS is Ubuntu OS
> based. 

> Can someone tell me what the problem is and suggest how to go round it please?

I suspect the problem is that the card numbers include lower case letters 
("pg").
If your card layout uses Code 39 for the barcode, that won't work because
Code 39 does not allow lower case letters.  See this:

  https://en.wikipedia.org/wiki/Code_39

I tried this on my own system, and verified this behavior.  However, when I 
changed
the card layout to use Code 39 + Modulo43 as the barcode format, which does 
support
lower case letters, Koha gave this error when I tried to export a library card 
batch:

  WARNING: Error while creating PDF file. Batch: 1 Layout: 1 Template: 1
  Please have your system administrator check the error log for details. 

I examined plack-error.log but didn't see anything that I could readily
understand as related to the problem.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] OPAC holdings table in 18.11 shows instead of blank

[Mark Alexander]

I've just upgraded one of my Koha VMs from 18.05 to 18.11, and also
created a new install of 18.11 in another VM, and both exibit a new
issue:

In the OPAC, when looking at the MARC view for an item, there is a
table at the bottom of the page showing some holding information.
Those table fields that used to be blank in 18.05 are now displaying
as "" (without the quotes) in 18.11.  In my particular case, the
fields that are displayed this way are:

* Withdrawn status
* Lost status
* Damaged status
* Not for loan

I have uploaded some screen shots here:

http://www.bloovis.com/artemis-18.05.png
http://www.bloovis.com/artemis-18.11.png

I tried to find something in Bugzilla about this but was not successful.
Is this a known problem?
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] OPAC holdings table in 18.11 shows instead of blank

[Mark Alexander]

Excerpts from Mark Alexander's message of 2018-12-22 11:56:33 -0500:
> In the OPAC, when looking at the MARC view for an item, there is a
> table at the bottom of the page showing some holding information.
> Those table fields that used to be blank in 18.05 are now displaying
> as "" (without the quotes) in 18.11.

After some searching, I believe this may be related to bug 13618.
I also looked at 21947, but that seems like a different issue
related to the changes for 13618.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] New OPAC design

[Mark Alexander]

This is wonderful work.  We're going to adopt it at our little rural
library, since most of our patrons are over 50, and we need to encourage
more young people to visit.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha importing biblio with items error

[Mark Alexander]

Excerpts from Dorothy Chong's message of 2019-02-12 20:14:48 +0800:
> Our library is hoping to transfer into Koha but has so far had issues with 
> staging the records with items. Without the 952 field it works fine, and it 
> also worked fine when it was just 952$a, $b, and $y. Whenever I try to stage 
> the file it just comes back with “fail to submit form: error”. What is the 
> problem with my MARC please?
> [...]
> =952  \\$a[library name]$b[library name]$o001.94 WIL$p06$yBook

I've run into import problems when either the library name or the
item type was invalid.

Make sure that "Book" is valid by visiting More / Administration /
Basic Parameters / Item types.  It should be one of the values in the
"Code" column.

Similarly, make sure that your library name is correct by visiting
More / Administration / Basic Parameters / Libraries.  The library
name should be one of values in the "Code" column.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Duplicating Items

[Mark Alexander]

Excerpts from Myriam Torres's message of 2019-02-12 11:22:18 +0200:
> [...] The problem is that instead of creating a single item with
> all the information it creates many items with different information. This
> is my mrc file:
> [...]
> =952  \\$aAKL
> =952  \\$bAKL
> =952  \\$o005.265
> =952  \\$p0014915
> =952  \\$yBK

The problem is that Koha treats each 952 field as a separate item.
So in this example, you have five item records instead of one.
You will need to merge each 952 subfield into a single 952 field,
like this:

  =952  \\$aAKL \\$bAKL \\$o005.265 \\$p0014915 \\$yBK

(Apologies if I have the syntax wrong; I use my own scripts
instead of Marcedit.)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 18.11

[Mark Alexander]

Excerpts from Luisa Korodrau's message of 2019-04-19 08:12:05 +1200:
> 1. uploading photos for patrons record. The photo uploading icon is not
> there.  Where can I find it and how is it done

Have you set the "patronimages" system preference to "allow"?  There is some
information here:

https://koha-community.org/manual/18.11/en/html/patrons.html?highlight=patronimages#add-patron-images
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Report help needed - lost items

[Mark Alexander]

Excerpts from Elaine Bradtke's message of 2019-08-23 11:32:44 -0700:
> I've got the following adapted from one in the reports library.  But I need
> to limit it by item type, or not return everything that doesn't have an
> item record attached. We've got lots of components in our catalogue that
> don't have items and it's returning all of them:
> 
> SELECT
> CONCAT(
> ' bib.biblionumber,
> '\">',
> bib.title,
> ''
> ) AS Title,
> bib.title,
> bib.biblionumber,
> lostitems.barcode,
> lostitems.ccode,
> lostitems.onloan AS 'Checkout date'
> FROM
> biblio bib
> LEFT JOIN items ON (bib.biblionumber = items.biblionumber AND
> items.itemlost = 0)
> LEFT JOIN items AS lostitems ON (bib.biblionumber =
> lostitems.biblionumber AND lostitems.itemlost != 0)
> GROUP BY bib.biblionumber
> HAVING count(items.itemnumber) = 0

While I'm not an SQL expert by any means, I think I was able to get
this to work on my catalog by removing the HAVING clause and
putting "WHERE items.itemnumber IS NULL" before the GROUP clause:

SELECT
CONCAT(
'',
bib.title,
''
) AS Title,
bib.title,
bib.biblionumber,
lostitems.barcode,
lostitems.ccode,
lostitems.onloan AS 'Checkout date'
FROM
biblio bib
LEFT JOIN items ON (bib.biblionumber = items.biblionumber AND
items.itemlost = 0)
LEFT JOIN items AS lostitems ON (bib.biblionumber =
lostitems.biblionumber AND lostitems.itemlost != 0)
WHERE items.itemnumber IS NULL 
GROUP BY bib.biblionumber
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] R: Problem with browser

[Mark Alexander]

[I'm copying the mailing list in case the real experts have 
better advice.]

Excerpts from Davide Spanu's message of 2019-11-10 11:52:27 +0100:
> I have seen that to solve the problem I have to modify a file,
> eliminating the lines from 6 to 10 and add, in their place, the line
> "var popup = '[% popup | html%]';"

Actually, the patch describes the reverse of that.  It deletes this line:

   var popup = '[% popup | html %]';

and replaces it with these lines:

   [% IF popup %]
 var popup = true;
   [% ELSE %]
 var popup = false;
   [% END %]

> Can you tell me the name and path of the file to be modified on the server?

The file to be patched is here on 19.05:

  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/str/cataloging_additem.inc

I discovered this using the locate command:

  locate cataloging_additem.inc

Note that the locate command depends on a file location database being updated
regularly.  On my Debian installation, this wasn't being done as a cron job,
so I updated the database manually using this:

  updatedb

One way to patch the file without using an editor is to download the patch
to the directory in question 
(/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/str),
give it a name like additem.patch, and apply it using this command:

  patch http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Problem with browser

[Mark Alexander]

Excerpts from Davide Spanu's message of 2019-11-10 09:58:08 +0100:
> I have a problem with my koha server. I realized that after
> importing a record (so before entering the copy data) the window of
> some browsers closes automatically (Chrome and Firefox). Before this
> problem did not occur (and I did not change any settings in either
> Koha or the server). Can you tell me what it can depend on? 

This is a known bug:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23680

I manually applied the patch shown in comment 7 and that fixed the problem.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Creating Lists of Item Numbers

[Mark Alexander]

Excerpts from Charles Kelley's message of 2019-10-14 18:18:16 +0900:
> Can someone help me? Is there a tutorial on compiling item lists, bib.
> record lists, patron lists, etc.?

I believe that generating of lists is usually done with reports.
See this section of the Koha manual:

https://koha-community.org/manual/19.05/en/html/reports.html

Also see this page, which shows many sample reports:

https://wiki.koha-community.org/wiki/SQL_Reports_Library
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] need help with accessing koha from outside via DynDNS

[Mark Alexander]

Excerpts from Heinz-Jürgen Oertel's message of 2020-02-06 13:32:34 +0100:
> I can reach my network vi   something.dnshome.de 
> With a port forwarding 80 -> 80 in the network router I can reach the test 
> page of the apache server.
> How  can I reach the koha server

It's possible that Koha is listening on a port other than 80.  This is
controlled by the VirtualHost line(s) in your Koha installation's
configuration file in /etc/apache2/sites-available/INSTANCE.conf, where INSTANCE
is the name of your Koha instance.

You can see what ports are in use with this command:

netstat -pn --tcp --listen | grep apache
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Using Koha on Android devices for revision

[Mark Alexander]

Excerpts from asakov...@hmcpl.org's message of 2020-02-11 16:20:11 -0600:
> We’ve been evaluating the Tera Barcode Scanner Wireless 1D/2D/QR 2-in-1 unit 
> from Tera Digital (Germany).

Thank you for this recommendation.  I ordered the cheaper version of
this scanner that works only with 1D scancodes, which is all we need
at our library.  It makes the Koha inventory tool much easier to use:
I can walk around the library scanning books right at the shelf
instead of carrying the books to the computer and back.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cataloging tables, chairs, etc.

[Mark Alexander]

Many thanks to all who offered suggestions!  I've forwarded
them to our librarians (who are not on the mailing list).
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Cataloging tables, chairs, etc.

[Mark Alexander]

Our little library is planning to lend out things like folding tables, folding
chairs, cake pans, tools, and all sorts of other equipment.  I'm trying
to figure out the best way to set up circulation rules for these things.

My initial thought was to minimize the number of items types, and hence
circulations rules.  So we could have item types called "EQUIPMENT-3DAYS",
"EQUIPMENT-1WEEK", and "EQUIPMENT-1MONTH", the names of which reflect
how long the circulation period would be.  Then the various things
we could lend out would fall into one of these buckets.  But this means
that if a user was searching for items by item type in the OPAC, cake
pans might be listed next to power drills, and so forth.  Maybe that's OK;
I don't know.

I was wondering how other libraries deal with this kind of thing.

Thanks in advance!

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Printing overdue letters

[Mark Alexander]

Excerpts from Mark Alexander's message of 2020-01-04 20:27:31 -0500:
> I think this might work, except that I can't figure out how to get a
> patron's list of overdue books into the generated letter.  The SQL
> would need to produce a CSV file with a single row for each patron,
> containing the patron name, address, and an arbitrarily long list of
> overdue books.

A kind person replied off-list and gave me the magic I needed:
GROUP_CONCAT.  Thanks!

In case anyone is interested, here is the SQL I ended up using:

SELECT p.cardnumber,
  CONCAT(p.firstname, ' ', p.surname) as name,
  p.address,
  CONCAT(p.city, ', ', p.state, ' ', p.zipcode) as city,
  GROUP_CONCAT(CONCAT_WS(' ', REPLACE(b.title, ' /', ''),
 CONCAT('$', i.replacementprice))
   SEPARATOR '; ') as overdues
FROM borrowers p
LEFT JOIN issues c ON (p.borrowernumber=c.borrowernumber)
LEFT JOIN items i ON (c.itemnumber=i.itemnumber)
INNER JOIN biblio b ON (i.biblionumber=b.biblionumber)
WHERE (TO_DAYS(curdate())-TO_DAYS(date_due)) >= <>
GROUP BY cardnumber
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Printing overdue letters

[Mark Alexander]

My librarian has asked me to make Koha do something that doesn't sound
easy to me.  She'd like to be able to generate letters to each patron
having overdues more than N days (where N is a variable).  The letter
would be then be printed, stuffed into an envelope, and mailed with
the postal service.  I know that sounds old-fashioned, but she seems
to really want to do this instead of using Koha's ability to email
notices and messages.  I can understand this, knowing that in this part
of rural New England, many of our patrons are elderly and either don't
have email, or have it but don't want to give us their email
addresses.

I am not sure I can do this in a simple SQL report, which generates
a table, not a form letter.  So my next idea was to write
a report that outputs the needed information (patron name, address,
list of overdue books and their replacement price).  Then I'd
export the results of the report to a CSV file.  Then I'd
do a mail merge in Libre Office Writer (or Word, which the
librarian uses) using the data in the CSV file.

The generated letter might look like this:

  To: PATRON_ADDRESS

  Dear PATRON_NAME,

  You have the following overdue books:

 BOOK1_TITLE, BOOK1_PRICE
 BOOK2_TITLE, BOOK1_PRICE
 ...

  Thanks,
  Your library


I think this might work, except that I can't figure out how to get a
patron's list of overdue books into the generated letter.  The SQL
would need to produce a CSV file with a single row for each patron,
containing the patron name, address, and an arbitrarily long list of
overdue books.  I am not sure that is possible, but then, my SQL
skills are not so great.

Any help with this would be appreciated greatly.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Printing overdue letters

[Mark Alexander]

Excerpts from SATISH's message of 2020-01-06 17:34:26 +0530:
> To overcome this problem, I have complied separate Library Dues Management
> System using PHP and MySQL.

Interesting.  I was thinking of doing something along these lines using
a Koha plugin.  I find plugins really difficult to debug (based on my
experience with writing a couple of simple ones), but it might be a little
easier for the staff at our little library to deal with.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Mark a batch of items as missing?

[Mark Alexander]

Excerpts from Katrin Fischer's message of 2020-03-26 16:28:05 +0100:
> check the settings for the subfield in your bibliographic frameworks and
> make sure it's not hidden.

Thank you for this hint.  It turns out that in the default bibliographic 
framework
in our installation (upgraded to 19.05.04), the 952$1 field (lost status) is 
hidden.
The manual warns against trying to edit the default framework, so I won't change
this setting.

Unfortunately, when I imported our catalog from Mandarin back in 2017,
I wasn't aware of this issue and all of those items seem to be using
the default framework.  Newer items added that I've added are using
the books framework, in which 952$1 is not hidden, so the lost status
appears in the item editor.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Mark a batch of items as missing?

[Mark Alexander]

After doing some inventory in our library, I obtained a list of the
barcodes of a few dozen lost items.  Now I'd like use the batch item
modification tool to change the "lost status" for that set of items.
But I don't see a way to do that with this tool.  Is there another
way?  I'd like to avoid having to mark the items as missing one by
one.  I'll resort to SQL if necessary.

Thanks in advance!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [koha] Barcode as a link report

[Mark Alexander]

Excerpts from muirunyeri's message of 2020-05-18 13:05:56 +0300:
> I'm looking to create a report with barcode as a link that when will clicked 
> will open the edit items page.

There are some examples here that might help:

https://wiki.koha-community.org/wiki/SQL_Reports_Library#Links_by_item
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Barcode as a link report

[Mark Alexander]

Excerpts from muirunyeri's message of 2020-05-19 11:10:33 +0300:
> However if anybody would help me understand why I get an error (biblionumber 
> is ambiguous) after adding any field from biblio table I'd be really 
> grateful. This after correctly adding a left join for the biblios table using 
> biblionumber on itemnumber in items.

It would help if you could post your entire query.  But my guess is
that the ambiguity is the result of joining two tables that have
fields with the same name.  The items and biblio tables both have a
field called biblionumber.  So in your query, you have to fix the
ambiguity by using the table name as a prefix: e.g.,
items.biblionumber or biblio.biblionumber . 
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Holds and quarantine

[Mark Alexander]

I've tried to search my Koha mailing list archives, and studied the
19.05 manual for a solution to the following problem, but I'm either
overlooking something or the problem hasn't been discussed.

Our little library has a pandemic protocol where books that are returned (in
a drop box) are checked in twice a week, then put on a special quarantine table.
On Sunday a volunteer comes in and sanitizes the books.  Then they can be
checked out again.

The problem has to do with holds.  When a book with a hold is checked in,
the librarian has to respond to Koha's popup in one of two ways: press 
"Confirm",
or press "Ignore":

1. If the librarian presses "Confirm", then the patron will eventually
notice when they log into to their account that the book is ready
for pickup, when in fact it is on the quarantine table and is NOT
ready.

2. If the librian presses "Ignore", then the patron won't get notified
that their book is ready for pickup.  Instead, their hold is
still pending and the book is seen as available in the catalog.

Either choice isn't quite right.  What we'd like to have happen is for
the patron somehow to be informed that their book is ready for pickup
not when it's checked in, but AFTER it's gone through the quarantine
process, which takes an unpredictable amount of time.

I don't see how the CART shelving location functionality and cron job
can deal with both holds and unpredictable quarantine times.

Thanks in advance for any ideas!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] SIP2 and telnet.

[Mark Alexander]

Excerpts from sam aikins's message of 2020-10-18 03:09:06 +0800:
> Has anyone been able to telnet to SIP2 successfully.

It works for me, and I also wrote a couple of Ruby scripts that use telnet
to test the SIP2 connection.  Here's one of those with the library,
username, and password anonymized.

#!/usr/bin/env ruby
require 'ruby_expect'
host = ARGV[0] || 'localhost'
$logger = ::Logger.new($stdout)
$logger.level = ::Logger::DEBUG # was WARN
exp = RubyExpect::Expect.spawn("telnet #{host} 6001", {logger: $logger})
exp.procedure do
  # Expect each of the following
  each do
expect /Trying .*\.\.\./ do
end

expect /Connected to #{host}/ do
end

cmd93 = '9300CNuser|COpassword|CLIB|'
expect /Escape character is/ do
  send cmd93
end

# telnet echoes back everything we send, so we have to expect that.
expect cmd93 do
end

cmd23 = '2300120060101084235AOLIB|AAuser|ACsip_01|ADpassword|'
expect /941/ do
  send cmd23
end

# telnet echoes back everything we send, so we have to expect that.
expect cmd23 do
end

expect /24.*USER\|AAR9901\|BLY\|CQY\|AFGreetings from Koha.*\|AOLIB\|/ do
  send "\r"
end

expect /Connection closed by foreign host/ do
end
  end
end

-- 
According to all the latest reports, there was no truth
in any of the earlier reports. --Ashleigh Brilliant
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha