|Summary:||Restricting patron category for online purchase suggestion|
|Component:||Patrons||Assignee:||Indranil Das Gupta <indradg>|
|Status:||In Discussion ---||QA Contact:|
|Priority:||P5 - low||CC:||amit.gupta, amitddng135, gmcharlt, indradg, katrin.fischer, kyle.m.hall, lisetteslatah, mishravk79, tejoskumar, vinod_librarian|
|Change sponsored?:||Seeking cosponsors||Patch complexity:||---|
|Bot Control:||---||When did the bot last check this:|
|Who signed the patch off:||Text to go in the release notes:|
|Version(s) released in:|
Description vinod 2012-12-14 18:31:27 UTC
At present by default all the category of patrons can either place purchase suggestions or not via opac. The requirement is the purchase suggestions should be restricted by category of users which can be provided by option at the time of creating patron category (i.e. can place purchase request via OPAC or not)
Comment 1 vinod 2015-06-18 15:38:28 UTC
Some educational institutes only allow purchase suggestion by the faculty or some specific category of users like in Indian context. Similarly in public and other libraries children's may not be allowed for purchase suggestions or lower level of non technical/teaching staffs in special libraries. Hence this restriction is very much needed which is applicable for all libraries.
Comment 2 Indranil Das Gupta 2018-02-16 09:31:23 UTC
@Vinod: L2C2 Technologies will sponsor a part of the cost of development, we are looking for co-sponsors for the rest of the development cost share.
Comment 3 Amit Gupta 2018-02-16 09:41:50 UTC
May i know total cost/effort of development? So i can make plan.
Comment 4 Vinod 2018-02-16 15:20:43 UTC
@Indranil, I will be the part of co-sponsor, trying to get some more very soon.
Comment 5 Amit Gupta 2018-02-19 16:12:10 UTC
@Indranil can you please publish some design or i have some idea.
Comment 6 Vinod 2018-02-19 17:09:08 UTC
My idea is: 1. At the time of creating category a option " Can place purchase suggesion" Yes/No 2. While login on OPAC member should not see purchase suggesion option if he can see than while clicking the message it should display "you are not authorised to place purchage suggesion" 3. Any direct link to purchase suggesion should not work for concern category through opac 4. Staff can still place order on his behalf as usual through koha staff client 5. Any other impact we have to see if any
Comment 7 Amit Gupta 2018-02-19 23:35:19 UTC
(In reply to Vinod from comment #6) > My idea is: > > 1. At the time of creating category a option " Can place purchase suggesion" > Yes/No > > 2. While login on OPAC member should not see purchase suggesion option if he > can see than while clicking the message it should display "you are not > authorised to place purchage suggesion" > > 3. Any direct link to purchase suggesion should not work for concern > category through opac > > 4. Staff can still place order on his behalf as usual through koha staff > client > > 5. Any other impact we have to see if any Seems good idea but main concern how current purchase suggestion preference will handle.
Comment 8 Katrin Fischer 2018-03-25 22:03:27 UTC
Maybe instead of using a yes/no setting on patron category, you could use a number of allowed suggestions. There already is already a global setting for this, that might be extendable in this way: MaxOpenSuggestions
Comment 9 Lisette Scheer 2018-04-24 18:09:50 UTC
+1 (In reply to Katrin Fischer from comment #8) > Maybe instead of using a yes/no setting on patron category, you could use a > number of allowed suggestions. There already is already a global setting for > this, that might be extendable in this way: MaxOpenSuggestions Even better would be if it was part of circulation and fines rules so each library in a multi-branch setting could set it differently.
Comment 10 Suresh Kumar 2018-05-27 05:26:02 UTC
please ignore the comment if this is already worked - I thought this way - system Preference - Workflow or any one can suggest Any one can suggest - Already existing feature Workflow - Member logs into his account - clicks on suggestions System should check for supervisor details (like cardnumber or any other details like mail - if supervisor is not a member) Then after filling the details - the system will submit request to his supervisor for approval - once the supervisor approves the request, it should reach the library for procurement