A knowledge data base (English Knowledge cousin) is a special data base for the knowledge management. It represents the basis for the collection of information. Usually a knowledge data base consists of explicit information of an organization, which contains problem solutions, article, White PAPER and user manuals. A knowledge data base requires a carefully structured classification, a formatting of contents and user friendly search functionality (see taxonomy; Ontologie (computer science)). Generally a knowledge data base describes a part of an expert system, which contains facts and rules, which are used for the release from enterprise problems.
An expert system could bspw. a technical support function its, whereby the knowledge data base represents a scanable collection of questions and answers. Other examples are systems for the support of medical diagnoses or for the analysis of scientific data.
The major task of a knowledge data base consists of the fact that it helps people"
The knowledge data bases mostly develop from relational data bases, which consist of various recordings and fields (attributes). Logic functions, will added relations and additional attributes, in order to become fair the requirements of a specific domain.
Publishing the knowledge data bases (Knowledge cousin Publishing) is a proceeding, which concerns itself with creating, receiving, integrating and the functional employment of the knowledge data base. The conversion is realized by programs and techniques from various ranges (e.g. computer science, knowledge management, journalism, Public relation, Businessmanagement, lifelong learning etc.).
The publication process, which resembles usually the publication of a Website - is strongly in the Workflow integrated thereby. Retaining the user friendliness is an important aspect of the process of integration. So the e.g. following functions are to be considered:
The treatment of the knowledge data base (Knowledge cousin Editing) includes the procurement, verification, organization and presentation of the information in a knowledge data base also. The task of the editor begins not with contents, but with the users and their enterprise-referred tasks. The intention consists of the fact that several editors (English editor) attain a founded understanding of the user tasks in the enterprise context. Like that efficient handling processes of the print, Web and data base publication is necessary.
Depending upon range and complexity of a knowledge data base this is maintained by several editors, who are assigned according to your field of application different roles. A general role separation does not exist, on the contrary the respective implementation varies depending upon targeted application and the system, which can be usually adapted by the operator after the own needs. Often several roles of the same person are fulfilled, and/or a role of several persons.
The following roles are typical for a knowledge data base:
This role is compellingly necessary for functioning a knowledge data base.
New contents are requested by the applicant (English Requestor). This can happen in the context of a business process or as required, e.g. if a coworker of the support compiled a new solution, which is not yet contained in the knowledge data base. In this phase usually only abstract contents are relevantly, not however stylistic elaboration, since primarily a need collection takes place. Applicant it is also called who to existing contents requests changes.
This role is compellingly necessary for functioning a knowledge data base. In some cases partial aspects of this role accompany with the role of the author and/or Rezensenten.
The responsibility of the intellectual infrastructure for a knowledge data base is carried by the contents contents of (English content manager, also editor in Chief). This concerns in particular the perception or delegation of the following tasks:
This role is compellingly necessary. It accompanies in some cases with the role of the 'applicant '''.
The elaboration of contents is accomplished by the author.
This role serves the quality assurance, is not not compellingly necessary for functioning a knowledge data base, is however often recommended due to the four-eye principle.
After the elaboration of contents this becomes from the Rezensenten (English Reviewer, also editor ) examined for observance more stylistic, more structurally, terminologically and if necessary different defaults as well as orthography, grammar and if necessary technical correctness and if necessary correct. In some cases this role is divided into a technical and a non-technical part. Afterwards de-energising and/or publication (English publishing) takes place by means of the contents contents.
This role serves the quality assurance, is not not compellingly necessary for functioning a knowledge data base, however lastingly the usability and/or Wartungsfreundlichkeit as well as the acceptance guarantees by users. It accompanies in some cases with the role of the contents manager.
The definition of standards, which have the consistency of contents for the purpose, takes place via the Taxonom (English Taxonomist). This covers in particular the following tasks:
This role is compellingly necessary for functioning a knowledge data base.
The responsibility of the technical infrastructure for a knowledge data base is carried by the operator. This concerns in particular the perception or delegation of the following tasks:
We found here 3 articles.
K» KISS principle» Knowledge data base » Knowledge management system |
Index | Privacy | Terms Of Use | Sitemap | Feedback