Wikis and Blogs: When, Why, and How to Use Them

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Wikis and Blogs: When, Why, and How to Use Them - Presentation Transcript

    1. Wikis and Blogs: When, Why, and How to Use Them Leslie O’Flahavan, E-WRITE Administrative Office of the US Courts Washington, DC September 4, 2008
    2. Presentation overview
      • What wikis and blogs are and how they work
      • Why wikis and blogs are such a popular way to publish content online
      • How a wiki or blog could help your agency
      • How to manage some of the liabilities of wikis and blogs
      • A little bit about social networking…if time allows
    3. Presentation schedule
      • Start and 9 a.m. EST
      • End at 1 p.m.
      • Have a 15-minute break at about 11 a.m.
      • Participate in activities throughout
    4. Part 1: Not all wikis are encyclopedias
    5. What is a wiki?
      • “ A wiki’s just like a web site, only you can edit it.”
    6. What is a wiki?
      • From Wikipedia, the free encyclopedia
      • “ A wiki is a website that allows visitors to add, remove, edit and change content, typically without the need for registration. It also allows for linking among any number of pages. This ease of interaction and operation makes a wiki an effective tool for mass collaborative authoring . The term wiki can also refer to the collaborative software itself ( wiki engine ) that facilitates the operation of such a site, or to certain specific wiki sites, including the computer science site (the original wiki) WikiWikiWeb and online encyclopedias such as Wikipedia .”
    7. Wikipedia: the most familiar wiki example
    8. Wikipedia Main Page
    9. Wikipedia: C&O Canal page
    10. C&O Canal Discussion page
    11. C&O Canal Discussion page
    12. C&O Canal Editing page
    13. C&O Canal Revision History page
    14. Common Craft: “Wikis in Plain English”
    15. Discuss: How might a wiki solve your department’s own e-mail-related communication problem?
    16. How do a wiki and web site differ?
    17. National Park Service’s C&O Canal site
    18. C&O Canal Association’s site
    19. What kinds of wikis does this presentation cover?
      • Federal, state, local
      • Project or task wikis:
        • Project Communication
        • Application Support
        • Research
        • Product Planning
        • Customer Service
    20. Some wiki samples …
    21. Shrink and Grow: “This wiki acts as a design doc for the game…”
    22. RocWiki.org – the People’s Guide to Rochester
    23. wikiHow: “The How-to Manual Anyone Can Write Or Edit”
    24. FLICC/Fedlink Environmental Scan wiki
    25. NCI caBIG
    26. National Alliance for Medical Image Computing wiki
    27. US Court of Appeals – Seventh Circuit
    28. Article on 7 th Circuit’s wiki
    29. Argonne National Lab’s SEED Project Wiki
    30. The AAA Wiki …
      • “ Welcome to the AAA Wiki - created to coordinate the Assembly, Alignment and Annotation of the now 12 sequenced Drosophila genomes.”
    31. Goochland County Public Schools
    32. MassGIS Geospatial Web Services project wiki
    33. “… caGrid provides the core enabling infrastructure necessary to compose the Grid of caBIG™”
    34. Intellipedia
    35. The “hall of mirrors” wiki: a presentation by Janel Brennan-Tillmann, UMD Coord. of Foreign Lang. Instructional Technology
    36. Is it a wiki or a web page?
    37. Why are wikis so popular?
      • Anyone can write or edit
      • Outside the normal permissions and approval process for web content
      • Encourage interaction
      • Easy to learn
      • User-defined life span
    38. Wikis vs. Web sites
      • Require permission to publish
      • Mediated by experts
      • Transactional
      • Governed by workflow or publishing cycle
      • Graphic design conveys content organization to user
      • Staffed by professionals with a range of skills: designers, developers, content types
      • Judged by outcomes
      • Relevant
      • Useful
      • Correct
      • Alive
      • Updated regularly
      • Read
      • Authored collaboratively
      • Little to no graphic design
      • Foster dialogue or conversation
      • Socially mediated
      • Content author in charge of content over time
      Web Sites Shared Traits Wikis
    39. Edit-before-publish vs. Edit-after-publish
      • “ Something that’s 80% accurate, on time, and shareable is better than something that is too much, perfectly formatted, too late, and over-classified.”
      • Chris Rasmussen, Knowledge Management Officer, Intellipedia, National Geospatial-Intelligence Agency, Department of Defense
    40. Discuss
      • What are the risks involved in launching a wiki for your department or court?
      • What kinds of policies or guidelines would you need to have in place to offset the risks?
    41. Why do you need wiki writing guidelines?
      • Organic growth of content can cause many communication problems
      • Producing valuable content of any type requires reviewing and editing
      • Wiki users search vs. navigate , thus putting extra pressure on words
    42. What should the wiki writing guidelines cover?
      • How to organize content
      • How to make content easy to read
      • How to write as a wiki citizen
    43. Guidelines on writing to organize
      • How to name pages
        • Use concrete descriptive words; use the most commonly searched terms: not ID but Social Security Number or Passport
        • Strive for names you can use in a sentence: not hips – replacement surgery but hip replacement surgery
        • Provide guidance on caps, numbers, special characters
        • Give a name that will last over time: not Proposal – Final Version
        • Avoid beginning with articles: not The Interagency Agreements Team
        • Develop naming guidelines for different types of pages/articles
      • How (or whether) to group pages
    44. Clear naming at Library Success: A Best Practices Wiki
    45. HRE Wiki: Naming Problem
      • HREwiki
      • Home
      • Ready-to-use resources
      • Resources in development
      • Images
      • New topics
      • Projects
      • Useful websites http://hrewiki.pbwiki.com/
      • Featured resources
      • the Univeral Declaration of Human Rights
      • Nepal
      • death Penalty - teaching materials
      • Discrimination
      • Voices of people affected by human rights abuses
      • Ideas for HRE
      • Using this wiki
      • Request a password
      • Writing for this wiki
      • Developing this wiki
      • 'How to'
      • Reporting problems
      • Reproducing content
      • Terms of Use
      • Disclaimer
      • About
    46. Debian wiki: organized by user
    47. Guidelines on writing readable wiki content
      • Headings
      • Vertical lists
      • Links (no click here )
      • Conciseness
      • Tone
      • Mechanical correctness
        • Spelling
        • Punctuation
        • Grammar
        • Abbreviations
        • Dates
    48. Wiki wall of words …
    49. Bulleted wiki article: Easy to scan or read?
    50. Developing a wiki that contains few content types requires explicit writing guidance.
    51. PolicyOptions Wiki: Lots of guidance about writing issue briefs
    52. Guidelines on writing as a wiki citizen
      • Use your real name
      • Write objectively (?)
      • Comment considerately
      • Contribute original content
      • Avoid slang
      • Explain edits in “Comments” section
    53. Wiki software options
      • MediaWiki – www.mediawiki.org
      • Tikiwiki - www.tikiwiki.org
      • PBwiki - http://pbwiki.com/
      • Wikipedia’s article “Comparison of wiki software” at http://en.wikipedia.org/wiki/Comparison_of_wiki_software
    54. Wiki writing guidelines
      • ColabWiki: Wiki Style Guide
      • IBM’s Redwiki Writing Guidelines and Etiquette
      • wikiHow’s Writer’s Guide
      • BattleMaster wiki Style Guide
      • LinuxQuestions.org’s LQWiki:Manual of Style
      • MuppetWiki Building a successful wiki community
    55. Wiki resources
      • NIH Wiki Fair – February 28, 2007
      • Wiki Home Page at COLAB , the collaborative work environment: “Hosted by GSA Intergovernmental Solutions”
      • “Which Wiki is Right for You?” in School Library Journal , May 1, 2007
    56. Part 2: Blogs
    57. What is a blog?
      • “ A weblog, which is usually shortened to blog, is a website where regular entries are made (such as in a journal or diary) and presented in reverse chronological order. Blogs often offer commentary or news on a particular subject, such as technology, politics, or local news… A…blog combines text, images, and links to other blogs, web pages, and other media related to its topic.
    58. How is a blog different from a website?
      • Easy
        • to set up
        • to update
        • to organize and archive
      • Interactive
      • Personal—Individual POV, not agency
    59. How do blogs work?
      • How do you publish a blog?
      • How do you read a blog?
    60. How do you publish a blog?
      • Use off-the-shelf, user-friendly software (blogware) to
        • Create new blog posts
        • Organize, archive and retrieve information from old posts
        • Create links from your posts
        • Enable other bloggers to link back to a specific post on your blog (Permalinks)
        • Let bloggers see who has viewed their posts and commented (TrackBack)
    61. How do you read a blog?
      • Subscribe to a blog with
      • RSS (Really Simple Syndication) feed
      • Portal or browser based aggregators (GoogleReader)
      • Web based aggregators (Bloglines, FeedReader)
      • E-mail updates
    62. Subscribe with RSS
    63. Use a blog aggregator
    64. Get blog posts by e-mail
    65. Who blogs?
      • “In April 2007, blog search and measurement firm Technorati was tracking over 70 million blogs and reported seeing about 120,000 new blogs created each day. That's 1.4 blogs every second.” (webcontent.gov)
    66. Who blogs in the Federal government?
    67. Why do Federal agencies blog?
      • Communicate with the public
      • Communicate internally
      • Blogging “puts a human face on government [and] makes government more open.”
      • --Bev Godwin, USA.gov
      • Humanize your agency
      • Create a dialogue
      • Get feedback
      • Keep public updated
      • Improve visibility—search engine placement
      A new way to communicate with the public
      • Share information
      • Create community agency-wide, nationwide or worldwide
      A new way to communicate within the agency
    68. Before starting a blog, consider
      • What’s your purpose?
      • Who will write the blog?
      • Will you allow comments?
      • What’s your approval process?
      • What legal issues should you address?
    69. Disseminate Information: DC Public Safety Blog
    70. Support a project: The Big Read
    71. Add Value: Eye Level
    72. Customer interaction: TSA’s Evolution of Security
    73. A 6-week special event blog: EPA
    74. Personal Experience: Volunteer Journals
    75. Discuss: How could a blog help your organization improve communication?
    76. Who will write the blog?
      • “They’ve got to be authentic. You must be the author of your post—not your staff, not your secretary or administrative staff, and certainly not your campaign manager or consultant.”
      • -- Christopher Barger, IBM blogging consultant
    77. Director, Corps of Engineers
    78. Director, CBO
    79. A team of employees
    80. Front-line employees
    81. Will you allow comments?
      • Most federal agencies allow comments
      • Will you moderate or edit the comments?
        • Edit for grammar
        • Edit for content
        • Limit comments to specific issues
      • What will you do with the comments—feedback?
    82. Will you allow comments?
      • Without comments, a blog is “just a glorified press release.”
      • -- Mike Cornfield, professor, George Washington University
    83. No Comments
    84. Enabling comments
    85. The Corps-e-spondence comments policy
    86. Evolution of Security comments policy
    87. How will you use comments?
      • Change policies or programs
      • Get customer feedback
      • Incorporate comments into your posts
    88. Incorporate comments: Corps-e-spondence
    89. The blog approval process?
      • Outside formal clearance process
      • Posts will need to be reviewed before they’re published
      • Blogger + blog’s purpose + blog publication schedule
    90. Legal issues
      • Confidentiality
        • Does your organization have confidentially guidelines for other types of communication?
      • Children’s Online Privacy Protection Act (COPPA)
      • Copyright
    91. Establish and publish blog policies
      • Incorporate your decisions on into a written blog policy
      • Purpose
      • Writers/contributors
      • Comments policy
      • Approvals process
      • Legal Issues
    92. Publish your blog policies: GSA GovGab
    93. Resources
      • Blogs from the U.S. Government http://www.usa.gov/Topics/Reference_Shelf/News/blog.shtml
      • Blogs in Government , Bev Godwin, July, 2006 http://www.usa.gov/webcontent/documents/Blogs_in_Government_June_2006.pdf
      • Webcontent.gov http://www.usa.gov/webcontent/technology/blogs.shtml
    94. Managing the liabilities of wikis and blogs
      • Before publishing, identify the purpose of your wiki or blog and measure the risk against that purpose
      • Remember that wikis and blogs are publishing tools; we CAN manage publishing
      • Develop guidelines for publishers/contributors and for users/readers
      • Limit access
      • Learn from those who have gone before you!
    95. Blog Scenario #1
      • Your agency director wants each division head to write an internal blog.
      • The director wants to review each blog post by each division head before it’s posted.
      • “We speak with one voice and that voice is the voice of the director.”
    96. Blog Scenario #2
      • Due to changes in legislation, a post from March 2008 contains incorrect information.
    97. Wiki scenario #1
      • You launch a wiki, tell the team about it, set up passwords for all contributors, and post information on the wiki yourself.
      • No one else contributes content or refers to the wiki.
    98. Wiki scenario #2
      • Your wiki is growing rapidly and some of the content is of “first draft” quality.
    99. Wiki scenario #3:
      • “Joe” writes an e-mail to “Sue.” His e-mail includes a well-written explanation of a complex process.
      • Sue likes the e-mail so well that she publishes it to the department’s wiki without asking Joe’s permission.
    100. Social Networking: Sharing, Rating, Connecting
    101. Sharing: YouTube
    102. Sharing: Slideshare
    103. Rating or social bookmarking
    104. Rating: Digg
    105. Rating: StumbleUpon
    106. Connecting: LinkedIn
    107. LinkedIn: US Courts
    108. Connecting: Facebook
    109. Connecting: Ning
    110. Connecting: Twitter
    111. Questions or comments?
      • Clare De Cleene
      • Web Communications Manager
      • Administrative Office of the U.S. Courts
      • [email_address]
      • 202-502-1182 (Direct Line)
      • 202-502-2615 (Web Help Desk)
      • Leslie O’Flahavan
      • E-WRITE
      • [email_address]
      • 301-989-9583

    + LeslieOflahavanLeslieOflahavan, 2 years ago

    custom

    475 views, 0 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 475
      • 475 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 3
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories