Dear Ian,<br><br>Thanks for your mail. Actually ugrading is one challenge here and we intend to plan when we upgrade carefully. Any upgrades will only be reflected in one library <a href="http://fpl.apkn.org">http://fpl.apkn.org</a>. For the changes to be reflected in the other libraries it will have to be done manually which is quite some work. However, we dont intend to upgrade whenever upgrades are released.<br>
<br>I am interested in the work around you hinted to and am going to look into it<br><br>Thanks again<br><br>Anselm <br><br><div class="gmail_quote">On Tue, Aug 17, 2010 at 4:19 PM, Ian Walls <span dir="ltr"><<a href="mailto:ian.walls@bywatersolutions.com">ian.walls@bywatersolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Anselm,<br><br><br>Thank you for sharing your method so clearly and concisely. This is open source at work!<br>
<br>My first reaction this is: how does one maintain this? If you've got as many copies of the template code as you do branches in the system, you'll have a lot of files to update when newer Koha code comes out. This gets even more complex with library-specific edits to those codes. Do you use a version control to keep track of the changes?<div>
<br></div><div>If the bulk of the template files are not being changed, maybe it'd make sense to use symlinks to point them back to the core Koha files. That way, at least for the files you aren't customizing, updating would only need to take place in one directory.</div>
<div><br></div><div>Cheers,</div><div><br></div><div><br></div><div>-Ian<br>
<br><div class="gmail_quote">2010/8/16 Lori Bowen Ayre <span dir="ltr"><<a href="mailto:lori.ayre@galecia.com" target="_blank">lori.ayre@galecia.com</a>></span><div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Anselm,<div><br></div><div>Thanks for this. I think it may come in very handy with a group I'm working with. </div><div><br></div><div>I have a question about holds. Do any of these libraries lend materials to one another (via patron initiated requests)?</div>
<div><br></div><div>If yes, do you have any limits on that? I'd be interested to hear more about that if you do. Or are you just keeping everything in one database as a cost saving measure more than as a way to support resource-sharing?</div>
<div><br></div><div>Lori<br><br><div class="gmail_quote">2010/8/15 Anselm Olweny <span dir="ltr"><<a href="mailto:aolweny@gmail.com" target="_blank">aolweny@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div>
Dear List members,<br><br>Recently I was involved in setting up a federated library system using koha for African parliamentary libraries. See <a href="http://fpl.apkn.org/" target="_blank">http://fpl.apkn.org/</a><br>In this set up all the libraries (18) are using a single database<br>
<br>If you visit the particpating libraries found at <a href="http://fpl.apkn.org/" target="_blank">http://fpl.apkn.org/</a> you will notice that they all have there own look and feel as well as different addresses for both the opac and staff interface. For example the opac for the Parliament of Kenya library is accessed using <a href="http://ke.fpl.apkn.org" target="_blank">http://ke.fpl.apkn.org</a> and its staff interface is at <a href="http://ke.fpl.apkn.org:8080" target="_blank">http://ke.fpl.apkn.org:8080</a>; whereas the opac for the Uganda Parliamentary Library is accessed using <a href="http://ug.fpl.apkn.org" target="_blank">http://ug.fpl.apkn.org</a> and its staff interface is at <a href="http://ug.fpl.apkn.org:8080" target="_blank">http://ug.fpl.apkn.org:8080</a>. Using these addresses these libraries are able to search only their collection.<br>
<br>With this mail I intend to share with you how I achieved this, just in case someone may want to develop the same or even help me improve.<br><br>The illustration below is limited to the creation of a single participating library, however, the steps described were peroformed for all the 18 libraries. The default koha installation serves as the Federated Parliamentary Library interface<br>
<br>After successfully installing koha: <br><ul><li style="font-family: arial,helvetica,sans-serif;"><font size="2">I duplicate the perl scripts located in koha/opac/cgi-bin/opac and koha/intranet/cgi-bin/.</font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I duplicated the templates located in /koha/opac/cgi-bin/opac/htdocs/opac-tmpl/prog/en/modules and koha/intranet/htdocs/intranet-tmpl/prog/en/modules</font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I duplicated the files located in koha/opac/htdocs/opac-tmpl/prog/en/includes and koha/intranet/htdocs/intranet-tmpl/prog/en/includes</font></li><li style="font-family: arial,helvetica,sans-serif;"><font size="2">I duplicated the file opac.css located in koha/opac/htdocs/opac-tmpl/prog/en/css</font></li>
<li style="font-family: arial,helvetica,sans-serif;"><font size="2">I duplicated the file Auth.pm located in koha/lib/C4</font></li><li style="font-family: arial,helvetica,sans-serif;"><font size="2">I identified a two letter code to represent the individual libraries e.g. "ug" for Uganda and "ke" for kenya. These codes were also used in distinguishing the opac and staff interface URLs</font></li>
<li style="font-family: arial,helvetica,sans-serif;"><font size="2">I renamed all the duplicated files, adding the two letter code e.g. "ug" as a suffix to the file names i.e a file like <a href="http://opac-main.pl" target="_blank">opac-main.pl</a> becomes <a href="http://opac-mainug.pl" target="_blank">opac-mainug.pl</a>, masthead.inc becomes mastheadug.inc; opac-main.tmpl, becomes <a href="http://opac-mainug.pl" target="_blank">opac-mainug.pl</a> and opac.css becomes opacug.css</font></li>
<li style="font-family: arial,helvetica,sans-serif;"><font size="2">I edited all the renamed files and modified all links in each of them to reflect the new file names e.g. a reference to a file like /cgi-bin/koha/<a href="http://opac-search.pl" target="_blank">opac-search.pl</a> was modified to /cgi-bin/koha/<a href="http://opac-searchug.pl" target="_blank">opac-searchug.pl</a>; opac-bottom.inc was modifed to opac-bottomug.inc etc in all files in which it occurs</font></li>
<li style="font-family: arial,helvetica,sans-serif;"><font size="2">In the perl scripts I change C4::Auth; to C4::Authug; and C4::Auth qw; to C4::Authug qw; in all ocurances<br></font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I created a new DNS record for the new library e.g <a href="http://ug.fpl.apkn.org" target="_blank">ug.fpl.apkn.org</a> for the Uganda Parliament Library and enabled the "Repeat this virtualhost stanza" found in /koha/etc/</font><font size="2">koha-httpd.confSavitra's advice see <a href="http://old.nabble.com/Re%3A-Koha-as-a-federated-library-p28289266.html" target="_blank">http://old.nabble.com/Re%3A-Koha-as-a-federated-library-p28289266.html</a>) (thanks to </font></li>
<li style="font-family: arial,helvetica,sans-serif;"><font size="2">I created new virtual host entries for the new library opac and staff interfaces in </font><font size="2"> /koha/etc/koha-httpd.conf</font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I restarted the apache server</font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I accessed the individual library opac e.g. the uganda Parliamentary library opac using <a href="http://ug.fpl.apkn.org" target="_blank">http://ug.fpl.apkn.org</a></font></li><li style="font-family: arial,helvetica,sans-serif;">
<font size="2">I created logo and banner images and transfered them to koha/opac/htdocs/opac-tmpl/prog/images and koha/intranet/htdocs/intranet-tmpl/prog/img</font></li><li><span style="font-size: 11pt;"><font style="font-family: arial,helvetica,sans-serif;" size="2">I edited mastheadxx.inc, opacxx.css, loginxx.css and staff-globalxx.css to achieve required look and feel</font><br>
</span></li></ul>I hope this may help anyone who might need to achieve the same kind of library with koha.<br><br>I will be glad to provide any clarification and receive advise from you all.<br><br>Thanks <br><br>Anselm O<br>
<br>
<br></div></div><div>_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br></blockquote></div></div></div><br><br clear="all"><br>-- <br>Ian Walls<br>Lead Development Specialist<br>ByWater Solutions<br>Phone # (888) 900-8944<br><a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a><br>
<a href="mailto:ian.walls@bywatersolutions.com" target="_blank">ian.walls@bywatersolutions.com</a><br>
Twitter: @sekjal<br>
</div>
</blockquote></div><br>