User Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:wikis_for_knowledge_management [2018/04/20 13:01]
scott.leslie
public:wikis_for_knowledge_management [2018/08/16 22:06] (current)
Line 2: Line 2:
 ~~SLIDESHOW~~ ~~SLIDESHOW~~
  
-====== Wiki'For Knowledge Management ======+====== Wikis For Better Collaboration and Learning ======
  
 VILSC 2018 \\ VILSC 2018 \\
Line 10: Line 10:
 ===== INTRO ===== ===== INTRO =====
  
-  * Who are you? \\ +  * Who are you? 
- +  * Do you currently wiki? If not - why not? 
-  * Do you currently wiki? If not - why not? \\ +
   * Who am I?   * Who am I?
  
 ===== Some things about the Coop ===== ===== Some things about the Coop =====
  
-  * We're not a library. we have a lot of tech-saavy people on staff.\\ +  * We're not a library.  
- +  * We have a lot of tech-savvy people on staff. 
-  * We do open source as exclusively as possible \\ +  * We do open source as exclusively as possible 
   * We are super cost-aware, don't like to spend when we don't have to \\   * We are super cost-aware, don't like to spend when we don't have to \\
  
Line 31: Line 28:
 ===== Why Wiki? ===== ===== Why Wiki? =====
  
-  * Easy collaborative document editing and creation+  * Easy collaborative document editing and creation but... 
 +  * Works [[https://wiki.libraries.coop/doku.php?id=cooperative:users:sleslie:start|just as well for the individual]] 
 +  * "[[https://www.slideshare.net/mcannonbrookes/organisational-wiki-adoption/10-Simple_contextual_content_More_archival|More archival than email, less process that Word]]"
   * Easy search and browse   * Easy search and browse
   * Improve transparency and help reduce silos   * Improve transparency and help reduce silos
-  * Anticipate knowledge growth even before it happens +  * Anticipate knowledge growth even before it happens 
 +  * For changeable info, likely the best approach (cf https://pdfs.semanticscholar.org/e138/f96aedcb18893a87bd22d95d3914db4d22ae.pdf) 
  
 ===== Why DOKUWIKI? ===== ===== Why DOKUWIKI? =====
Line 44: Line 44:
  
 ===== Why DOKUWIKI? Part II ===== ===== Why DOKUWIKI? Part II =====
-  * Access control - can control both visibility and editabling; can include public sections +  * Access control - can control both visibility and edit-ablity; can include public sections (such as this page!) 
-  * Re-skinning; the nav bars are actually wiki pages! +  * Re-skinning; the nav bars are actually wiki pages! https://wiki.libraries.coop/doku.php?id=sidebar 
-  * Easily embed other content [[https://wiki.libraries.coop/doku.php?id=cooperative:coop_calendars|calendars]] [[https://wiki.libraries.coop/doku.php?id=cooperative:users:sleslie:start|list of google docs in a folder]] +  * Easily embed other content  
-  * Can host structured data and offer ways to export it?+     [[https://wiki.libraries.coop/doku.php?id=cooperative:coop_calendars|calendars]] 
 +     *  [[https://wiki.libraries.coop/doku.php?id=cooperative:users:sleslie:start|list of google docs in a folder]] 
 +  * Can host structured data and offer alternative ways to use it? https://www.dokuwiki.org/plugin:data:list_of_employees
  
  
Line 53: Line 55:
 ===== How we made it work ===== ===== How we made it work =====
  
-  * If you have even a few people using it - don't kill it, build on it! +  * If you already have one, with even a few people using it - don't kill it, build on it! 
-  * Redesigninfo architecture +  * Redesign can help + "a bit" of info architecture 
-  * Gardening! together and separately+  * Wiki Gardening! together and separately 
 +  * Focus on "collaboration" not "publishing", folksonomy (+search) not taxonomy 
 +  * If a good exchange has happened elsewhere (IRC, email) suggest a wiki entry as a result 
 +  * Keep it as open as possible - we have public/private distinction, but after that try not to create too many internal groups
  
  
Line 63: Line 68:
   * Very small groups/locations - a binder may make a ton more sense   * Very small groups/locations - a binder may make a ton more sense
   * Non-volatile information - may not be the best way to handle official policy docs you don't want edited   * Non-volatile information - may not be the best way to handle official policy docs you don't want edited
 +
 +===== Thanks! Questions? =====
 +
 +  * slides at http://bit.ly/vislc2018-wikis
 +  * scott.leslie@bc.libraries.coop / @sleslie on twitter
public/wikis_for_knowledge_management.1524254490.txt.gz · Last modified: 2018/04/20 13:01 by scott.leslie