> Deeper hierarchies are not implausible. For example, a Koha database
> used by a consortium of academic libraries could have six levels:
>
> Consortium (Koha DB) : University : Campus : Library : Branch :
> Circulation/Reserve Desk
Thank you for this explanation. I appreciate to learn more abou
Very interesting! Here are my immediate thoughts.
Is a multi-level branches hierarchy via parent-child relationship really
necessary? Do you really plan to have something like that? (with your
example):
Dewey Library
John branch
John-John sub-branch
Caroline sub-branch
Mel
This sounds brilliant.
How about being able to customise certain things (Add/Edit user page) to
show/hide fields depending on which branch/group you are a member of.
For example : Library 1 might only need First name, Surname and Email address
where as Library 2 might require full address detai
Hi,
On Mon, Jun 9, 2008 at 12:03 PM, Frédéric DEMIANS <[EMAIL PROTECTED]> wrote:
> I see 3 obvious levels, no more, in the vast majority of situations:
>
> 1. Koha -- global settings
> 2. Library -- settings for each library
> 3. Branch -- branches belong to one library inherit parameters from
