Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Wikis and knowlege management, Bernhard Krabina, SMWCon Fall 2014, Vienna

Intro to the turorial day of SMWCon. Things to consider when using wikis as knowlege management tool.

Audiolibros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo
  • Sé el primero en comentar

Wikis and knowlege management, Bernhard Krabina, SMWCon Fall 2014, Vienna

  1. 1. Wikis and Knowledge Management October 1st, 2014, SMWCon User Tutorial Bernhard Krabina
  2. 2. Introduction KDZ – Centre for Public Administration Research Open Knowledge – Austrian Chapter Semantic MediaWiki 07. Oktober 2014 · Seite 2
  3. 3. Agenda IT and Knowlege Management Wikis Semantic Wikis Example and conclusion 07. Oktober 2014 · Seite 3
  4. 4. 4 How do we organize?
  5. 5. What tools do we use? Where do we save? Wo will find it?
  6. 6. 6 ? Users need solutions for use cases, but cannot talk IT language are not up to date regarding IT possiblilities IT knows IT solutions, does not understand use cases enough Dilemma in IT projects
  7. 7. Wikis and Web 2.0 – „Wikimania“ wikis became well-known through Wikipedia technologically, nothing groundbraking Hypertext system, usually with database simple user interface, full text search social software everyone can make changes: initial idea of WWW! wisdom of the crowd shared knowledge creation and quality management knowledge creation „on the fly“ no need to pre-define structure links to non-existing pages generate ideas for others Wiki Software: > 100 Wiki engines on Most of them Open-Source: no license cost some like MediaWiki very stable with big community 07. Oktober 2014 · Seite 7
  8. 8. Wikipedia – Wikimedia – Mediawiki Encyclopedia – Operator – Software 07. Oktober 2014 · Seite 8
  9. 9. Wiki Software – 07. Oktober 2014 · Seite 9
  10. 10. Wiki vs. Document Management Documents = DMS Word Excel PowerPoint PDF Approval Electronic Signature, User rights (File system), Sharepoint, Fabasoft, Alfresco… Content = Wiki Content of documents Text with categories Database functions with forms Document upload as an exception 07. Oktober 2014 · Seite 10
  11. 11. Wiki vs. Content Management Control = CMS Access control on different content types (Filesystem), Sharepoint, Drupal, Typo3, Joomla… Transparency = Wiki Everyone can view/edit everything Restrictions on actions (who can view/edit), not on content types (what) Changes visible Easy rollback Advantage: enables cultural change! 07. Oktober 2014 · Seite 11
  12. 12. Get to know MediaWiki Interface and Navigation Categories Discussion pages User pages Namespaces Versioning Search Special Pages Editing (Wiki syntax) 07. Oktober 2014 · Seite 12
  13. 13. 07. Oktober 2014 · Seite 13
  14. 14. Strenghts and Weaknesses of Wikis Wikis are great for text… easy to use, easy to edit full text search Categories to organise pages  Wikis have weaknesses for knowledge management! no data, only text: 995 32 no relations, just links: Tbilisi —> Krakow no querying of data lack of structure leads to manual effort manual edited lists (List of danube bridges, list of Autrian museums by city) 14
  15. 15. 15
  16. 16. 16
  17. 17. 17
  18. 18. Semantic Wiki MediaWiki extension make data in a (Media)Wiki accessible via SemanticWeb technology Open Source no license cost active community many extensions commercial support available 07. Oktober 2014 · Seite 18
  19. 19. 07. Oktober 2014 · Seite 19
  20. 20. Semantic MediaWiki leaves your MediaWiki installation intact no patching, just a (bunch of) MW extension(s) already existing unstructured content can stay as it is or be transformed gives you all the tools you need for a collaborative web database entering data and text representing data and text within the wiki visualise data re-use/export data outside the wiki everything is done through configuration Attributes, Forms, Templates, Filters… are wiki pages 07. Oktober 2014 · Seite 20
  21. 21. Semantic MediaWiki Unstructured Text Strenghts of Wikis Structure via Categories and Namespaces Full Text Search Collaborative editing … Structured Data Web database Online forms Result lists Facetted search Automatically generated pages … 07. Oktober 2014 · Seite 21
  22. 22. Vienna History Wiki 07. Oktober 2014 · Seite 22
  23. 23. 07. Oktober 2014 · Seite 23 „Bennant nach“ = „named after“
  24. 24. {{#ask:…}} query for pages named after „Sigmund Freud“ 07. Oktober 2014 · Seite 24
  25. 25. 07. Oktober 2014 · Seite 25 List all pages of Category:Person with Birthyear::1856 and Sex::male
  26. 26. RDF export = Open Data! 07. Oktober 2014 · Seite 26
  27. 27. > 40 different „result formats“ 07. Oktober 2014 · Seite 27
  28. 28. Application landscape in organizations: Wikis as niche product Documents text documents presentations, spreadsheets, PDFs storage in file system Search: Enterprise Search DMS (Records man.) metadata: Databases desktop databases specialized applications web based databases ... metadata text fields 07. Oktober 2014 · Seite 28 Wikis unstructured text collaborative edition versioning & rollback content management access control complex layouts Websites
  29. 29. Semantic MediaWiki as Knowledge Management System 07. Oktober 2014 · Seite 29 Semantic MediaWiki Semantic Web Datenein- und –ausgabe Eingabeformulare, Ausgabeformate Semantic-Web-Standards
  30. 30. Semantic MediaWiki Use cases Intranet portals Project management and –documentation Internal Knowlege Management Knowledge Portals (external) Web databases Case/Skills Management OpenGLAM/crowdsourcing SemanticWeb projects …. 07. Oktober 2014 · Seite 30
  31. 31. Don underestimate organizational success factors content that users need not to be confused with content that organization whishes for! culture of trust and appreciation everybody can see everything and change everything users can‘t do anything wrong – errors can be undone easily motivation and pressure managers need to be role models and actively support the project no redundant content: turn off alternative sources! obligations to use the wiki quantity and quality of content Initial content is important! no-one feels at home in empty rooms usability und fun design, acces to wiki, (single-sign-on, RSS-feeds, intranet) forms for data input, avoid too much wikitext for regular users 07. Oktober 2014 · Seite 31
  32. 32. Contact 4. Oktober 2012 · Seite 32 Bernhard Krabina   @krabina