[Koha-devel] RE: Hello

[Nicholas Rosasco]

Koha is designed to support multiple branches (for example, the original
implementation was for a library with 3 different sites).  So your union
catalog problem is covered, I think.

Koha is normally run on a dedicated server (most of us use what is in
practice a high performance PC) connected to the internet and the catalog
information is delivered via the web (in other words, whatever your schools
use for book check out will need a network connection, as will whatever is
used to view the catalog).

Forgive me for the bullet points...
What kind of technology do you currently have?
[Koha is normally configured and run on a Unix/Linux machine, but the
catalog and circulation system can be used with anything with a web
browser.]

What kind of support (staff? contractor?) do you have?
[Koha is intended to be pretty easy to handle, but installation at the
moment is a little complicated at the moment.]

What kind of budget do you have for this project?
[Koha is free, I'm free, but Murphy's law :)]

Are there are sort of standards (cataloging, circulation) you must abide by
[you may need to check with your librarians on that]?

What sort of record exporting does your catalog support? [If we're lucky,
you may be able to feed all the book records directly from one to the
other...]




> -----Original Message-----
> From: Karen Littlefield [mailto:address@hidden
> Sent: Monday, July 01, 2002 9:01 AM
> To: address@hidden
> Subject: Re: Hello
>
>
> ** Reply Requested When Convenient **
>
>
>
> Reply requested when convenient
>
> So Nick where do we begin?  What do you need to know from me?  I
> am just trying to find a way to economically join our separate
> catalogs together to be viewed as one.  Can the Koha Library
> Project help us?
>
>
> Karen Littlefield
> address@hidden
> Mid Del Schools
> Midwest City, OK 73110
> 405-737-4461 x294
>