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

When deleting a collection role the group is also deleted, which is not appropriate for non-system-created groups

    Details

    • Attachments:
      0
    • Comments:
      14
    • Documentation Status:
      Needed

      Description

      We have bee testing the packager tools. On import, the packager tools issue a warning if no default read access is present. In order to work around this error messaged we assigned the group "Administrator" to have default read access for a collection.

      Our collection administrator wanted to remove this role from the collection.

      In the process of deleting the collection access role, the epersongroup "Administrator" (id 1) was deleted.

      The create-administrator group was unable to assign administrators because group #1 was not present.

      To resolve the issue, we needed to manually re-insert group 1 into the epersongroup table.

      ------

      To repeat the issue:

      1. Create a collection without default item read/default bitstream read access
      2. Click Edit Collection
      3. Click Assign Roles
      4. Click "Click here to add a new policy"
      5. Grant "Administrator" Default Bitstream Read Access
      6. Click "Click here to add a new policy"
      7. Grant "Administrator" Default Item Read Access
      8. Click "Return"
      9. You will return to the "Assign Roles" Tab
      10. Note that Default Read Access is set to Administrator
      11. Click Delete for Default Read Access
      12. A confirmation screen will appear: "Confirm deletion for role DEFAULT_READ"
      13 Click delete - this will delete the "Administrator" group.

      --------------

      Because the Administrator group is deleted, you cannot re-add an administrator via the command line.

      .../bin/dspace create-administrator
      Creating an initial administrator account
      E-mail address: terry.brady@geogetown.edu
      First name: Terry
      Last name: Brady
      WARNING: Password will appear on-screen.
      Password: —
      Again to confirm: —
      Is the above data correct? (y or n): y
      Exception: Error, no admin group (group 1) found
      java.lang.IllegalStateException: Error, no admin group (group 1) found
      at org.dspace.administer.CreateAdministrator.createAdministrator(CreateAdministrator.java:243)
      at org.dspace.administer.CreateAdministrator.negotiateAdministratorDetails(CreateAdministrator.java:216)
      at org.dspace.administer.CreateAdministrator.main(CreateAdministrator.java:82)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225)
      at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)

      ----------------
      Note that SQL is required to fix the issue

      [dspace@dspace-aux-1 GUDSpace]$ psql
      psql (8.4.20)
      Type "help" for help.

      dspace=> insert into epersongroup values(1,'Administrator');
      INSERT 0 1
      dspace=> select
      i.item_id, handle from handle where resource_id=778;

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                terrywbrady Terry Brady
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: