In one of the previous posts , I thought about how it would be possible to use a WIKI engine to implement CCB within an organization. To summarize, my idea was to allow CCB members to develop interactive content within a wiki engine. Wiki can be easy available in the organization as part of most enterprise packages today – from Microsoft to Oracle. Also, open WIKI engines are available.
Now, let’s get back to the original idea. One of the main points is how to organize the history of changes without disturbing users. Each additional “create version” operation will be considered as less usable. I was thinking about how to organize an immersive environment for users – creating and collaborating on the same content without having to burden them with version control. Version control is important to be able to maintain changes, traceability and formal change control. So, I was thinking about implementing it by using two functionalities –
(1) Export Wiki Page to PDF;
(2) Search inside of PDF content.
Export Wiki Page to PDF is almost a standard functionality supported by many wiki engines. It’s available in IBM, supported in TWIKI. In addition, there are “export to PDF” components that can be used together with various wiki software (i.e. Microsoft SharePoint). Some of the wiki software allows you to export a collection of pages to PDF, which is even more powerful. By using this functionality you can organize the creation of snap-shorts from a wiki page each time the changes are submitted. So, we can get a full history of all CCB meetings.
Search inside of PDF document will be a cool feature to support. This functionality is also quite standard and can be supported, for example, by Microsoft SharePoint, IBM and other search software. So, you can easily find anything you discussed and worked on during your CCB meetings.
I think this cool functionality is also simple to implement and quite powerful.
Pingback: change management model()