- Koha - lists.katipo.co.nz

Autocomplete values in catalogue data entry
by Olugbenga Adara 05 Dec '11

05 Dec '11

Hello, Is it possible to turn on autocomplete in certain fields in the framework used in cataloging? For example tag 260 place of publication and publisher can really benefit from picking from a value entered before. Regards Olugbenga Adara Mobile: 234 (0) 8033220288 Home: 234 (2) 8721720 Skype: gbengaadara Blog: http://gbengaadara.blogspot.com Twitter: http://twitter.com/gbengaadara Profile: http://www.linkedin.com/in/gbengaadara

2 3

Zebra indexing problem of unimarc file
by Giulio Bonanome 04 Dec '11

04 Dec '11

Hi all, I'm trying to install Koha 3.0.3 to my debian lenny machine for testing purpose. The installation goes fine, but i've a lot of problem with the indexing of files. I have a .mrc file in UNIMARC that I try to import with bulkmarcimport.pl, BUT ......here my output: koha@kindebian:~/codice/misc/migration_tools$ perl -I/home/koha/codice bulkmarcimport.pl -d -c UNIMARC --file cafo-test.mrc deleting biblios 1100....Use of uninitialized value in length at /home/koha/codice/C4/Biblio.pm line 3248, <GEN11> line 1104. 1200................................................................................................. 1297 MARC records done in 17.486762046814 seconds koha@kindebian:~/codice/misc/migration_tools$ perl -I/home/koha/codice rebuild_zebra.pl -r -b -w 19:26:44-08/10 zebraidx(14400) [warn] Index 'tpubdate' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Modified-code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'char-encoding' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'char-encoding' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'char-encoding' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'script-Title' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Country-heading' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Illustration-code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Conference-code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Festschrift-indicator' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Index-indicator' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Literature-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Biography-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Type-Of-Serial' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Frequency-code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Regularity-code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Content-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Conference-publication-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Title-Page-availability-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Index-availability-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Cumulative-Index-availability-Code' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Video-mt' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Graphics-type' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Graphics-support' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Graphics-support' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Serials' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Serials' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Printed-music' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Printed-music' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Electronic-ressource' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'Title-host' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'title-host' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'lcn' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'lcn' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'popularity' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'popularity' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Index 'item' not found in attset(s) 19:26:44-08/10 zebraidx(14400) [warn] Record didn't contain match fields in (bib1,Local-number) I cannot understand if the problem came from zebra settings or from my .mrc file. I've tried the nozebra indexing and worked fine. When I've tried to connect with yaz-client seems to have some problems, but as now I cannot understand how to solve. Sorry for my bad english and thanks a lot for any help. Giulio Bonanome

3 3

Koha 3.2.11 is now available [Security Release]
by Chris Nighswonger 04 Dec '11

04 Dec '11

It is with pleasure that I announce the release of Koha 3.2.11. The package can be retrieved from: http://download.koha-community.org/koha-3.02.11.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.11.tar.gz.MD5 http://download.koha-community.org/koha-3.02.11.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.11.tar.gz.sig Release notes for 3.2.11 are below. Come and get it! RELEASE NOTES FOR KOHA 3.2.10 - 3 December 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.2.10 can be downloaded from: http://download.koha-community.org/koha-3.02.10.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation IMPORTANT ANNOUNCEMENT CONCERNING 3.2.x EOL ======================================================================== 3.2.x has reached its EOL and is officialy unsupported at this point. Releases beyond 3.2.10 are for security issues only and are not gauranteed. Highlights of 3.2.10 ====================== NOTE: This release is a security release. It is strongly recommended that users apply this upgrade immediately to production systems. If you are installing a new system, please use this version rather than earlier versions. System Requirements ====================== Changes since 3.0: * The minimum version of Perl required is now 5.8.8. * There are a number of new Perl module dependencies. Run ./koha_perl_deps.pl -u -m to get a list of any new modules to install during upgrade. Upgrades ====================== The structure of the acquisitions tables have changed significantly from 3.0.x. In particular, the budget hierarchy is quite different. During an upgrade, a new database table is created called fundmapping that contains a record of how budgets were mapped. It is strongly recommended that users of Koha 3.0.x acquisitions carefully review the results of the upgrade before resuming ordering in Koha 3.2.x. Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, several translations of the Koha manual are available: English: http://koha-community.org/documentation/3-2-manual/ Spanish: http://koha-community.org/documentation/3-2-manual-es/ French: http://koha-community.org/documentation/3-2-manual-fr/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Chinese * Danish * English (New Zealand) * English (USA) * French (France) * French (Canada) * German * Greek * Hindi * Italian * Norwegian * Portuguese * Spanish * Turkish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.2 is Release Manager: Galen Charlton <gmcharlt(a)gmail.com> Documentation Manager: Nicole Engard <nengard(a)gmail.com> Translation Manager: Chris Cormack <chris(a)bigallofwax.co.nz> Release Maintainer (3.0.x): Henri-Damien Laurent <henridamien.laurent(a)biblibre.com> Release Maintainer (3.2.x): Chris Nighswonger <cnighswonger(a)foundations.edu> Credits ====================== We thank the following individuals who contributed patches to Koha 3.2.10: FrÃ©dÃ©rick Capovilla Chris Cormack Chris Nighswonger We regret any omissions. If a contributor has been inadvertantly missed, please send patch against these release notes to koha-patches(a)lists.koha-community.org. The 3.2.x Release Maintainer especially thanks the 3.6 Release Team and all who participated in QA for their diligent labors in testing and pushing well over 680 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.10 on its announced schedule. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.2.x (i.e., this version of Koha and future bugfix releases) is 3.2.x. The next major feature release of Koha will be Koha 3.4.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Naku te rourou, nau te rourou, ka ora ai te iwi.

1 0

Koha Training in Samoa
by jowitt_al 03 Dec '11

03 Dec '11

Talofa Koha Community Hopefully in 2012 the USP Library in Alafua, Samoa will start using the Koha Library software. At the moment we are working on the migration and testing process. I need to put in a proposal for funding to train local library and IT staff in Koha operation and support. 1. Does anyone have a week long training programme they would be willing to share showing topics/modules covered and time taken to cover each? This would need to cover library staff end user training and IT technical training. 2. If you offer technical and library staff training in the Koha system I would be happy to hear what you can offer and most importantly how much it costs! Samoa is a beautiful but developing country. We have many coconut palm trees here and lovely beaches however money trees are not common! In order to get funding, costs will have to be very reasonable. We expect to pay flights and per diem for the days someone will be in Samoa however during the training I would like to cover technical support and any problem solving we require, some development to ensure functionality we need and library staff training in the essential modules they will be using. I hope this is not a tall order?! I look forward to hearing from you asap as my proposal for funding is due in on 6th December 2011. Thanks for any help you can give. Angela (()())) (| |) (((o) (o))) =========oOO===(_)===OOo========= Angela Jowitt Senior Librarian USP - University of the South Pacific Alafua Campus Library Private Bag Apia Samoa PH: +685 21671 ext 299 WEB: http://www.usp.ac.fj/index.php?id=5699 ------------------Oooo---------- oooO ( ) ( ) ) / \ ( (_/ \_)

1 0

Show suspension days left
by anjoze 03 Dec '11

03 Dec '11

Hi again, When I try to checkout an Item to a *suspended Patron* I receive the message saying: /Patron has had overdue items and is blocked for XX day(s)./ If I try to checkout again on the next day, it will show* the same number of days.* Until the end of the suspended period it shows the same number of days! So, if a few days later that Patron ask me how many days left, I can't tell him :( Is there a way to show the suspension remaining days? Or Is it possible to build a report with that info? Thank you very much, JA -- View this message in context: http://koha.1045719.n5.nabble.com/Show-suspension-days-left-tp5043511p50435… Sent from the Koha-general mailing list archive at Nabble.com.

2 1

Re: [Koha] logrotate.conf
by MJ Ray 02 Dec '11

02 Dec '11

Jeff Friesen <jfriesen(a)lewistown.k12.mt.us> > We have been getting an error from KOHA v. 3.6 that says "error: cannot > stat /home/koha/kohaclone/etc/logrotate.conf: No such file or directory." > Can anyone clue me in generally or exactly to what this error is referring? > I'm not sure what the logrotate.conf file does. Thanks. Where are you getting that error? URL? Emails with a subject? The logrotate.conf file controls keeping the disk space used by logs under control. "The logrotate utility is designed to simplify the administration of log files on a system which generates a lot of log files. Logrotate allows for the automatic rotation compression, removal and mailing of log files. Logrotate can be set to handle a log file daily, weekly, monthly or when the log file gets to a certain size. Normally, logrotate runs as a daily cron job." - http://packages.debian.org/logrotate Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha

1 0

7310 Improving permissions on lists (virtual shelves)
by Marcel de Rooy 02 Dec '11

02 Dec '11

Somehow I wonder if this message came through on the Koha list today. Resending it: Hi, If you have a suggestion on report 7310 about lists management, please respond. Following up on report 7281 (hide lists from OPAC) I am sending the following question to the ml in order to improve lists management: 1 Who should be allowed to delete a public [closed] list (category 2 only!) or add/remove items from that list? (Note that removing all items from a list is more or less the same as removing the list at once.) My answer would be: the owner should only be allowed to do that in the OPAC. A user in the staff client may do it too. [Currently, any opac login can delete the list. This is a bug!] 2 Who should be allowed to delete an public open list (category 3 only!) or add/remove items from that list? My answer would be: any login from OPAC or staff. It should be made clear that creating such a list is really at your own risk ;) Currently, a user in the opac cannot create an open list. (Is that a bug?) 3 Proposed revisions to lists management: If we solve points 1 and 2, management of lists comes down to all or nothing. You can do everything with an open list, but if you are not owning a closed list, you can't do anything. Would it be useful to have something in between? Like deleting your own added items from a closed list (we could save borrowernumber in virtualshelfcontents)?? Or give the owner of an open list the choice between full access for other logins, adding items only or deleting own added items? What do you think? Marcel

1 0

logrotate.conf
by Jeff Friesen 02 Dec '11

02 Dec '11

We have been getting an error from KOHA v. 3.6 that says "error: cannot stat /home/koha/kohaclone/etc/logrotate.conf: No such file or directory." Can anyone clue me in generally or exactly to what this error is referring? I'm not sure what the logrotate.conf file does. Thanks. -- Jeff Friesen Library Media Specialist Fergus High School Lewistown, MT (406) 535-2321 ext. 112

1 0

Re: [Koha] Koha Virtual Appliance 3.6 Now Available For Download
by Muhammad Abdullah 02 Dec '11

02 Dec '11

Thanks alot for this. Been using it for awhile now, very useful appliance. This upgrade should make it more robust, now that it is running on Debian 6. On Thu, Dec 1, 2011 at 10:48 PM, Kyle Hall <kyle.m.hall(a)gmail.com> wrote: > Hey All, > I just wanted to let everyone know that I've updated my virtual > appliances to 3.6. This is a complete rebuild using Debian 6.0 ( > Squeeze ) instead of Lenny. I also added a bit more to the Koha > Console program for automatically fixing the networking issue that > crops up on virtual machines from time to time. Enjoy! > > http://millruntech.com/koha/koha-virtual-appliances > > Kyle > > http://www.kylehall.info > Mill Run Technology Solutions ( http://millruntech.com ) > Crawford County Federated Library System ( http://www.ccfls.org ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

[Bug 7310] Improving permissions on lists (virtual shelves)
by Marcel de Rooy 02 Dec '11

02 Dec '11

Hi, If you have a suggestion on report 7310 about lists management, please respond. Following up on report 7281 (hide lists from OPAC) I am sending the following question to the ml in order to improve lists management: 1 Who should be allowed to delete a public [closed] list (category 2 only!) or add/remove items from that list? (Note that removing all items from a list is more or less the same as removing the list at once.) My answer would be: the owner should only be allowed to do that in the OPAC. A user in the staff client may do it too. [Currently, any opac login can delete the list. This is a bug!] 2 Who should be allowed to delete an public open list (category 3 only!) or add/remove items from that list? My answer would be: any login from OPAC or staff. It should be made clear that creating such a list is really at your own risk ;) Currently, a user in the opac cannot create an open list. (Is that a bug?) 3 Proposed revisions to lists management: If we solve points 1 and 2, management of lists comes down to all or nothing. You can do everything with an open list, but if you are not owning a closed list, you can't do anything. Would it be useful to have something in between? Like deleting your own added items from a closed list (we could save borrowernumber in virtualshelfcontents)?? Or give the owner of an open list the choice between full access for other logins, adding items only or deleting own added items? What do you think? Marcel

1 0