Summary: | Add option for patron to view archived suggestions on the OPAC | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | bdaeuber, f.demians, george, jonathan.druart, severine.queune |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32531 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 22784 | ||
Bug Blocks: |
Description
Nick Clemens (kidclamp)
2021-02-05 12:43:54 UTC
It's a good idea, but it would also be good if patrons could delete their old suggestion history from the OPAC -- similar to deleting their old checkout history. Perha(In reply to George Williams (NEKLS) from comment #1) > It's a good idea, but it would also be good if patrons could delete their > old suggestion history from the OPAC -- similar to deleting their old > checkout history. Perhaps link it to OPACPrivacy syspref? Maybe we could offer to "anonymize" too. As suggestions are linked to the acq process it can be a bit confusing if they disappear suddenly. But it might require that we fix the linking (database side) between the suggestion and the order first :( (In reply to Katrin Fischer from comment #3) > Maybe we could offer to "anonymize" too. Ideally it could work just like anonymizing circs: a user can anonymize, retain or leave as default (anonymize on the library's schedule) and not even need a separate option for suggestions. I suppose I could see a patron deciding they no longer want a request, so perhaps we do need to keep a case by case anonymize option. > As suggestions are linked to the > acq process it can be a bit confusing if they disappear suddenly. Where in the process would this become an issue? As far as I can tell, once a suggestion is placed in a basket the information is retained, even after the suggestion is deleted.
> Where in the process would this become an issue? As far as I can tell, once
> a suggestion is placed in a basket the information is retained, even after
> the suggestion is deleted.
It might cause questions on why something was ordered in the first place. Or: If it was removed after accepting, but before ordering, it will just be gone. Same goes for suggestions that might have been placed in custom status, waiting for review.
(In reply to Nick Clemens from comment #0) > Bug 22784 added the ability to archive suggestions on the staff interface. > It would be nice to allow patrons to view their archived suggestions Since bug 23991, archived suggestions are not filtered (masked) anymore for users on OPAC. It may be seen as a regression for some libraries. Should the previous behavior (pre v22.11) be restored? (In reply to Frédéric Demians from comment #6) > (In reply to Nick Clemens from comment #0) > > Bug 22784 added the ability to archive suggestions on the staff interface. > > It would be nice to allow patrons to view their archived suggestions > > Since bug 23991, archived suggestions are not filtered (masked) anymore for > users on OPAC. It may be seen as a regression for some libraries. Should the > previous behavior (pre v22.11) be restored? I thought this had been fixed on a separate bug, but cannot find it. Frederic, could you please file a new bug if this is still an issue? (In reply to Katrin Fischer from comment #7) > (In reply to Frédéric Demians from comment #6) > > (In reply to Nick Clemens from comment #0) > > > Bug 22784 added the ability to archive suggestions on the staff interface. > > > It would be nice to allow patrons to view their archived suggestions > > > > Since bug 23991, archived suggestions are not filtered (masked) anymore for > > users on OPAC. It may be seen as a regression for some libraries. Should the > > previous behavior (pre v22.11) be restored? > > I thought this had been fixed on a separate bug, but cannot find it. > Frederic, could you please file a new bug if this is still an issue? It's bug 32531. |