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

From Dataspects
Jump to: navigation, 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.

Concerns[edit | edit source]

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

Responsibilities[edit | edit source]

Add new

Roles[edit | edit source]

Add new

Use Cases[edit | edit source]

Add new

Recipes[edit | edit source]

Add new

Tools[edit | edit source]

Add new

Methodologies[edit | edit source]

Add new

Aspects[edit | edit source]

Cooperation[edit | edit source]

Promotion[edit | edit source]

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

Curation[edit | edit source]

Maintain knowledge structured, coherent, consistent, manageable and accessible

Viewing[edit | edit source]

Optimize pertinent facets findable through search

Editing[edit | edit source]

Facilitate editing knowledge content and its affinities

Configuration / Maintenance[edit | edit source]

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

Extensions[edit | edit source]

Add features and interfaces

Integration[edit | edit source]

Make use of external and provide internal data and functionality

Installation[edit | edit source]

Deploy a MediaWiki-centric Knowledge Management system

Development[edit | edit source]

Develop all aspects of a MediaWiki-centric Knowledge Management system

Use cases by role[edit | edit source]

Role "Community Member"[edit | edit source]

Role "Hoster"[edit | edit source]

Role "Knowledge Management Consultant"[edit | edit source]

Role "MediaWiki Sales"[edit | edit source]

Role "Academic Stakeholders"[edit | edit source]

Role "Customers"[edit | edit source]

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

Role "Patron"[edit | edit source]

= "decision maker"

Role "Reader"[edit | edit source]

Role "Contributor/Editor"[edit | edit source]

= 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"[edit | edit source]

  • 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"[edit | edit source]

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

Role "User Interface Designer/User Experience Designer"[edit | edit source]

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

Role "Administrator"[edit | edit source]

Role "OntologyEngineer"[edit | edit source]

  • 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"[edit | edit source]

  • 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"[edit | edit source]

  • 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"[edit | edit source]

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"