Summary: | Superlibrarian can't export all biblios when IndependantBranches is enabled | ||
---|---|---|---|
Product: | Koha | Reporter: | Frédéric Demians <f.demians> |
Component: | Staff interface | Assignee: | Frédéric Demians <f.demians> |
Status: | CLOSED FIXED | QA Contact: | Ian Walls <koha.sekjal> |
Severity: | minor | ||
Priority: | P5 - low | CC: | chris, gmcharlt, jcamins, nengard, paul.poulain |
Version: | 3.6 | ||
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: | ||
Attachments: |
Proposed patch
Bug 7505 Superlibrarian can't export all biblios when IndependantBranches is enabled |
Description
Frédéric Demians
2012-02-06 18:57:22 UTC
Created attachment 7469 [details] [review] Proposed patch To test: - Do a ALL records export as superlibrian on a multi-branches Koha instance - Examine the resulting MARC file with the tool of your choice (MArcEdit, yaz-marcdump, etc.) - You will see that 952/995 contains exlusively items from your branch (as Koha user) Created attachment 7476 [details] [review] Bug 7505 Superlibrarian can't export all biblios when IndependantBranches is enabled When a Koha user has superlibrarian permissions, and if IndependantBranches is enabled, in Tools > Export bibliographic and holdings, this user can't export all biblio records. He will just export the biblio from the branch he belongs to. This patch fix that. To test: - Do a ALL records export as superlibrian on a multi-branches Koha instance - Examine the resulting MARC file with the tool of your choice (MArcEdit, yaz-marcdump, etc.) - You will see that 952/995 contains exlusively items from your branch (as Koha user) Signed-off-by: Jared Camins-Esakov <jcamins@cpbibliography.com> Uses bitwise AND syntax for permission check (preferred method), and adds check to export function as necessary to solve the issue. Marking Passed QA. *** Bug 3002 has been marked as a duplicate of this bug. *** This patch was incorporated into 3.6.x prior to 3.6.4. |