Forum Moderators: open
The main issues are that, a year down the line, people are beginning to lose track of out of date information. So far, no-one has kept a record of when changes have been made and what those changes were.
So the first thing to do is an audit, to see what is out of date. My thoughts are that some kind of shared diary/tracking system needs to be put in place so that as soon as a change is made, each editor can add the details (a non-technical change log essentially).
Does anyone have any suggestions as to the best way to manage this process?
Also any recommendations for a cheap/open source system that may help with this, would be welcome.
I've looked at Contribute Server (the editors use the client of Contribute), but that seems more geared at tracking dates and types of changes and less useful for non-technical users.
The big question is, what is the best way to keep a track of out of date content?
Thank for any suggestions.
What came to my mind when I read your problem was a very simple solution in your case - don't use any specific editorial software. What probably will work perfectly for you is to make sure you capture with every document details, such as type of change made, its author, date and time when the change is made. All that you can have in, let's say, a plain worksheet in MS Excel (surely accessible to everyone).
The materials themselves may be collected as a simple encrypted zip-archive.
Have a wonderful day.
[edited by: Turbulence at 9:43 am (utc) on Feb. 8, 2007]
Thanks for that.
Yes a simple solution is always good. The issue with an Excel file is with people opening the file at the same time and saving different copies of it in different places and so on. If it can be done, this group of editors will do it. ;)
I really was thinking of a two pronged solution;
1. A system of auditing 'old' pages. I'm definitely stuck on how to best do this.
2. Some kind of cheap and chearful changelog system. Perhaps a web based/login version of what you suggested with Excel.
I see what you get in mind. The problems with Excel that you mentioned are indeed existent to a greater extent when teams incorporate many members. Probably anyone here would be able to give you a nice, working solution for your specific case. So we are waiting here for the imput of others.
Have a nice day.
