2 different circulation rules against a patron
Hello, First of all, Happy New Year! How do I apply 2 different circulation rules to a patron? Here is my setup I have 2 patron categories. Each of them has its own circulation rule. Since a patron can only have one patron category assigned, how do I that if I want to configure a patron to have more than 1 category? In other words. based on patron category, a patron can have different circulation rule. I don't want to create another patron card for 2 patron categories. Please advise. Thank you. Best regards, Chee
Hi Chee Hong, Kindly refer earlier post - circulation rules on this forum at http://koha.1045719.n5.nabble.com/koha-circulation-policies-and-patron-restr... Hope it helps. -- *Satish MV* Librarian - Govt. Engineering College Opp. Dairy Circle, B.M.Road, Hassan 573 201 Karnataka, INDIA Mobile: +91 9449765737 Personal Email: lis4satish@gmail.com <arun.adrakatti@gmail.com> Official Email :smv@gechassan.ac.in <Id%3Asmv@gechassan.ac.in> College Website: www. <http://www.git.edu/>gechassan.ac.in Library OPAC: http://library.gechassan.ac.in Library Portal : https://librarygechassan.wixsite.com/library
Hi Satish, Thanks for your reply. I have read the post. It does not help me in my scenario. In this case, I wanted to have a patron that potentially can have 2 patron categories so that he/she can choose a patron category when he/she checks out a book. As you know, you cannot assign more than 1 category to a patron in Koha. Is there a way to achieve the same thing? Best Regards, Chee On Fri, Jan 4, 2019 at 12:18 AM SATISH <lis4satish@gmail.com> wrote:
Hi Chee Hong,
Kindly refer earlier post - circulation rules on this forum at
http://koha.1045719.n5.nabble.com/koha-circulation-policies-and-patron-restr...
Hope it helps.
-- *Satish MV* Librarian - Govt. Engineering College Opp. Dairy Circle, B.M.Road, Hassan 573 201 Karnataka, INDIA Mobile: +91 9449765737 Personal Email: lis4satish@gmail.com <arun.adrakatti@gmail.com> Official Email :smv@gechassan.ac.in <Id%3Asmv@gechassan.ac.in> College Website: www. <http://www.git.edu/>gechassan.ac.in Library OPAC: http://library.gechassan.ac.in Library Portal : https://librarygechassan.wixsite.com/library
There is a patch to a bug that has my use case. https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44762&action=edit My question now is this available in Koha 18.05? Thanks, Chee -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
Hi Chee
There is a patch to a bug that has my use case.
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44762&action=edit
My question now is this available in Koha 18.05?
No, this patch was never pushed to master. The discussion about it ended in 2015. Thus, it is not in Koha 18.05 or any other Koha version. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
Hi Michael, Thanks for your reply. Is there any problem if I want to apply the patch to Koha 18.05? If not, please provide the steps to do so. I appreciate that. Thank you. Best Regards, Chee On Sun, Jan 6, 2019 at 10:20 AM Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi Chee
There is a patch to a bug that has my use case.
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44762&action=edit
My question now is this available in Koha 18.05?
No, this patch was never pushed to master. The discussion about it ended in 2015. Thus, it is not in Koha 18.05 or any other Koha version.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Chee, I am going to answer 'No, it can't be applied to 18.05', for a few reasons: - the patch was submitted over three years ago: that is six versions of Koha ago; - even if it applies to the code base, it could cause any number of problems - it has not been tested by project maintainers or subjected to quality assurance (QA) testing; - the concept is a bad idea, if you read the discussion in the bug report: the concept has been rejected by the project's QA Manager no less; - patches that are not part of Koha have to be re-applied at every upgrade: if you do this once, you will keep doing it, and create a maintenance headache for yourself. The only way in Koha for a user to have two categories is to create two records for them. That can cause its own problems. Why not just put them in the category with the most generous circulation rules? Otherwise, Koha does not support the functionality you are seeking. I hope this explains, Bob Birchall Calyx On 7/1/19 9:00 am, Chee Hong wrote:
Hi Michael,
Thanks for your reply. Is there any problem if I want to apply the patch to Koha 18.05? If not, please provide the steps to do so. I appreciate that. Thank you.
Best Regards, Chee
On Sun, Jan 6, 2019 at 10:20 AM Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi Chee
There is a patch to a bug that has my use case.
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44762&action=edit
My question now is this available in Koha 18.05?
No, this patch was never pushed to master. The discussion about it ended in 2015. Thus, it is not in Koha 18.05 or any other Koha version.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Bob, Thanks for your reply and explanation. I agree with you that it will be a maintenance nightmare for the upgrade. Personally, I think this is a nice to have feature. In order to realize my use case, I need to create 2 patron accounts for users who need to have this special privilege. Best Regards, Chee On Sun, Jan 6, 2019 at 9:05 PM Bob Birchall <bob@calyx.net.au> wrote:
Hi Chee, I am going to answer 'No, it can't be applied to 18.05', for a few reasons: - the patch was submitted over three years ago: that is six versions of Koha ago; - even if it applies to the code base, it could cause any number of problems - it has not been tested by project maintainers or subjected to quality assurance (QA) testing; - the concept is a bad idea, if you read the discussion in the bug report: the concept has been rejected by the project's QA Manager no less; - patches that are not part of Koha have to be re-applied at every upgrade: if you do this once, you will keep doing it, and create a maintenance headache for yourself. The only way in Koha for a user to have two categories is to create two records for them. That can cause its own problems. Why not just put them in the category with the most generous circulation rules? Otherwise, Koha does not support the functionality you are seeking. I hope this explains, Bob Birchall Calyx
On 7/1/19 9:00 am, Chee Hong wrote:
Hi Michael,
Thanks for your reply. Is there any problem if I want to apply the patch to Koha 18.05? If not, please provide the steps to do so. I appreciate that. Thank you.
Best Regards, Chee
On Sun, Jan 6, 2019 at 10:20 AM Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi Chee
There is a patch to a bug that has my use case.
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44762&action=edit
My question now is this available in Koha 18.05?
No, this patch was never pushed to master. The discussion about it ended in 2015. Thus, it is not in Koha 18.05 or any other Koha version.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
On Mon, Jan 07, 2019 at 06:34:54PM -0500, Chee Hong wrote:
Thanks for your reply and explanation. I agree with you that it will be a maintenance nightmare for the upgrade. Personally, I think this is a nice to have feature. In order to realize my use case, I need to create 2 patron accounts for users who need to have this special privilege.
Unless I'm misunderstanding or have forgotten what you wrote in your original post, what you're looking for is a way to enable an interaction such as this... ------------------------------------------------------------------------ Maria (a graduate student who also works as an adjunct faculty member) brings a book to the circulation desk and asks to check it out. Bob (a circ staff member) scans Maria's barcode, or searches using her name. Koha indicates that there are two options to choose from when performing the checkout: (1) Check it out to Maria as a graduate student. (2) Check it out to Maria as an adjunct faculty member. Bob selects the desired option. (Alternatively, Koha sees that #2 would result in a longer loan period and selects that option automatically.) ------------------------------------------------------------------------ Furthermore, you would prefer to do this without the added burden of having two separate patron records (i.e., two different rows in the "borrowers" table) in Koha. Am I understanding correctly? If so, it might be useful to think of this at a higher level of abstraction. Here are my ideas... We keep the two separate records -- each must continue to have a unique cardnumber, which may make this idea unusable -- but link them in some way. Maria is a person with two roles at your institution. We create a new "object" -- a Person -- and reference Maria (the Person) from each patron record. In concrete terms, this might mean: ------------------------------------------------------------------------ CREATE TABLE persons ( personnumber INTEGER PRIMARY KEY, preferred_borrowernumber INTEGER REFERENCES borrowers(borrowernumber); ); ALTER TABLE borrowers ADD COLUMN personnumber INTEGER REFERENCES persons(personnumber); ------------------------------------------------------------------------ Then (*handwave*) we add an interface for linking borrowers, another for selecting the desired borrower from a list of linked borrowers, etc. It's just a thought... Paul. -- Paul Hoffman <paul@flo.org> Software Manager Fenway Library Organization 550 Huntington Ave. Boston, MA 02115 617-989-5032
Hi Paul, Thanks for your suggestion and a detailed use case Yes, that is what I to implement. In your example, Maria will tell Bob which option she wants to use when she checks out a book. In this case, this is a custom solution and I need to worry about it during the upgrade process. I don't want to go for custom solution if possible. Best Regards, Chee On Tue, Jan 8, 2019 at 11:24 AM Paul Hoffman <paul@flo.org> wrote:
Thanks for your reply and explanation. I agree with you that it will be a maintenance nightmare for the upgrade. Personally, I think this is a nice to have feature. In order to realize my use case, I need to create 2
On Mon, Jan 07, 2019 at 06:34:54PM -0500, Chee Hong wrote: patron
accounts for users who need to have this special privilege.
Unless I'm misunderstanding or have forgotten what you wrote in your original post, what you're looking for is a way to enable an interaction such as this...
------------------------------------------------------------------------ Maria (a graduate student who also works as an adjunct faculty member) brings a book to the circulation desk and asks to check it out.
Bob (a circ staff member) scans Maria's barcode, or searches using her name.
Koha indicates that there are two options to choose from when performing the checkout:
(1) Check it out to Maria as a graduate student. (2) Check it out to Maria as an adjunct faculty member.
Bob selects the desired option.
(Alternatively, Koha sees that #2 would result in a longer loan period and selects that option automatically.) ------------------------------------------------------------------------
Furthermore, you would prefer to do this without the added burden of having two separate patron records (i.e., two different rows in the "borrowers" table) in Koha.
Am I understanding correctly?
If so, it might be useful to think of this at a higher level of abstraction. Here are my ideas...
We keep the two separate records -- each must continue to have a unique cardnumber, which may make this idea unusable -- but link them in some way.
Maria is a person with two roles at your institution. We create a new "object" -- a Person -- and reference Maria (the Person) from each patron record.
In concrete terms, this might mean:
------------------------------------------------------------------------ CREATE TABLE persons ( personnumber INTEGER PRIMARY KEY, preferred_borrowernumber INTEGER REFERENCES borrowers(borrowernumber); ); ALTER TABLE borrowers ADD COLUMN personnumber INTEGER REFERENCES persons(personnumber); ------------------------------------------------------------------------
Then (*handwave*) we add an interface for linking borrowers, another for selecting the desired borrower from a list of linked borrowers, etc.
It's just a thought...
Paul.
-- Paul Hoffman <paul@flo.org> Software Manager Fenway Library Organization 550 Huntington Ave. Boston, MA 02115 617-989-5032 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hello What is your intension can you please Elaborate with example here? On Sat, 5 Jan 2019 07:29 Chee Hong, <cfhong2000@gmail.com> wrote:
Hi Satish,
Thanks for your reply. I have read the post. It does not help me in my scenario. In this case, I wanted to have a patron that potentially can have 2 patron categories so that he/she can choose a patron category when he/she checks out a book. As you know, you cannot assign more than 1 category to a patron in Koha. Is there a way to achieve the same thing?
Best Regards, Chee
On Fri, Jan 4, 2019 at 12:18 AM SATISH <lis4satish@gmail.com> wrote:
Hi Chee Hong,
Kindly refer earlier post - circulation rules on this forum at
http://koha.1045719.n5.nabble.com/koha-circulation-policies-and-patron-restr...
Hope it helps.
-- *Satish MV* Librarian - Govt. Engineering College Opp. Dairy Circle, B.M.Road, Hassan 573 201 Karnataka, INDIA Mobile: +91 9449765737 Personal Email: lis4satish@gmail.com <arun.adrakatti@gmail.com> Official Email :smv@gechassan.ac.in <Id%3Asmv@gechassan.ac.in> College Website: www. <http://www.git.edu/>gechassan.ac.in Library OPAC: http://library.gechassan.ac.in Library Portal : https://librarygechassan.wixsite.com/library
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
My use case is captured in this bug. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
participants (7)
-
Bob Birchall -
cfhong -
Chee Hong
-
Michael Kuhn -
Paul Hoffman -
SATISH -
vinod mishra