Forums » Modifiable user priveleges?

RSS feed for this topic

Info

  1. ebellempire Posted 3 years ago

    In future releases, will there be an option to manually grant certain rights to certain users without upgrading their user role? For our project, we are working with student researchers, and have given them "Contributor" status, which is well-suited in every way except that they are unable to add their materials to a collection. This means the Admin or Super users have to go in and add them to the collections manually.

    Anyway, that's on my wishlist.

    Thanks for all the great work! Omeka is getting better and better with each release.

  2. DaveLester Posted 3 years ago

    We have no immediate plans to develop this added feature, but if there's enough interest we can consider adding it to the core. At this point, it'd be possible to build a plugin that could administrate the permissions of users beyond Omeka's presets.

    Anyone interested should consider joining the Developer Mailing List to discuss this further. http://groups.google.com/group/omeka-dev

  3. pcoutas Posted 3 years ago

    I too would love "contributors" to be able to add their materials to a collection.

  4. DaveLester Posted 3 years ago

    Upon closer examination, contributors CAN in fact add their own items to a collection. Did I misunderstand your original question, ebell?

  5. pcoutas Posted 3 years ago

    But no collections appear in the drop-down box for collector-users when they're adding items, even if they've been added as collectors by admin/super. And when they try to add a collection under the "collections" tab themselves, a 403 page error appears.

  6. ebellempire Posted 3 years ago

    This is also my experience.

  7. KrisKelly (Omeka Dev Team) Posted 3 years ago

    Contributor level users cannot add their own collections, nor can they see collections that are not listed as 'public'.

    What's happening here is that contributor users cannot choose to add their items to a collection that is not yet public. You'll see if you make a collection public and then get a contributor to add their item to it, it works fine.

    What I'm not sure of is whether or not this should be considered a bug or expected behavior. Contributor users cannot see items that are not public yet, so it made sense to assume that they shouldn't be able to see collections that are not public yet.

    This causes the aforementioned problem with data entry, though users with higher permissions don't face the same problem.

    A short term workaround would be to hack the application/core/acl.php file to set ACL permissions to include 'showNotPublic' for Contributor users.

    Does anybody have any ideas for more permanent solutions to this problem?

  8. hopegreenberg Posted 1 year ago

    Is this still true in 1.3.2?

    "Contributor level users cannot add their own collections, nor can they see collections that are not listed as 'public'...A short term workaround would be to hack the application/core/acl.php file to set ACL permissions to include 'showNotPublic' for Contributor users."

    I have created a colletion and have listed names of the contributors in the "Collectors: List collectors for this collection" box but they cannot see a collection listed in the drop down list when they are trying to add an Item to that Collection. We would prefer to build the items/collections/exhibits as private, then when done set it all to public.

Reply

You must log in to post.