Bug 9290 - Restricting patron category for online purchase suggestion
Summary: Restricting patron category for online purchase suggestion
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Amit Gupta
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-14 18:31 UTC by vinod
Modified: 2020-09-16 13:29 UTC (History)
13 users (show)

See Also:
Change sponsored?: Seeking cosponsors
Patch complexity: ---
Who signed the patch off:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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
Comment 11 Vinod 2019-11-27 13:12:19 UTC
Hello

Is there any update on this development, please?
Comment 12 Vinod 2020-01-07 11:23:42 UTC
Hello,

Seems very slow progress in this bug, may I know any temporary solution so that I can hide the purchase suggestion menu on OPAC from a specific category of users?

Thanking You.
Comment 13 Katrin Fischer 2020-04-29 06:44:22 UTC
Hi Vinod, I thnk the patron category is in the source on the pages now when they log in, you could use that information and jQuery to hide the suggestion pages...  a little tricky. but maybe a work around.

There has been no action from the assignee in a while, I am resetting the bug.
Comment 14 Amit Gupta 2020-04-29 06:59:13 UTC
(In reply to Katrin Fischer from comment #13)
> Hi Vinod, I thnk the patron category is in the source on the pages now when
> they log in, you could use that information and jQuery to hide the
> suggestion pages...  a little tricky. but maybe a work around.
> 
> There has been no action from the assignee in a while, I am resetting the
> bug.

Hi Katrin,

I can take this bug and do the development.

My Plan:

We can create two systempreferences for purchase suggestion.

Systempreference name: 

 1. Onlinepurchase suggestion: Allow/Don't Allow
 2. OnlinepurchasesuggestionvalidCategories: ST|XT|TT
Comment 15 Katrin Fischer 2020-05-05 22:27:59 UTC
Maybe we could reuse the existing suggestion system preference:

Suggestion = if suggestions are available in staff
OpacSuggestion = if suggestions are available in OPAC

Or make it a pref with 3 entries:

Allow suggestions in (OPAC and staff interface|in staff interface|not at all)

Native speakers might do better at phrasing these.

And maybe: OpacSuggestionValidCategories ?
Comment 16 Jonathan Druart 2020-05-06 08:52:10 UTC
There are 3 ways to implement this: Syspref with a list of code, define at category level (admin/categories.pl) or circ rules.

Circ rules seem overkill, even if more flexible (we can discuss if "adding suggestions" is a *circ* rule however...)

Defining at category level is a bit more difficult here, especially for librarians to configure it (you have to go through the different categories).

So yes, we could go with the pref (the uglier), even if far from perfect.
Comment 17 Harsh 2020-06-12 17:15:08 UTC
Hello Everyone,
I'm a 2nd year engineering student and i have done the development work and solved this bug and now i am able to restrict certain categories from making purchase suggestions via OPAC.

Also, wanted to know whether it is a sponsored bug ?
Comment 18 Amit Gupta 2020-06-12 17:31:14 UTC
(In reply to Harsh from comment #17)
> Hello Everyone,
> I'm a 2nd year engineering student and i have done the development work and
> solved this bug and now i am able to restrict certain categories from making
> purchase suggestions via OPAC.
> 
> Also, wanted to know whether it is a sponsored bug ?

Can you publish your design?
Comment 19 Vinod 2020-09-13 08:29:19 UTC
Hi

This bug is sponsored by many library professionals of India and L2C2 technology, but till date it is not finalized. I will be happy if work will be done as soon as possible as this feature is very much needed during Covid-19 situation too.

Thanks
Comment 20 Harsh 2020-09-16 13:22:55 UTC
(In reply to Vinod from comment #19)
> Hi
> 
> This bug is sponsored by many library professionals of India and L2C2
> technology, but till date it is not finalized. I will be happy if work will
> be done as soon as possible as this feature is very much needed during
> Covid-19 situation too.
> 
> Thanks

Hi Sir, I have done the required stuff on my local machine, can you guide me as to how should i submit a patch ?
Comment 21 Harsh 2020-09-16 13:29:12 UTC
(In reply to Amit Gupta from comment #18)
> (In reply to Harsh from comment #17)
> > Hello Everyone,
> > I'm a 2nd year engineering student and i have done the development work and
> > solved this bug and now i am able to restrict certain categories from making
> > purchase suggestions via OPAC.
> > 
> > Also, wanted to know whether it is a sponsored bug ?
> 
> Can you publish your design?

My design idea is :
1.)To create a system preference using which the admin can select whether he has to restrict certain category from making purchase suggestion or no.
2.)Thereafter, another button in the category to restrict/not restrict that category from making purchase suggestions.