BusinessService "Run your organizational Find-And-Learn network!"
Story[edit | edit source]
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.
- It is based on dataspectsSystemCoreOntology and implements a distinct set of knowledge management concepts (see below).
- It integrates optimally with Component0406283300 providing a single "Google-style" interface to your knowledge (see https://dataspects.com for the current development version).
- It allows for mentally traveling through a web of subject affinities starting with an intuitive and spontaneous statement.
- 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.
- It is deployed by Component1127210567.
Distinct set of knowledge management concepts[edit | edit source]
- The Concept "Every Page is Page One Topics" 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.
- …are of a Single Type and can assume Multiple Roles.
- …is based on Knowledge Topics/Subjects/Bites, which…
- Annotations can be reified in order to annotate annotations.
Slogans[edit | edit source]
- 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[edit | edit source]
Using the system must be:
- clear by intuition/GUI
- clear by mouseover message/hint
- clear by documentation at mouseclick on link/button to popup or toggled div
- clear by documentation at mouseclick on link/button to information in new window
- clear by calling/mailing to a supporting party
Costs in terms of transactional brain cycles and time units used/wasted increase logarithmically.
Conceptual Layers[edit | edit source]
- Write the code you wish you had.
- Good architecture maximizes the number of decisions not made.
Conceptual Layer "Assertional Ontologies"[edit | edit source] |
Conceptual Layer "Tools"[edit | edit source]
| |||
Conceptual Layer "Terminological Ontologies"[edit | edit source] | ||||
Conceptual Layer "Extensions"[edit | edit source]
| ||||
relies on everything below ↓ | ||||
Conceptual Layer "MediaWiki"[edit | edit source]
| ||||
relies on everything below ↓ | ||||
Conceptual Layer "Web services"[edit | edit source]
| ||||
relies on everything below ↓ | ||||
Conceptual Layer "Infrastructure"[edit | edit source]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.
| ||||
relies on everything below ↓ | ||||
Conceptual Layer "Server Operating System Abstraction"[edit | edit source]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: E.g. where to map an OS-agnostic {{sites-available-directory}} Ansible variable to | ||||
relies on everything below ↓ | ||||
Conceptual Layer "Server Operating System"[edit | edit source] |