Everything linked with any Knowledge Management must focus in customization, because not all companies an scenarios involved are the same. The first stage on any Knowledge Management implementation is a consultant to get goals, description of the process, discover existing information etc... basically get an image of where are you now and where do you want to go.
After it you can focus on each customization, build specific reports ( for example invoices what might be interesting for some department what are automatically communicated to them ), the desicion support system usually will be some customization between several applications ( not only OpenKM ) to retrieve into a single view several information what is critical for manager when they are taking decisions.
The process for identifying documentation might be based on learning machine ( what obviously requires preliminary training ) for content analysis in combination with document type recognition ( OCR document templates recognition ). Advanced preview is only a feature what we talk about it as an usability feature.
For my point of view, Knowledge Management is not a single application, are a couple of application what working together in some manner for getting some goals in your company. OpenKM as a Document Management and Record Management software are part of this ecosystem and might be the core of them, but will never cover everything. Usually must be build a thirparty layer ( User interface ) for specialized explorer and user interaction. The most important thing are the preliminary analysis ( what is not trivial and demands get almost company involved and find relevant persons into the company for doing it ).
Finally build Knowledge Management is not only a software solution it also demands policy changes into the company ( new rules, new bussiness logic and workflows ) you might see as a process what can take several years ( implemented step by step into your company ). Probably at the begining you have an image in your mind what at the end when you will arrive at the finish point will be changed ( sure ), because during the evolution ( I recommend incremental ) you will review your needs etc... and will be applied changes.
After it you can focus on each customization, build specific reports ( for example invoices what might be interesting for some department what are automatically communicated to them ), the desicion support system usually will be some customization between several applications ( not only OpenKM ) to retrieve into a single view several information what is critical for manager when they are taking decisions.
The process for identifying documentation might be based on learning machine ( what obviously requires preliminary training ) for content analysis in combination with document type recognition ( OCR document templates recognition ). Advanced preview is only a feature what we talk about it as an usability feature.
For my point of view, Knowledge Management is not a single application, are a couple of application what working together in some manner for getting some goals in your company. OpenKM as a Document Management and Record Management software are part of this ecosystem and might be the core of them, but will never cover everything. Usually must be build a thirparty layer ( User interface ) for specialized explorer and user interaction. The most important thing are the preliminary analysis ( what is not trivial and demands get almost company involved and find relevant persons into the company for doing it ).
Finally build Knowledge Management is not only a software solution it also demands policy changes into the company ( new rules, new bussiness logic and workflows ) you might see as a process what can take several years ( implemented step by step into your company ). Probably at the begining you have an image in your mind what at the end when you will arrive at the finish point will be changed ( sure ), because during the evolution ( I recommend incremental ) you will review your needs etc... and will be applied changes.