#998 - 'Content review' add-on
-
By Robbie Goacher
- Added
- 5 views
| Identifier | #998 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | 'Content review' add-on |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | core |
| Description | An option that can be applied to any piece of Composr content that would flag it (triggers: staff notification, Admin Zone checklist) for review on a specified date.
I envisage this being an option on the editing screens, under the 'Advanced' hider. The option should allow you to specify an exact date, or just say "in x days/months/years" and let Composr do the rest. There should be an optional setting (for each piece/item of content) for a "Last reviewed: <date>. Next review: <date>." to be automatically added to the bottom of the content's main display. For a Comcode page, this would be at the bottom, and for a download, it would be in the grid of stats/information, etc. See how the NHS site does this: http://www.nhs.uk/conditions/diarrhoea/Pages/Introduction.aspx |
| Steps to reproduce | |
| Additional information | Default content review frequency for Comcode pages
Default content review frequency per catalogue Staff checklist hook for reviewing content (should explain edit to mark reviewed) Notification hook for staff, make it a discussable one ; notification should mention what the content is, and what the auto_action has been Display review status in appropriate place in each content type template; language string that is by default "Last reviewed: <date>" but could be "Last reviewed: <date>. Next review: <date>." Put on form under new 'Staff reviews' section allow specification of time in days OR months OR years OR not at all specification of a specific date for a one-off review (optional) say whether to make review status public specification of auto-action to perform New table content_type content_id ?review_frequency_in_days next_review_time auto_action=leave|unvalidate|delete |
| Related to | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
The custom field mechanism has been utilised so this also works for all content types supporting custom fields - i.e. you can specify individual default review frequencies for each default content type.
"Notification hook for staff, make it a discussable one"
Not been made a discussable notification, for technical reasons (plus it's borderline whether this would or would not be bloatage).