<?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/"
		>
<channel>
	<title>Comments for Blogs at the University of Florida Libraries</title>
	<atom:link href="http://blogs.uflib.ufl.edu/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.uflib.ufl.edu</link>
	<description>News, Events, &#38; More</description>
	<lastBuildDate>Wed, 26 Nov 2008 07:15:52 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Project Management with Basecamp by ITIL  Training</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-39</link>
		<dc:creator>ITIL  Training</dc:creator>
		<pubDate>Wed, 26 Nov 2008 07:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-39</guid>
		<description>At first I was very impressed with the Base Camp features and ease of use, the interface was very good looking and intuitive. One of the main reasons I was keen to start using project management was to allow my clients to track the progress of their projects and the amount of time I spend on work, Base Camp did these very well. The only problem with Base Camp is the price, for the lowest package (there are several different packages) you have to pay a hefty price per month.</description>
		<content:encoded><![CDATA[<p>At first I was very impressed with the Base Camp features and ease of use, the interface was very good looking and intuitive. One of the main reasons I was keen to start using project management was to allow my clients to track the progress of their projects and the amount of time I spend on work, Base Camp did these very well. The only problem with Base Camp is the price, for the lowest package (there are several different packages) you have to pay a hefty price per month.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Project Management with Basecamp by Ram</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-38</link>
		<dc:creator>Ram</dc:creator>
		<pubDate>Wed, 26 Nov 2008 07:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-38</guid>
		<description>Well written , I liked this info, Thanks</description>
		<content:encoded><![CDATA[<p>Well written , I liked this info, Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Project Management with Basecamp by Mike</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-37</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 25 Nov 2008 09:30:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-37</guid>
		<description>I&#039;ve just found your blog, and am enjoying what I&#039;ve read so far.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just found your blog, and am enjoying what I&#8217;ve read so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Project Management with Basecamp by John</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-36</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 11 Nov 2008 10:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-36</guid>
		<description>I too agree with base camp..</description>
		<content:encoded><![CDATA[<p>I too agree with base camp..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Project Management with Basecamp by Greg</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-33</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Thu, 30 Oct 2008 10:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-33</guid>
		<description>Yes, BaseCamp is an excellent PMS System.</description>
		<content:encoded><![CDATA[<p>Yes, BaseCamp is an excellent PMS System.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We&#8217;ve Got the Biscuit; You Bring the Gravy. by Reference</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/10/23/weve-got-the-biscuit-you-bring-the-gravy/comment-page-1/#comment-32</link>
		<dc:creator>Reference</dc:creator>
		<pubDate>Fri, 24 Oct 2008 16:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/?p=17#comment-32</guid>
		<description>Your blog is great!

Here is the url of the blog from the Archives of the Sandusky Library, if you would
like to take a look:

http://sanduskyhistory.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Your blog is great!</p>
<p>Here is the url of the blog from the Archives of the Sandusky Library, if you would<br />
like to take a look:</p>
<p><a href="http://sanduskyhistory.blogspot.com/" rel="nofollow">http://sanduskyhistory.blogspot.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Project Management with Basecamp by UF Libraries&#8217; Meeting Minutes &#187; Blog Archive &#187; Library 2.0 Working Group</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/comment-page-1/#comment-19</link>
		<dc:creator>UF Libraries&#8217; Meeting Minutes &#187; Blog Archive &#187; Library 2.0 Working Group</dc:creator>
		<pubDate>Tue, 26 Aug 2008 00:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/05/11/project-management-with-basecamp/#comment-19</guid>
		<description>[...] Basecamp signup information, Fireshot for documentation; Google doc templates, especially with Gmail for students; [...]</description>
		<content:encoded><![CDATA[<p>[...] Basecamp signup information, Fireshot for documentation; Google doc templates, especially with Gmail for students; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Library 2.0 Group available to help! by laurien</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/04/18/library-20-group-available-to-help/comment-page-1/#comment-6</link>
		<dc:creator>laurien</dc:creator>
		<pubDate>Tue, 03 Jun 2008 12:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/04/18/library-20-group-available-to-help/#comment-6</guid>
		<description>Smathers Libraries Watercooler E-mail List

To subscribe, send an email to listserv@lists.ufl.edu with “Subscribe libwatercooler-l firstname lastname” in the body of the message.

To send messages, just email the list address: libwatercooler-l@lists.ufl.edu</description>
		<content:encoded><![CDATA[<p>Smathers Libraries Watercooler E-mail List</p>
<p>To subscribe, send an email to <a href="mailto:listserv@lists.ufl.edu">listserv@lists.ufl.edu</a> with “Subscribe libwatercooler-l firstname lastname” in the body of the message.</p>
<p>To send messages, just email the list address: <a href="mailto:libwatercooler-l@lists.ufl.edu">libwatercooler-l@lists.ufl.edu</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blogs for the University of Florida Libraries by laurien</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/03/31/hello-world/comment-page-1/#comment-5</link>
		<dc:creator>laurien</dc:creator>
		<pubDate>Tue, 03 Jun 2008 12:11:04 +0000</pubDate>
		<guid isPermaLink="false">#comment-5</guid>
		<description>Policies and Procedures

For

Smathers Libraries Blog

 

Date Created:     3/5/2007

Account Creation:

   1. All blog usernames, with the exception of Systems’ created administrators(i.e., Blog owners) must correspond to the users library username (ex sallygator@uflib.ufl.edu = sallygator on the Smathers library blog)
   2. All blog passwords must be 12 characters in length
   3. All account creation will be through sys help
         1. For blog creation, the name, purpose of the blog, audience, blog administrator and blog users should be submitted.

1.       Names can be no longer than 100 characters

2.       Administrators must be full time library staff

3.       Blog purpose must be related to the mission of the libraries

         2. For additional blog users, just the full name of the user and their library username. 
         3. For changes in blog administrators, the name of the blog, the name of the previous administrator, and the name of the new administrator.  (Changes may be confirmed with department supervisors)
         4. Anonymous comments will be allowed
         5. Users will be allowed to self  identify when commenting

 

Blog Moderation:

1.       Blog moderation is at the discretion of the blog administrator registered by the accounts creation with systems.  They are responsible for both content moderation and comment moderation.  They may block any user they feel has been threatening or offensive, and remove any content.  They are responsible for maintaining University Standards.

 

Blog Template

   1. All Templates created by Library Staff will be available for use in the blog system
   2. All Blog templates must be submitted to systems, for code review, before they will be added to the Smathers’ blog system.</description>
		<content:encoded><![CDATA[<p>Policies and Procedures</p>
<p>For</p>
<p>Smathers Libraries Blog</p>
<p>Date Created:     3/5/2007</p>
<p>Account Creation:</p>
<p>   1. All blog usernames, with the exception of Systems’ created administrators(i.e., Blog owners) must correspond to the users library username (ex <a href="mailto:sallygator@uflib.ufl.edu">sallygator@uflib.ufl.edu</a> = sallygator on the Smathers library blog)<br />
   2. All blog passwords must be 12 characters in length<br />
   3. All account creation will be through sys help<br />
         1. For blog creation, the name, purpose of the blog, audience, blog administrator and blog users should be submitted.</p>
<p>1.       Names can be no longer than 100 characters</p>
<p>2.       Administrators must be full time library staff</p>
<p>3.       Blog purpose must be related to the mission of the libraries</p>
<p>         2. For additional blog users, just the full name of the user and their library username.<br />
         3. For changes in blog administrators, the name of the blog, the name of the previous administrator, and the name of the new administrator.  (Changes may be confirmed with department supervisors)<br />
         4. Anonymous comments will be allowed<br />
         5. Users will be allowed to self  identify when commenting</p>
<p>Blog Moderation:</p>
<p>1.       Blog moderation is at the discretion of the blog administrator registered by the accounts creation with systems.  They are responsible for both content moderation and comment moderation.  They may block any user they feel has been threatening or offensive, and remove any content.  They are responsible for maintaining University Standards.</p>
<p>Blog Template</p>
<p>   1. All Templates created by Library Staff will be available for use in the blog system<br />
   2. All Blog templates must be submitted to systems, for code review, before they will be added to the Smathers’ blog system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Library 2.0 Group available to help! by laurien</title>
		<link>http://blogs.uflib.ufl.edu/blog/2008/04/18/library-20-group-available-to-help/comment-page-1/#comment-3</link>
		<dc:creator>laurien</dc:creator>
		<pubDate>Fri, 18 Apr 2008 18:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.uflib.ufl.edu/blog/2008/04/18/library-20-group-available-to-help/#comment-3</guid>
		<description>OOps! I fixed the link--sorry about that!</description>
		<content:encoded><![CDATA[<p>OOps! I fixed the link&#8211;sorry about that!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
