By OnkelTem on

Hi all!

What can I use for organizing docflow on Drupal?

For example:

1) A user creates an ad (node) and pushes it to moderation
2) A moderator either silently Accepts the posting or Declines it with a comment or a reason of refusal.
3) The user receives his declined ad, read the moderator's commend, optionally add his own comment/question, optionally edit the ad, and optionally sends it to moderation again.
4) The moderator sees this activity in UI, takes part in discussion, and finally when everything is ok pushes it forth
5) A site editor gets the ads passed moderation phase, makes final checks, and publish ads.
6) A published ad has ordinary Drupal comments.
7) Later if an editor/moderator find an ad inappropriate anymore (on some reasons) they can unpublish it and pull it back to the flow.

So we have:

1) Node with states
2) Transition matrix
3) Comments realted more to revisions, not ordinary user comments
4) A crew involved in differenct phases of a document lifecycle

Any ideas how this could be done?

⋅ Categories: Drupal 7.x

Comments

OnkelTem’s picture

OnkelTem commented

Up

chianti’s picture

chianti commented

Try the workflow module: http://drupal.org/project/workflow

I can't remember whether workflow disables the node's 'publish' permission by itself, so you might need this too: http://drupal.org/project/override_node_options

The workflow module can notify the mod by email when the node is created and edited. It's the subsequent communication between mod and editor that's going to be tricky...

The mod and editor could leave a simple comments on the edit page using:
http://drupal.org/project/admin_notes

I've never used the core revisioning before, but maybe that has something to offer in the way of comments/communication too; I think there is a text box for explanations of why a node was edited and what was done to it. This is nice, because the mod would have a record of the changes made.

Also, the editor could start a (private) forum topic to go with his submission, and reference the forum thread in a node reference cck field. So the editor/mod exchange could be in the forum rather than in the node comments or edit page. This is nice because the mod could easily see and reply to new posts.

I'd be interested in hearing what your final solution is.