<div dir="ltr">Henry --<br><br>I'm glad to hear your consortium has installed and is trying to set up Koha. <br><br>On Mon, Jul 21, 2008 at 4:34 AM, Henry Lam <span dir="ltr"><<a href="mailto:henry@silas.org.sg">henry@silas.org.sg</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div>Can Koha be used in a consortium environment? </div>
</div></blockquote><div><br>Yes. There are other consortia using and currently deploying Koha.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div>Is there any special procedure in setting up the environment?</div></div></blockquote><div><br>Probably, but most of the difficulty is in setting up the consortium and agreeing on cataloging practices.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div></div>
<div>I have just installed the Koha 3.0. It seems that it is a two-level structure: Group and Library. 'Group' is used to indicate a library . 'Library' is actually a branch in a library. In theory, we can set up different 'Groups' for different libary members. But we are using a shared catalog, therefore, we may need a three-level structure. </div>
</div></blockquote><div><br>Nothing you have said indicates that you need any structure whatsoever. I'm sure it is clear to you the various constraints and differences amongst your member institutions, but I have no idea what they might expect. So the question is "what protections do you need?" <br>
<br>Our French colleagues make use of the IndpendantBranches system preference to help protect consortium members' patron data and records. This may satisfy your needs also. <br><br>--Joe Atzberger<br></div></div></div>