- Koha - lists.katipo.co.nz

Koha linking entries not as analytics
by Linda Culberson 09 Dec '10

09 Dec '10

All, Is anyone using any of the other 76X-78X fields in Koha besides for analytics? We have some that are 776 (additional physical form) and 777 (issued with), as well as a couple that probably should be 787 (other relationship entry). If so, how does it work in Koha and what fields/subfields are you using? Are there any special tips/tricks/suggestions you could share? Thanks in advance. -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

1 0

Request to participate in 2010 Library Technology Guides automation survey
by Breeding, Marshall 09 Dec '10

09 Dec '10

Please respond to the 2010 library automation perceptions survey. This page describes how to participate: http://www.librarytechnology.org/blog.pl?ThreadID=184&BlogID=1 More details: For the last three years I have conducted a survey and written a report on the perceptions that libraries form of the quality of the core automation products they use and their satisfaction with the service they receive. Results from previous editions: http://www.librarytechnology.org/perceptions2009.pl http://www.librarytechnology.org/perceptions2008.pl http://www.librarytechnology.org/perceptions2007.pl I have begun to collect data for the 2010 edition of the survey. This is an opportunity for libraries to register their impressions of the ILS product they use, its support vendor, and the quality of support delivered. Is support getting better or worse? The survey also probes at considerations for migrating to new systems and the level of interest in open source ILS. While the numeric rating scales support the statistical results of the study, it's the comments offered that provide the most insight into the current state of library automation satisfaction. Please help your fellow libraries who might be in the process of evaluating library automation options by responding to the survey. Any information regarding vendor performance and product quality can be helpful when making strategic decisions regarding automation alternatives. A large number of responses strengthen the impact of the survey and the subsequent report. If you have responded to previous editions of the survey, please give your responses again this year. It's very helpful to understand whether things are getting better or worse. As with the previous versions of the survey, only one response per library is allowed. While all the individuals that work in a library may have their own opinions, please respond to the extent that you can from the general experiences of your library. Please contact me if you have any questions regarding the survey. Marshall Breeding Director for Innovative Technology and Research Vanderbilt University Library Editor, Library Technology Guides http://www.librarytechnology.org<http://www.librarytechnology.org/>

1 0

Fw: Libraries not independent as yet
by Steve Kiarie 09 Dec '10

09 Dec '10

Kindly look at that below --- On Thu, 12/9/10, Steve Kiarie <sorosteroge(a)yahoo.com> wrote: From: Steve Kiarie <sorosteroge(a)yahoo.com> Subject: Libraries not independent as yet To: "Owen Leonard" <oleonard(a)myacpl.org> Date: Thursday, December 9, 2010, 6:15 AM Greetings Koha version: 3.02.00.007 IndependantBranches Don't prevent Prevent staff (but not superlibrarians) from modifying objects (holds, items, patrons, etc.) belonging to other libraries. Scenario 1 I have created users and given the head librarians all rights except they are not super librarians and can't Modify login / permissions for staff users however if one of them searches for a book and finds it and clicks on edit record then edits and click on save the changes are made to the original record and saved in the original branch even if it is not in his home branch (The branch that he is registered). Try the above scenario and let me know the way forward. Scenario 2 Then what happens if you want to give a individual head of a branch these rights he or she can add himself as a supper librarian and hence over ride the actual super librarian staffaccess Modify login / permissions for staff users The ideal situation is where one who has the following roles staffaccess Modify login / permissions for staff use can only Change his library alone and he can't make himself a super librarian First look at the scenario 1 for a start Stephen --- On Thu, 12/9/10, Owen Leonard <oleonard(a)myacpl.org> wrote: From: Owen Leonard <oleonard(a)myacpl.org> Subject: Re: [Koha] Libraries not independent as yet To: "Steve Kiarie" <sorosteroge(a)yahoo.com> Cc: koha(a)lists.katipo.co.nz Date: Thursday, December 9, 2010, 5:31 AM > Libraries independent has not been realized as yet a cataloger from one library can > edit and save changes of a Biblios records from a different library What version are you using, and do you have the IndependantBranches preference turned on? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 2

Control number fields (001)
by Zachary Osborne 09 Dec '10

09 Dec '10

Hello, My library is having the same problem as the one below, described by Elaine Bradtke (re: "is there a way to auto-generate 001 fields in Koha?). We are using Koha version 3.00.01.005. Have any of you encountered this before? Any advice would be greatly appreciated. Thanks in advance! -Zack From: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Elaine Bradtke Sent: November-30-10 12:48 PM To: koha Subject: [Koha] Control number fields (001) Is there a way to auto generate 001 fields in Koha? We already have numbers that came in with uploaded records from our old database. Anything we download will likely have a control number from the original cataloguing agency - which I'm thinking of modifying by adding a letter prefix, so it can't possibly duplicate what we've already got in the system. But what about original cataloguing? I'd hate to think we just have to guess. . . Just off the top of my head, using YYYYMMDD followed by a two digit sequential number should do the trick. But it would be a lot easier if something like that could be auto generated. It's unlikely we would ever have more than one person cataloguing at once, but one never knows. -- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 ext 36 ------------------------------------------------------------------------ -- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 ------------------------------------------------------------------------ --- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52) _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Libraries not independent as yet
by Owen Leonard 09 Dec '10

09 Dec '10

Please CC the mailing list so that everyone can read and respond to your messages. On Thu, Dec 9, 2010 at 9:15 AM, Steve Kiarie <sorosteroge(a)yahoo.com> wrote: > > Greetings > > Koha version: 3.02.00.007 > > IndependantBranches staff (but not superlibrarians) from modifying objects (holds, items, patrons, etc.) belonging to other libraries. > > Scenario 1 > > I have created uses and given the head librarians all rights except they are not super librarians and can't Modify login / permissions for staff users however if one of them searches for a book and finds it and clicks on edit record then edits and click on save the changes are made to the original record and saved in the original branch even if it is not in his home branch (The branch that he is registered). > > Try the above scenario and let me know the way forward. > > > Scenario 2 > Then what happens if you want to give a individual head of a branch these rights he or she can add himself as a supper librarian and hence over ride the actual super librarian staffaccess Modify login / permissions for staff users > > > The ideal situation is where one who has the following roles staffaccess Modify login / permissions for staff use can only Change his library alone and he can't make himself a super librarian > > > First look at the scenario 1 for a start > > Stephen > > > --- On Thu, 12/9/10, Owen Leonard <oleonard(a)myacpl.org> wrote: > > From: Owen Leonard <oleonard(a)myacpl.org> > Subject: Re: [Koha] Libraries not independent as yet > To: "Steve Kiarie" <sorosteroge(a)yahoo.com> > Cc: koha(a)lists.katipo.co.nz > Date: Thursday, December 9, 2010, 5:31 AM > > > Libraries independent has not been realized as yet a cataloger from one library can > > edit and save changes of a Biblios records from a different library > > What version are you using, and do you have the IndependantBranches > preference turned on? > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org >

1 0

Libraries not independent as yet
by Steve Kiarie 09 Dec '10

09 Dec '10

Greetings everyone Libraries independent has not been realized as yet a cataloger from one library can edit and save changes of a Biblios records from a different library Kindly if any one has a way to prevent this let me know for we want full independence Stephsn

2 1

unable to run apache after upgrade from 3.0 to 3.2
by Yatheesh Y 09 Dec '10

09 Dec '10

I am getting this error when updated my koha 3.0 to 3.2 what does it mean schm@sschm-desktop:~$ sudo /etc/init.d/apache2 restart * Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName ... waiting apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName -- ---------------------------- Y.Yatheesh babu Librarian Shri Shakti College of Hotel Management Venus Plaza Begumpet Hyderabad-500 016 09966178388

2 3

Package updates for 3.2.0
by Robin Sheat 09 Dec '10

09 Dec '10

With the release of 3.2.0, I've upgraded the packages in the repository, and at the same time adjusted their layout a bit. The nutshell version is that there are now two Koha distributions included in the repository: 'squeeze' and 'squeeze-dev'. Squeeze will be updated only when koha has a version bump, most likely this'll be 3.2.1. Squueze-dev will be updated every week or so when the master branch is updated. So the 'squeeze' stable releases can be considered production ready. 'squeeze-dev' is for those who like to watch things break and get fixed again. The gritty details can be found here: http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze And almost exactly 10 minutes after Chris mentioned it in his talk :) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

4 6

installing koha via mizstik live CD
by Caitlin McGurk 08 Dec '10

08 Dec '10

Hello All, I'm trying to install Koha via the Mizstik Live CD. Has anyone else done this before? I'm running into some issues because I can't seem to connect to "http://localhost:8080", or via my server IP. Any advice? I'm clueless Thanks! Caitlin McGurk Head Librarian The Center for Cartoon Studies <http://www.cartoonstudies.org> mcgurk(a)cartoonstudies.org

1 0

MARC tag for noting Koha auto-modification?
by MJ Ray 08 Dec '10

08 Dec '10

A little introduction before the question: I'm working on making Koha recover a little from an incomplete marcxml record. This should reduce the number of times that Koha fails (with a code 500 Internal Server Error) or returns a misleading 404 Not Found to a search or link, usually because a MARC record was imported with incorrect settings. Currently we have to intervene directly in the database to repair such problems and that's no fun. This is a symptom of http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2916 that I mentioned in another thread yesterday. My solution is to make Koha try to recover by regenerating marcxml from the binary MARC record. This would be harmful for mature records, but you can't get very far with an incomplete MARCXML record anyway, so this doesn't usually happen to mature records. It usually happens when someone has managed to be imported or entered with inconsistent character encodings or other corruption. Regeneration should be just enough to allow opening the record editor or using the Koha C4 API to fix whatever's broken. Further discussion: http://stats.workbuffer.org/irclog/koha/2010-11-25#i_550339 http://stats.workbuffer.org/irclog/koha/2010-12-08#i_559023 I've been advised to dump the broken MARCXML record to system logs and note in the regenerated record when it was done. So, the question is this: Where should the regeneration note go? jcamins suggested tag 993 because it's used for such things by the ANS. Would that be OK with everyone? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. 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