My idea comes from creating 1 Koha installed with 1 Database for 100 small branches libraries. Each branch has separated template OPAC. There should be a folder in koha and logic in the application that saying ... ok, load branchA's template OPAC for BranchA's user when they login. A,B or C are diff branch libraries, they can have there own data set and can share if possible (it has done quite well with independent branches preference now). Hope some one can improve this! Sorry for my bad English! Best regards!
I think what you want is not entirely impossible, but I can say that it would likely be a lot of work to maintain. A few years ago we had a RFC for the following work, which was never done but I think would do something similar to what you are describing, and possibly be easier to maintain through upgrades: http://wiki.koha-community.org/wiki/Support_for_multiple_PAC_interfaces_by_U... Liz Rea On 04/01/13 12:01, Quoc Uy wrote:
My idea comes from creating 1 Koha installed with 1 Database for 100 small branches libraries. Each branch has separated template OPAC. There should be a folder in koha and logic in the application that saying ... ok, load branchA's template OPAC for BranchA's user when they login. A,B or C are diff branch libraries, they can have there own data set and can share if possible (it has done quite well with independent branches preference now). Hope some one can improve this! Sorry for my bad English!
Best regards!
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Actually, upon further review I find that this work *was* done, and you can simply create multiple virtualhosts, each with a unique URL, and specify a CSS file to use for each one. Details can be found in the koha-httpd.conf file. Liz Rea On 04/01/13 12:17, Liz Rea wrote:
I think what you want is not entirely impossible, but I can say that it would likely be a lot of work to maintain.
A few years ago we had a RFC for the following work, which was never done but I think would do something similar to what you are describing, and possibly be easier to maintain through upgrades:
http://wiki.koha-community.org/wiki/Support_for_multiple_PAC_interfaces_by_U...
Liz Rea On 04/01/13 12:01, Quoc Uy wrote:
My idea comes from creating 1 Koha installed with 1 Database for 100 small branches libraries. Each branch has separated template OPAC. There should be a folder in koha and logic in the application that saying ... ok, load branchA's template OPAC for BranchA's user when they login. A,B or C are diff branch libraries, they can have there own data set and can share if possible (it has done quite well with independent branches preference now). Hope some one can improve this! Sorry for my bad English!
Best regards!
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
I've had a play with this in the past and it works nicely. You just add the config options to your VirtualHost in Apache SetEnvIf Host "demo1.xxx.xxx.xxx" OPAC_CSS_OVERRIDE=opac-main.css OPAC_SEARCH_ LIMIT=branch:MAIN OPAC_LIMIT_OVERRIDE=1 SetEnvIf Host "demo2.xxx.xxx.xxx" OPAC_CSS_OVERRIDE=opac-branch.css OPAC_SEARCH_ LIMIT=branch:BRANCH OPAC_LIMIT_OVERRIDE=1 You have to address the OPAC by the correct hostname of course. So, in this case, demo1.xxx.xxx.xxx would default to searching the MAIN library and demo2 the BRANCH. Jonathan On 3 January 2013 23:49, Liz Rea <liz@catalyst.net.nz> wrote:
Actually, upon further review I find that this work *was* done, and you can simply create multiple virtualhosts, each with a unique URL, and specify a CSS file to use for each one. Details can be found in the koha-httpd.conf file.
Liz Rea
On 04/01/13 12:17, Liz Rea wrote:
I think what you want is not entirely impossible, but I can say that it would likely be a lot of work to maintain.
A few years ago we had a RFC for the following work, which was never done but I think would do something similar to what you are describing, and possibly be easier to maintain through upgrades:
http://wiki.koha-community.org/wiki/Support_for_multiple_PAC_interfaces_by_U...
Liz Rea On 04/01/13 12:01, Quoc Uy wrote:
My idea comes from creating 1 Koha installed with 1 Database for 100 small branches libraries. Each branch has separated template OPAC. There should be a folder in koha and logic in the application that saying ... ok, load branchA's template OPAC for BranchA's user when they login. A,B or C are diff branch libraries, they can have there own data set and can share if possible (it has done quite well with independent branches preference now). Hope some one can improve this! Sorry for my bad English!
Best regards!
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Jonathan Field Technical Director, PTFS Europe Limited jonathan.field@ptfs-europe.com http://www.ptfs-europe.com
participants (3)
-
Jonathan Field -
Liz Rea -
Quoc Uy