- Koha - lists.katipo.co.nz

Re: [Koha] MarcEdit / Koha Set-up
by David Cook 10 Dec '15

10 Dec '15

Hi Lezlie: I failed to set up the MarcEdit-Koha integration a long time ago, but your email has prompted me to try again... I filled in the ILS details, and I'm able to create/update records in Koha. However, I'm also having difficulties setting up the Z39.50 searching. Here are the steps I took: * I uncommented the "publicserver" sections, leaving the defaults untouched, and restarted the Zebra server. I tested the connection using the Z39.50 tools that come bundled with Koha: On the Koha/Zebra server, I was able to connect to Zebra using "yaz-client tcp:XXX.XXX.X.XX:9998/biblios" and " yaz-client tcp:localhost:9998/biblios" (where XXX.XXX.X.XX is a private IP address on the network). However, when I tried to connect to Zebra using "yaz-client tcp:XXX.XXX.X.XX:9998/biblios" from another server, my desktop, or MarcEdit, the connection timed out every time. I looked at the server firewall and it looked like it should've accepted the connection, so I'm guessing there might be an issue at the router level. The network admin is currently in a meeting, so I decided to play around with the port numbers a bit... and I found success with port 3000, which isn't officially assigned to anything else (see https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers) I chose port 3000 somewhat at random, and then I ran 'netstat -ln | grep "3000"' on the server to make sure that nothing else on the server was using that port. I changed the configuration in koha-conf.xml, restarted Zebra, and I was able to connect from my Desktop "yaz-client" and in MarcEdit. -- My question to you would be: where is the Koha server that you're trying to reach in relation to your computer running MarcEdit? I'm on the same wired LAN as my server, so I'm able to connect using a private network IP address. Are you on the same LAN or trying to connect over the Internet or...? I'm also curious about how you installed Koha... If you're seeing ZEBRA_SRU_HOST and ZEBRA_SRU_BIBLIOS_PORT, it would seem that you're looking at Koha source code rather than an installed Koha. "localhost" and "8081" would be fine in those cases, so long as port 8081 on that server is reachable by outside computers. In my case, I couldn't use port 8080, as something else on the server was already listening on that port. You might find the following links helpful: http://www.indexdata.com/yaz/doc/installation.win32.html http://ftp.indexdata.com/pub/yaz/win32/ While I run Koha on Linux, I use Windows for my desktop work station. I use yaz-client a lot on the server to diagnose issues with Z39.50 searching, but in this case where you want to connect using TCP rather than via a unix socket on the server itself, it could be helpful to download YAZ and use yaz-client.exe to diagnose your connection woes (as well as troubleshooting Zebra in the future). Sorry if this email has too much or not enough information. I take a special interest in Zebra with Koha, so feel free to send more Zebra/Z39.50 queries my way : ). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > Date: Wed, 9 Dec 2015 18:20:16 +0000 > From: "Shell, Lezlie" <Lezlie.Shell(a)contractor.cengage.com> > To: "koha (koha(a)lists.katipo.co.nz)" <koha(a)lists.katipo.co.nz> > Subject: [Koha] MarcEdit / Koha Set-up > Message-ID: > <BLUPR02MB1746FA7A8E1D50AF0D1B84C5BBE80@BLUPR02MB1746. > namprd02.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > I've been struggling to set-up the Koha integration in MarcEdit. I searched > the mailing list archive and found a useful thread on the need to designate a > listen to port. I passed on the information to the person helping me out, but > it still isn't working. > > This is his description of what he did. Are we on the right track? > > > >> I just uncommented that listen tag & set the port to 8080. I also > >> uncommented the server/serverinfo sections (which the koha-conf.xml > >> file said to do if you uncomment the listen tag). BUT, I'm not sure > >> what it wants the "ZEBRA_SRU_HOST and "ZEBRA_SRU_BIBLIOS_PORT" > set > >> to. From an example, I think it's just the localhost & a different > >> port (I used 8081).>> > > > Thanks, > Lezlie

2 1

To link a pdf file in /usr/share/opac/htdocs
by Vimal Kumar V. 10 Dec '15

10 Dec '15

Dear Friends, We would like to link PDF file in 856$u PDF Files copies in /usr/share/opac/htdocs Present practice is that give ip address along with pdf. e.g. http://10.26.1.82/report.pdf How can we give relative path in 856$u, i.e. without ip ? Regards, -- Vimal Kumar V. Technical Assistant Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.info Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in http://moovandan.blogspot.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

1 0

Certain single character searches fail in koha 3.22.00 but work fine in 3.02.02
by Andreas Roussos 10 Dec '15

10 Dec '15

Hello everyone, We are running koha 3.22.00 in a development VM and have a problem when making single character searches (i.e. searches that would normally return a lot of results). Oddly enough, our production koha which is on 3.02.02 does not suffer from the same issue (please see the relevant screenshots http://i.imgur.com/gFPtLBi.png http://i.imgur.com/ehJiURu.png) I followed the instructions in http://wiki.koha-community.org/wiki/Troubleshooting_Zebra and confirmed that the Zebra daemon does indeed return a result set when making a single character search (by issuing the "f α" command for example). So, I think the actual problem must lie with one of the Perl scripts that process the data fed back from Zebra/MySQL. How do we figure out which Perl script is choking on invalid UTF8 data? Is there a way to find which biblios/authorities contain invalid characters and to correct them? Thanks in advance for your help. Kind regards, Andreas

1 0

Re: [Koha] MarcEdit / Koha Set-up (yet another follow-up)
by David Cook 10 Dec '15

10 Dec '15

Hi once again: I just remembered that the official TCP port for ANSI Z39.50 is 210. You might also notice some Z39.50 servers are available on port 7090. If you're running a public Z39.50 server, you will probably want to change the username and password for your Z39.50 server as well. By default, you connect using anonymous read-only access, but it would be trivial for someone to look at the Koha source code to read the defaults and use those to get write-access to your Zebra server... David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > From: David Cook [mailto:dcook@prosentient.com.au] > Sent: Thursday, 10 December 2015 12:03 PM > To: 'koha(a)lists.katipo.co.nz' <koha(a)lists.katipo.co.nz> > Cc: 'Lezlie.Shell(a)contractor.cengage.com' > <Lezlie.Shell(a)contractor.cengage.com> > Subject: RE: MarcEdit / Koha Set-up (follow-up) > > Hi again: > > I also noticed that you'll want to set the syntax for the Z39.50 to "MARC21". I > like working with MARCXML, but MarcEdit apparently can't handle that > option, at least as of MarcEdit 6.0.5532.39684 from 23/02/2015. > > With that option, I'm now able to search Koha's Z39.50 server Zebra using > MarcEdit, and update the records I find : ). > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St, Ultimo, NSW 2007 > > > > -----Original Message----- > > From: David Cook [mailto:dcook@prosentient.com.au] > > Sent: Thursday, 10 December 2015 11:56 AM > > To: 'koha(a)lists.katipo.co.nz' <koha(a)lists.katipo.co.nz> > > Cc: 'Lezlie.Shell(a)contractor.cengage.com' > > <Lezlie.Shell(a)contractor.cengage.com> > > Subject: RE: MarcEdit / Koha Set-up > > > > Hi Lezlie: > > > > I failed to set up the MarcEdit-Koha integration a long time ago, but > > your email has prompted me to try again... > > > > I filled in the ILS details, and I'm able to create/update records in Koha. > > However, I'm also having difficulties setting up the Z39.50 searching. > > > > Here are the steps I took: > > * I uncommented the "publicserver" sections, leaving the defaults > > untouched, and restarted the Zebra server. > > > > I tested the connection using the Z39.50 tools that come bundled with > Koha: > > > > On the Koha/Zebra server, I was able to connect to Zebra using > > "yaz-client tcp:XXX.XXX.X.XX:9998/biblios" and " yaz-client > tcp:localhost:9998/biblios" > > (where XXX.XXX.X.XX is a private IP address on the network). > > > > However, when I tried to connect to Zebra using "yaz-client > > tcp:XXX.XXX.X.XX:9998/biblios" from another server, my desktop, or > > MarcEdit, the connection timed out every time. > > > > I looked at the server firewall and it looked like it should've > > accepted the connection, so I'm guessing there might be an issue at the > router level. > > > > The network admin is currently in a meeting, so I decided to play > > around with the port numbers a bit... and I found success with port > > 3000, which isn't officially assigned to anything else (see > > https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers) > > > > I chose port 3000 somewhat at random, and then I ran 'netstat -ln | > > grep "3000"' on the server to make sure that nothing else on the > > server was using that port. I changed the configuration in > > koha-conf.xml, restarted Zebra, and I was able to connect from my > Desktop "yaz-client" and in MarcEdit. > > > > -- > > > > My question to you would be: where is the Koha server that you're > > trying to reach in relation to your computer running MarcEdit? I'm on > > the same wired LAN as my server, so I'm able to connect using a private > network IP address. > > Are you on the same LAN or trying to connect over the Internet or...? > > > > I'm also curious about how you installed Koha... If you're seeing > > ZEBRA_SRU_HOST and ZEBRA_SRU_BIBLIOS_PORT, it would seem that > you're > > looking at Koha source code rather than an installed Koha. "localhost" > > and "8081" would be fine in those cases, so long as port 8081 on that > > server is reachable by outside computers. In my case, I couldn't use > > port 8080, as something else on the server was already listening on that > port. > > > > You might find the following links helpful: > > http://www.indexdata.com/yaz/doc/installation.win32.html > > http://ftp.indexdata.com/pub/yaz/win32/ > > > > While I run Koha on Linux, I use Windows for my desktop work station. > > I use yaz-client a lot on the server to diagnose issues with Z39.50 > > searching, but in this case where you want to connect using TCP rather > > than via a unix socket on the server itself, it could be helpful to > > download YAZ and use yaz- client.exe to diagnose your connection woes > > (as well as troubleshooting Zebra in the future). > > > > Sorry if this email has too much or not enough information. I take a > > special interest in Zebra with Koha, so feel free to send more > > Zebra/Z39.50 queries my way : ). > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St, Ultimo, NSW 2007 > > > > > -----Original Message----- > > > Date: Wed, 9 Dec 2015 18:20:16 +0000 > > > From: "Shell, Lezlie" <Lezlie.Shell(a)contractor.cengage.com> > > > To: "koha (koha(a)lists.katipo.co.nz)" <koha(a)lists.katipo.co.nz> > > > Subject: [Koha] MarcEdit / Koha Set-up > > > Message-ID: > > > <BLUPR02MB1746FA7A8E1D50AF0D1B84C5BBE80@BLUPR02MB1746. > > > namprd02.prod.outlook.com> > > > > > > Content-Type: text/plain; charset="us-ascii" > > > > > > I've been struggling to set-up the Koha integration in MarcEdit. I > > > searched the mailing list archive and found a useful thread on the > > > need to designate a listen to port. I passed on the information to > > > the person helping me out, but it still isn't working. > > > > > > This is his description of what he did. Are we on the right track? > > > > > > > > > >> I just uncommented that listen tag & set the port to 8080. I > > > >> also uncommented the server/serverinfo sections (which the > > > >> koha-conf.xml file said to do if you uncomment the listen tag). > > > >> BUT, I'm not sure what it wants the "ZEBRA_SRU_HOST and > > "ZEBRA_SRU_BIBLIOS_PORT" > > > set > > > >> to. From an example, I think it's just the localhost & a > > > >> different port (I used 8081).>> > > > > > > > > > Thanks, > > > Lezlie

1 0

Re: [Koha] MarcEdit / Koha Set-up (follow-up)
by David Cook 10 Dec '15

10 Dec '15

Hi again: I also noticed that you'll want to set the syntax for the Z39.50 to "MARC21". I like working with MARCXML, but MarcEdit apparently can't handle that option, at least as of MarcEdit 6.0.5532.39684 from 23/02/2015. With that option, I'm now able to search Koha's Z39.50 server Zebra using MarcEdit, and update the records I find : ). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > From: David Cook [mailto:dcook@prosentient.com.au] > Sent: Thursday, 10 December 2015 11:56 AM > To: 'koha(a)lists.katipo.co.nz' <koha(a)lists.katipo.co.nz> > Cc: 'Lezlie.Shell(a)contractor.cengage.com' > <Lezlie.Shell(a)contractor.cengage.com> > Subject: RE: MarcEdit / Koha Set-up > > Hi Lezlie: > > I failed to set up the MarcEdit-Koha integration a long time ago, but your > email has prompted me to try again... > > I filled in the ILS details, and I'm able to create/update records in Koha. > However, I'm also having difficulties setting up the Z39.50 searching. > > Here are the steps I took: > * I uncommented the "publicserver" sections, leaving the defaults > untouched, and restarted the Zebra server. > > I tested the connection using the Z39.50 tools that come bundled with Koha: > > On the Koha/Zebra server, I was able to connect to Zebra using "yaz-client > tcp:XXX.XXX.X.XX:9998/biblios" and " yaz-client tcp:localhost:9998/biblios" > (where XXX.XXX.X.XX is a private IP address on the network). > > However, when I tried to connect to Zebra using "yaz-client > tcp:XXX.XXX.X.XX:9998/biblios" from another server, my desktop, or > MarcEdit, the connection timed out every time. > > I looked at the server firewall and it looked like it should've accepted the > connection, so I'm guessing there might be an issue at the router level. > > The network admin is currently in a meeting, so I decided to play around with > the port numbers a bit... and I found success with port 3000, which isn't > officially assigned to anything else (see > https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers) > > I chose port 3000 somewhat at random, and then I ran 'netstat -ln | grep > "3000"' on the server to make sure that nothing else on the server was using > that port. I changed the configuration in koha-conf.xml, restarted Zebra, and > I was able to connect from my Desktop "yaz-client" and in MarcEdit. > > -- > > My question to you would be: where is the Koha server that you're trying to > reach in relation to your computer running MarcEdit? I'm on the same wired > LAN as my server, so I'm able to connect using a private network IP address. > Are you on the same LAN or trying to connect over the Internet or...? > > I'm also curious about how you installed Koha... If you're seeing > ZEBRA_SRU_HOST and ZEBRA_SRU_BIBLIOS_PORT, it would seem that > you're looking at Koha source code rather than an installed Koha. "localhost" > and "8081" would be fine in those cases, so long as port 8081 on that server is > reachable by outside computers. In my case, I couldn't use port 8080, as > something else on the server was already listening on that port. > > You might find the following links helpful: > http://www.indexdata.com/yaz/doc/installation.win32.html > http://ftp.indexdata.com/pub/yaz/win32/ > > While I run Koha on Linux, I use Windows for my desktop work station. I use > yaz-client a lot on the server to diagnose issues with Z39.50 searching, but in > this case where you want to connect using TCP rather than via a unix socket > on the server itself, it could be helpful to download YAZ and use yaz- > client.exe to diagnose your connection woes (as well as troubleshooting > Zebra in the future). > > Sorry if this email has too much or not enough information. I take a special > interest in Zebra with Koha, so feel free to send more Zebra/Z39.50 queries > my way : ). > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St, Ultimo, NSW 2007 > > > -----Original Message----- > > Date: Wed, 9 Dec 2015 18:20:16 +0000 > > From: "Shell, Lezlie" <Lezlie.Shell(a)contractor.cengage.com> > > To: "koha (koha(a)lists.katipo.co.nz)" <koha(a)lists.katipo.co.nz> > > Subject: [Koha] MarcEdit / Koha Set-up > > Message-ID: > > <BLUPR02MB1746FA7A8E1D50AF0D1B84C5BBE80@BLUPR02MB1746. > > namprd02.prod.outlook.com> > > > > Content-Type: text/plain; charset="us-ascii" > > > > I've been struggling to set-up the Koha integration in MarcEdit. I > > searched the mailing list archive and found a useful thread on the > > need to designate a listen to port. I passed on the information to > > the person helping me out, but it still isn't working. > > > > This is his description of what he did. Are we on the right track? > > > > > > >> I just uncommented that listen tag & set the port to 8080. I also > > >> uncommented the server/serverinfo sections (which the koha-conf.xml > > >> file said to do if you uncomment the listen tag). BUT, I'm not > > >> sure what it wants the "ZEBRA_SRU_HOST and > "ZEBRA_SRU_BIBLIOS_PORT" > > set > > >> to. From an example, I think it's just the localhost & a different > > >> port (I used 8081).>> > > > > > > Thanks, > > Lezlie

1 0

MarcEdit / Koha Set-up
by Shell, Lezlie 09 Dec '15

09 Dec '15

I've been struggling to set-up the Koha integration in MarcEdit. I searched the mailing list archive and found a useful thread on the need to designate a listen to port. I passed on the information to the person helping me out, but it still isn't working. This is his description of what he did. Are we on the right track? >> I just uncommented that listen tag & set the port to 8080. I also uncommented the server/serverinfo sections (which the koha-conf.xml file said to do if you uncomment the listen tag). BUT, I'm not sure what it wants the "ZEBRA_SRU_HOST and "ZEBRA_SRU_BIBLIOS_PORT" set to. From an example, I think it's just the localhost & a different port (I used 8081).>> Thanks, Lezlie

1 0

Re: [Koha] Design of OPAC
by Paul A 09 Dec '15

09 Dec '15

At 11:17 AM 12/8/2015 -0500, Owen Leonard wrote: [snip] >If you're genuinely asking a question, rather than snarking about >upgrades: The HTML5 specification no longer considers "unapi-server" >an acceptable value for the attribute "rel" on <link> elements. This >has no effect on the functionality of the OPAC. It was a genuine question -- I don't "snark" (for whatever that means) but do remain true to my beliefs in proper coding dating back to pre-transistor days when computers glowed in the dark, and international standards of which the World Wide Web Consortium (W3C) is one authority. The unAPI conundrum (and thank you for clarifying that this is the problem) has been ongoing for many years (see 2007 <https://forums.zotero.org/discussion/1174/unapi-support-does-not-resolve-re…>) Perhaps (in a totally non-confrontational perspective) there is a justification why the error "has no effect on the functionality of the OPAC" but fails to meet ISO standards (<http://www.w3.org/2011/07/wspas-pr.html>)? No big thing: curiosity, accuracy, perhaps even pedantism... Best -- Paul

1 0

Re: [Koha] Design of OPAC
by Paul A 08 Dec '15

08 Dec '15

At 05:44 PM 12/8/2015 +0530, Indranil Das Gupta wrote: >[snip] The NISCAIR opac is actually a rather poor example. It falls short of >W3C standard compliance - see >https://validator.w3.org/nu/?doc=http%3A%2F%2Fopac.niscair.res.in%2F Right now, the validator is returning a 500 error for that OPAC, and a direct attempt is timing out (504 from a CentOS server) so I can't see the results. >(Remark: Ignore the the first 2 info and the first error message in >the above output, every Koha instance will have these. The rest should >be fixed by the implementer) What are these "2 info and the first error message"? Our Koha instance does not have any errors, warnings, info (due perhaps to the evolution of !doctype from XHTML to HTML[5]): <https://validator.w3.org/check?uri=http%3A%2F%2Fopac.navalmarinearchive.com> On the other hand, we have a "wish list" project to try and look into the CSS -- the jigsaw.w3.org validation is intimidating :=} Best -- Paul >hope this helps > >-- >Indranil Das Gupta >L2C2 Technologies > >Phone : +91-98300-20971 >IRC : indradg on irc://irc.freenode.net >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >https://lists.katipo.co.nz/mailman/listinfo/koha --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

Design of OPAC
by Balaji Ravichandran 08 Dec '15

08 Dec '15

Hi All, How can I change the interface of Koha OPAC in such a way that it feels more attractive and user friendly? Is there any specific tools or modules that does this work? I prefer to do like this website - http://opac.niscair.res.in/ or http://catalog.bywatersolutions.com/ Can somebody help? Thanks in advance... -- Regards, Balaji Ravichandran ( பாலாஜி ) , Volunteer at Free Software Foundation - Tamilnadu, Mobile : 9790528505 My Blog - balogic.wordpress.com

2 1

Re: [Koha] Update from 3.20
by Matthew Charlesworth, S.J. 08 Dec '15

08 Dec '15

Good evening everybody, I saw 3.22 packages for Debian are available. Unfortunately I have no > test environment so I would appreciate any kind of feedback on update > from 3.20 version. > I tried upgrading and noticed that the RSS link for recently-acquired books ( http://library.sj.org.za/cgi-bin/koha/opac-search.pl?&limit=mc-itype%252Cph…) does not seem to be formatted. (I'm trying to use Vinod's customization). I'm not sure if this was affected by the upgrade from 3.20 -> 3.22? Has anyone else noticed something with RSS going awry? I am reading http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14524 to see if that might have had an effect? Matthew

1 0