Page History

...

When the module is enabled, objects ingested by most users are given an inactive state will be given the Fedora state 'inactive' until another user with proper permissions activates them.   If a the user creating the objects has the permission "Bypass default inactive object state" the default behaviour (object with active state) will persist, objects will be given the normal, 'active' state. The "Drupal Super User" (uid = 1) will always bypass the inactive state.

By default, 'inactive' objects are not displayed in collections and are not indexed in Solr, but they are accessible directly (if the PID is known) by anyone who can view Islandora objects. To restrict access to inactive objects, check the "Lock down inactive and deleted objects" option in Islandora configuration (admin/islandora/configure) and grant the resulting permission to appropriate roles.

Dependencies

This module requires the following modules/libraries:

...

Once the module is active, Simple Workflow causes Islandora to react differently to certain users' permissions upon ingest of an object. Most users' uploads will be set to 'inactive' upon ingest, which is a flag that prevents them from being searched to or browsed.

and will be invisible* to anyone without permission to view inactive objects. The following permissions can be set up for particular groups at htttp http://path.to.your.site/admin/people/permissions, under the Islandora Simple Workflow section:

• Bypass default inactive object state - Groups with this permission ingest objects as 'active' instead of 'inactive'.
• Manage inactive objects - Groups with this permission are able to view and manage a list of inactive objects at http://path.to.your.site/admin/islandora/simple_workflow/list; this page contains links to the 'Properties' page of the 'Manage' tab for each object whose state is set to Inactive.

Optionally (if enabled under Islandora configuration), in the Islandora section:

• Access inactive and deleted objects - If this permission is enabled, then groups without this permission can not access inactive objects. If this permission is not enabled, then anyone with the permission to 'View repository objects' can access inactive objects. 

Beyond this, any user wishing to upload objects needs to be part of a group with appropriate uploading permissions, i.e. 'Create new repository objects' and 'View repository objects' at http://path.to.your.site/admin/people/permissions.

...

.

...