BusinessService "Run your organizational Find-And-Learn network!"

About In this context… What links here? CONTENT [edit] Knowledge management consists of optimizing the access to and the management of knowledge for the sake of decision and performance support. EntityType "BusinessService" Keywords/Contexts DataspectsSystem · DataspectsSearch  Annotations HasGitHubRepository::https://github.com/dataspects/dataspectsSystem [edit] [edit] Main Page ‎ (← links) Contexts ‎ (← links) BusinessService ‎ (← links) Template:EntitiesByEntityType ‎ (← links) Property:HasEntityType ‎ (← links) Property:HasEntityBlurb ‎ (← links) Property:HasEntityTitle ‎ (← links) Property:HasEntityKeyword ‎ (← links) Property:HasEntityTypeAndEntityTitle ‎ (← links) Property:HasGitHubRepository ‎ (← links) Property:HasNotice ‎ (← links) DataspectsSystem ‎ (← links) DataspectsSearch ‎ (← links) [edit] See below…

Story

1.	People are accustomed to searching things on Google.	That's why your enterprise knowledge management search engine must model itself on Google.
2.	People are accustomed to reading things on Wikipedia.	That's why your enterprise knowledge management presentation must model itself on Wikipedia.
3.	People are accustomed to editing things on Microsoft Word.	That's why your enterprise knowledge management editor must model itself on Microsoft Word.
4.	People are accustomed to linking things using Properties.	That's why your enterprise knowledge management structure must model itself on Semantic Web Concepts.
5.	Organisations are accustomed to working with files and documents.	That's why your enterprise knowledge management presentation must smoothly integrate files and documents (upload, preview, versioning).
6.	Organisations are accustomed to working with printouts and PDF.	That's why your enterprise knowledge management presentation must output printer friendly formats and PDF.
7.	Organisations are accustomed to working with hierarchical workflows and access control.	That's why your enterprise knowledge management presentation must provide basic workflows and access control.
8.	Organisations are accustomed to working with tables.	That's why your enterprise knowledge management presentation must provide intuitive creation and design of tables within a visual editor

This article is about dataspectsSystem — a system that facilitates managing all aspects (e.g. install, upgrade, configure, manage, restore, etc.) of Semantic MediaWikis and WYSYWIG editors in a narrow sense and complementary/auxiliary systems in a broader sense, e.g. search, backup, integration, etc.

The dataspects Knowledge Management Framework DSKMF facilitates managing and using your knowledge.

1. It is based on dataspectsSystemCoreOntology and implements a distinct set of knowledge management concepts (see below).
2. It integrates optimally with dataspectsSearch providing a single "Google-style" interface to your knowledge (see https://dataspects.com for the current development version).
3. It allows for mentally traveling through a web of subject affinities starting with an intuitive and spontaneous statement.
4. It allows for managing terminological ontology facets (extracting, injecting, versioning, e.g. DSKMFCoreOntology) and managing assertional ontology facets (move, scale, backup, synchronize, archive, e.g. What can be used how in a facets-management-script.rb?), see https://dataspects.com/structured-data-management-suite.
5. It is deployed by Restore/clone a system (snapshot).

Distinct set of knowledge management concepts

• The Component1523286906 whose goal it is to turn data into narrative structures…
  • …is based on Knowledge Topics/Subjects/Bites, which…
    • …are of a Single Type and can assume Multiple Roles.
      • As such they possess Regular Affinities (properties).
      • As such they use a display title format Type "Title".
    • They are tagged by Keywords, which are the only untyped entities (simply HasEntityKeyword) in DSKMF.
    • They can be annotated by Irregular Affinities, which allow for user-driven ontologization and a subsequent derivation of the terminological ontology from assertions (see Insight).
    • They can be put into Contexts without specifying its exact nature of relationship (simply HasContext).
    • They can be assigned Active and Passive Actions:
      • active actions: things that a subject can DO
      • passive actions: things that can be done with/to a subject
    • When being managed as SMW pages (Dataspects::Resource) on a SMW (Dataspects::ResourceSilo) they can be semantiziced along SMW-typical aspects…
      • …annotations happen according to Component0170103276,
      • …and MediaWiki categories are not used for content structuring but only for organizing terminological ontology facets.
• Annotations can be reified in order to annotate annotations.

Slogans

• https://github.com/dataspects
• Mutually Exclusive, Collectively Exhaustive (MECE)
• A place for everything and everything in its place
• Convention over configuration
• Completely decomposable
• Let your data teach your business to new employees
• Organize your knowledge as interrelated subjects

User Experience

Using the system must be:

1. clear by intuition/GUI
2. clear by mouseover message/hint
3. clear by documentation at mouseclick on link/button to popup or toggled div
4. clear by documentation at mouseclick on link/button to information in new window
5. clear by calling/mailing to a supporting party

Costs in terms of transactional brain cycles and time units used/wasted increase logarithmically.

Conceptual Layers

Notice:

• Write the code you wish you had.
• Good architecture maximizes the number of decisions not made.

Conceptual Layer "Assertional Ontologies"	Conceptual Layer "Tools" AnsibleRole "Install easy system cloning"
Conceptual Layer "Terminological Ontologies"
Conceptual Layer "Extensions" This conceptual layer provides Ansible roles to install any selection of MediaWiki extensions. Methods: Composer, Special:ExtensionDistributor, GitHub These Ansible roles will extend/alter Conceptual Layer "Infrastructure" and Conceptual Layer "MediaWiki" according to the requirements of the MediaWiki extensions being installed.
relies on everything below ↓
Conceptual Layer "MediaWiki" This conceptual layer provides Ansible roles to install any version of MediaWiki that hasn't yet reached its end-of-life. These Ansible roles will extend/alter Conceptual Layer "Infrastructure" in accordance with the requirements of the MediaWiki version being installed.
relies on everything below ↓
Conceptual Layer "Web services" AnsibleRole "Install Parsoid" AnsibleRole "Install BlueSpice Webservices"
relies on everything below ↓
Conceptual Layer "Infrastructure" This conceptual layer provides Ansible roles to provision a single or multiple machine(s) so that it/they is/are able to host a MediaWiki-centric system. AnsibleRole "Upgrade infrastructure" Web server E.g. Apache Database management system (DBMS) E.g. MariaDB AnsibleRole "Install DBMS" AnsibleRole "Upgrade DBMS" AnsibleRole "Secure DBMS" Server frameworks E.g. Node.js Search engines E.g. Elasticsearch
relies on everything below ↓
Conceptual Layer "Server Operating System Abstraction" This layer is necessary if there is no pertinent Ansible module or plugin available and it is decided not to implement such. E.g. for managing Apache virtual hosts: e.g. virtual host files: Ubuntu: /etc/apache2/sites-available/, CentOS: /etc/httpd/sites-available/. Notice: E.g. where to map an OS-agnostic {{sites-available-directory}} Ansible variable to /etc/apache2/sites-available/ or /etc/httpd/sites-available/ respectively?
relies on everything below ↓
Conceptual Layer "Server Operating System"