<?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 on: Microsoft SharePoint in Law Firms</title>
	<atom:link href="http://www.slaw.ca/2009/12/02/microsoft-sharepoint-in-law-firms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slaw.ca/2009/12/02/microsoft-sharepoint-in-law-firms/</link>
	<description>A Canadian cooperative weblog on all things legal.</description>
	<lastBuildDate>Thu, 05 Aug 2010 13:58:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Wendy Reynolds</title>
		<link>http://www.slaw.ca/2009/12/02/microsoft-sharepoint-in-law-firms/comment-page-1/#comment-709006</link>
		<dc:creator>Wendy Reynolds</dc:creator>
		<pubDate>Fri, 04 Dec 2009 14:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=14722#comment-709006</guid>
		<description>Having participated in two Sharepoint portal projects, I can&#039;t say enough about the flexibility of the product. I seems that, if you are willing to learn the vocabulary of Sharepoint and spend some time getting to know the back end, you can literally do anything you want.
That said, it is incredibly tempting to do *everything*. Mistake! Mistake! The literature is full of &quot;Sharepoint gone wrong&quot; horror stories. Some observations:
- Governance is important. Each project/product should have a clear goal and audience, and deviation should be discouraged. 
- For your first project, use Sharepoint &quot;out of the box&quot;. Customization is tempting, but can be a killer (and won&#039;t make you any friends with your IT department). You can do a remarkable amount of great work with the product as it is. Get good at that first. 
- Don&#039;t reproduce your shared drives inside Sharepoint. Shared drives become a nightmare when anyone can create a folder, nobody is responsible for records management in there, and junk accumulates. The same thing can happen in Sharepoint if there is no control.</description>
		<content:encoded><![CDATA[<p>Having participated in two Sharepoint portal projects, I can&#8217;t say enough about the flexibility of the product. I seems that, if you are willing to learn the vocabulary of Sharepoint and spend some time getting to know the back end, you can literally do anything you want.<br />
That said, it is incredibly tempting to do *everything*. Mistake! Mistake! The literature is full of &#8220;Sharepoint gone wrong&#8221; horror stories. Some observations:<br />
- Governance is important. Each project/product should have a clear goal and audience, and deviation should be discouraged.<br />
- For your first project, use Sharepoint &#8220;out of the box&#8221;. Customization is tempting, but can be a killer (and won&#8217;t make you any friends with your IT department). You can do a remarkable amount of great work with the product as it is. Get good at that first.<br />
- Don&#8217;t reproduce your shared drives inside Sharepoint. Shared drives become a nightmare when anyone can create a folder, nobody is responsible for records management in there, and junk accumulates. The same thing can happen in Sharepoint if there is no control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Tjaden</title>
		<link>http://www.slaw.ca/2009/12/02/microsoft-sharepoint-in-law-firms/comment-page-1/#comment-708940</link>
		<dc:creator>Ted Tjaden</dc:creator>
		<pubDate>Wed, 02 Dec 2009 22:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=14722#comment-708940</guid>
		<description>Hi Sue:

Thanks for your comment. I haven&#039;t heard too much about SharePoint for an academic law library.

As you may know, SharePoint can be used for deploying or creating external websites. However, I suspect many academic law libraries might be subject to their central university web management policies, etc.

For internal information management, there could be lots of useful applications using SharePoint: internal research and writing guides, wikis to create and publish manuals/guides, tracking faculty requests for research materials, integrating (assuming this is possible) with BlackBoard or other electronic classroom/teaching sites, and so on.

If you assume a law school professor/library/law student total head count of say 700 people, you are close in size to a mid-sized law firm, although there would perhaps be less need for internal communication in a law school setting than in a law firm.

One benefit of SharePoint I forgot to mention in my post is the easier implementation of automated document workflow, something which might have less application in academia.

However, I would defer to someone else&#039;e comments, if any.</description>
		<content:encoded><![CDATA[<p>Hi Sue:</p>
<p>Thanks for your comment. I haven&#8217;t heard too much about SharePoint for an academic law library.</p>
<p>As you may know, SharePoint can be used for deploying or creating external websites. However, I suspect many academic law libraries might be subject to their central university web management policies, etc.</p>
<p>For internal information management, there could be lots of useful applications using SharePoint: internal research and writing guides, wikis to create and publish manuals/guides, tracking faculty requests for research materials, integrating (assuming this is possible) with BlackBoard or other electronic classroom/teaching sites, and so on.</p>
<p>If you assume a law school professor/library/law student total head count of say 700 people, you are close in size to a mid-sized law firm, although there would perhaps be less need for internal communication in a law school setting than in a law firm.</p>
<p>One benefit of SharePoint I forgot to mention in my post is the easier implementation of automated document workflow, something which might have less application in academia.</p>
<p>However, I would defer to someone else&#8217;e comments, if any.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue Connor</title>
		<link>http://www.slaw.ca/2009/12/02/microsoft-sharepoint-in-law-firms/comment-page-1/#comment-708926</link>
		<dc:creator>Sue Connor</dc:creator>
		<pubDate>Wed, 02 Dec 2009 16:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=14722#comment-708926</guid>
		<description>I&#039;ve heard an awful lot about SharePoint recently, but usually only in reference to law firms. Does anyone think this resource would be useful in an academic law library? I don&#039;t know enough about it to know whether or not it would be useful in that environment.

Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve heard an awful lot about SharePoint recently, but usually only in reference to law firms. Does anyone think this resource would be useful in an academic law library? I don&#8217;t know enough about it to know whether or not it would be useful in that environment.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
