Hi Dalton,
It sounds weird to me to add such specific rules (based on sort1 and/or
sort2).
Maybe it would be more useful define circ rules per patron?
As you may have noticed the UI is pretty bad currently, there is a work in
progress (or abandoned?) from ByWater (see bug 15522). It would be good
Hi Dalton,
That sounds not that hard to implement. Not sure how useful it could be,
maybe ask on the other mailing list (koha).
Regards,
Jonathan
On Thu, 23 Mar 2017 at 16:19 Dalton Fury wrote:
> As per my knowledge, we can't restrict a patron in one branch from
> checking out books in another
As per my knowledge, we can't restrict a patron in one branch from checking
out books in another branch. Also, one patron cannot belong to multiple
branches.
If we work on this feature, will it be accepted into koha?
On Wed, Mar 22, 2017 at 9:52 PM, Dalton Fury wrote:
> Hey,
>
> Thanks for the
Hey,
Thanks for the quick reply.
3.1 This won't be an issue, because the student would, after completion of
the internship, be appointed as a student administrator at the library. He
will be given a stipend and will work with us for 2 years. Our library
systems are managed with the help of such a
Hi Dalton,
We've played in that area, and as such I'll offer some answers to your
questions
1. feasible? Yes, easily. Adding columns in the UI and in the backend
should be relatively easy.
2. Most IT undergrad with curiosity, common sense and access to Google
for perl/mysql questions s
Hi,
I am writing this email representing Central Library, National Institute of
Technology, India. We migrated to Koha from a propitiatory software over an
year ago, and are very happy with Koha.
After moving to Koha, various departments have approached us so that they
can use our Koha installat
