User Tools

Site Tools


webteam:webplan:2011:section6_recommendations

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
webteam:webplan:2011:section6_recommendations [2011/09/07 18:18]
jimcraner added knowledge management notes to section F
webteam:webplan:2011:section6_recommendations [2011/09/07 18:19] (current)
jimcraner [F. Implement a knowledge base to easily store highly-relevant and frequently-accessed Evergreen technical information]
Line 128: Line 128:
 http://​evergreen-ils.org/​dokuwiki/​doku.php?​id=feature_list http://​evergreen-ils.org/​dokuwiki/​doku.php?​id=feature_list
  
-==== F. Implement a knowledge base to easily store highly-relevant and frequently-accessed Evergreen technical information ====+==== F. Implement a searchable and browsable ​knowledge base to easily store highly-relevant and frequently-accessed Evergreen technical information ====
  
 This knowledge base could be as complex as a dedicated knowledge management application or as simple as a dedicated set of wiki pages kept up-to-date and highlighted for website visitors. This knowledge base could be as complex as a dedicated knowledge management application or as simple as a dedicated set of wiki pages kept up-to-date and highlighted for website visitors.
Line 136: Line 136:
 These three areas - docs, wiki, and mailing list - can ideally be used as three different “tiers” or “phases” of collaboration and community knowledge management. For instance, a discussion about a particular problem or feature may take place on the mailing list, where it appears in the archives. Information that is deemed especially valuable in the mailing list archives might be moved by an enthusiastic website contributor into the unofficial documentation stored on the wiki. Documentation Interest Group members may then regularly review popular wiki pages to determine if they are suitable for inclusion in the “official” documentation where they would most likely be accessed by the largest number of potential users. These three areas - docs, wiki, and mailing list - can ideally be used as three different “tiers” or “phases” of collaboration and community knowledge management. For instance, a discussion about a particular problem or feature may take place on the mailing list, where it appears in the archives. Information that is deemed especially valuable in the mailing list archives might be moved by an enthusiastic website contributor into the unofficial documentation stored on the wiki. Documentation Interest Group members may then regularly review popular wiki pages to determine if they are suitable for inclusion in the “official” documentation where they would most likely be accessed by the largest number of potential users.
  
-This is a type of knowledge management is a form of curation, by which people in different roles or contexts manually move knowledge from a limited discussion context into a context accessible to all on the website. However, website visitors increasingly rely on search, especially for finding specific information within a broad topic such as Evergreen. ​ Therefore, ​is critical that all identified information sources are incorporated into a search corpus and that end-user search tools on the site are able to return useful results to user queries. ​ In addition, the website should be structured in a way that optimizes automated indexing by third parties such as Google. This will help ensure that the site is ranked as a valuable resource for those searching with off-site tools.+This is a type of knowledge management is a form of curation, by which people in different roles or contexts manually move knowledge from a limited discussion context into a context accessible to all on the website. However, website visitors increasingly rely on search, especially for finding specific information within a broad topic such as Evergreen. ​ Therefore, ​it is critical that all identified information sources are incorporated into a search corpus and that end-user search tools on the site are able to return useful results to user queries. ​ In addition, the website should be structured in a way that optimizes automated indexing by third parties such as Google. This will help ensure that the site is ranked as a valuable resource for those searching with off-site tools.
  
 ==== G. Implement a support forum as an alternative to the mailing list and IRC for user-to-user support ==== ==== G. Implement a support forum as an alternative to the mailing list and IRC for user-to-user support ====
webteam/webplan/2011/section6_recommendations.1315433908.txt.gz · Last modified: 2011/09/07 18:18 by jimcraner

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.