Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • Knowledge Base implementation/MOD/plugin?

    Posted by lmcphre

    Hi all,

    We have installed TikiWiki (ver. 1.11) with the intention of building up a Knowledge Base to allow us to document all IT problems we meet in order to make everyone benefit from past experiences.

    However, it turns out that building the KB using the classic "wiki way" would eventually become a real mess of inter-referring pages. We were hoping we would find a MOD for TikiWiki that would implement a clean and simple infrastructure of a typical Knowledge Base.

    We did find a Knowledge Base extension for TikiWikiQuestion but it turns out it was built for TikiWiki 1.6 and it seems like it was not completely integrated to TW...We installed it anyway and are still in the process of trying to make it work (we have no php expertise at all in our staff)...so far, no good! 😑

    Has anyone heard of a complete TikiWiki MOD/plugin/extension that actually works fine, out-of-the-box for PHP-illiterates like us?

    I'd also be curious to hear tips from others who have successfully implemented their Technical Knowledge Base on Tiki's platform... (by Knowledge Base, I mean some kind of a help desk issue tracker where issues/problems are logged and documented while being troubleshooted and fixed, that can be categorized, tagged, searched, edited, deleted, etc).

    Any pointer would be highly appreciated.

    Best regards,

    /Phil

    Reads: 1893

    Posted by Rogelio F. Galliano

    Hi Phil,

    I'll answer you as an end user from the organizational learning field who is working in a project with similar goals to those you declare in your post.

    I believe that Genuine knowledgeQuestionhas two irreducible aspects:

    1. it is seldom structured in the form of fixed fields or dependable rules, and
    2. it is social, i.e., it is distributed as shared understanding among human groups that often have little respect for artificial organizational boundaries. Knowledge differs intrinsically from data in that it evolves along a critical path from story to culture, to organization, to technology.

    Real knowledge almost never is available from a …a clean and simple infrastructure. It almost always exists as a real mess of apparently incoherent units. It's the social human activity that as a persistent play with those building blocks imposes meaning, order and clarity to the disorganized net of disconnected pages.

    To Rick your post seems to be an use case for trackers.
    I do agree with him and from a complementary point of view I suggest you consider the whole TW project as a real Knowledge Base.
    I also invite you to examine the Wiki-based Project management approach as explained here by Marc Laporte:

    • Each wiki page is a mini-project.
    • Users or groups are associated to a page via a customizable role.
    • Possible roles:
      • Project/page leader
      • Interested party
    • CMS type workflow roles
      • Author
      • Translator
      • Editor

    We're structuring our departmental KB this way.
    Till here my contribution,
    Rogelio