Download as PDF, PPTX
Uploaded byEllyssa Kroski
How to Create Your Own Knowledge Base
The document outlines how to create personal and organizational knowledge bases using wikis, detailing their features, types, and examples. It provides best practices for building a knowledge base, including creating a navigation structure, seeding content, establishing policies, and marketing the wiki. Additionally, it emphasizes the importance of gaining team buy-in and offers training methods for effective implementation.
In this document
Powered by AI
Overview of knowledge bases as information repositories for personal and organizational use.
Ideas for personal knowledge bases, including brainstorming, article tracking, and organization.
Discussion of organizational tools like staff intranets and subject guides for structured information sharing.
Introduction to wikis as collaborative tools, highlighting their features and examples like Wikipedia.
Demo and exercise for creating a new wiki, outlining types of software available for this purpose.
Guidelines for creating a structured, user-friendly wiki and encouraging contributions effectively.
Strategies for gaining team buy-in and training for effective wiki usage to ensure engagement.
Information on accessing the presentation materials and additional resources.
More Related Content
Similar to How to Create Your Own Knowledge Base
How to Create Your Own Knowledge Base
- 1. Create Your Own Knowledge Base Ellyssa Kroski
- 2. Knowledge Bases • Repositoriesor hubs where information can be collected, organized, shared, stored, searched and utilized. • Public or private • Personal or organizational
- 3.
- 4. Brainstorming Hub Current Archives
- 5. Article ideas Time Off Tracker LIS course Lesson Plans Most Recent Bio & CV
- 6. Class Reading Lists Library Conference CFP’s Conference Proposals Book Series Plans
- 7. What Else? • Archive past research for articles, courses, etc. • To-Do Lists • Annual Goals Lists • Website Design Notes • Book Ideas • Project Ideas • Grant Ideas
- 8.
- 9.
- 10.
- 11. Trip and EventPlanning
- 12.
- 13.
- 14.
- 15. Forms Policies Collaborative Documents Technical Documentation
- 16. What Else? • Staff Project Pages • Directories • Charters • Planning and Strategy Documents • Meeting Agendas and Notes • Statistics
- 17. Disciplinary or SubjectKnowledge Bases
- 18. Subject Guides orLocal Info
- 19.
- 20.
- 21. Software • Wikis – From the Hawaiian, meaning quick or fast, a wiki is a collaborative online space in which many users can work together on a shared document or webpage. A wiki allows users to create documents and websites quickly and easily, sometimes without even logging in. – Special Features • Allows WYSIWYG interface for authors • User Roles/Permissions • Simultaneous Editing • HTML View • Version Control • Many are Free • No Technical Knowledge Necessary • RSS Feeds
- 22. Wikis • Examples – Wikipedia – OpenCongress – wikiHow – Wookieepedia • Great Tools for: – Team projects – Remote collaboration – FAQs – Course instruction – Encyclopedias – Intranets
- 23. Anatomy of aWiki Add a New Page Edit Page Recent Changes
- 24. Anatomy of aWiki Show All Pages Search Comments
- 25. Anatomy of aWiki Upload Files
- 26. Hands-On • Demo • Practicewiki: http://web20practice.pbworks.com – Username: web20student Password: walrus2cherry • Exercise: – Add a new page and some text
- 27. Start a NewWiki • Types of Wiki Software – PBWorks – Wetpaint – Google Sites – Mediawiki – Microsoft SharePoint – Wiki Comparison Matrix • Demo – Starting New – Settings – User Permissions
- 28. Build a KnowledgeBase • Create a navigational structure - Although it may change with use, create a menu for navigation at the outset to make it easy for your team to start finding their way around. • Seed your wiki - No one wants to be the first to contribute to a blank wiki, seed it with content that others can add to. • Establish a mission statement and usage policy - Give your team a set of loose guidelines as to what you are trying to accomplish with your wiki. It could be as brief as one sentence, but let them know what the purpose of the wiki is so that they can contribute. • Track changes - As the wiki administrator, you will want to keep abreast of what's happening on your wiki so that you can help out, remove spam, etc.
- 29. Build a KnowledgeBase • Utilize permissions levels - Most wikis will enable you to attribute certain rights to specific users, make use of this feature to control access to your wiki. • Create an FAQ - You can save yourself a lot of time and redundant email responses by creating an Frequently Asked Questions page on your wiki. • Create regular backups - You will want to make an effort to backup your data on a regular basis, especially if you are creating a permanent online resource such as a subject guide, etc., most wikis offer this functionality. • Market your wiki – Whether you are creating a public or private resource through a wiki, let people know it's available!
- 30. Training and Buy-In •Gaining Buy-In – Ask for Team Leaders – Give them the ROI – Show them Proof-of-Concept • Training – Live Demo – Technical Documentation – Video Demo – Drop-in Sessions – Help Page(s)
- 31.
- 32. Access this Presentation http://www.slideshare.net/ellyssa ELLYSSA KROSKI http://www.ellyssakroski.com