<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" 	>
<channel>
	<title>Comments on: Draft Blog Guidelines</title>
	<atom:link href="http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/</link>
	<description>K.G. Schneider's blog on librarianship, writing, and everything else</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:59:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Craig Hayward</title>
		<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/comment-page-1/#comment-3137</link>
		<dc:creator>Craig Hayward</dc:creator>
		<pubDate>Fri, 05 Jan 2007 20:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2006/12/30/draft-blog-guidelines/#comment-3137</guid>
		<description>Well done. It is very refreshing to read some guidelines that cover new types of policies for a new age. In the Web 2.0 and Library 2.0 world we need to think about all things tied to a concept. The technology is great and very important for reaching our audience, but often we miss the important big picture details and get lost in wow factor of the tool. Thanks for sharing, Craig.
</description>
		<content:encoded><![CDATA[<p>Well done. It is very refreshing to read some guidelines that cover new types of policies for a new age. In the Web 2.0 and Library 2.0 world we need to think about all things tied to a concept. The technology is great and very important for reaching our audience, but often we miss the important big picture details and get lost in wow factor of the tool. Thanks for sharing, Craig.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kgs</title>
		<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/comment-page-1/#comment-3136</link>
		<dc:creator>kgs</dc:creator>
		<pubDate>Thu, 04 Jan 2007 02:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2006/12/30/draft-blog-guidelines/#comment-3136</guid>
		<description>Alane, I like your points. Walt, chewing over your input. (Long day. Brain tired. Needs rest. :&gt; )</description>
		<content:encoded><![CDATA[<p>Alane, I like your points. Walt, chewing over your input. (Long day. Brain tired. Needs rest. :> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny Levine</title>
		<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/comment-page-1/#comment-3135</link>
		<dc:creator>Jenny Levine</dc:creator>
		<pubDate>Wed, 03 Jan 2007 16:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2006/12/30/draft-blog-guidelines/#comment-3135</guid>
		<description>Perfect timing, as I will be writing a best practices document for ALA staff bloggers. Thank you!</description>
		<content:encoded><![CDATA[<p>Perfect timing, as I will be writing a best practices document for ALA staff bloggers. Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walter Underwood</title>
		<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/comment-page-1/#comment-3134</link>
		<dc:creator>Walter Underwood</dc:creator>
		<pubDate>Wed, 03 Jan 2007 01:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2006/12/30/draft-blog-guidelines/#comment-3134</guid>
		<description>I would clearly separate the rules and the advice. Also, think about what it means to break one of the rules. Does the university do something if a blog doesn&#039;t check facts? If it isn&#039;t updated frequently? If a posting is a personal attack on someone else? If an employee&#039;s performance evaluation is posted? Some of these rules may be different for tenured faculty and for staff, some will get you fired, and some don&#039;t matter.

In the &lt;a href=&quot;http://www-03.ibm.com/developerworks/blogs/page/jasnell?entry=blogging_ibm&quot; rel=&quot;nofollow&quot;&gt;IBM blogging guidelines&lt;/a&gt;, the first rule is to follow the existing IBM Business Conduct Guidelines. There is some additional info around that, but the blogging guidelines do not simplify or even restate the general business conduct guidelines. That is a good idea.

It doesn&#039;t work to have separate rules for blogging, so you need to reference existing organizational guidelines whereever they apply. If those don&#039;t work for blogging, they need fixed.

The advice is good, by the way. I might separate the &quot;found content&quot; bit into a separate item, noting that information needs to be useful but it doesn&#039;t need to be original.

You might spend some time thinking of valid blogs that violate one of the rules. The art department is a good place to start. What about a photograph that already has a different copyright and can&#039;t use creative commons? Does that mean they can&#039;t publicize their gallery with university blog?</description>
		<content:encoded><![CDATA[<p>I would clearly separate the rules and the advice. Also, think about what it means to break one of the rules. Does the university do something if a blog doesn&#8217;t check facts? If it isn&#8217;t updated frequently? If a posting is a personal attack on someone else? If an employee&#8217;s performance evaluation is posted? Some of these rules may be different for tenured faculty and for staff, some will get you fired, and some don&#8217;t matter.</p>
<p>In the <a href="http://www-03.ibm.com/developerworks/blogs/page/jasnell?entry=blogging_ibm" rel="nofollow">IBM blogging guidelines</a>, the first rule is to follow the existing IBM Business Conduct Guidelines. There is some additional info around that, but the blogging guidelines do not simplify or even restate the general business conduct guidelines. That is a good idea.</p>
<p>It doesn&#8217;t work to have separate rules for blogging, so you need to reference existing organizational guidelines whereever they apply. If those don&#8217;t work for blogging, they need fixed.</p>
<p>The advice is good, by the way. I might separate the &#8220;found content&#8221; bit into a separate item, noting that information needs to be useful but it doesn&#8217;t need to be original.</p>
<p>You might spend some time thinking of valid blogs that violate one of the rules. The art department is a good place to start. What about a photograph that already has a different copyright and can&#8217;t use creative commons? Does that mean they can&#8217;t publicize their gallery with university blog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alane</title>
		<link>http://freerangelibrarian.com/2006/12/30/draft-blog-guidelines/comment-page-1/#comment-3133</link>
		<dc:creator>Alane</dc:creator>
		<pubDate>Tue, 02 Jan 2007 20:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2006/12/30/draft-blog-guidelines/#comment-3133</guid>
		<description>Existing organizational communication guidelines may be sufficient as long as it&#039;s clear blogging is included in the types of communications covered. There are, we think, some things that are sufficiently different about blogging that warrant particular mention as rules or guidelines.

The issue of &quot;shouldn&#039;t people just know&quot; what to do or not to do has come up as we&#039;ve been working on guidelines for blogging at OCLC. Most of us said &quot;yes, but....&quot; The &quot;but&quot; includes new employees who may not know that certain kinds of topics are verboten (particularly if they come from a different field); people who think blogging on a personal blog about work stuff is OK; and people who really do need reining in for whatever reasons. 

Once the OCLC guidelines are done (ie, approved) we&#039;d be happy to share.</description>
		<content:encoded><![CDATA[<p>Existing organizational communication guidelines may be sufficient as long as it&#8217;s clear blogging is included in the types of communications covered. There are, we think, some things that are sufficiently different about blogging that warrant particular mention as rules or guidelines.</p>
<p>The issue of &#8220;shouldn&#8217;t people just know&#8221; what to do or not to do has come up as we&#8217;ve been working on guidelines for blogging at OCLC. Most of us said &#8220;yes, but&#8230;.&#8221; The &#8220;but&#8221; includes new employees who may not know that certain kinds of topics are verboten (particularly if they come from a different field); people who think blogging on a personal blog about work stuff is OK; and people who really do need reining in for whatever reasons. </p>
<p>Once the OCLC guidelines are done (ie, approved) we&#8217;d be happy to share.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.183 seconds -->

