Use Case - Editorial / Curatorial Workflows with different roles and permissions

[rosiel]

Title (Goal)	Editorial / Curatorial workflows with different roles and permissions
Primary Actor	Collection Manager, Site Administrator, Cataloguer, End User, Evaluator
Scope	Access, Workflows
Story	"As a collection manager/site administrator, I wish to view a well documented sample enabling me to set up my secure editorial workflow using Drupal."

Source:
Features Survey as "Examples of using Drupal's workflows to create editorial workflows."
ICG Report as "Default editorial workflow (configurable approval process for ingest/deposit) - Similar to simple workflow."

Tickets that will become relevant:

• Enhance object creation workflow #919 (workflow could be significantly simpler)
• Meta-Issue: Access Restrictions and Embargoes #928 (roles with different permissions, as well as creating "unpublished" content.)
• Restrict use of specific taxonomies to specific roles #825 (if allowing less-permissioned users to start creating content, we need to restrict "controlled" vocabularies so they are actually controlled)
• Manage local authorities within Drupal #815 (related to the above)
• Users without fedoraAdmin role can't upload images; other roles needed #1025 (if allowing less-permissioned (or anonymous!) users to ingest, this will need to be addressed)