PKP Bugzilla – Bug 4138
Allow for optional JM authorization of new comments
Last modified: 2009-06-01 16:27:39 PDT
This as a possible spam-block feature, and perhaps rendered obsolete by Matt's Notifications work. This kind of feature appears in Wordpress, and I make good use of it.
The Journal Manager should have the option to enable a check on any new comments to the site: new comments are not published right away; rather they are held in a moderation queue and must be confirmed as valid before being published.
This check should be performed by the JM or an Editor (probably the Editor?). The JM should also be able to mandate whether this check happens for each comment; or whether any user with a previously-approved comment (or who are part of the editorial team) has their comments posted immediately.
(courtesy of http://pkp.sfu.ca/support/forum/viewtopic.php?f=2&t=4250&p=16530#p16530)
Not currently implemented by the notification system, but easily implement-able (without thinking of the journal settings, which shouldn't be too difficult to implement either).
(In reply to comment #1)
> Not currently implemented by the notification system, but easily implement-able
> (without thinking of the journal settings, which shouldn't be too difficult to
> implement either).
That'd be great -- I couldn't remember if this was implemented or not. Also, I'm assuming this functionality (ditto notifications stuff) is something perhaps more applicable to the core itself?
Not sure about that--I don't think comments have been abstracted to the core yet. Lets just leave this under OJS for now.
next month there will be a big abstraction commit that will have announcements abstracted. The approach can then me mimicked to abstract comments and a whole bunch of other stuff... patience young grasshoppers.
Deferring. (Probably needs consideration within RT redesign -- i.e. what will we do about comments in general?)