Summary: | Allow editing of item notes on moredetail.pl with circulation permission | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | dcook, jgaine, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Andrew Fuerste-Henry
2020-10-09 19:57:44 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. 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. |