Additional workflow state for spam comments

[ksuess]

It would be nice for the moderator not being forced to approve or delete a comment but also being able to mark it as spam. With this additional workflow state a comment stays for reporting / documentation issues.
The moderation view needs to be extended by these spam comments. A filter for optional viewing all comments, only to be moderated comments, approved comments or spam comments would help moderating.

[agitator]

As I recall from our discussion, maybe also a rejected/disapproved state?

[ksuess]

I have just one additional workflow state in mind for a comment that is not OK to be approved.
And yes I also prefer the term rejected or disapproved instead of spam. The term spam is used by Wordpress and Disqus. See screenshots:

Worpress

Disqus

Unfortunatly the term rejected is already used in Plone workflows for a transition that does not mean definitly rejecting, but more of 'back to editor for improvement". So disapproved would be an option.

I do not see any need for a distinction between spam (call it rejected,disapproved,refused) and trash as Wordpress and Disqus do a differentiation.

[agitator]

For me spam is spam and rejected has a different meaning.
Having a separate state, would enable me to handle spam in a different way, for example analyse it and make rules to prevent future similar submissions.