Dashboard "Enterprise Knowledge Management Aspects (Concerns, Responsibilities, Roles, Use Cases and Tools/Methodologies)"

From dataspects::Wiki
Jump to navigation Jump to search
This article explains all aspects (roles, responsibilities, use cases and tools/methodologies) that keep your enterprise knowledge management healthy, effective and efficient.
EntityType "Dashboard"


See below…

See Ontology "EnterpriseKnowledgeManagementOntology" for visualizations and explanations.


Concern Talks/Tutorials/CreateCamps/Workshops addressing this concern
Organize a knowledge management conference


Add new


Add new

Use Cases

Add new


Add new


Add new


Add new




Make management decide for MediaWiki-centric Knowledge Management
Make all roles enjoy using MediaWiki-centric Knowledge Management


Maintain knowledge structured, coherent, consistent, manageable and accessible


Optimize pertinent facets findable through search


Facilitate editing knowledge content and its affinities

Configuration / Maintenance

Upgrade, tune, optimize and secure a MediaWiki-centric Knowledge Management system


Add features and interfaces


Make use of external and provide internal data and functionality


Deploy a MediaWiki-centric Knowledge Management system


Develop all aspects of a MediaWiki-centric Knowledge Management system

Use cases by role

Role "Community Member"

Role "Hoster"

Role "Knowledge Management Consultant"

Role "MediaWiki Sales"

Role "Academic Stakeholders"

Role "Customers"

  • Why did you decide for MediaWiki?
  • Which software solutions did you consider?

Role "Patron"

= "decision maker"

Role "Reader"

Role "Contributor/Editor"

= contributing with content to the wiki & editor = person who is editing the wiki/putting content into the wiki

  • edits, adds text
  • fills in a form
  • adds basic formatting
  • uses Visual Editor to edit text

Role "PowerUser"

  • all of editor/contributor
  • sorts pages into categories
  • moves and deletes pages
  • does gardening activities
  • demands new functionalities

  • All of the above +
  • Use Case "Add/edit regular subject affinities"
  • Use Case "Add/edit complex facet views" (lua/compound #ask: using templated result formats)
  • Use Case "Train end users"

Role "Ontology Designer"

  • creates templates, properties, forms, queries
  • organises the ontology
    • e.g. groups ontology components in logical ways (example)

Role "User Interface Designer/User Experience Designer"

  • designs the wiki, configures the user interface
  • designs search interface

Role "Administrator"

Role "OntologyEngineer"

  • technically improves the ontology of the ontology designer
  • automates certain ontology processes
  • groups and structures the ontology
  • works not only with wikitext, but also with GitHub, RDF, XML etc. – other formats and platforms

  • Use Case "Upgrade dataspects Knowledge Management Framework (DSKMF)"
  • Use Case "Manage DSKMF customization part" using Component 759410

Role "SearchEngineer"

  • Use Case "Manage resource silos indexing (entitizing and feature extraction and synthesis)"
  • Use Case "Manage resource silos index update policies"
  • Use Case "Manage search result facet views"
  • Use Case "Integrate resource silos, interfaces"

One of a SearchEngineer's main tasks is to customize a search engine.

Role "Curator"

  • Use Case "Consolidate, curate, clean content and manage coherence" using Component 759410 (example: Component 600319)
  • Use Case "Manage, monitor and interpret quality metrics" (What are they?)

Role "Developer"

An important general task for developers is to create DSLs that facilitate other roles' tasks at the right abstraction level balancing the needs for flat learning rates, flexibility and reuse.

  • Use Case "Develop dataspects tools"