| Term | Description |
|---|---|
| Approver |
User approving / releasing documents. Only after approval/releasing documents are visible to normal users (readers). In big organisations the approver is normally different from editor and expert(s). However in small organisations and companies he can be identical to editor and/or expert as well. |
| Expert | User who is contributing knowledge to the database. |
| Editor |
User writing / editing knowledge documents. In big organisations the editor (sometimes also called 'debriefer') is normally a different person from the expert(s). However in small organisations and companies the editor will usually be identically to the expert. |
| Knowledge Manager |
User administrating powerKNOW This user is able to change the configuration, the document structure, the search keyword tree, and the user registration. |
| Reader |
User registered as a normal reader in powerKNOW This is a user who is registered in powerKNOW but has no special roles / rights assinged. Such a user is able to read documents which have been marked as 'approved/released'. |
| Knowledge document | A document containing knowledge about a special aspect of business, information, ... . powerKNOW is maintaining such documents and making them easily accessible. |
| Document status |
In powerKNOW each knowledge document is in one of 3 statuses:
|
| Attachment | A file which has been attached to a knowledge document. In powerKNOW such attachments are store with the knowledge document in the database. powerKNOW is able to include the file types most used into the full text search. |
| Search keyword tree | Keywords in powerKNOW are organized in a tree structure to be able to present a hierarchically organized search structure. see "Search Keyword Tree" for details. |
| My Structure | Structure of a knowledge document. see "Structure Fields" for details. |
| User role | Defines the functions a user is able to perform within powerKNOW. see "User Roles" for details. |
| Structure fields |
Structure fields are used to provide all knowledge documents
with a uniform structure. The count of structure fields used and the titles
can be configured. See "Structure Fields" for details. |
| Structure text | We use this as a synonym for "Structure field" (see above). |