Saturday 29 March 2003 12:03:32 am
I think the reason why its difficult to find a word for this is that the screen is trying to complete two tasks. The first task is the approval mechanism, which should of course be "approve" and "deny" which is the process driven element of the system. The second task of the screen is for a communication mechaism to pass comments back and forth between the editor and the publisher. There are two elements to this:
The first is the simple comment where you are talking about the article.
i.e.
"Alice, I like the article and will be publishing it once i have John review it". "Alice, I like the Article, i cannot review now but will review on monday, is this ok?"
The second is a firmer line.
i.e.
"Alice, I cannot publish this article until you change the legal notice from 2002 to 2003" "Alice, Please change your article to reflect the companies more open stance on opensource" My point is, i think there are two mechanisms at work here, the first a simple yes/no, the second a more unstructured communication. Now, all the functionality is there I think possibly all that is needed is some design to allow the user to know what elements they are using, this could be done via text positions and iconography. The mechanism needs to be straightforward, and there are really only two options here, "approve" and "deny" with the deny options having various shades..
So maybe you keep the Approve button as it is, but add a radio button to the right of the Deny button. With the following options:
"Requires changes" "Request denied"
These radio buttons would then dictate the type of action the workflow would take. "Requires changes" would replace the current "Pushback" and "Request denied" would replace the "Deny" button. The words could then be placed in a ini file that would allow developers to change then based on the company and culture the site is required for. And allow for future functionality such as adding pre assigned replies in the case of a support desk environment. Now this leaves the current "Add Comment" free to be used for what is is great for, adding comments. It would however be good to change this in an INI file so you could have words more appropriate to the audience. For example, I might change this to "Send Comment" which reflects more its purpose. I am sorry I could not answer your question with a simple word, but i think this needs exploring a bit, what do you think?
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|