- Koha - lists.katipo.co.nz

getting the global preference BiblioAddsAuthorities to work
by Ella Delaney 23 Apr '09

23 Apr '09

Greetings, I set this global preferences option to "on" but the system is not creating authority records on the fly as promised. Am I missing something? Is there another setting I need to change? Thanks! Ella Delaney Head Librarian Flashpoint Academy 28 North Clark Street, 5th Floor Chicago IL 60602 ella.delaney(a)flashpointacademy.com (312)506-0645

1 0

Re: [Koha] koha features
by Doug Dearden 23 Apr '09

23 Apr '09

Sebastien, Your answer might be to define item types for the different formats (pdf, daisy, etc) and then add an item record to the biblio for each item type. The item record includes a subfield u - universal resource locator - that can be used to point to the file. You then have one biblio with the bibliographic information and a copy record for each of the different types of formats you have for that title. Best, Doug >>> Sébastien Hinderer <Sebastien.Hinderer(a)snv.jussieu.fr> 4/23/2009 7:51 AM >>> Hi Galen, thanks for your quick reply. > The 856 (URL) field is a repeatable field in MARC21, so you can have a > single bib record for each title that links to all of the formats. Okay. We plan to use Unimarc rather than marc21, but I believe 856 is also repeatable in this marc dialect. However, I'd say that we need to store not only a link for each format, but also the type of ressource the link points to. But maybe this is easy to do and I can find out about that by myself. You guys already helped a lot. Cheers, Sébastien. _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

request
by Twinamatsiko Smith 23 Apr '09

23 Apr '09

Hey, Firstly thank you for the work u guys are doing.. I installed Koha3.0, does the call number item work? mine jammed What abt the Sms to the librarian by users? The e-mail module does t work properly? Do i need to change somethin help please Smith Uganda

2 1

New user account on wiki, no message received
by Ben Finney 23 Apr '09

23 Apr '09

Howdy all, A few days ago I attempted to create a new user account on the Koha wiki <URL:http://wiki.koha.org/>. The procedure ended with a page telling me an email message had been sent. I've not received auch an email message. I created two accounts: ‘bignose’ first, then (when I realised a WikiName was preferred) ‘BenFinney’. Both of them resulted in a web page telling me an email message has been sent, but neither of them ever arrived. Can someone with admin access on the wiki site please check the logs for error messages? (I'd rather not keep creating new accounts, nor changing the email address.) -- \ “He who allows oppression, shares the crime.” —Erasmus Darwin, | `\ grandfather of Charles Darwin | _o__) | Ben Finney

2 2

For multiple Database for koha to run in zebra server
by mohan pradhan 23 Apr '09

23 Apr '09

Dear all, I want to run the koha for two different databases in two different ip addresses in the same computer. I have two databases already which are "koha" and "book" and also two different xml and httpd-conf files for the same. Here, I can add the marc records into the second database "book" having configuration files as "book-conf.xml" and "book-httpd.conf"; which is also shown in mysql for the newly added biblio, but the problem is when i run the zebra server and try to search the added catalogue from the staff client, it doesnot show. It is showing the records from the first database "koha" only while it has to be shown from second database "book" instead. How can i run zebra server for two different databases "koha" and "book" addressed at two different ip addresses in the same computer. The procedure that i have done are mentioned below in detail. To use multiple databases: Modify the /etc/network/interfaces file to bind multiple ip addresses to the ethernet interface. After much trial and error I wound up with this: -------------------------------------------------------------------------------------------------------- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo eth1 eth1:0 eth1:1 iface lo inet loopback # The primary network interface allow-hotplug eth1 iface eth1 inet static address 192.168.1.133 netmask 255.255.255.0 gateway 192.168.1.10 iface eth1:0 inet static address 192.168.1.139 netmask 255.255.255.0 gateway 192.168.21.10 iface eth1:1 inet static address 192.168.1.140 netmask 255.255.255.0 gateway 192.168.1.10 ------------------------------------------------------------------------------------------------------ This creates three static addresses on the same interface eth1. Using phpmyadmin or the MySQL command line, login as kohaadmin and create the new database. You need to dump the structure of the koha database and then import it into the new databases. To dump the database use mysqldump . At the command line, create a new directory and cd into it. Then enter: mysqldump -u kohaadmin -p koha > kohaout.sql You enter the password for kohaadmin, and this creates an sql file of the koha database. Create the new databases using phpmyadmin or the mysql command line - example below. Start the mysql command line utility with: mysql -u kohaadmin -p After you enter your password, this gives you a mysql prompt. Then enter: show databases; to see the list of databases. To create one enter: create database <new db name>; Then change to that dataabase: use <new DB name>; This command will import all the koha structure into the new database: source kohaout.sql; quit gets you out of the MySql utility and back to the command line. Next you copy the config files. Change to the /etc/koha directory, and copy the koha-conf.xml and koha-httpd-conf files using the new name of your database. So if your database is named "book", you now have book-conf.xml and book-httpd.conf. Edit the book-conf.xml file, and change the name of the database. You should find this near the end of the file under the <config> section. Edit the book-httpd.conf file and make the following changes: Edit the VirtualHost entry and change the name to one of the IP addresses you bound to the network interface - using a different address for each configuration/database. So your entry looks like <VirtualHost 192.168.1.139:50180> for the OPAC and <VirtualHost 192.168.1.139:50188> for the staff client. The IP addresses need to be in the interfaces config file, and the ports (after the :) are from the address range 50000 - 63535. These are unassigned ports in the internet scheme, and since they will be used only on the internal network can be whatever you like. The normal koha ports are the standard http port 80 for the OPAC and 8080 for the staff client. Further down in each VirtualHost section find the SetEnv KOHA_CONF declaration. Change the file to the new one, in our example "/etc/koha/book-conf.xml". You need to change this in two places, one for each VirtualHost section. Change to the /etc/apache2 directory and edit the ports.conf file. Add the new ports you just put into the VirtualHost directives 50180 and 50188 in our example. If you want to use the default koha database, also add 8080 - the default staff client port. You need to add symbolic links for the httpd.conf file and enable the site, so as above you do: ln -s /etc/koha/book-httpd.conf /etc/apache2/sites-available/book a2ensite koha Then restart Apache - /etc/init.d/apache2 reload If you have done all your edits correctly, apache will reload without any errors. Browse to the new IP address - i.e. 192.168.1.139:50180 and you should see the koha opac screen. Browse to the staff client - 192.168.21.139:50188 and you should get that screen. Login as kohaadmin. with regards, Mohan Raj Pradhan HEALTHNET NEPAL KATHMANDU, NEPAL

1 0

Re: [Koha] Till Reconciliation - Create from SQL
by Joann Ransom 23 Apr '09

23 Apr '09

Hi Sandeep, Ahh ... another one of those wondeful things which were dropped out of 3.0. It is definitely in 2.9; can you extract the code from there somehow? So sorry, Jo. SANDEEP BHAVSAR wrote: > Dear Mr. Joann > > In my koha 3.01 version I am not having this till reconciliation > option and that' s why I would like to know the SQL command for it. > > Thanks and Regards > > Sandeep Bhavsar > Librarian > Dr.V.N.Bedekar Institute of Management Studies > Thane(W) 400601 > MUMBAI. INDIA > @@@@@@@@@@@@@@@@@@@@@@@@@@ > email : sandeep.bhavsar(a)gmail.com <mailto:sandeep.bhavsar@gmail.com> > Mob : 9987049099 > elibrary :http://www.vpmthane.org/im/elib/main.htm > @@@@@@@@@@@@@@@@@@@@@@@@@@

1 0

Till Reconciliation - Create from SQL
by SANDEEP BHAVSAR 23 Apr '09

23 Apr '09

Respected All I have gone through the previously posted messages on “ Report Generation- Till Reconciliation for each branch libraries” by Mr. Basu on *Wed, Dec 10, 2008 at 10:31 AM* and also read the views of Joe Atzberger , BWS Johnson, Joshua Ferraro and Henri-Damien I am sure that the each and every public library in India would like to know about how much money they have collected at the end of the day from their all category of patrons. Is it possible to generate the same Till Reconciliation Report with *Total amount paid* through *Home › Reports › Guided Reports Wizard › Create from SQL* . If yes, Please share the SQL Command. -------Advance Technology News for elibrarians http://sandeepbhavsar.blogspot.com/ ------ Thanks and Regards Sandeep Bhavsar Librarian Dr.V.N.Bedekar Institute of Management Studies Thane(W) 400601 MUMBAI. INDIA @@@@@@@@@@@@@@@@@@@@@@@@@@ email : sandeep.bhavsar(a)gmail.com Mob : 9987049099 elibrary :http://www.vpmthane.org/im/elib/main.htm @@@@@@@@@@@@@@@@@@@@@@@@@@

2 4

Re: [Koha] retrieving checkout data
by Rachel Hollis 23 Apr '09

23 Apr '09

Thanks Joe and Owen, I’d hoped that there would be some way to retrieve checkout data but it seems not. In addition to being a dummy and making checkouts (even the current ones) anonymous, we’ve not been very good about backing up our data either. Fortunately we haven’t migrated all our data and processes over yet; it could have been a much greater predicament. Rachel Hollis, librarian Stevens-Henager College, Boise Idaho Campus From: Joe Atzberger [mailto:ohiocore@gmail.com] Sent: Wednesday, April 22, 2009 2:53 AM To: Rachel Hollis Subject: Re: [Koha] retrieving checkout data You can try to extract the data from backups. It will be a great pain though, to merge it with whatever transaction data you have left since the last backup point. --Joe On Tue, Apr 21, 2009 at 1:07 PM, Rachel Hollis <Rachel.Hollis(a)stevenshenager.edu<mailto:Rachel.Hollis@stevenshenager.edu>> wrote: The wrong way is to anonymize check-out history older than <today>. Like a dummy, I did that and now patron data tied to titles does not display. I'm not sure that it is a bug, I can see benefit in making checkout history anonymous after items are returned. I'd anonymize check-out history again but use a date a year or two in the past. The step I took and screen shots are at the following link: http://home.earthlink.net/~rhollis/Koha/anonymize.pdf<http://home.earthlink.net/%7Erhollis/Koha/anonymize.pdf> I'd really like to notify our patrons with overdues and get the library's materials back. Any ideas or help will be most appreciated. Rachel Hollis, librarian Stevens-Henager College, Boise Idaho Campus -----Original Message----- From: Owen Leonard [mailto:oleonard@myacpl.org<mailto:oleonard@myacpl.org>] Sent: Tuesday, April 21, 2009 7:08 AM To: Rachel Hollis Cc: koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz> Subject: Re: [Koha] retrieving checkout data > Everything I know, I learned the hard way. Recently I learned the wrong way to anonymize > check-out history. Is the "wrong way" to use Koha 3's new anonymize checkout history tool? If that's the case, a bug report needs to be filed at the very least. Let us know the details of how it happened so it can be tested. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

1 0

Re: [Koha] koha features
by Doug Dearden 22 Apr '09

22 Apr '09

Hello Sebastien, In reading your post I am reminded of one of the ways we implemented koha. We are using it to catalog archived images that have been scanned. Like your users, our need was for better searching capabilities to find the images that were needed. The connection to the image files was then accomplished using the 856 $u field - URL. A URL in this field is a clickable link in koha, and could be set up to point to your daisy files. Perhaps I am oversimplifying your needs as the public key infrastructure might add some complexity, but from your description I think this is an easy fit into koha. You may not need all the features, but being able to import bibliographic data and have full search capabilities sounds like the big plus. If the connection to the correct file is a URL address then you're done. I got some help from the list to format the URL on the record so that it could be easily redirected later using a simple change in the Apache configuration, in the event the files needed to be moved to a different server. I would suggest you talk to your librarian about MARC. I found that once I had a good handle on how it worked I saw how to easily implement Koha to fulfill our needs. I think you would find the same. You will need to hone your linux skills, but you may not need to do any heavy perl programming. Best, Doug >>> Sébastien Hinderer <Sebastien.Hinderer(a)snv.jussieu.fr> 4/22/2009 8:06 AM >>> HI Zeno, many thanks for your two e-mails and for all the good questions raised in this one. > why do you want a library management system ? > Do you need to setup circulation policies ? No, I think this we don't need. > Do you need to catalague serials ? I don't know what serials are... I'm not a librarian myself, rather computer scientist. > Do you need to manage acquistion ? Perhaps. One thing I have in mind is that the acquisition module ould be used to mnage the file requests submitted to publishers and awaiting to be processed by them. > If from Koha you need only catalogue and Opac with 'simple' metadata, > well Koha is too much for you. You probably do a best choice if you > select a software like Greestone or Dspace. Well, one of the complains from our readers is that the present catalogue is not searchable enough. They say that they have to know preisely what they want to read to find it. We thought that, among other things, using koha could solve this problem. > Koha, IMHO, is ok if you want: > -- to catalogue with full MARC21/UNIMARC set of metatda As far as I understand things,yes, this is something we want.However, I have to say that I do not fully understand why this is important. > -- do you want an Opac with specific indexes on your data. Is not easy > but with Zebra you can index every field/subfield do you want This may perhaps turn out to be interesting. > -- a Z39.50 / SRU server is good extra for you Yes, I think this is interesting for us. We want to provide a standard-based way for other libraries to consult our catalogue and so on. Also, I think we'd like to be able to import bibliographic information easily, and in my iunderstanding this is an other reason why koha is interesting for us, i.e. it is marc-based, which makes us able to import data from the french national library, e.g. Does this make sense ? > -- To use an authority to catalogue is a good extra for you I think this is also the case, but I don't feel qualified enough to be more affirmative on this. > In fact you still have many work to do on Koha to gain your gaols. > Do you need inside (or you need to pay): > -- People with good Library Science knowledge (exp. on Z39.50) > -- People good on Linux and with good dev skills on perl Oh well, I'm the one supposed to do all that. Linux knowledge is okay, knowledge about development in general, too, though I'm less familiar with Perl than with other languages like OCaml. My Library science knowledge is almost inexistant, but we have a librarian working full time inour organization. As mentionned before, any comments will be warmly appreciate, so please donot hesitate to say everything this e-mail inspires to you. Thanks much in advance, Sébastien. _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] koha features
by Sébastien Hinderer 22 Apr '09

22 Apr '09

HI Zeno, many thanks for your two e-mails and for all the good questions raised in this one. > why do you want a library management system ? > Do you need to setup circulation policies ? No, I think this we don't need. > Do you need to catalague serials ? I don't know what serials are... I'm not a librarian myself, rather computer scientist. > Do you need to manage acquistion ? Perhaps. One thing I have in mind is that the acquisition module ould be used to mnage the file requests submitted to publishers and awaiting to be processed by them. > If from Koha you need only catalogue and Opac with 'simple' metadata, > well Koha is too much for you. You probably do a best choice if you > select a software like Greestone or Dspace. Well, one of the complains from our readers is that the present catalogue is not searchable enough. They say that they have to know preisely what they want to read to find it. We thought that, among other things, using koha could solve this problem. > Koha, IMHO, is ok if you want: > -- to catalogue with full MARC21/UNIMARC set of metatda As far as I understand things,yes, this is something we want.However, I have to say that I do not fully understand why this is important. > -- do you want an Opac with specific indexes on your data. Is not easy > but with Zebra you can index every field/subfield do you want This may perhaps turn out to be interesting. > -- a Z39.50 / SRU server is good extra for you Yes, I think this is interesting for us. We want to provide a standard-based way for other libraries to consult our catalogue and so on. Also, I think we'd like to be able to import bibliographic information easily, and in my iunderstanding this is an other reason why koha is interesting for us, i.e. it is marc-based, which makes us able to import data from the french national library, e.g. Does this make sense ? > -- To use an authority to catalogue is a good extra for you I think this is also the case, but I don't feel qualified enough to be more affirmative on this. > In fact you still have many work to do on Koha to gain your gaols. > Do you need inside (or you need to pay): > -- People with good Library Science knowledge (exp. on Z39.50) > -- People good on Linux and with good dev skills on perl Oh well, I'm the one supposed to do all that. Linux knowledge is okay, knowledge about development in general, too, though I'm less familiar with Perl than with other languages like OCaml. My Library science knowledge is almost inexistant, but we have a librarian working full time inour organization. As mentionned before, any comments will be warmly appreciate, so please donot hesitate to say everything this e-mail inspires to you. Thanks much in advance, Sébastien.

1 0