http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5725 --- Comment #8 from Nicole C. Engard <nengard@gmail.com> 2011-02-18 14:45:16 UTC --- IRC Log on this topic: [08:57] <nengard> i'm logged in a superlibrarian [08:58] <nengard> i'll go ahead and try with only the edit permissions [09:00] <oleonard> Hmmm, no I see the batchedit permission in my database [09:00] <nengard> i don't have that either - but the patch doesn't say it adds a new permission [09:00] <oleonard> ...and it's checked in my permissions setup [09:00] <nengard> oh [09:00] <nengard> under what? [09:01] <oleonard> At first I thought it would be under cataloging, but it's under tools [09:01] <nengard> under tools i have items_batchmod [09:01] <nengard> but not batchedit [09:02] <oleonard> I ought to trash this database and start over... I'm not good about keeping it "clean" when testing [09:03] <nengard> :) [09:03] <nengard> paul_p can you take a look at questions on bug 5725 [09:03] <huginn> Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5725 enhancement, PATCH-Sent, ---, paul.poulain, ASSIGNED, Batch modifications for Biblios [09:03] <kf> only a thought: but do we need different permissions for items_batchedit and biblio_batchedit? [09:05] <nengard> i think we do [09:05] <nengard> but right now we don't have one [09:05] <nengard> i'd argue that if you're allowed to edit the catalog then you should be able to do batch edits ... but others might disagree [09:06] * oleonard does [09:06] <oleonard> A batch edit is potentially much more destructive [09:06] <oleonard> No reason not to include a separate permission and let the supervisor decide. [09:10] <oleonard> nengard: I'll bet the batchedit permission didn't make it into the patch because of the way rangi is putting together the patches [09:11] <oleonard> He probably didn't cherry-pick that part (if cherry pick is the right word here) [09:11] <nengard> so there is a permission in another patch? [09:13] <oleonard> Yes, I see it in the original Biblibre branch [09:13] <oleonard> That must be why I have it... messy database. [09:13] <oleonard> But that doesn't explain why it didn't work for me even though that permission was there [09:21] <oleonard> It seems strange that someone could have batch edit permission and not catalog edit permission [09:30] <sekjal> I'd agree that if you can edit in batch, you should be able to edit individually [09:34] <kf> so it should be grouped into the cataloging rights? [09:37] <oleonard> How deep can the permissions hierarchy go? Right now we only have two levels [09:38] <oleonard> Theoretically you'd want "batchedit" to be a sub-permission of "edit_catalogue" (not "editcatalog," the parent category) [09:39] <kf> oleonard: perhaps even the batch item delete/modify should moved to cataloging? [09:39] <kf> i think they are under tools, because we have no cataloging start page? [09:39] <paul_p> nengard, seen you msg. Could you drop me a mail pls, i'll forget... [09:39] <nengard> okey dokey [09:40] <oleonard> kf: I think so. I think that grouping reflects where to find the tool in Koha, but really the permissions should reflect roles [09:40] <kf> hm. I think we only have kind of a start page for circ and tools? [09:40] <kf> perhaps we should think about that too - tools gets crowdy [09:40] <kf> crowded? [09:40] <oleonard> Crowded. [09:40] <nengard> I don't mind where the batch edit is located - it is a tool - but the permissions should be in the logical spots -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.