[Drupal] Workflows

Walker, Robert T. walker.45 at osu.edu
Wed Apr 23 09:01:56 EDT 2014


Good morning!

In preparation for moving from a custom CMS with no workflows (all users can publish their own work) to Drupal, I'd like to get everyone's take on workflows, not necessarily limited to Drupal but for any CMS.

We currently have 80 total CMS users with each office, department or center with one or more users.

The three things we'd like to accomplish with workflows:

*         Allow non-technical users to provide content but get it reviewed before publishing

*         Notify stakeholders (supervisors) of content changes

*         Ensure correct branding from a marketing perspective

In our brainstorming sessions, here's the workflow we've come up with:

Author (non-technical user); cannot publish content on their own

*         Can create new drafts of content

*         Can change content status to Needs Reviewed which sends the content to an Editor for review

Editor (a well-trained CMS user); can publish content

*         Can create new drafts of content

*         Can change content status to Published

o   Publish Author changes

o   Publish their own changes

*         Can change content status to Needs Approved which sends the content to an Approver for review

Approver (a non-technical supervisor to the Editor); can approve content and optionally publish

*         Can change content status to Needs Work which sends the content back to the Editor

*         Can change content status to Published

The idea is that most of our current CMS users would be Editors for their area in Drupal and able to publish their own changes. Editors would be well-trained to recognize proper branding. Authors could be others in their office that contribute content but it would need to be reviewed by an Editor before the Editor published it (or sent back to the Author for changes). The Editor role can also send content to an Approver for review if it is high-visibility content (like a department landing page

One feature that we'd like that we haven't seen yet in a module is the ability to assign content to a user. A use case would be that if two users are collaborating on content, they could be able to pass it back and forth.

What do you think? Is there a better workflow that can accomplish our needs? Do we need more than one workflow?

Thanks,
Rob

[The Ohio State University - Fisher College of Business]
Robert Walker
Web Application Developer
Information Technology Services
320F Mason Hall, 250 W. Woodruff Ave., Columbus, OH 43210
614-247-5477 Office
walker.45 at fisher.osu.edu<mailto:walker.45 at fisher.osu.edu> fisher.osu.edu<http://fisher.osu.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/drupal/attachments/20140423/ed0a620c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6753 bytes
Desc: image001.png
URL: <http://lists.osu.edu/pipermail/drupal/attachments/20140423/ed0a620c/attachment.png>


More information about the Drupal mailing list