Here's an interesting question - 'part of iso9000 is that documents be reveiwed atleast once a year, is there any mechanism is Drupal that could acomplish this?'. NB: the site is 5.9, a week-old, has no email, and is predominently blog based.

Comments

hershel’s picture

Firstly, why are you using 5.9? Unless 6.3 can't provide some critical feature, it is recommended to use 6.3.

As far as reviews, I presume you mean human-review. If so, this could be accomplished by marking each node (either via taxonomy or via a CCK field) as having been reviewed last on such and such a date. If I understand the question correctly.

richard102’s picture

Why 5.9? well, I started this project with 6.2 and there were problems with the 'update' module, the admin/modules page took ages to load, and, well, it just didn't feel as solid as 5.x - to me. I know there's 6.3 now but, well, at somepoint you have to put a stick in the sand.

re: human review >> It would need some mechanism where-by pages that hadn't been updated for over twelve months were automatically flagged to the authors, somehow.

davedelong’s picture

This is easy enough using a custom module or with workflow or something. If going the custom route (which I would do since I don't really "get" how workflow works), it'd be a matter of querying the {node} table in the database for all nodes (perhaps of a certain type) that haven't been updated in a year. For all those nodes, set a little flag (perhaps unpublish them or something) and display them in a view.

Dave

Get great Drupal hosting at MM Hosting. (I don't work for them; I'm just a very satisfied customer)

richard102’s picture

Thanks davedelong

how about this - everyday the three text colours R,G,B, are incremented by one. Assuming the text colour start-out as black (o,o,o) then after 255 days without being updated the text would have faded away completely, //just like old parchment// (255,255,255).

then the onus to keep information up-to-date would be on the author, not the administrator.

possible?

I guess admin's and application text would have to be exempt, and every page would have to have seperate settings, and theme interference would need to be overwritten.

still drupal would be an ideal 'walled-garden' to test it

there are obvious issues - like not being as useful as an automated email, but similar to a 'wiki' its a flawed, but delicious idea (to me :-)).

davedelong’s picture

I wouldn't count on rgb(255,255,255) as being "faded out completely". What if it's on a blue background? Then it would be quite visible.

I would probably just use a countdown style method - "42 days left" or something. Maybe you could send them a friendly email once it hits a week left. This, by the way, is really easy to do. Just take the time() - node created date, and divide by 86400, then round down.

Dave

Get great Drupal hosting at MM Hosting. (I don't work for them; I'm just a very satisfied customer)

richard102’s picture

Hi davedelong

I guess you're right - which brings me right round in a circle, to the root issue I was trying to ignore ... how do I get drupal to send mail in WAMP? :-(

WorldFallz’s picture

If you have access to a different smpt server, just edit your php.ini file for the windows "SMTP =" settings, enter the info, and recycle. I'm on a corporate intranet and that's what i did (i just put the name of our main smtp server there) and it works great.

Another option might be http://drupal.org/project/smtp or to install an os smtp server (like hMailServer) on your windows box.

If you ===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime."
-- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz

richard102’s picture

sorted thanks, used the SMTP module