<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>nSourceIT &#187; best practices</title>
	<atom:link href="http://www.nsourceit.com/tag/best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nsourceit.com</link>
	<description>Information Technology, e-Discovery, and Litigation Support Services</description>
	<lastBuildDate>Sun, 24 Jul 2011 23:55:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>In Search of Quality: Is It Time for E-Discovery Search Process Quality Standards?</title>
		<link>http://www.nsourceit.com/2011/03/22/in-search-of-quality-is-it-time-for-e-discovery-search-process-quality-standards/</link>
		<comments>http://www.nsourceit.com/2011/03/22/in-search-of-quality-is-it-time-for-e-discovery-search-process-quality-standards/#comments</comments>
		<pubDate>Tue, 22 Mar 2011 17:44:42 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=934</guid>
		<description><![CDATA[From e-Discovery Team:
Robert Pirsig spent a good deal of time on his motorcycle in the 1970s contemplating the metaphysics of quality. In my own way, I’ve been on a similar quixotic mission for at least the past eight years — in search of “quality” in the e-discovery search space. This particular quest for the Holy [...]]]></description>
			<content:encoded><![CDATA[<p>From e-Discovery Team:</p>
<div id="_mcePaste">Robert Pirsig spent a good deal of time on his motorcycle in the 1970s contemplating the metaphysics of quality. In my own way, I’ve been on a similar quixotic mission for at least the past eight years — in search of “quality” in the e-discovery search space. This particular quest for the Holy Grail has involved seeking out the perfect search where one finds “just” highly relevant documents in response to a FRCP 34 document request,  or, as a matter of early case assessment, “just” the hot documents one needs to win the case. I’ve searched the world over for answers, and along the way decided that I had been asking the wrong question.</div>
<div id="_mcePaste">At one time, I thought I knew what the problem was, and what the information retrieval “task” should be to overcome the problem. The problem, I thought, was simply the naïve use of keywords. Or at least, the way lawyers naively think about keywords when going about the task of searching for electronic evidence. I think many lawyers still practice with the assumption that using simple keywords, without more, to find responsive ESI is sufficient to get them through the day in dealing with their e-discovery obligations. While this remains a problem, it is not in my view the problem. And the task is not simply to try to “beat Boolean” with other search methods.</div>
<p>Robert Pirsig spent a good deal of time on his motorcycle in the 1970s contemplating the metaphysics of quality. In my own way, I’ve been on a similar quixotic mission for at least the past eight years — in search of “quality” in the e-discovery search space. This particular quest for the Holy Grail has involved seeking out the perfect search where one finds “just” highly relevant documents in response to a FRCP 34 document request,  or, as a matter of early case assessment, “just” the hot documents one needs to win the case. I’ve searched the world over for answers, and along the way decided that I had been asking the wrong question.<br />
At one time, I thought I knew what the problem was, and what the information retrieval “task” should be to overcome the problem. The problem, I thought, was simply the naïve use of keywords. Or at least, the way lawyers naively think about keywords when going about the task of searching for electronic evidence. I think many lawyers still practice with the assumption that using simple keywords, without more, to find responsive ESI is sufficient to get them through the day in dealing with their e-discovery obligations. While this remains a problem, it is not in my view the problem. And the task is not simply to try to “beat Boolean” with other search methods.</p>
<p><a href="http://e-discoveryteam.com/2011/03/13/in-search-of-quality-is-it-time-for-e-discovery-search-process-quality-standards/" target="_blank">e-Discovery Team - In Search of Quality: Is It Time for E-Discovery Search Process Quality Standards?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2011/03/22/in-search-of-quality-is-it-time-for-e-discovery-search-process-quality-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dell: 90% of data is never read again</title>
		<link>http://www.nsourceit.com/2010/07/13/dell-90-of-data-is-never-read-again/</link>
		<comments>http://www.nsourceit.com/2010/07/13/dell-90-of-data-is-never-read-again/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 15:53:44 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[Dell]]></category>
		<category><![CDATA[IT departments]]></category>
		<category><![CDATA[storage]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=857</guid>
		<description><![CDATA[From PC Pro: &#8221;According to Dell, 90% of company data is written once and never read again. This arresting claim cropped up in the middle of a presentation from Dell’s Enterprise division, recently given to Jon Honeyball and me. Given our usual style of dealing with such events, the poor devils didn’t stand a chance [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.pcpro.co.uk/realworld/359293/dell-90-of-data-is-never-read-again" target="_blank">PC Pro</a>: &#8221;According to Dell, 90% of company data is written once and never read again. This arresting claim cropped up in the middle of a presentation from Dell’s Enterprise division, recently given to Jon Honeyball and me. Given our usual style of dealing with such events, the poor devils didn’t stand a chance of actually working though their prepared order of slides, and I’d have to confess that we didn’t even try to stick to the script we’d discussed in the run-up to the meeting.</p>
<p><img class="aligncenter size-full wp-image-858" title="data" src="http://www.nsourceit.com/wp-content/uploads/2010/07/data.jpg" alt="" width="347" height="346" /></p>
<p>But even allowing for our natural tendency towards anarchy, this statement stood right out from the other stuff in the presentation. It’s an odd statistic. How is that data measured? 90% of all documents? 90% of stored bytes? When they said “ever again” did they mean explicitly retrieved by name, or should we include free text searches in that statistic? How long an interval needs to pass before some piece of data is clearly identified as belonging to the 90%, so that steps can be taken to reflect its reduced importance? These questions are just the starting point for an issue that demands quite a lot of thinking. It’s a fascinating finding to be offered to you by a vendor of servers, given that so few of the devices they try to sell to smaller organisations actually reflect this “fact” in their hardware and software specification.&#8221;</p>
<p><a href="http://www.pcpro.co.uk/realworld/359293/dell-90-of-data-is-never-read-again" target="_blank">PC Pro &#8211; Dell: 90% of data is never read again</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/07/13/dell-90-of-data-is-never-read-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PrintConductor Prints Documents in Batches Without Opening Them</title>
		<link>http://www.nsourceit.com/2010/05/27/printconductor-prints-documents-in-batches-without-opening-them/</link>
		<comments>http://www.nsourceit.com/2010/05/27/printconductor-prints-documents-in-batches-without-opening-them/#comments</comments>
		<pubDate>Thu, 27 May 2010 15:43:51 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[batch printing]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[tips & tricks]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=844</guid>
		<description><![CDATA[From Addictivetips: &#8221;Lets say you want to print different types of documents in one go, such as, Adobe PDF, Word Document, Wordpad text, Excel spreadsheet, Visio or AutoCAD diagram, and so on. The only way would be to manually open each one of them and click Print. This is a tiresome procedure which will waste [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.addictivetips.com/windows-tips/batch-print-19-different-document-types-together/" target="_blank">Addictivetips</a>: &#8221;Lets say you want to print different types of documents in one go, such as, Adobe PDF, Word Document, Wordpad text, Excel spreadsheet, Visio or AutoCAD diagram, and so on. The only way would be to manually open each one of them and click Print. This is a tiresome procedure which will waste half of your day (if you do a lot of printing at work).</p>
<p style="text-align: center;"><img class="aligncenter size-thumbnail wp-image-845" title="insert_coin" src="http://www.nsourceit.com/wp-content/uploads/2010/05/insert_coin-121x91.jpg" alt="" width="121" height="91" /></p>
<p>Luckily we have discovered a lifesaver, called PrintConductor. This nifty little tool helps in batch printing multiple document types. According to the developer, it supports 16 document types, which includes, PDF, DOC, WRI, WPS, RTF, TXT, XLS, PPT, PPS, POT, VSD, DWG, DXF, SNP, HTM, and HTML. While testing, I found that it also supports the latest DOCX, XLSX, and PPTX formats, making the total supported file types to 19.</p>
<p>It uses the COM/DDE interfaces of the official applications in order to print, which means that it will first detect the installed document readers and editors before allowing user to add the documents for batch printing. This has one downside, i.e, you cannot add PDF files for printing unless you have Adobe Acrobat installed, the same problem arises with other formats where the original program must be installed.&#8221;</p>
<p><a href="http://www.addictivetips.com/windows-tips/batch-print-19-different-document-types-together/" target="_blank">Addictivetips &#8211; Batch Print 19 Different Document Types Together</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/05/27/printconductor-prints-documents-in-batches-without-opening-them/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to avoid death by backup in e-Discovery</title>
		<link>http://www.nsourceit.com/2010/04/19/how-to-avoid-death-by-backup-in-e-discovery/</link>
		<comments>http://www.nsourceit.com/2010/04/19/how-to-avoid-death-by-backup-in-e-discovery/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 14:09:22 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[ESI]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=823</guid>
		<description><![CDATA[From Information Week:  &#8221;Many organizations are sitting on stockpiles of dangerous materials. No, we&#8217;re not talking about hazardous chemicals or unstable explosives. We mean backup tapes, which are routinely included in requests to produce electronically stored information (ESI) as part of potential or ongoing litigation.
The e-discovery realm is rife with cautionary tales of organizations tripped [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.informationweek.com/news/business_intelligence/information_mgt/showArticle.jhtml?articleID=224400402" target="_blank">Information Week</a>:  &#8221;Many organizations are sitting on stockpiles of dangerous materials. No, we&#8217;re not talking about hazardous chemicals or unstable explosives. We mean backup tapes, which are routinely included in requests to produce electronically stored information (ESI) as part of potential or ongoing litigation.</p>
<p>The e-discovery realm is rife with cautionary tales of organizations tripped up by backup tapes. For instance, in 2009 a judge fined a defendant more than $1 million for failing to retrieve information stored on backup tapes. In the same year, the government&#8217;s Office of Federal Housing Enterprise Oversight was compelled by a court to search its off-site disaster recovery backups for ESI, a search that ended up costing the agency $6 million&#8211;a jaw-dropping amount for a single discovery exercise. What&#8217;s even scarier is that the agency wasn&#8217;t even a party in the lawsuit; it had simply been subpoenaed for documents in litigation involving Fannie Mae.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-824" title="tapebackup" src="http://www.nsourceit.com/wp-content/uploads/2010/04/tapebackup.jpg" alt="" width="425" height="282" /></p>
<p>This article examines the challenges that backup tapes pose. It also discusses strategies organizations can use to reduce the number of tapes that get stockpiled, and it outlines technologies and services that help reduce the cost and time it takes to retrieve ESI from tape.&#8221;</p>
<p><a href="http://www.informationweek.com/news/business_intelligence/information_mgt/showArticle.jhtml?articleID=224400402" target="_blank">Information Week &#8211; E-Discovery: How To Avoid Death By Backup</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/04/19/how-to-avoid-death-by-backup-in-e-discovery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Please do not change your password</title>
		<link>http://www.nsourceit.com/2010/04/12/please-do-not-change-your-password/</link>
		<comments>http://www.nsourceit.com/2010/04/12/please-do-not-change-your-password/#comments</comments>
		<pubDate>Mon, 12 Apr 2010 17:48:36 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[IT departments]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[tips & tricks]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=793</guid>
		<description><![CDATA[From The Boston Globe:  &#8221;To continue reading this story, enter your password now. If you do not have a password, please create one. It must contain a minimum of eight characters, including upper- and lower-case letters and one number. This is for your own good.

Nonsense, of course, but it helps illustrate a point: You will [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.boston.com/bostonglobe/ideas/articles/2010/04/11/please_do_not_change_your_password/" target="_blank">The Boston Globe</a>:  &#8221;To continue reading this story, enter your password now. If you do not have a password, please create one. It must contain a minimum of eight characters, including upper- and lower-case letters and one number. This is for your own good.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-794" title="password" src="http://www.nsourceit.com/wp-content/uploads/2010/04/password.jpg" alt="" width="400" height="286" /></p>
<p>Nonsense, of course, but it helps illustrate a point: You will need a computer password today, maybe a half dozen or more — those secret sign-ins that serve as sentries for everything from Amazon shopping carts to work files to online bank accounts. Just when you have them all sorted out, along comes another “urgent” directive from the bank or IT department — time to reset those codes, for safety’s sake. And the latest lineup of log-ins you’ve concocted won’t last for long, either. Some might temporarily stay in your head, others are jotted on scraps of paper and stuffed in a wallet. A few might be taped to your computer monitor in plain view (or are those are from last year’s batch? Who can remember?).</p>
<p>Now, a study has concluded what lots of us have long suspected: Many of these irritating security measures are a waste of time. The study, by a top researcher at Microsoft, found that instructions intended to spare us from costly computer attacks often exact a much steeper price in the form of user effort and time expended.</p>
<p>“Most security advice simply offers a poor cost-benefit trade-off to users,” wrote its author, Cormac Herley, a principal researcher for Microsoft Research&#8230;&#8221;</p>
<p><a href="http://www.boston.com/bostonglobe/ideas/articles/2010/04/11/please_do_not_change_your_password/" target="_blank">The Boston Globe: Please do not change your password</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/04/12/please-do-not-change-your-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to deploy and support the iPhone in a law firm</title>
		<link>http://www.nsourceit.com/2010/02/09/how-to-deploy-and-support-the-iphone-in-a-law-firm/</link>
		<comments>http://www.nsourceit.com/2010/02/09/how-to-deploy-and-support-the-iphone-in-a-law-firm/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 23:25:46 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[mobile devices]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=650</guid>
		<description><![CDATA[From TechnoLawyer Blog (registration required): &#8221;Apple&#8217;s iPhone is cool, but could it compete with the BlackBerry as a business tool at Sonnenschein Nath &#38; Rosenthal LLP, one of the world&#8217;s largest law firms? In thisTechnoFeature article, Sonnenschein&#8217;s Manager of Software Services Christopher Lewis explains why Sonnenschein decided to deploy the iPhone to its lawyers, how [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://blog.technolawyer.com/2010/02/how-to-deploy-and-support-the-iphone-in-a-law-firm.html" target="_blank">TechnoLawyer Blog</a> (registration required): &#8221;Apple&#8217;s iPhone is cool, but could it compete with the BlackBerry as a business tool at Sonnenschein Nath &amp; Rosenthal LLP, one of the world&#8217;s largest law firms? In this<em>TechnoFeature</em> article, Sonnenschein&#8217;s Manager of Software Services Christopher Lewis explains why Sonnenschein decided to deploy the iPhone to its lawyers, how it handled the deployment, the functions it supports and doesn&#8217;t support, and the results thus far.</p>
<p style="text-align: center;"><a href="http://nsourceit.com/wp-content/uploads/2010/02/iphone_home.gif"><img class="aligncenter size-medium wp-image-652" title="iphone_home" src="http://nsourceit.com/wp-content/uploads/2010/02/iphone_home-271x447.gif" alt="iphone_home" width="271" height="447" /></a></p>
<p>If the lawyers at your firm are clamoring for iPhone support, look no further than Christopher&#8217;s invaluable advice.&#8221;</p>
<p><a href="http://blog.technolawyer.com/2010/02/how-to-deploy-and-support-the-iphone-in-a-law-firm.html" target="_blank">TechnoLawyer Blog: How to deploy and support the iPhone in a law firm</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/02/09/how-to-deploy-and-support-the-iphone-in-a-law-firm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>30 Years of Failure: The username/password combination</title>
		<link>http://www.nsourceit.com/2009/10/19/30-years-of-failure-the-usernamepassword-combination/</link>
		<comments>http://www.nsourceit.com/2009/10/19/30-years-of-failure-the-usernamepassword-combination/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 20:30:00 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.nsource.info/wptest/?p=307</guid>
		<description><![CDATA[From ARS Technica:
&#8221;A lot of the effort involved in establishing a secure computing environment focuses on technological solutions, from providing warnings about phishing attacks to blocking the propagation of botnets. But, as previous research has shown, security involves a significant human component. Nowhere is that more true than the item at the heart of basic [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://arstechnica.com">ARS Technica</a>:</p>
<p>&#8221;A lot of the effort involved in establishing a secure computing environment focuses on technological solutions, from providing warnings about phishing attacks to blocking the propagation of botnets. But, as previous research has shown, security involves a significant human component. Nowhere is that more true than the item at the heart of basic security: the humble password. Here, our best practices—something that&#8217;s not in the dictionary or written down, differs for every account, etc.—ignores basic research, which shows that humans have a limited capacity to associate random text with, well, just about anything. A new survey of institutional IT users provides a glimpse into just how bad the password situation is, with less than five percent of users managing to use best practices.</p>
<p style="text-align: center;"><img class="alignnone size-medium wp-image-308" title="password" src="http://www.nsource.info/wptest/wp-content/uploads/2009/10/password-271x193.jpg" alt="password" width="271" height="193" /></p>
<p>What is perhaps most striking about the new study, which is being published in the Proceedings of the Human Factors and Ergonomics Society, is its background section, which details just how long we&#8217;ve been aware of the password problem. It cites a study of Unix passwords from 1979, which showed that about 30 percent of the passwords were four characters or less, and about 15 percent being words that appear in the dictionary. Fast forward to 2006, when a separate survey of 34,000 MySpace passwords revealed that the most common were &#8216;password1&#8242;, &#8216;abc123&#8242;, &#8216;myspace1&#8242;, and &#8216;password&#8217;.&#8221;</p>
<p><a href="http://arstechnica.com/business/news/2009/10/30-years-of-failure-the-user-namepassword-combination.ars" target="_blank">Click to read full article:  ARS Technica: 30 Years of Failure: The username/password combination</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2009/10/19/30-years-of-failure-the-usernamepassword-combination/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

