Summary: | Locked records can still be modified/deleted by an unauthorized librarian with merge and in advanced editor | ||
---|---|---|---|
Product: | Koha | Reporter: | Janusz Kaczmarek <januszop> |
Component: | Cataloging | Assignee: | Arthur Suzuki <arthur.suzuki> |
Status: | ASSIGNED --- | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | arthur.suzuki, david, dcook, m.de.rooy |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36372 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35380 |
||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | 36372 | ||
Bug Blocks: |
Description
Janusz Kaczmarek
2024-07-04 18:45:24 UTC
Hello Janusz, I see different ways of solving this issue. Anyway i'm working on a bz to be able to modify locked record (or change the record source with marc modification template). I wonder what solution would be best, either of which: - not letting users without the permission to edit locked records to be able to enqueue a mass modification job (that would make sense). -let simple users launch there jobs but "bypassing" the changes for any locked record which is in the list. I'd say I prefer the first solution, otherwise you might get quite a huge mess in your records. Plus it quite make sense to me that only "power-users" would be able to batch modify records... + I'd say this bug could be solved in BZ36975 Oh, after carefully reading your comment I see that it is a different problem. I'll try to provide a patch for that as well. methods to add some checks to : Koha/Biblio.pl -> merge_with C4/Biblio.pm -> ModBiblio, DelBiblio perl tests can use t::lib::Mocks::mock_userenv( { patron => $patron } ) to mock restricted user and check for return value. |