> Having heard no objection, I congratulate Frédéric, the new
> Translation Manager for 3.4.
I'd like to thank the audience. I'm very proud and honored!
--
Frédéric DEMIANS
http://www.tamil.fr/u/fdemians.html
___
Koha-devel mailing
ing dealt with db updates coordinated with code
updates, you're obviously in position to design an functional updates
system for Koha. If you could elaborate various scenario describing
step-by-step issues you encountered, it may help to design a new system
that decrease complexity rath
> 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
ibility_and_multi-licensing
--
Frédéric DEMIANS
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
