- Koha - lists.katipo.co.nz

Hello we are MASmedios
by Alicia Sellés Carot 05 Jul '10

05 Jul '10

Hello / Hola: Let us to introduce ourselves formally on this list. We are MASmedios.com, a spanish software, creative, flexible and multitalented company, with more than ten years experience in the IT and Digital communications sector, specially on the Library & Information Management Solutions sector, betting on Open source software (repositories tools, CMS, etc., based on LAMP platform) since 1997. On the Library & Information Management Solutions sector, we have been focused on Koha for four years now, offering to our clients: - Installation, parametrization and customization (interfaces design and information architecture) - Support and Maintenance - Developing innovative features - Interoperability and integration - Evangelization on Open Source and Koha: we organize and participate in librarian open source events and meetings such as Fesabid, the Spanish National Meeting on libraries, where we have the participation of Henri Damien Laurent, biblibre.com (thank you Henry so much again, by the way) Also, you can visit our online social demo at: http://demokoha.masmedios.info where we invite clients and interested users to dig into it. That´s why We would like to participate actively on the Koha Community with spanish documentation issues, translation, proffesional support, developing new features, solving bugs and everything you need ;-) We are at your disposal. Thank you very much indeed. Yours Sincerely, Alicia Sellés Carot http://www.masmedios.com <http://www.masmedios.com/> http://demokoha.masmedios.info <http://www.masmedios.com/> ============= Hola: Permitidnos presentarnos formalmente en esta lista. Somos MASmedios.com, una compañía española de software, creativa, flexible e interdisciplinar, con más de 10 años de experiencia en el sector de las Nuevas Tecnologías Digitales, especialmente servicios y soluciones para bibliotecas y Documentación. Hemos apostado desde siempre por herramientas Open source (herramientas para repositorios, gestores de contenidos, gestores de bibliotecas, etc., basados en la plataforma LAMP. En el sector específico de los Servicios Documentales, nos hemos focalizado en Koha durante ya 4 años, ofreciendo a nuestros clientes: - Instalación, parametrización y customización mediante diseño de interfaces y arquitectura de información - Soporte y Mantenimiento - Desarrollo de funcionalidades innovadoras - Interoperabilidad e integración - Evangelización sobre Open Source y Koha: organizamos y participamos en eventos y encuentros profesionales bibliotecarios sobre open source, como por ejemplo Fesabid, las Jornadas Españolas de Documentación, donde ya contamos con la inestimable participación de Henri Damien Laurent, de biblibre.com (gracias de nuevo Henri, por cierto) Además, podéis visitar nuestro demo social en línea en: http://demokoha.masmedios.info donde invitamos a nuestros clientes y usuarios interesados en explorar la herramienta. Así, nos gustaría participar activamente en la comunidad de Koha en labores de documentación en español, traducción, soporte profesional, desarrollo de nuevas funcionalidades, resolución de errores y cualquiera cosa que necesitéis ;-) Estamos a vuestra disposición. Muchas gracias de antemano. Sinceramente, Alicia Sellés Carot http:// <http://www.masmedios.com/> www.masmedios.com http:// <http://www.masmedios.com/> demokoha.masmedios.info Alicia Sellés Carot Servicios y Soluciones Documentales C/ Garcilaso, 15-B 46003 Valencia Telf: 96 369 41 23 Telf: 636 26 71 78 Fax: 96 369 34 39 <http://www.masmedios.com> www.masmedios.com Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, puede contener información de carácter confidencial exclusivamente dirigida a su(s) destinatario(s). De acuerdo con la LOPD, MASmedios informa de que los datos personales contenidos quedarán sometidos a un tratamiento del que aquélla es responsable. Los interesados consienten el tratamiento de sus datos para estos fines, pudiendo ejercitar sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito a MASmedios para la gestión de la información, calle Garcilaso 15-B 46003 Valencia o en protecciondatos(a)masmedios.com

1 0

z3950
by Luís Díaz 05 Jul '10

05 Jul '10

Hello all we would like to convert a koha server to: z39.50 server and srw ¿Is it possible? Does some one has done it yet? Is there any doc about this? Thanks a lot in advance Cheers

3 3

Running Zebra Server Automatically
by bariki.kamara＠out.ac.tz 05 Jul '10

05 Jul '10

Hi, Hope you all are pretty fine. I would like to ask if there is a way of running Zebra server automatically during the main server start-up. I cant find the records which added into the system until I run manually zebra server, I use the following command to run the zebra server sudo -u kohaadmin zebrasrv -f /etc/koha/koha-conf.xml. I use Ubuntu server 9.10 as my platform. Regards, Bariki G. Kamara ---------------------- CONFIDENTIALITY NOTICE -------------------------------- PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E-MAIL This email is intended only for the person to whom it is addressed and may contain confidential information and may be legally privileged. If you are not the intended recipient, you are notified that you may not use, distribute or copy this document in any manner whatsoever. Kindly also notify the sender by email and/or delete this e-mail. Any views or opinions expressed in this e-mail are those of the sender and do not necessarily coincide with those of the Open University of Tanzania. --------------------THE OPEN UNIVERSITY OF TANZANIA--------------------------

4 7

Re: [Koha] Koha releases
by Stacy Pober 03 Jul '10

03 Jul '10

Owen Leonard <oleonard(a)myacpl.org> wrote: >I certainly hope PTFS will not > release an update to Harley. I would hope their efforts are being put > into integrating it into the real Koha instead. A few days ago, at the Liblime Users Group meeting held at the ALA conference, customers were told that LibLime plans to merge Harley and LEK (Liblime Enterprise Koha) at some point in the future. I don't recall hearing any specific timeline for that. Liblime also displayed a policy document regarding code release of their software. I think they said it was on their website, but I can't find it right now. I just emailed them for a link or copy of it, but for now I'll give you a summary based on my memory of what was shown.. AIR, the policy says that sponsored software featureswill go through a testing cycle with the sponsoring organization, then will be released to other Liblime customers for six months. After that, the code will be released to the larger Koha world. As I understand it, most of the enhancements sponsored by one of the customer groups (the group sponsoring most of LEK features, I think) are currently contractually defined as a single project rather than individual enhancements. So until the full "bundle" of enhancements goes through the full process of testing and deployment to the other LEK customers, no part of it will be released. After the "Phase I" project is finished, which is scheduled for the end of 2010, then those enhancements will be released to other LEK users, so if there is a release of that code, it is unlikely to be prior to the middle or end of 2011. That date assumes that the project finishes on time. I believe the original date for the end of Phase one was summer, 2009, so this schedule may be overly optimistic. Since the "phase I" includes a large number of features, I asked in the meeting how long they thought it would take for those to be integrated into the official community version of Koha. The estimate I was given was four to five years. I must admit I don't really fully understand the process in which sponsored enhancements are integrated into the official Koha software. Is an evaluation done for sponsored features before they are integrated into the software? I would think the programmers involved in each release would want to evaluate them to see whether they in fact are improvements over the either the current software or whether another feature supplied by a different support vendor may accomplish the same functionality in a better way. If such evaluation is done, who does it? We have had at least one instance when we were told that a feature of official Koha would have to be sacrificed in order for a LEK feature to work correctly. I don't know whether that is going to be a common issue, but I assume that within the official Koha project, there is some decision-making protocol for deciding whether a new feature is worth more than the existing feature that it disables or worth integrating at all if there is an existing feature developed elsewhere that adds the same functionality. -- Stacy Pober Information Alchemist Manhattan College Library Riverdale, NY 10471 stacy.pober(a)manhattan.edu

10 16

Re: [Koha] Koha releases - Clarification/correction
by Stacy Pober 03 Jul '10

03 Jul '10

I wrote: > Since the "phase I" includes a large number of features, I asked in > the meeting how long they thought it would take for those to be > integrated into the official community version of Koha. The estimate > I was given was four to five years. Several people have misinterpreted the passage above, and I apologize for any confusion my remarks have caused. First, just to clarify, the estimate of "four or five years" was clearly NOT given as the time it would take for PTFS/Liblime to release to code. As I understand it, in the new policy the enhancements are first tested by the sponsoring customers, and then the new features are used by the other Liblime customers using that 'flavor' of Koha (i.e. either Harley or LEK) for six months. After six months of use by Liblime customers, the code for these features is then released to the larger Koha community, assuming that the sponsor agrees to the release of the code at all. Since the code is developed as a work for hire, the customer can decline to release the code at all. In the meeting, I asked how long they estimated it would take for the official Koha community to integrate the code once it had been released. First one Liblime staffer said two or three years and then another one said, 'more like four or five years'. This was where the figure of "4 or 5 years" came up - they clearly did not mean that they were going to withhold the code for that long. So the 4 or 5 year figure was never given as the delay before the code was released. It was given as the amount of time it would take for the Koha community to integrate the large amount of code from LEK's "phase I" development into the official version of Koha. But wait - there's more. Today, someone from Liblime contacted me to explain that the estimate of 4 or 5 years as the time for the community to integrate such a large amount of code was a "humorous ad lib comment" rather than a serious answer to my question I am not a programmer, and thus lacked the context to understand that this was a joke. I don't know if the initial "2 or 3 years" answer to my question was also a humorous remark. In any case, they really never did say or imply that they were going to hold onto the code for four or five years, and I'm sorry if this was not clear in my original post. -- Stacy Pober Information Alchemist Riverdale, NY 10471 stacy.pober(a)manhattan.edu

2 1

Printer for Circulation Slip
by Vikas Kumar 02 Jul '10

02 Jul '10

Hi, Hope you all will be doing fine! This is Vikas from Libsoul (www.libsoul.com) We are helping one of our clients to set up Koha for their library. To print circulation slip they have decided to use thermal printer like Zebra. The concern is that in case book's title is long then how does printer adjust it? Does it skip some part of title or take it to the next line? Thanks in advance. Cheers, Vikas Kumar

2 1

Schools Consortia Idea
by Mike McCormack 02 Jul '10

02 Jul '10

Hi, (I'm going to cross post this to the consortia list too) We have an interest in Koha from many schools libraries in Ireland, but the schools are very badly funded, so we need to come up with a solution that will we relatively inexpensive to implement and support. We favour a hosted system for a number of schools and we need to come up with some additional functionality in Koha to support a schools consortia. We expect to develop these extra features at oslo.ie but would welcome any input, ideas that the community may have. We would also welcome getting together with any potential partners out there who may have a similar requirement for such a consortia. I have included below the 2 options that we have in mind to provide this solution. We favour Option 2, the Filtered solution, since many schools could share the costs of one big hosted system, but are open to suggestions for either solution. Please see below our high level functional spec which lists the features that we believe will be necessary for Koha to operate as a school consortia. Schools Consortia. 1. Many Instances of Koha on one Box Install one instance of MySQL containing one database for each school with a corresponding instance of Koha/Apache per school. There would be a limit to the number of instances that could be installed on a Linux box and any more than 5 would probably get difficult to manage and would use a lot of system resources. 2. One Big Koha System with Filtered Access Modify the Koha application to enable us to install one instance of MySQL, with a single database shared by a number of schools. Install one instance of Koha/Apache with the Koha application modified to filter the data so that each school would only see their own patrons and item records. A system of sharing common bib records would be very useful as the collections across all schools are very similar, especially for electronic resources. The schools generally have between 500 and 1500 students in each school with around 5,000 to 6,000 items in each school, so nothing too huge there. Transaction-wise, you would be talking tens of circulations per library per day, not thousands, so it would be fairly light use. Below are the kinds of things the Filtered system (Option 2) should be able to do: Requirements Bibliographic Database A single bibliographic database onto which libraries can hook their own items. o System administrators / librarians could see every bib, but only their own holdings. o Each library would have control over its own codes – collection, loan categories, borrower categories etc. Perhaps there could be an additional field on the codes records indicating which branch (ie school) “owns” this code. o OPAC users can see only their own school’s local bib/holdings. Requests on own stock only – no inter-lending etc. Book Rental Many schools have a book rental scheme where the school provides all students with their text books for a number of years. Essentially it is a form of circulation where there is a very long loan. There are a few things we could do to enhance it: Koha has a book rental charge on the Item Type – not sure of the full details of how it works. o Have the items in a separate collection / location that is invisible to the OPAC, so that only managers can see the data o Have a switch in the circulation area so that these items are suppressed, unless explicitly included in the display (maybe 3 states: Show all loans, Show no bookrental items, Show bookrental items only) o Have a standard report on the system where the school can print-off a listing of the student’s items and have them in the form of a contract setting out the terms and conditions of the scheme. OPAC We’d need to be able to brand each school with its own look and feel to some extent. Cover images, links to reviews, biographies etc etc would also be required. There are a lot of nice things we could do with the OPAC – I am thinking of an itunes-like coverflow presentation – but that would be a separate topic once the basic technology is in place. Any feedback is welcome thanks, Mike

4 3

Koha releases
by Amy Schuler 01 Jul '10

01 Jul '10

Hello, I am a little unclear on the Koha stable version releases. The current stable release is v.3.0.6, but 3.2 is on its way? What differentiates these versions from Harley? I am running Koha 3.0001005 but have not yet gone live with it. I wonder if we should just upgrade now to the newest version, or wait for 3.2? I would hate to roll out the new system to my library users, then 6 months down the road feel pressured to upgrade. I welcome any suggestions. Thanks! Amy C. Schuler Manager of Information Services Cary Institute of Ecosystem Studies PO Box AB Millbrook, NY 12545 (845) 677-7600 x164 schulera(a)caryinstitute.org<mailto:schulera@ecostudies.org>

6 5

catalogue problem
by naste dwoya 01 Jul '10

01 Jul '10

Hi, please help me out on this, i have been running koha 228, which has a few 229 upgrades. I experienced a problem with the display of the MARC records, when i search the catalogue i am able to see the content, but when i click on any of the items it simply gives me a blank page with the marc number that the record is. On trying to back up using mysqlyog, it gives me an error Error.: No 1016 Cant open file : "marc_subfield_table.MYD.' (errno:145) Any assistance on how to correct this will be appreciated.

2 1

Re: [Koha] managing staged marc records for upload through "tools"
by Chris Cormack 01 Jul '10

01 Jul '10

CCing the list so others can comment On 30 June 2010 08:26, Jeremy Shellhase <Jeremy.Shellhase(a)humboldt.edu> wrote: > Chris, > > I mean the a - Permanent Location, c- Shelving Location, b- Current > Location, and other item values. > > The staging and importing screens offer options to create new items, but I > can't find where I tell it which location and which shelving location to > use. They only create items if you have item data attached in the 952 field. So if you want to upload a bunch of records with items attached you need to add 952 fields to your records, 952a and 952b and 952c are the subfields for location, 952p is for barcode. > > I can add items individually, but that's sort of painful. > If your MARC records don't have item information, that is really the only way to do it. I would recommend using a tool like MarcEdit to add item information to your marc records before importing them Chris

3 2