System "KIM/SMW Academy Syllabus"

From SMW CindyKate - Main
Jump to: navigation, search
SMW CindyKate Main

Facet type System

Show facet/graph

System "KIM/SMW Academy Syllabus" is constituted by properties... ...having values
Is accomplished by Any value(s)
Is addressed by Any value(s)
Is based on Any value(s)
Is grouped in Any value(s)
Is making use of Any value(s)

Facet ID: Component 200001
End Points:
    Script Path:
    Ask Query Sets:
        - Query: "[[Property constitutes::Component 200001]]" #Aspect "KIM/SMW Academy Syllabus"
          Dummy: dummy
  Type: Graph
    Rankdir: TD

KIM Goals

Check out typical challenges met by KIM.
Goal "Minimize transaction thoughts in order to maximize production thoughts"
Goal "Shorten the time it takes for your new employees to get productive"
achieved, accomplished by

KIM Use Cases: Questions, Problems and Tasks handled by KIM

Check out typical challenges met by KIM.
addressed, solved, handled and met by

KIMPractice Patterns

These patterns explain practices and policies proven successful for KIM.
Practice Pattern/Workflow "Keywording"
Practice Pattern/Workflow "Label use case entry points across the entire knowledge base"
Practice Pattern/Workflow "Let factorization and structure emerge from tentatively generally tagged information"
based on

KIM Organization Patterns

These patterns explain organizational setups proven successful for KIM.
Organization Pattern "How your employees cooperate with your IT/computers/data"
Organization Pattern "Interfacing"
Organization Pattern "Three-Ontologies-Method"
Organization Pattern "Three-Structure-Grades-Method"
Organization Pattern "Usecasing"
... further results
enabled by

SMW Special Use Cases

These use cases explain actions specific to SMW.

based on

SMW Design Patterns

These patterns explain how to structure, design and configure SMW features and ontology objects for enabling specific applications.
SMW Design Pattern "Add a statement"
SMW Design Pattern "Allow for component types to have multiple synonymous titles"
SMW Design Pattern "Component title prefix"
SMW Design Pattern "Disambiguation by keywording"
SMW Design Pattern "Display elements based on template field values"
... further results
identified by


Guidelines help you to identify optimal practice, organization and design patterns for fulfilling your use cases.
making use of

SMW Concepts/Features


Illustration "Add something new to the knowledge base flowchart"
SMW Concept 349796.png
Component 571935.png
Component 571936.png
Component 664799.png
... further results


SMW Feature "Approved Revs"
SMW Feature "BlueSpice Assign Responsible Editors"
SMW Feature "BlueSpice ExtendedSearch (Lucene/Solr)"
SMW Feature "BlueSpice Notifications"
SMW Feature "BlueSpice Permission Management"
... further results

SMW Ontology Components

SMW Objects encompasses all pages that are necessary to enable a certain functionality (app) on a SMW: categories, templates, properties, concepts, forms, queries and special content pages, as well as namespaces.
Ontology Component "CTDI:Component Type Instantiation Form Blueprint"
Ontology Component "CTDI:Component Type Instantiation Template Blueprint"
Ontology Component "CTDI:Form:Add Component"
Ontology Component "CTDI:Form:Component Type"
Ontology Component "CTDI:Template:Component Type"
... further results
grouped in

Ontologies/Semantic Models

These are collections of SMW objects like namespaces, categories, templates, properties, concepts, widgets and forms, e.g. the Ontology "Keywording (KWDG)".

They can be injected into an SMW using smw-cindykate content inject.

Ontologies/Semantic Models List
Ontology "IT System Documentation (ITSD)"
Ontology "Keywording (KWDG)"
Ontology "SMW Component Types in Domains Infrastructure (CTDI)"
Ontology "SMW Galaxy (SMWG)"
Ontology "Usecasing (USCG)"
grouped in

SMW Apps

SMW Apps encompass
  • SMW Features (OS- and SMW-level modules and extensions) and
  • Ontologies.

Knowledge/Information Management (KIM) Principles

Just as lift and thrust are two fundamental principles of flying, learn about and appreciate fundamental theoretical and practical principles of knowledge and information management.
KIM Principle "A documentation IS not a document"
KIM Principle "A place for everything and everything in its place."
KIM Principle "Allow for Request&Suggest Functional Faceting"
KIM Principle "Approach challenges pragmatically (ACP)"
KIM Principle "Be informed what others do (BOD)"
... further results