- Koha - lists.katipo.co.nz

Call for news for December newsletter
by Chad Roseburg 23 Dec '13

23 Dec '13

Fellow Koha users ~ We're collecting news for the December newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- * News items can be of any length. We can link to longer entries. * Anything and everything Koha. * Submit by the 26th. If you are working on an interesting project or development related to Koha, please let us know and we'll include it in the gossip/society section. Aware of any new Koha libraries? Let us know! Thank you! -- Chad Roseburg Joanne Dillon Editors, Koha Newsletter

2 2

Importing Koha Database to a new install
by Phillip Ponchot 22 Dec '13

22 Dec '13

Does anyone have some "monkey text" instructructions on how to dump the old koha database from the old server and import it into the new one. From instructions and other readings on the web, I have tried to export the database and import it without acceptable results. When I log into Staff Koha, I still have to login with the username and password that comes with the installation. Also when I do log in, I see as a choice of libraries - My Library and several other libraries so I am assuming there's an issue with the import or maybe something else. I did the following using the instructions below: 1. Using mysqldump, dumped the old koha database which is named Koha. 2. Copied the dump to the new server. 3. Deleted the new koha_library database on the new server. 4. Created a new koha_library database. 5. Using mysql imported the koha_library database from the dump . I also do not have a Library Set so something is not right on the import. Thanks to everyone who's helped me so far. I'm making progress. Phillip Instructions: Koha Database Restoration process. Open a terminal and apply following commands. Remove existing database in new installation sudo su mysql -uroot -p [Enter the MySQL Root password] drop database koha_library; create database koha_library; quit; Copy your database backup from your pen drive to home folder. Then restore the old backup to new installation. Database Restoration command, mysql -uroot -p koha_library < koha.sql koha_library - name of database in new installation koha.sql - name of database in old installation Enter the MySQL root password. Then rebuild the Zebra Index. Apply following command in a terminal, sudo koha-rebuild-zebra -v -f library End of Instructions

3 4

Fwd: What's up with That?
by David Nind 22 Dec '13

22 Dec '13

Copying of Phillip's response to the list. ---------- Forwarded message ---------- From: Phillip Ponchot <pponchot(a)live.com> Date: 21 December 2013 09:04 Subject: RE: [Koha] What's up with That? To: David Nind <david.nind(a)gmail.com> Thanks David for replying. Here is a link to the instructions: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages The message that I'm getting is just that the apache web server is active. This takes place anytime I use the browser with: http://ipaddress: 80. I'll have to wait until I go back into work to find get the original message. Thing in your email that may fix the problem: I did not disable the default web browser site. The server is not listening on port 8080 only on port 80. Other things: Other instructions indicate that I should delete the default web site also. One set of intructions says I should delete the koha website and then start a new one under the name of my instance as shown below. ( http://wiki.lib.sun.ac.za/index.php/Koha/Installation) - Disable the default website. *Remember to disable this after a software upgrade when using the packages method.* sudo a2dissite 000-default - Disable the default koha website. *Remember to disable this after a software upgrade when using the packages method.* sudo a2dissite koha - Enable the custom "library" web site. sudo a2ensite library - Restart the apache2 web server sudo service apache2 restart I'm going back in to try this again tonight. Hang in there, Phillip

2 1

Re: [Koha] What's up with That?
by David Nind 22 Dec '13

22 Dec '13

Hi Phillip. On 22 December 2013 13:59, Phillip Ponchot <pponchot(a)live.com> wrote: > Thanks David, you were right. The actual issue is that there are 3 webs > on a new server. The default, the koha staff and the koha public and all > of these have to be addressed in the dns or a hosts file. I've been able > to attach to the staff and public side on the server now, but from a remote > computer, I'm only able to get to the staff even though I've changed out > the hosts file on the remote computer. > Line 370 of the current manual installation instructions for Koha on Ubuntu mentions that access to the Koha site using the default configuration (for both the public and administration sites) are limited to connections from 127.0.1.1 (or 127.0.0.1). Finding and changing the setting that does this may solve the problem. The current version of manual installation instructions for Ubuntu are here: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.ubuntu;hb… (This is linked from http://wiki.koha-community.org/wiki/Category:Installation) I've never experienced this in Debian though. Note: using the packages is generally the recommended way to install Koha on Debian or Ubuntu, not manually installing. There is generally only one Apache config file needed (on Debian anyway), unless you have deliberately split it up into separate files for the public site and the administration site (normally the administration site is on port 8080 and the configuration for both sites is in the same file). The koha-sites.conf file is crucial in how you setup the public and staff > side and the instructions are rather vague concerning this file and how it > works. I was able to get another tech guy from Butte, Mt to give me some > pointers and I've spent today playing with the Host file and > Koha-Sites.conf. Also some changes in this file pertains to how the > /etc/apache2/ports.conf is setup and of course with vague instructions, its > all trial and error. > > Thank you so much for your comments as they have helped me understand how > this who thing works. > Your welcome! Koha has many components (operating system, database, webserver and Koha itself), and this can present a steep learning curve. Normally packaged installations are very straight forward, so not sure what has not worked in this instance. Once you do get things installed and setup it will be worth it though. I normally have to install things from scratch several times to get the hang of things... (I normally use VirtualBox to install and setup things on my laptop when trying them out). When I get a chance I will try the installation on Ubuntu using packages and suggest any changes to the instructions. > One question that I have however, is this. Is Opac the public side or > something else? > The OPAC (Online Public Access Catalogue) is the public side - what your library customers get to see. What is normally referred to as the 'intranet' is the administration side - library staff use this to manage a library and to configure most aspects of Koha. Thanks again, >

1 0

automated response
by georgew 21 Dec '13

21 Dec '13

I'll be away from my desk until Friday, December 27. If you have an emergency and need to talk to someone immediately, please contact the circulation desk at the Latah County Library District, Moscow branch, at 208-882-3925. George

1 0

Re: [Koha] What's up with That?
by David Nind 21 Dec '13

21 Dec '13

Hi Phillip. I think I will leave it up to the more experienced people who install on Ubuntu to comment on the ins and outs of Apache configuration for Koha on Ubuntu, as this is where I think the issue is. Here is a link to the instructions: > http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages > The message that I'm getting is just that the apache web server is > active. This takes place anytime I use the browser with: http://ipaddress: > 80. I'll have to wait until I go back into work to find get the original > message. > > Thing in your email that may fix the problem: > > I did not disable the default web browser site. > The server is not listening on port 8080 only on port 80. > I would tend to go with the koha-community wiki instructions. Note: I think they need to be updated to clarify the port numbers and Apache configuration. On a default installation the public catalogue runs on port 80 and the administration interface (also called the staff client) runs on port 8080. I will work on updating the wiki when I get a chance, unless someone else beats me to it. > Other instructions indicate that I should delete the default web site > also. > One set of intructions says I should delete the koha website and then > start a new one under the name of my instance as shown below. ( > http://wiki.lib.sun.ac.za/index.php/Koha/Installation) > I think the difference with these instructions is in step 4 where it says 'sudo apt-get install koha koha-common bibutils etckeeper' - normally you only go 'sudo apt-get install koha-common' rather than 'sudo apt-get install koha koha-common'. I think you are only supposed to do one or the other, not both. If you are only running Koha on the server then you do need to disable the default site. If you are running other sites on the same server then the assumption is you will know what you are doing and know how to configure Apache correctly. With a default Koha installation (on Debian anyway) an Apache configuration file is only created when you create an instance. This configuration file needs to be updated with the correct port numbers/server names. Then the ports.conf file needs to be updated with the correct port numbers for Apache to listen on. If you are installing Koha on a networked server and have a server name assigned to the server IP address then the server, Apache and the Koha Apache configuration file needs to be configured appropriately for this. I'm sure someone will correct me if I'm wrong about any of this. > I'm going back in to try this again tonight. > > Hope the port issue solves the problem.... Note: with the mailing list you need to reply all for any responses to be sent to the list, forgot to do this for my initial response! Regards.

1 0

Re: [Koha] What's up with That? (installing on Ubuntu)
by David Nind 21 Dec '13

21 Dec '13

Note: copy to list as I forgot to 'reply all'. Hi Phillip. I installed Ubuntu 12.04 and then following the instructions on the Koha > website, I installed Koha not once but three times while trying to get it > to work. > Could you provide a link to the instructions you used? Did you install using the packages? (The recommended way for most standard installations)? > On the third time I installed Lynx and tried to connect to Koha directly > on the box but all I could get was what looked like an apache web page as > the webbrowser said: "Its working but there's no data when I tried to > connect using the localhost and then the server IP Address. > What is the exact message you are getting? If you have used the packages for installation you need to disable the default Apache configuration, make sure your site configuration is enabled, and enable listening on port 8080. On Debian (not sure for Ubuntu, but I think it is similar and assuming you have sudo installed rather than using root) it is: sudo a2dissite default sudo vi (or nano) /etc/apache2/ports.conf and add Listen 8080 after the Listen 80 entry make sure your site configuration is enabled under /etc/apache2/sites-enabled (sudo a2ensite nameofyoursiteconfig) sudo /etc/init.d/apache2 restart David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098

1 0

problem with bulk imported data
by Babu_koha 21 Dec '13

21 Dec '13

Hi, in bulk import of data, i have used the tags *942$c and 952$y* for Item Type, but they not displayed in staff client and opac search. in edit items screen, selected the *Item Type* as *Books* from the drop down list and saved. then the values automatically displayed in staff client and opac search. please see the screen shots. any help............ <http://koha.1045719.n5.nabble.com/file/n5781747/1staff_client.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/2opac.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/3edit.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/4edit.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/5opac.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/6staff.jpg> -- View this message in context: http://koha.1045719.n5.nabble.com/problem-with-bulk-imported-data-tp5781747… Sent from the Koha-general mailing list archive at Nabble.com.

3 4

Conference stuff
by BWS Johnson 20 Dec '13

20 Dec '13

Salvete! Funny you mention mid Spring >:) The 2014 International Evergreen Conference is 19 - 22 March in Bean Town. They sent us bshum and gmcharlt, so we should crash their party at some point. Or at least not slate over it. Though coughing up $220 or $270 is less than appealing to me, BUT David Weinberger. I _am_ tempted to ninja plan summat for mid Spring of 2015. Spring is substantially more expensive here than Fall, BUT cherry blossoms. 2015 is also more attractive to me as a host, since it's NOT any ilk of major elections year. August is unappealing to me, since it's silly season for me AND hotter than heck for most attendees. This is why I don't want to bid on next year's North American Conference, since a decision has already been taken to have Conference then. July and September work much better for me. So basically, let's play a game. I'm throwing a Conference at some point, and glaws is prolly coming. If I can add two more out of town names* to that list, then I'll definitely do eet. So if you're interested, write me off list or just say "I'll prolly go" on list. The workflow I'm using is this: 1. Gauge interest 2. Toss out dates that work for me, don't conflict with KohaCon, ALA, or Evergreen, and then see if they work for y'all too 3. Secure a venue 4. Wrangle some speakers Cheers, Brooke (*I consider you an out of towner if you're not from Southern Maryland, Da Fancy Pants District of Columbia, or the Great Commonwealth of Northern Fake Virginia. If you're an in towner, you've prolly already met me. But if you haven't, let's have coffee or lunch or whatevahs.) >________________________________ > From: glaws <glawson(a)rhcl.org> >To: BWS Johnson <abesottedphoenix(a)yahoo.com> >Cc: Galen Charlton <gmc(a)esilibrary.com>; Scott Kushner <skushner(a)mplmain.mtpl.org>; kohana(a)lists.bywatersolutions.com >Sent: Wednesday, December 18, 2013 11:45 AM >Subject: Re: [Koha] Koha Users of North America Email List > > > >1. I'll bring the coffee. > >2. Mid spring and through the summer are good event times for me. Things start getting busy in early fall. > >3. Two day conferences are better than just one. Amortizing fixed costs like airfare over two days is a better investment than just one day. > >Greg Lawson >Network Administrator >Rolling Hills Consolidated Library >1912 N. Belt Highway >St. Joseph, MO 64506 >816-232-5479 x2303 >----------------------------------------------------------------- > > > > > >On 12/18/2013 10:16 AM, BWS Johnson wrote: > >Salvete! >>One thing to consider is that it doesn't have to take much to host a one-day or even half-day local Koha event. If you're located in an area where there's at least one other Koha library within reasonable driving distance, all you really need to host an unconference [1] is time, a meeting room, and the desire to promote the event. Everything else, including internet access and even coffee and snacks, is optional. This can scale up. There are certainly larger geographic areas in North America where there's a high enough concentration of Koha users to support a regional event. And if somebody wants to run such an event... go for it: speak up, say what you want to do, and gather some like-minded people to help. [1] http://en.wikipedia.org/wiki/Unconference >> Once again, my arm can be twisted to host at whatever level. Doesn't even require that much twisting, I just don't want to throw a party and have no one show. :) All I ask is that y'all let me pick dates, or let me in on the voting so that I can express whether they are inconvenient to me or no. #justsayin Cheers, Brooke _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha > > >-- > >

5 5

What's up with That?
by Phillip Ponchot 20 Dec '13

20 Dec '13

I installed Ubuntu 12.04 and then following the instructions on the Koha website, I installed Koha not once but three times while trying to get it to work. On the third time I installed Lynx and tried to connect to Koha directly on the box but all I could get was what looked like an apache web page as the webbrowser said: "Its working but there's no data when I tried to connect using the localhost and then the server IP Address. The files that I had to configure look like this: koha-sites.conf: DOMAIN=".livingston.org" INTERPORT="80" INTRAPREFIX="" INTRASUFFIX="=intra" DEFAULTSQL="" OPACPORT="80" OPACPREFIX="" OPACSUFFIX="" ZEBRA_MARC_FORMAT="marc21" ZEBRA_LANGUAGE="en" I can ping the server so the network card interface is working. My Hosts File: 127.0.0.1 LocalHost 192.168.0.3 Web1.Livingston.org Web1 Listen 80 and NameVirtualHost *: 80 is in the ports.conf. My interface file and ifconfig shows that 192.168.0.3 is assigned to this server and the netmask and gateway is correct. personally, I think that although the install was good, Koha is not stating. (I did reboot the server just in case). I followed the instructions to the T! Does anyone have an ideas? I did not disable the primary web site as I didn't know if I was going to need it later, but according to one set of instructions, this is not necessary. Would it be better for me to download the Koha install tar.gz file and install from it? I tried connecting by: lynx http://192.168.0.3:80 and also tried 8080. I'm not quite sure at this point as to where I would start looking to find out why Koha is not working. Thanks, Phillip

1 0