Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-270

Make delegate admin permissions configurable

    XMLWordPrintable

    Details

    • Attachments:
      6
    • Comments:
      6
    • Documentation Status:
      Complete or Committed

      Description

      This jira record comes from the suggestions received on DS-261.
      We want make configurable in dspace.cfg the answer at the follow question: what is the mean of delegate admin for communities/collections and items?

      I plan to make configurable (on/off) the following functionalities:

      Community admin

      • create subcommunities and collections
      • delete subcommunities and collections
      • manage community admin group
      • manage community policies
      • create new group (NOT IMPLEMENTED DUE AT LACK OF TIME AND NEED OF FURTHER ANALYSYS)
      • manage collection template item
      • manage collection policies
      • manage collection workflow group
      • manage collection submitter group
      • manage collection admin group
      • delete item owned by collections within the community
      • withdrawn item owned by collections within the community
      • reinstatiate item owned by collections within the community
      • manage policies of item/bundle/bitstream owned by collections within the community
      • add bitstreams in item/bundle owned by collection within the community
      • remove bitstream in item/bundle owned by collection within the community
      • manage cc license of item owned by collections within the community

      Collection admin

      • manage the collection template item
      • manage the collection policies
      • manage the collection workflow groups
      • manage the collection submitter group
      • manage the collection admin group
      • delete item owned by the collection
      • withdrawn item owned by the collection
      • reinstatiate item owned by the collection
      • manage policies of item/bundle/bitstream owned by the collection
      • add bitstreams in item/bundle owned by the collection
      • remove bitstream in item/bundle owned by the collection
      • manage cc license of item owned by the collection

      Item admin

      • manage item/bundle/bitstream policies
      • add bitstream
      • remove bitstream
      • manage cc license

      Please note that always a community admin will be a collection admin for all the collections within the community and a collection admin will be always an item admin for all the item owned by the collection. All the function that are allowed to user with WRITE permission on an object will always allowed to the ADMIN of the object (i.e community/collection/admin will be always allowed to edit metadata of the object ). The default will be "on" for all the configurations.

      I will try to make also the dspace API aware of this configuration but some of this will need to be take care on the UI because we don't have specific permission form them (i.e. withdrawn, manage policies, etc.)

        Attachments

        1. ds-270-alternate-oracle.diff.txt
          3 kB
        2. ds-270-api-r2.patch
          88 kB
        3. ds-270-configuration-db-r2.patch
          8 kB
        4. ds-270-full.patch
          193 kB
        5. ds-270-jspui.patch
          54 kB
        6. ds-270-xmlui.patch
          42 kB

          Activity

            People

            Assignee:
            jtrimble Jeffrey Trimble
            Reporter:
            bollini Andrea Bollini (4Science)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved: