<div dir="ltr">Hi Dalton,<div><br></div><div>That sounds not that hard to implement. Not sure how useful it could be, maybe ask on the other mailing list (koha).</div><div><br></div><div>Regards,</div><div>Jonathan</div><br><div class="gmail_quote"><div dir="ltr">On Thu, 23 Mar 2017 at 16:19 Dalton Fury <<a href="mailto:daltonfury42@gmail.com">daltonfury42@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">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. <div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">If we work on this feature, will it be accepted into koha?</div></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg">On Wed, Mar 22, 2017 at 9:52 PM, Dalton Fury <span dir="ltr" class="gmail_msg"><<a href="mailto:daltonfury42@gmail.com" class="gmail_msg" target="_blank">daltonfury42@gmail.com</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">Hey, <div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Thanks for the quick reply. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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 team of student admins. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">3.2 We also plan on using branches. Is there a way to make a patron be able to use his account on multiple branches? Also as of now, koha allows patrons from one branch to checkout books from another branch. I don't think there is a system preference to limit this. Will these two features qualify? </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Regards,</div><div class="gmail_msg"><div class="m_-1970187329766557938h5 gmail_msg"><div class="m_-1970187329766557938m_-6752023169168015181HOEnZb gmail_msg"><div class="m_-1970187329766557938m_-6752023169168015181adm gmail_msg"><div id="m_-1970187329766557938m_-6752023169168015181q_15af6e98132ac79e_1" class="m_-1970187329766557938m_-6752023169168015181ajR m_-1970187329766557938m_-6752023169168015181h4 gmail_msg"><div class="m_-1970187329766557938m_-6752023169168015181ajT gmail_msg"></div></div></div><div class="m_-1970187329766557938m_-6752023169168015181h5 gmail_msg"><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg">On Wed, Mar 22, 2017 at 7:03 PM, Philippe Blouin <span dir="ltr" class="gmail_msg"><<a href="mailto:philippe.blouin@inlibro.com" class="gmail_msg" target="_blank">philippe.blouin@inlibro.com</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<p class="gmail_msg">Hi Dalton,</p>
<p class="gmail_msg">We've played in that area, and as such I'll offer some answers to
your questions</p>
<ol class="gmail_msg">
<li class="gmail_msg">feasible? Yes, easily. Adding columns in the UI and in the
backend should be relatively easy.</li>
<li class="gmail_msg">Most IT undergrad with curiosity, common sense and access to
Google for perl/mysql questions should manage.</li>
<li class="gmail_msg">Acceptance is not a given. You start with two strikes against
you:</li>
<ol class="gmail_msg">
<li class="gmail_msg">Your dev will leave after four weeks. Who will maintain the
work, rebase it regularly, promote it, until it gets accepted
?</li>
<li class="gmail_msg">This is very specialized request. Most libraries manage
with using branches to differenciate these situations.
Getting support MIGHT prove a hurdle.</li>
</ol>
</ol>
<p class="gmail_msg">Regards,<br class="gmail_msg">
</p>
<div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-signature gmail_msg">
<div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606sig_inlibro gmail_msg">
<div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606sig_content gmail_msg"> <span class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606nom gmail_msg">Philippe Blouin,</span><br class="gmail_msg">
<span class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606tagline m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606small gmail_msg">Responsable du développement
informatique</span><br class="gmail_msg">
<p class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606desc m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606small gmail_msg"> Tél. : (888) 604-2627<br class="gmail_msg">
<a href="mailto:philippe.blouin@inLibro.com" class="gmail_msg" target="_blank">philippe.blouin@inLibro.com</a>
</p>
</div>
<div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606sig_footer gmail_msg"> <span class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606in gmail_msg">in</span><span class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606libro gmail_msg">Libro</span> <span class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606tagline m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606small gmail_msg">|
pour esprit libre |</span> <a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606small gmail_msg" href="http://www.inLibro.com" target="_blank">www.inLibro.com</a> </div>
</div>
</div><div class="gmail_msg"><div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178h5 gmail_msg">
<div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-cite-prefix gmail_msg">On 03/22/2017 06:47 AM, Dalton Fury
wrote:<br class="gmail_msg">
</div>
</div></div><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178h5 gmail_msg">
<div dir="ltr" class="gmail_msg"><span style="font-size:12.8px" class="gmail_msg">Hi,</span>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">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.</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606gmail-m_5844306911482753241gmail-Apple-interchange-newline gmail_msg">
After moving to Koha, various departments have approached us
so that they can use our Koha installation to mange their
libraries. One obstacle we face is that Circulation Rules can
be defined only based on Patron Categories.<br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">Our patrons are categorized as
UG(Under graduate), PG(Post Graduate), PHD, STAFF, FACULTY
etc. Sort1 and Sort2 fields are used to classify patrons into
departments (Mechanical, Civil , CS, Electrical etc) and
programs (B. Tech, MCA, BCA, MBA etc) respectively.</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">Our patron categories are too
broad. We need to define rules based on sort1 and sort2 fields
as well. </div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">We are planning on taking a CS
student as an intern during the summer vacation and get him to
work on this feature.</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">I am not a developer, and hence I
want to get opinions from the koha developer community before
I proceed with this. Some questions I have in mind are:</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">Will the Koha community accept
this change?</div>
<div style="font-size:12.8px" class="gmail_msg">Is it feasible?</div>
<div style="font-size:12.8px" class="gmail_msg">Can an undergrad student learn and
implement this in 4 weeks of time? What is the difficulty
level?</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">I also have a high level objective
of introducing a student to opensource contributions. If there
is some other useful task that the intern can do for the
community, please mention them too.</div>
<div style="font-size:12.8px" class="gmail_msg"><br class="gmail_msg">
</div>
<div style="font-size:12.8px" class="gmail_msg">Regards, </div>
</div>
<br class="gmail_msg">
<fieldset class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606mimeAttachmentHeader gmail_msg"></fieldset>
<br class="gmail_msg">
</div></div><pre class="gmail_msg">_______________________________________________
Koha-devel mailing list
<a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-txt-link-abbreviated gmail_msg" href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>
<a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-txt-link-freetext gmail_msg" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-txt-link-freetext gmail_msg" href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a>
git : <a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-txt-link-freetext gmail_msg" href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a>
bugs : <a class="m_-1970187329766557938m_-6752023169168015181m_-5976275041479689178m_-862241988887146606moz-txt-link-freetext gmail_msg" href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br class="gmail_msg">
</div>
</blockquote></div><br class="gmail_msg"></div>
</div></div></div></div></div>
</blockquote></div><br class="gmail_msg"></div>
_______________________________________________<br class="gmail_msg">
Koha-devel mailing list<br class="gmail_msg">
<a href="mailto:Koha-devel@lists.koha-community.org" class="gmail_msg" target="_blank">Koha-devel@lists.koha-community.org</a><br class="gmail_msg">
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br class="gmail_msg">
website : <a href="http://www.koha-community.org/" rel="noreferrer" class="gmail_msg" target="_blank">http://www.koha-community.org/</a><br class="gmail_msg">
git : <a href="http://git.koha-community.org/" rel="noreferrer" class="gmail_msg" target="_blank">http://git.koha-community.org/</a><br class="gmail_msg">
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" class="gmail_msg" target="_blank">http://bugs.koha-community.org/</a></blockquote></div></div>