Alex King a écrit :
This is easy enough.
Each school has a different VirtualHost set up in apache (ie, it is accessed under a different URL) The VirtualHost config specifies a different koha.conf for each school, which in turn specifies a separate mysql database for each school.
You end up with a single install of the Koha files, but each school has it's own independent instance of Koha.
You need to understand virtual hosting, mysql and how to initialise the Koha db for each school.
Cheers,
Alex
Huck wrote:
Lets say you set up a Koha Server...added multiple Libraries...
How would you make it so specific admin's could ONLY access THEIR library.
And users from specific sites could only access the library of their site?
I'm thinking multiple elementary schools sharing 1 server.
--Huck _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
This answer is technically good, but not fair with Koha. You can share a same catalogue but specifying IndependantBranches in system preferences, librarians who donot have superlibrarian role will be able to modify only biblios in their library. Sharing the same catalogue would be much benefit : - Enter only One biblio for all the schools. - See what other sites have and use transfers if necessary. You can test this feature on Koha-2.2.5 up till now. Hope this helps. -- Henri-Damien LAURENT