it would be very useful if we had a report of actions taken on a given piece of content. specifically, we will be using the email feature with 'no action' on groups site and will be useful for moderators to all know status of some piece of content. we might be moving into the realm of workflow though.

Comments

moshe weitzman’s picture

moshe weitzman commented

any chance this one will get in? we have many moderators on drupal.org and we can't tell what state the conversation is in with any given post ... i do recognize that this complicates the module a bit. we will need another table which lists messages sent for a given node.

scott.mclewin’s picture

scott.mclewin commented

@Moshe - bringing over a piece of the conversation from http://drupal.org/node/98182, I've got a simple question. Is there a log of actions on an item anywhere in another module already? Rolling a patch that adds a table to the modr8 module and stores off a record of the actions, builds displays and perhaps an RSS feed is not exceedingly complex. But it might be inappropriate if there is already a de facto home for this sort of information.

moshe weitzman’s picture

moshe weitzman commented

@scott - well, privatemsg.module is a bit like a logger for messages you have received. thats the first that comes to mind. there aren't exact analogies that i know of.

scott.mclewin’s picture

scott.mclewin commented

@moshe - I'll take a look at privatemsg.module before I roll a different set of changes to modr8. If it does not look appropriate I'll create a table that is specific to modr8 that just tracks the changes done through it. Any concerns with this approach?

pwolanin’s picture

pwolanin commented

I thins is to be implemented, I think there needs to be some thought about the workflow- on the content moderation page, perhaps each items need to indicate whether and how many comments exist already in the log for a particualr item. Also, the issue of revisions needs some careful thought- what if a later revision is sent back into moderation, but with substantially different content. Should the original comments still be visible? Should the log be erased when the content is approved?

moshe weitzman’s picture

moshe weitzman commented

my .02 ... the comments belong to the node, and they stay around as long as the node exists (never dumped). furthermore, they are not especially revision dependant. we can log what revision was active when a message was sent, but thats about it.

thanks for thinking about this.

pwolanin’s picture

pwolanin commented
Status: Active » Closed (duplicate)

addressed in this issue: http://drupal.org/node/108748