Bug 26653 - Allow editing of item notes on moredetail.pl with circulation permission
Summary: Allow editing of item notes on moredetail.pl with circulation permission
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-09 19:57 UTC by Andrew Fuerste-Henry
Modified: 2025-08-22 03:32 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2020-10-09 19:57:44 UTC
If a user has circulation permissions, they can edit the lost/damaged/withdrawn statuses of an item on moredetail.pl (the items tab in the catalog). However, they cannot edit the public and non-public notes for that item. Those notes are only editable on this if one also has edit_items permission, which opens up a lot more actions.

I feel the editing of these notes from moredetail should also fall under circulation permissions.
Comment 1 Jeff Gaines 2020-10-10 15:28:52 UTC
This would be very useful to us, as circ staff may need to add notes to items where a problem cannot be addressed at the time. For example, if a piece of a multi-part set is missing, but the patron still wants to check the item out. With a note on the item, when the item is returned staff will know that it was missing when the current patron checked it out.
Comment 2 David Cook 2025-08-22 03:32:56 UTC
I've never paid much attention to moredetail.pl and updateitem.pl, but now that I am... I am not loving what I'm seeing.

From my perspective, the problem is... how do we manage the permissions for these things? 

Managing Lost/Damaged/Withdrawn status... that probably makes sense for circulation, especially since they're fixed fields.

But notes fields... there are more restricted/security-conscious environments where that's a big problem. (It's even a problem with the status quo because they bypass SubfieldsToAllowForRestrictedEditing which is not great.)

Actually even in a normal environment... you'd probably want to be able to see who added the note. By editing the public/non-public notes... it seems like a workaround to a real problem that isn't being addressed.