Help with Translator Approval Workflow for Notepad++ Documentation Translation Site

Events happening in the community are now at Drupal community events on www.drupal.org.
stieglitz's picture

I have volunteered my time to help with the Notepad-plus-plus documentation project. I am trying to streamline the workflow for approval of translators. I have created a "Translator application" which sends an email with the relevant tokens from the application node. Ideally I would like to just click on a link in the email which takes me to the node where I can approve the translator or deny it. Once it is approved I'd like to have other actions fired.

One of the things I began to try was When the application was submitted an "approval" node was created with the default being unpublished. The idea was that once I published the "approval" their role would change from authenticated to translator. I would then have to add the language etc.

Does anybody have some suggestions, ideas, exportable code or anything? At this point anything would be helpful.

Thank you,

Jon

Comments

^

ayesh's picture

I too have a similar application(not for translations though) and used the publish/unpublished status to detect certain events. But later, I realized that published/not status is not very suitable for this type of things.

  1. To view an unpublished node, the user must have permissions. So users "below" the translator can't see them.
  2. We are going to loss the original use of published/unpublished status.

What I suggest is, use Flag module. Flag performs well with Rules. On even the user submit the translation, you can have Rules to flag it as (unpublished and) flagged(say flagA). When admins approve it, you can unflag and publish the node. If somehow admins need to ask the translator to refine the translation, they can add another flag to (say FlagB) resend the node to translator.
Using Views,you can create a form where translators see that the admins want him to revise the translation.
The advantage of Flag module is admins can flag translations which are already published. But they are marked as another flag so translators can have them in their queues.

Pretty sure I didn't describe what I have to say, but bottom line, have a look at Flag module as well!

Exactly what I needed

stieglitz's picture

Thank you Ayesh. That is exactly what I needed to get my mind moving in the right direction. Being fairly new to Rules I do not have the experience of what modules work well. I had not considered the flag module but I can see how that would work! I'll let you know how it goes as I work on configuring it.

Rules

Group organizers

Group categories

Categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week