Bug 17533 - Syncing private to public list or adding more specific permissions?
Summary: Syncing private to public list or adding more specific permissions?
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Lists (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-01 16:07 UTC by Marcel de Rooy
Modified: 2017-03-09 12:09 UTC (History)
1 user (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Crowdfunding committed: 0
Crowdfunding contact:
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 Marcel de Rooy 2016-11-01 16:07:44 UTC
I now have two lists: private list A (shared between some users), and public list B. A local custom cron job daily syncs changes from A to B.

What I would like, is: Let this group of users that now share A, have permissions to add/delete entries from public list B (but no one else).
The current permission strategy on public lists is all or nothing, but not just a group of selected users.

What would be the best way to go to achieve this goal?
What about giving staff users the right to add/delete entries from public lists? In my specific case the editors include a normal user ;)
Redesign the whole permissions thing on lists? Aarg.
Add a sync lists option?
What do you think?
Comment 1 Katrin Fischer 2016-11-01 16:12:07 UTC
I think a permission 'Manage entries on public lists' would work - it would fit with the already existing permission to delete public lists.
Comment 2 Marcel de Rooy 2016-11-01 17:04:46 UTC
(In reply to Katrin Fischer from comment #1)
> I think a permission 'Manage entries on public lists' would work - it would
> fit with the already existing permission to delete public lists.

Sounds good. Maybe that is the easiest solution. Will not cover all scenarios, but would be enough for my use case.
Comment 3 Marcel de Rooy 2017-03-09 12:08:11 UTC
On second thought, I dont think it would be a good idea to check this permission for each list we show in the opac.
Maybe I will open a new report for facilitating import/export list contents between lists.