Luís Díaz | 1 Jul 10:05 2010
Picon

z39.50 server

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

_______________________________________________
Koha mailing list
Koha@...
http://lists.katipo.co.nz/mailman/listinfo/koha
naste dwoya | 1 Jul 14:53 2010
Picon

catalogue problem

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.
Mike McCormack | 2 Jul 10:16 2010
Picon

Schools Consortia Idea

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

_______________________________________________
Koha mailing list
Koha <at> lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
Rick Welykochy | 1 Jul 18:31 2010
Picon

Re: Schools Consortia Idea

Mike McCormack wrote:

> 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.

This is probably the simplest option for you. It has been accomplished before
and has been discussed on this list.

You only need one instance of MySQL to run multiple databases. Each instance of
Koha reuires its own database, but all databases can run on one MySSQl server.

You only need one Apache as well, with one Virtual Host for each Koha.

Then all you need to do is multiple configuration management, i.e.
install a Koha source tree for each instance you want. I would not advise
trying to save space and share one source code tree, since you are bound
to make minor tweaks for each library.

Each instance of Koha requires its own config in /etc, which specifies
unique things like the database name, super user name and password, etc.etc.

If you run out of machine resources, another Linux server can be
deployed. Hardware is cheap these days :) But I am sure you can run
more than five instances on a reasonably provisioned Linux box, i.e.
2 GB++ RAM and 100 GB  or so of disk, at a wild guess.

Another option is to treat each school as a different branch of the same
library and run all of them under one single instances of Koha. I am a developer,
not a librarian, so cannot advise you well enough on the differences between
several branches of one library and a consortium of unrelated libraries.

cheers
rickw

--

-- 
_________________________________
Rick Welykochy || Praxis Services

You should be open minded, but not so open minded that your brain falls out.
      -- Richard Dawkins
Lars J. Helbo | 1 Jul 21:06 2010

Re: Schools Consortia Idea

Den 01-07-2010 18:31, Rick Welykochy skrev:
If you run out of machine resources, another Linux server can be deployed. Hardware is cheap these days :)

That provokes a question from me. What is the advantage of running several instances on one server?

We are here having a similar scenario (small private schools in Denmark). Our school is the first to use Koha, but I am pretty sure, as soon as the others see it, many will want such a thing as well. I am now considering to offer these schools preinstalled servers based on used hardware. For 100 Euros you can can get something like this:

Server IBM xSeries 345
2x Intel XEON 2GHz
2GB RAM
2x 36GB HDD

which I think would be more than enough for a school library. But even if you could install 5 instances on such a server, you should consider, if it is worth that? You would save a little money of course; but if that is the only advantage - compared to the more complicated installation and maintenance.
--
Lars J. Helbo
Borgergade 44
DK-8450 Hammel

Tlf.: +45 8696 9315
lars.helbo-BEMtUrJjfQNr8omB6DmDsw@public.gmane.org


www.frijsendal.dk

_______________________________________________
Koha mailing list
Koha@...
http://lists.katipo.co.nz/mailman/listinfo/koha
Amy Schuler | 1 Jul 21:17 2010

Koha releases

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 <at> caryinstitute.org

 

 

_______________________________________________
Koha mailing list
Koha@...
http://lists.katipo.co.nz/mailman/listinfo/koha
Lori Bowen Ayre | 1 Jul 21:27 2010

Re: Koha releases

Amy, 

As I understand it, Harley had a bunch of improvements included in it that were done by Liblime/PTFS but it isn't synced up with the community release.  So I recommend you stick with one of the community release versions but I do know that some libraries are pulling off a more current version than 3.0.6 while waiting for 3.2 but unfortunately now we have come to end of my knowledge on this matter.

Actually, one more thing...I think it may be only another 4 weeks or so until 3.2 is ready so the wait probably isn't going to be too bad.  This per the 3.2 release manager.

Lori Ayre

2010/7/1 Amy Schuler <schulera <at> caryinstitute.org>

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-jWmlhwyuPk+CpdWC22Fi7g@public.gmane.orgg

 

 


_______________________________________________
Koha mailing list
Koha-MiqU8s9CcdeGg0aVt5PjEHTaI6DYlTYJ@public.gmane.org
http://lists.katipo.co.nz/mailman/listinfo/koha


_______________________________________________
Koha mailing list
Koha@...
http://lists.katipo.co.nz/mailman/listinfo/koha
Jane Wagner | 1 Jul 21:31 2010

Re: Koha releases

The PTFS Harley release is based off community code as of about last October (plus several subsequent bugfixes), and integrates a lot of development we have done.  Those features have been released to community, but not in time to make the 3.2 release.  The Harley release does not include new development added to head after October, such as the BibLibre acquisitions features.   When the 3.2 release is final (it’s in beta now), it will have those features but not most of the Harley ones.

 

The ultimate goal is to integrate everything, but that will take a while.  Between our list of roughly 70 Harley features (not to mention new development under way) and the 400-odd features that BibLibre has waiting, it’s a long process to integrate and test everything.

 

Your choice for the immediate future really depends on whether you need the Harley features (mostly written for public libraries) or the 3.2 features.

 

Jane Wagner

Library Systems Analyst

PTFS Inc.

Content Management and Library Solutions

6400 Goldsboro Road, Suite 200

Bethesda, MD  20817

(301) 654-8088 x 151

jwagner-o75DBQD9arw@public.gmane.org

 

From: koha-bounces-MiqU8s9CcdeGg0aVt5PjEHTaI6DYlTYJ@public.gmane.org [mailto:koha-bounces <at> lists.katipo.co.nz] On Behalf Of Amy Schuler
Sent: Thursday, July 01, 2010 3:17 PM
To: koha-MiqU8s9CcdeGg0aVt5PjEA@public.gmane.orgnz
Subject: [Koha] Koha releases

 

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-jWmlhwyuPk+CpdWC22Fi7ti2O/JbrIOy@public.gmane.org

 

 

_______________________________________________
Koha mailing list
Koha@...
http://lists.katipo.co.nz/mailman/listinfo/koha
Chris Nighswonger | 1 Jul 21:30 2010

Re: Koha releases

Hi Amy,

2010/7/1 Amy Schuler <schulera <at> caryinstitute.org>:
> 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?

Correct.

  What differentiates these
> versions from Harley?

Harley is a release by PTFS/LL and that code is not (at present)
incorporated in the official Koha code base.

>
> 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 would upgrade to 3.0.6 and then to 3.2 when it is released. The step
from 3.0.6 to 3.2 should not be too big.

Kind Regards,
Chris
_______________________________________________
Koha mailing list
Koha <at> lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
Owen Leonard | 1 Jul 21:34 2010

Re: Koha releases

> Your choice for the immediate future really depends on whether you need the
> Harley features (mostly written for public libraries) or the 3.2 features.

That choice should be made with the understanding that at the moment
there is no upgrade path for Harley. 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.

  -- Owen

--

-- 
Web Developer
Athens County Public Libraries
http://www.myacpl.org

Gmane