General
To understand what we mean by a Knowledge Base, we have to first realize that there are two types of knowledge: tacit knowledge and explicit knowledge. Tacit knowledge, the most valuable knowledge, is 'internal' personal knowledge. It is contained within our heads and is constantly being refreshed and updated through learning. Explicit knowledge is the knowledge that needs to be 'externalized' in some suitable form.
In the context of organizational knowledge management (KM), we should externalize the important or critical knowledge that needs to be accessed, shared, applied, and developed by others. But KM should certainly not be about externalizing and codifying as much knowledge as possible. That would simply be impossible and ineffective. We should consider codifying the knowledge that is considered 'critical' to develop and apply in the organization and that would make 'a big difference' to the organization’s performance. This is where we can effectively create explicit 'knowledge bases'.
It is certainly a good idea to first identify the 'key knowledge areas' in the organization that, if better managed, would truly make a big difference to performance. As a guideline, for each key knowledge area identified, it is good KM practice to develop a knowledge base (to maintain the critical explicit knowledge) and also a community of practice/interest or knowledge network around this key knowledge area (to surface and transfer the tacit knowledge).
What is the Difference between a Knowledge Base and a Database?
A database contains information that is structured in records, so that it can be sorted, categorized, and accessed. Typically, a database is updated and maintained, centrally, by a database manager(s) or administrator(s). A database is typically centrally controlled and the information is 'one way', that is, from owner to user.
Databases first contained simple structured records of text and numbers. They then became more able to link to corresponding records as 'relational databases'.
In the 1980–90 period, with the development of information management as a science, it became possible to populate databases with pictures and graphics, videos, tables, spreadsheets, and powerpoint presentations, etc. The information became richer, even though it was still typically centrally managed and controlled. However, instead of calling them information bases—a term that never really caught on—we still tend to call them databases.
In the 1990–2000 period, with the development of collaborative team working tools, it became possible to create databases with far more collaborative team input, feedback, and collaborative authoring. Centralization gave way to more 'participative development'. Furthermore, we learned how to better capture and store new learning and ideas within these spaces, so that the knowledge base became more alive with 'continuous learning and ideas' and even 'continuous innovation'.
GeneralTo understand what we mean by a Knowledge Base, we have to first realize that there are two types of knowledge: tacit knowledge and explicit knowledge. Tacit knowledge, the most valuable knowledge, is 'internal' personal knowledge. It is contained within our heads and is constantly being refreshed and updated through learning. Explicit knowledge is the knowledge that needs to be 'externalized' in some suitable form.In the context of organizational knowledge management (KM), we should externalize the important or critical knowledge that needs to be accessed, shared, applied, and developed by others. But KM should certainly not be about externalizing and codifying as much knowledge as possible. That would simply be impossible and ineffective. We should consider codifying the knowledge that is considered 'critical' to develop and apply in the organization and that would make 'a big difference' to the organization’s performance. This is where we can effectively create explicit 'knowledge bases'.It is certainly a good idea to first identify the 'key knowledge areas' in the organization that, if better managed, would truly make a big difference to performance. As a guideline, for each key knowledge area identified, it is good KM practice to develop a knowledge base (to maintain the critical explicit knowledge) and also a community of practice/interest or knowledge network around this key knowledge area (to surface and transfer the tacit knowledge).What is the Difference between a Knowledge Base and a Database?A database contains information that is structured in records, so that it can be sorted, categorized, and accessed. Typically, a database is updated and maintained, centrally, by a database manager(s) or administrator(s). A database is typically centrally controlled and the information is 'one way', that is, from owner to user.Databases first contained simple structured records of text and numbers. They then became more able to link to corresponding records as 'relational databases'.In the 1980–90 period, with the development of information management as a science, it became possible to populate databases with pictures and graphics, videos, tables, spreadsheets, and powerpoint presentations, etc. The information became richer, even though it was still typically centrally managed and controlled. However, instead of calling them information bases—a term that never really caught on—we still tend to call them databases.In the 1990–2000 period, with the development of collaborative team working tools, it became possible to create databases with far more collaborative team input, feedback, and collaborative authoring. Centralization gave way to more 'participative development'. Furthermore, we learned how to better capture and store new learning and ideas within these spaces, so that the knowledge base became more alive with 'continuous learning and ideas' and even 'continuous innovation'.
การแปล กรุณารอสักครู่..