<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-6791672639619957449</atom:id><lastBuildDate>Mon, 23 Apr 2012 18:16:14 +0000</lastBuildDate><title>Information Nation</title><description></description><link>http://infonation.kahnconsultinginc.com/</link><managingEditor>noreply@blogger.com (Kahn Consulting, Inc.)</managingEditor><generator>Blogger</generator><openSearch:totalResults>96</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4731499396742360164</guid><pubDate>Wed, 29 Feb 2012 22:43:00 +0000</pubDate><atom:updated>2012-03-09T09:26:34.911-08:00</atom:updated><title>A Stream of Auto-Classification Consciousness by Randolph Kahn, ESQ.</title><description>&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:enableopentypekerning/&gt;    &lt;w:dontflipmirrorindents/&gt;    &lt;w:overridetablestylehps/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif][if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif][if gte mso 10]&gt; &lt;style&gt;  /* Style Definitions */  table.MsoNormalTable  {mso-style-name:"Table Normal";  mso-tstyle-rowband-size:0;  mso-tstyle-colband-size:0;  mso-style-noshow:yes;  mso-style-priority:99;  mso-style-parent:"";  mso-padding-alt:0in 5.4pt 0in 5.4pt;  mso-para-margin:0in;  mso-para-margin-bottom:.0001pt;  mso-pagination:widow-orphan;  font-size:10.0pt;  font-family:"Times New Roman","serif";} &lt;/style&gt; &lt;![endif]--&gt;  &lt;p class="MsoNormal"&gt;“But how will a court judge our use of auto-classification technology to do the heavy lifting regarding what information was a record and what was junk?”&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt; “I want to be comfortable with our decision that using algorithmic classification software technology to apply our records retention rules and clean up the contents of our shared drive won’t get us flogged by a regulator or a court.”&lt;br /&gt;&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;    &lt;p class="MsoNormal"&gt;“I am concerned that if we get rid of this data without having our employees review it manually, that we are open to attack in a court.”&lt;br /&gt;&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;We have empirical data to support the proposition that employees classify and code information way worse than computers, by a long shot. Yet most companies continue to rely on their employees to manage information.  “[T]echnology-assisted process, in which only a small fraction of the document collection is ever examined by humans, can yield higher recall and/or precision than an exhaustive manual review process, in which the entire document collection is examined and coded by humans.” &lt;i&gt;Technology-Assisted Review in E-Discovery Can Be More Effective and More Efficient Than Exhaustive Manual Review, Maura R. Grossman, JD., Ph.D. and Gordon V. Cormack, Ph.D.&lt;/i&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Most big companies have petabytes of structure and unstructured content, which is billions of files. Do you think a judge would say it was "reasonable" to expect employees to classify and review billions of files before they could be purged? According to the Council of Information Auto-Classification’s “The Information Explosion Survey”, 98% of organizations reported rapid information growth that they predict will extend into the future and that growth is creating a variety of challenges and consequences. Half of the respondents indicated they are forced to recreate information previously created because they cannot find it. 74% of the organizations stated valuable information is being lost (i.e. can’t find, disposed of, misplaced) due to the lack of proper technology solutions. 73% of respondents reported their organization misses business opportunities because they can’t efficiently access information.&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt; Technology is amazingly powerful at uncovering value from information and connecting dots, at the same time people are impotent in the face of the mountain of data to make it make sense.  People bet their life on the Genome project made possible by technology unearthing the connections in data, but you are not sure if you should use auto-classification technology to determine if an email is a record.&lt;br /&gt;&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt; In an article entitled “Search, Forward: Will manual document review and keyword searches be replaced by computer-assisted coding” US Federal Magistrate Judge Andrew Peck wrote, “[p]erhaps they are looking for an opinion concluding that: “It is the opinion of the court that the use of predictive coding is a proper and acceptable means of conducting searches under the Federal Rules of Civil Procedure, and furthermore that the software provided for this purpose by [Insert name of your favorite vendor] is the software of choice in this court.”  If so, it will be a long wait… Until there is a judicial opinion approving (or even critiquing) the use of predictive coding, counsel will just have to rely on this article as a sign of judicial approval.  In my opinion, computer-assisted coding should be used in those cases where it will help “secure the just, speedy, and inexpensive” (Fed. R. Civ. P. 1) determination of case in our e-discovery world.&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;And Judge Peck strikes again in Moore v. Publicis Groupe, in his February 22, 2012 order in this case, “Computer-assisted review appears to be better than the available alternatives, and thus should be used in appropriate cases. While this Court recognizes that computer-assisted  review is not perfect, the Federal Rules of Civil Procedure do not require perfection…Counsel no longer have to worry about being the “first” or “guinea pig” for judicial acceptance of computer assisted review.”&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;br /&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;If computer-assisted review is ok for finding relevant information for a lawsuit, why shouldn’t you be comfortable with using these types of technologies to classify records? Clearly applying records management rules is a far less risky proposition than responding to discovery. Auto-classification is a way to better manage and if appropriate, defensibly dispose of huge volumes of data when people can’t.  The courts are now making that decision easier.   &lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4731499396742360164?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2012/02/stream-of-auto-classification.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-2961240602084429751</guid><pubDate>Mon, 12 Dec 2011 15:33:00 +0000</pubDate><atom:updated>2011-12-12T08:32:41.908-08:00</atom:updated><title>Is It Potentially Relevant?</title><description>&lt;p class="MsoNormal"&gt;&lt;span style="color:#1F497D"&gt;Remember, no matter what Daisies you WANT to chuck, you can’t take ANY action unless you make sure the information is not even potentially relevant and/or needed for threatened, imminent or active lawsuits, investigations or audits. Take for example the Hackergate investigation. That’s the case of News Corp. journalists hacking into the voice mails of people in the news to learn insights into their lives so they could report on the information.  Lots of folks are under scrutiny (and they have already shut down the offending newspaper in England) because of the scandal. However, as reported in the Wall Street journal on December 12, 2011 in an article entitled ‘Hacking Investigation Questions Who Erased Voice Mails’, the investigation is  focusing on the deletion of the certain voice mail messages as such action might point to the guilty party.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2961240602084429751?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/12/is-it-potentially-relevant.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-2112823887767109406</guid><pubDate>Thu, 20 Oct 2011 19:35:00 +0000</pubDate><atom:updated>2011-10-20T12:58:18.191-07:00</atom:updated><title>Randy Kahn says . . .</title><description>Press Release:  Autonomy Unveils Meaning-Based Policy Control Solution for Governance and Compliance&lt;br /&gt;&lt;br /&gt;"Businesses need a comprehensive tool to automatically and consistently administer policies and determine risk," said Randolph Kahn, founder of Kahn Consulting and author of "Information Nation". "Autonomy is taking a unique approach to implementing and managing policies to govern the lifecycle of information."&lt;br /&gt;&lt;br /&gt;Read the full &lt;a href="http://www.marketwatch.com/story/autonomy-unveils-meaning-based-policy-control-solution-for-governance-and-compliance-2011-10-17"&gt;Press Release&lt;/a&gt; here.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2112823887767109406?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/10/randy-kahn-says.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-8619098837736874208</guid><pubDate>Thu, 08 Sep 2011 17:46:00 +0000</pubDate><atom:updated>2011-09-08T10:47:45.262-07:00</atom:updated><title>Records Memorialize</title><description>NY Times reports that an “independent investigative committee found that the governor of Saga prefecture told the operator, Kyushu Electric Power, to send e-mails supporting the restart of two reactors at the company’s Genkai Nuclear Power Station. The company has already admitted to ordering employees to pose as regular citizens by sending e-mails during an online town hall-style meeting in June over whether to allow the restart of the reactors.”&lt;br /&gt;&lt;br /&gt;Records memorialize and can hurt. Time for some business ethics, risk management and email training. Nice job Japan - Allow a disaster to happen and add insult upon injury until you have no credibility. Brilliant.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-8619098837736874208?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/09/records-memorialize.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-8118044418293307100</guid><pubDate>Tue, 26 Jul 2011 17:09:00 +0000</pubDate><atom:updated>2011-07-26T10:10:47.126-07:00</atom:updated><title>Your Business Needs to Rightsize</title><description>A Dozen Really Good Reasons Why Your Business Needs to Rightsize its Information Footprint&lt;br /&gt;&lt;br /&gt;“Rightsizing Your Information Footprint” is my made-up term for turning your Information Parking Lots into a Goldie Locks and the Three Bears amount of information — not too much, not too little, but just the right amount.  There is too much digital content with more created continuously. We need to clean up the past in a defensible way. While the daisies are beautiful at the beginning of their life, they lose their appeal as they decay. The same is generally true for information.  Businesses also need a better path forward so that content comes into being because the business needs it, and all records are better managed. &lt;br /&gt;&lt;br /&gt;Too much stuff, you fail to be business efficient and you get your clock cleaned when litigation strikes.&lt;br /&gt;Too little information, you can’t run your business and you fail to comply with record keeping requirements, among other things. &lt;br /&gt;&lt;br /&gt;So here are 12 remarkably compelling reasons to Rightsize, right now:&lt;br /&gt;&lt;br /&gt;1. Information is growing at such a rapid rate that costs related to storing, finding, using, migrating, extracting, preserving information are too high &lt;br /&gt;2. Knowing what information exists and where it is parked to be able to efficiently run your business is too complex&lt;br /&gt;3. Technology has failed to find a good way to manage content with little impact to employee productivity (but Kahn is working on auto-classification to help) &lt;br /&gt;4. Employees get too much content to be able to properly manage it&lt;br /&gt;5. Content has sat for years in old Information Parking Lots and it is a decaying asset (Working on my new book called Chucking Daisies to help companies deal with this precise issue)&lt;br /&gt;6. Companies spend too much time looking through way too much irrelevant stuff to respond to litigation, audits and investigations&lt;br /&gt;7. Companies have out of date records used against them in litigation, which could have been disposed earlier&lt;br /&gt;8. Systems are breaking down or no longer work as efficiently as they should, due to information volume burden &lt;br /&gt;9. Data parking lots are being ill-managed and that failure is causing other failures, not the least of which is failing to harness needed information to be “faster, better and cheaper.” &lt;br /&gt;10. Going Green. No list is complete until it has a bit of Green. Technology is using all kinds of energy and by cutting your energy, emission and every other relevant footprint, you are greener, you look better to the outside world and maybe the marketers have something Green to say about the effort&lt;br /&gt;11. Information finds itself on unsanctioned data Parking Lots, when sanctioned ones fill up, making life more challenging&lt;br /&gt;12. Along with volume, growth has been the creator of many new Information Parking Lots (Smart phones, Cloud, Twitter, Blogs, etc.) which makes management that much more challenging  &lt;br /&gt;&lt;br /&gt;Rightsizing will never be as easy as it is right now as information Parking Lots grow and grow.    Clean house of digital data junk. Develop a thoughtful plan for future information retention. Rightsize now because it’s good business.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-8118044418293307100?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/07/your-business-needs-to-rightsize.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-1995385455652471679</guid><pubDate>Mon, 11 Jul 2011 14:33:00 +0000</pubDate><atom:updated>2011-07-11T09:30:25.748-07:00</atom:updated><title>Too much data is bad</title><description>The June 30, 2011, The Economist covers a story about “Too Much Information” and “How to cope with data overload.” At a minimum that means the folks across the pond are also realizing at some point too much data is a bad thing.  The business world is at the place where we are over run with digital stuff and it is now taking away a competitive advantage, negatively impacting customer response times and impacting our ability to be the nimble business machine honed to win.  &lt;br /&gt;&lt;br /&gt;I have been writing about this topic for years but now it is at a point that business executives need to act.  We have more technologies making more content with or without our involvement 24-7. Data volume nearly double every year and we couldn’t manage last year’s stuff efficiently. It only gets harder and something has to give. The real answer is not building bigger clouds of storage stacks. We can’t keep everything forever and there must be a prudent way to make wheat/chaff decisions about what should exist and what can be disposed of. &lt;br /&gt;&lt;br /&gt;Three things you need to think to do right now:&lt;br /&gt;1. Develop a team to start to clean up the past. Existing data needs to go away according to law and policy now.&lt;br /&gt;2. Better decisions need to be made about what comes into existence. Not everything needs to be retained. &lt;br /&gt;3. Directives that stop the wheels of progress due to FUD (Fear,Uncertainty and Doubt)should not rule the day. Fight the lawyer’s shotgun approach to preservation.  For example, if back up tapes are recycled regularly don’t stop that process if a lawsuit if filed, unless required to. &lt;br /&gt;&lt;br /&gt;Get your information house in order. Your business depends on it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-1995385455652471679?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/07/too-much-data-is-bad.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-7599073336158651595</guid><pubDate>Thu, 19 May 2011 16:35:00 +0000</pubDate><atom:updated>2011-05-19T09:45:10.693-07:00</atom:updated><title>The Three Bears Solution</title><description>Can I get rid of all that “old” information tomorrow? &lt;br /&gt;&lt;br /&gt;“My company is so full of info debris that we are no longer efficient." “Hey Randy, why can't we just get rid of everything right now and have clean servers and start fresh tomorrow?"  Seems like a wonderful idea.  After all its spring time—the perfect time for spring cleaning.&lt;br /&gt;&lt;br /&gt;Don’t hit the delete button so fast, bucko. You can’t just blow everything away tomorrow and here is why.&lt;br /&gt;&lt;br /&gt;Four compelling reasons why jail would be so not fun.&lt;br /&gt;1. I don’t want a forced roommate.&lt;br /&gt;2. I like going OUT for Asian food.&lt;br /&gt;3. I don’t do well when told when to eat, sleep, relax, exercise etc.  I like freedom.&lt;br /&gt;4. I like to travel and jail would severely limit my freedom of movement. &lt;br /&gt;&lt;br /&gt;Ok, so the law requires that records are retained.  Every business, big and small is required to retain records of their business. &lt;br /&gt;&lt;br /&gt;Four compelling business reasons why destroying everything immediately is stupid.&lt;br /&gt;1. How can you manage your day-to-day and long range business activities without records?&lt;br /&gt;2. How do you know what your business rights and obligation are if you don’t have documentation?&lt;br /&gt;3. How will you manage employees and customer relationships without something to rely upon?&lt;br /&gt;4. How will you keep managers, board members, and executives apprised of what’s going on?   &lt;br /&gt;&lt;br /&gt;Ok, so there are business reasons to manage records and have a way to access and retrieve content to run your business. &lt;br /&gt;&lt;br /&gt;The issue of over-retention of information is a major issue for most businesses today.  Way too many companies are storing too much stuff, way too long.  That equates to real money which could be better used for other business activities.  So, more is not necessarily better.  All is not tenable.  Too little is a business impediment and a legal headache waiting to happen.  So, I need a Three Bears Solution—“This pile of information is too big, this pile of information is too small.  Oh—this pile of information is just right.”  Easy in the porridge business.  Not so easy in the information management business.  &lt;br /&gt;&lt;br /&gt;So, let me help you start to think about getting your business to the place that says we have just the right amount—not too much, not too little.&lt;br /&gt;&lt;br /&gt;In order to retain the right amount of information, you first have to know what information you have, what business value it provides and the many legal, regulatory and compliance needs for the information.  Then, by considering all those inputs you can determine how long to retain the information.  As with anything, there is always an end to the value.  This explains why you shouldn’t keep everything forever.&lt;br /&gt;&lt;br /&gt;Now, I’m sure there is a whole bunch in the email system, on shared drives, on old servers, etc. just screaming to go to the info graveyard right now.  But, how can you get rid of the data that has been stored and ill-managed over time.  First, you need to do due diligence around what information exists. Second, you need to determine what information is subject to any audit, investigation or litigation preservation obligations.  In that case, the information has to continue to exist until the matter is over and lawyers say it’s OK to destroy.  Finally, you need to assess what record retention rules apply.  It gets rather complicated pretty quick, so if you have question, please don’t hesitate to ask.  Send your questions to RKahn@kahnconsultinginc.com.  Better being safe than sorry.&lt;br /&gt;&lt;br /&gt;Finally, I strongly believe in cleaning house but in today’s litigation environment you need to do it in a defensible way.  No doubt leaner running is better business.  But, innocent house cleaning can be considered “destruction of evidence”  so clean with a documented plan that is followed and blessed by the business folks and the lawyers.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-7599073336158651595?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/05/three-bears-solution.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-6025357125549302934</guid><pubDate>Tue, 19 Apr 2011 18:31:00 +0000</pubDate><atom:updated>2011-04-19T11:36:03.644-07:00</atom:updated><title>Time for Spring Cleaning</title><description>Long ago, certain Indian tribes were given plots of land out west from the Federal government because the US took their real land years earlier.  Thereafter, the Federal government realized that the land they had given out could be used for mining, grazing, extracting oil and gas and other money making ventures. So the federal government told the Indian land owners they would lease their land out for them and deposit the proceeds into accounts set up for the benefit of the Indian landowners.  Well, things didn’t go as planned. In fact, many Indians didn’t receive what they thought they should be receiving and the monies from the leases weren’t finding their way into Indian hands. So after many years of trying to get what they had coming to them, in 1996ish, the Indians decided to sue the federal government. They sued for an accounting of the monies taken in from the leases and where the money was being dispersed. The problem was that the federal government had done a really bad job at record keeping so they weren’t even sure what went where and to whom.  &lt;br /&gt;&lt;br /&gt;Let me share a civics lessons I learned in middle school — the government is here for the US people (which includes Indians) and are put in a position of trust because they are believed to be able to do right by the people of the country.  When the money didn’t come as expected the trust began to be eroded (actually the Indians trust in US had been eroded over a couple centuries pretty substantially any way).&lt;br /&gt;&lt;br /&gt;As the lawsuit got underway, what was really clear is that there was so much information which had been mismanaged over decades, piecing together what really happened was going to be a major challenge. In deed, the Wall Street Journal, a paper which focuses on business and business failures, asserted the prediction that unearthing and producing records and evidence in the lawsuit would cost in the billions just to see if anything was relevant.  &lt;br /&gt;&lt;br /&gt;Let me share lessons learned from our consulting practice. If you don’t start cleaning info crud up, you fail to be as efficient a business as you can be and run a huge risk if a lawsuit or audit happens. &lt;br /&gt;&lt;br /&gt;Back to our saga.  Years go by, and the government gets lambasted for record keeping failure after record keeping failure of various kinds by the court. High-level government officials are held in contempt, get wacked for gross mismanagement, security failures etc. &lt;br /&gt;&lt;br /&gt;After roughly 17 years of litigating the case is about to settle for around 3 billion dollars. &lt;br /&gt;&lt;br /&gt;Seems like bad business all around. &lt;br /&gt;&lt;br /&gt;Spring cleaning time folks. Get serious about cleaning over retained records. If you don’t know where to start, call us.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6025357125549302934?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/04/time-for-spring-cleaning_3135.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-3363969973273613371</guid><pubDate>Tue, 15 Mar 2011 16:16:00 +0000</pubDate><atom:updated>2011-03-15T09:22:12.994-07:00</atom:updated><title>Records speak for themselves</title><description>Peter king, the Congressman that heads up the Homeland Security Committee, is preparing for hearings to evaluate the threat and security risk presented by the American Muslim community.  Seems prudent as Muslims seem to be the only folks blowing themselves up the world over on a daily basis to kill, maim and scare. Muslims from many places around the world hate America and have acted to kill us and would act again if given the chance.  Seems like there are innumerable data points to suggest that King’s efforts are prudent. That doesn’t mean that all Muslims are terrorists. Rather it means that there are enough data points to evaluate the risk posed by the community.&lt;br /&gt; &lt;br /&gt;Then I read the WSJ story about this issue. According to the report the Obama administration’s deputy national security adviser apparently attacked Congressman King’s hearings stating to a group of Muslims “…and let’s remember that just as violence and extremism are not unique to any faith…”  That’s true but there is overwhelming information that there are radical Muslims in every corner of the globe willing to take on and/or take out the Judeo-Christian heritage.   I’m a student of history and I’m not a fan of Political Correctness.   Let the records of the past 10 years speak for themselves. Records record. Evidence Provides. Political Correctness denies.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-3363969973273613371?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/03/records-speak-for-themselves.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-443233999461975918</guid><pubDate>Tue, 01 Mar 2011 20:07:00 +0000</pubDate><atom:updated>2011-03-01T12:08:00.377-08:00</atom:updated><title>Cleaning house is good but know when to stop.</title><description>As I have written about many times, even predating the Massey mines disaster that killed 29 miners last year, there are so many record keeping issues that are part of the mining industry.  From the government database tracking mining disasters, to documenting safety infractions, record keeping is central to getting it right and reporting on what went wrong. But let’s leave that for a moment to talk about the latest developments in the Massey mine saga. &lt;br /&gt;The security chief at Massey was indicted yesterday for covering stuff up, including destroying safety records after the 29 miners were killed.  I’m not sure whose bright idea it was to “clean house” allegedly nefariously (AKA destroying evidence, or spoliation) after the guy, the company, or both knew they were in deep dodo.   One thing is clear, when cleaning house happens to cover your tracks when you know (or reasonable should anticipate) there will be lawsuits or government investigations or both, that is the time to not destroy anything. Unless of course you are desirous of having a new boy friend and a limited meal plan while doing time.  &lt;br /&gt;Interestingly, in the case the General Counsel of Massey claimed that they advised the U.S. attorney's office “within hours of learning that documents” had been destroyed “and took immediate steps to recover documents and turn them over to the U.S. attorney's office."  &lt;br /&gt;&lt;br /&gt;Lessons-- Have retention rules that allow you to clean house. Cleaning house is good cause it gets rid of the crud to allow you to be a more efficient business. However, at the first smell of trouble stop cleaning house and preserve everything that may be potentially relevant if you have a lawsuit, investigation or audit coming.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-443233999461975918?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/03/cleaning-house-is-good-but-know-when-to.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-2968778201674463705</guid><pubDate>Fri, 25 Feb 2011 17:36:00 +0000</pubDate><atom:updated>2011-02-25T09:42:25.142-08:00</atom:updated><title>Let Employees Park Their Data Where They Want?</title><description>Face it,  employees don’t really care about records management.  They believe it is somebody else’s problem. After all, it isn’t in their job description and it doesn’t make money - right?  &lt;br /&gt;&lt;br /&gt;The saying, “don’t try to put a square peg in a round hole” holds true when trying to park or store corporate information.  Employees want the flexibility and user interface that SharePoint offers, so why fight it?  Forcing employees into a rigid, non-friendly records management storage environment will only cause them to squirrel away data into their own storage environments such as hard drives, removable media, home PCs, etc.  Let them use SharePoint if they want to - just get the right governance and controls in place behind the scene, upfront.  It is better to give employees the environment they want, and are willing to use, then to force them to go underground with their data.   Records management governance can be practically transparent to the end user in SharePoint, if done correctly.  The employee gets the environment they want and the corporation gets the governance they want.  Both win!  &lt;br /&gt;&lt;br /&gt;Brightstarr has partnered with Kahn Consulting, an industry leader in information management, to aid corporations in the use of SharePoint as their records management tool of choice.  Let us help you manage your SharePoint environment to meet compliance requirements and give your employees an environment they love to work in.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2968778201674463705?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/let-employees-park-their-data-where.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4378315538417641622</guid><pubDate>Thu, 17 Feb 2011 22:45:00 +0000</pubDate><atom:updated>2011-02-17T14:46:10.995-08:00</atom:updated><title>Information Flows</title><description>Information flows. Sometimes really fast. Sometimes it causes waves that are unintended and even seriously problematic. For example, email was never intended to be the business medium of choice for all business for all reasons. I’m sure no one ever thought that secret email communiqués from Arabian leaders supporting the US taking military action against Iran’s nuclear facilities would be disclosed. Wikileaks has made many government officials blush about many secrets sent in email form. Thus there is fall out. Ok, Enough of that.&lt;br /&gt;&lt;br /&gt;I came up with a really great idea. Tell me what you think. I was going to advance an idea that changes the world with Twitter or FaceBook or any of the social networking sites. I was going to call it “Social Networking Overthrowing Totalitarianism” or “SNOT” for short.  That way a few people in lands where leaders are not democratically elected can overthrow the bums. But wait, is the whole world ready for democracy? Do they really aspire for that type of freedom? Is the guy that stepped down actually a  bum? Maybe he is way better than what will be coming. Overthrowing a “life-long” president, for example, doesn’t mean that democracy rings out all over.  &lt;br /&gt;&lt;br /&gt;Recently we failed to support our friend in Egypt and due to pressure “from the street” he was forced to step down. Remember he was our friend for years. We gave him billions of dollars in military support and some of our military technology. Now Egypt has the military running the show. A step forward?   &lt;br /&gt;&lt;br /&gt;When or if they have an election in Egypt, what if the Muslim Brotherhood is elected “fair and square?” What if another terrorist organization uses the democratic process to gain power so they could impose Sharia  (Islamic law) on everyone. Maybe they will countenance the continued harassment and killing of the Coptic Christians.   If it happens I guess I could change the name of my organization to “Social Networking Overthrowing Theocracy” or “Social Networking Overthrowing Thugs”.&lt;br /&gt;&lt;br /&gt;Nuts. I just realized the Arab world is on fire in places like Bahrain, Syria, Iran all because information is flowing way too fast.  Now maybe my organization is moot. I am so last week.  &lt;br /&gt;&lt;br /&gt;Yikes.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4378315538417641622?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/information-flows.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4235155984390543754</guid><pubDate>Fri, 11 Feb 2011 16:20:00 +0000</pubDate><atom:updated>2011-02-11T08:28:33.404-08:00</atom:updated><title>Plan, anticipate and deal now.</title><description>My mantra for every new technology used in the business context is that there will be employees that misuse the technology or otherwise create liability or a major headache or both. Years ago I wrote about an employee who used the company email system to rank on his employer, more specifically his boss. For his efforts the guy was fired. Thereafter the fired employee sued. Because the business was unionized the union argued that the employees bashing was “protected” within the meaning of the labor relations laws. The employee won and the company had to reinstate the fired employee. &lt;br /&gt;&lt;br /&gt;Fast forward to today. Imagine an employee bashing his boss on FaceBook or some other social networking site. Imagine no more. The case has already happened and the guy got canned for doing the same thing. &lt;br /&gt;&lt;br /&gt;Well, taking the conversation out of the union context for a moment. Before every new technology is allowed at work, policy should already be in place to regulate the employees conduct. If you don’t address it upfront, I am sure you will be force fed the failure not too far down the road. &lt;br /&gt;&lt;br /&gt;Plan, anticipate and deal now.  Issues of information control, proper use of company technology, location of company records, and now third party technology are the issues of the day.  Deal now before you learn the hard way.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4235155984390543754?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/plan-anticipate-and-deal-now.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-6756887404948428065</guid><pubDate>Thu, 10 Feb 2011 21:57:00 +0000</pubDate><atom:updated>2011-02-10T14:10:32.310-08:00</atom:updated><title>Heed the lessons</title><description>While some might question the journalistic legitimacy of Al Jazeera anyway, they are now “leaking” documents of the peace process between Israel and Palestinian Arabs. One could argue that they are engaged in partisan politics to undermine the Palestinian authority in much the same way that Wikileaks did when they disclosed that Arab governments worried about a nuclear Iran as much as the west.  In any event, is information dumping now the way journalism will evolve or will real media outlets take the higher road to responsible journalism? But that’s not really what I wanted to tell you. What I wanted to remind you is that more information fits into smaller places making taking it that much easier. So when trying to protect your corporate secrets, better heed the lessons of leaks and dumps — manage information like it’s an asset and expect that others want your assets.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6756887404948428065?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/heed-lessons.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4922606245801232959</guid><pubDate>Thu, 10 Feb 2011 15:44:00 +0000</pubDate><atom:updated>2011-02-10T07:49:01.970-08:00</atom:updated><title>Destruction of Evidence</title><description>A nascent IT guy says to his colleague “Hey, these lawyers have their shorts in a bundle over this e-discovery thing. Besides I am not sure what destruction of evidence looks like.”  The colleague giggles and says it’s like pornography, you will know when you see it” Are you sure, mutters nascent IT guy”.&lt;br /&gt;&lt;br /&gt;Let me help&lt;br /&gt;&lt;br /&gt;On February 9, the Wall Street Journal reported about ongoing insider trading scandal. According to the article one note stated “Just go into office…shred as much as u can”. The missive was sent by instant messaging.  Well that would clearly be destruction of evidence if you had an obligation to preserve for a imminent or pending legal matter.&lt;br /&gt;&lt;br /&gt;Then the article states “One of them allegedly ripped up his computer drives with pliers after the reading the Wall Street Journal report on the probe”.  Ok, there is a imminent legal problem and that would be destruction or attempted destruction.&lt;br /&gt;&lt;br /&gt;The fund manager who destroyed the computer later dumped the pieces in four separate garbage trucks around New York”…  Does not look as it related to intent, now does it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4922606245801232959?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/destruction-of-evidence.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-1605588817446722342</guid><pubDate>Mon, 07 Feb 2011 20:57:00 +0000</pubDate><atom:updated>2011-02-07T13:02:19.665-08:00</atom:updated><title>Internet records as potential evidence</title><description>As all sorts of internet records are reviewed as potential evidence in the government’s prosecution of Jared Loughner for his heinous assault in Arizona that killed 6 including a small child, a judge and seriously wounded a special Congresswoman and others, the other side is preparing to defend this obvious criminal (yeah, yeah I know, we are innocent until proven guilty). Also interesting is the lawyer he was appointed free of charge, to undermine the evidence and defend Loughner (we do have a great country indeed), is Judy Clark who also represented the Unibomber and Sept. 11 criminal, Moussaoui.   I sure hope the evidence is strong and the trial swift.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-1605588817446722342?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/02/internet-records-as-potential-evidence.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-2685296001495668455</guid><pubDate>Mon, 31 Jan 2011 19:36:00 +0000</pubDate><atom:updated>2011-01-31T11:45:32.216-08:00</atom:updated><title>You just can't keep it all forever.</title><description>The January 17, 2011, NY Times article entitled, “In New Military, Data Overload Can Be Deadly” makes a point I try to make almost every day to some business executive. More information is not necessarily better and at some point the law of diminishing returns applies. If you have so much information, finding the needed nugget or digesting the salient stuff from the crap is near impossible. Information needs to be born, be used and die at some point to make room for more important timely information. In essence information has a life cycle. Problem is many don’t actually believe that most information needs to die at some point. They cling to the misguided notions that storage is cheaper and search tools are more and more powerful. All true, but they both miss the real point. You can’t keep everything because there are all sorts of soft and hard costs that impact the bottom line of business well beyond storage costs per gigabyte.  Also, search tools while more capable, are not the panacea because they can’t traverse complex systems and hundreds of file types without challenge no matter what anyone tells you.  A soldier is manning a drone in Afghanistan from his cubicle in Arizona. Some innocent citizens die and now the military says that it is because of information overload. SO, keep what you need to and get rid of the crud. Bigger is not always better.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2685296001495668455?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/01/you-just-cant-keep-it-all-forever.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-5219913410903715247</guid><pubDate>Fri, 28 Jan 2011 16:01:00 +0000</pubDate><atom:updated>2011-01-28T08:16:45.658-08:00</atom:updated><title>I had a dream . . .</title><description>I had a dream that I wanted to share with you to see if you could help me interpret it. I was a big and important electronic record and was given a archive home in a white fluffy thing floating in the sky. I was provided a home with other documents from all over the place which had no relationship to me or my parents but we lived next door to each other anyway. I am not sure why?  I was given my home, which was pretty spartan, because I guess we paid very little for me to stay there. So I guess it’s not that weird my digs were not so special and I shouldn't complain. Anyway, at some point I was needed to be returned and fast because there was something important going on, in front was a guy with a black cloak with a mallet that he uses to make sure people are quiet. The thing was, no one was available to find me because that’s not what they do. So, I sat and sat and many people were very upset and I felt bad about that, but what could I do? I sat in my fluffy archive in the sky which wasn’t really in the sky after all, but rather in Europe somewhere, and I couldn't make it home even if they were so excited to see me. They told me later there was “private” information in me and the Europeans wanted to protect me from disclosure. So I sat and sat and never made it to that important place. I guess they call it a court. &lt;br /&gt;&lt;br /&gt;What do you think it means?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-5219913410903715247?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/01/i-had-dream.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-7514753976842782394</guid><pubDate>Thu, 27 Jan 2011 16:30:00 +0000</pubDate><atom:updated>2011-01-27T08:35:31.472-08:00</atom:updated><title>It is a record upon creation.</title><description>Often I’m asked about what records to keep based on how they may play in court. Records are neither good nor bad. They simply document what happened. Make decisions about what to retain based on business need for them and legal requirements that tell you to retain them. In a recent revelation, the Catholic church disclosed there was a 1997 letter from the Vatican to the Irish bishops advising them to refrain from reporting all cases of sexual abuse of children to the police. For the church the record, now evidence, is painful. For the families seeking to get compensation for the molestation of their children, the record is manna from heaven. &lt;br /&gt;&lt;br /&gt;A records is determined to be a record at the time of creation. Don’t anticipate its use down the road. Retain or not based on business use and legal mandate,PERIOD.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-7514753976842782394?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/01/it-is-record-upon-creation.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-493961241382898247</guid><pubDate>Tue, 25 Jan 2011 18:06:00 +0000</pubDate><atom:updated>2011-01-25T10:08:26.272-08:00</atom:updated><title>Dialoginars are here!</title><description>Dialoginars are a great new way to learn about a variety of enterprise content management topics.   The first of ten Dialoginars which feature Randy Kahn and IBM is now available on IBM’s website at &lt;a href="http://www.ibm.com/software/ilg/dialoginars"&gt;www.ibm.com/software/ilg/dialoginars&lt;/a&gt;.  In this Dialoginar you will learn how you can use information as an asset in your organization.  Check back with us on a regular basis to see future Dialoginars that will feature a new topic each month.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-493961241382898247?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2011/01/dialoginars-are-here.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4130756721716573962</guid><pubDate>Thu, 16 Dec 2010 16:30:00 +0000</pubDate><atom:updated>2010-12-16T08:52:32.503-08:00</atom:updated><title>Dialoginar #1 - Content Analytics</title><description>I am the host of “Dialoginar”. It is great way to learn more about Information Lifecycle Governance. Check it out and tell me what you think. Topic one will explore Content Analytics.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www14.software.ibm.com/webapp/iwm/web/signup.do?source=swg-Dialoginar"&gt;Dialoginar #1 - Content Analytics&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4130756721716573962?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2010/12/dialoginar-1-content-analytics.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-3716376185620959714</guid><pubDate>Fri, 03 Dec 2010 19:51:00 +0000</pubDate><atom:updated>2010-12-03T12:18:11.329-08:00</atom:updated><title>What's a Dialoginar?</title><description>I have spoken far and wide, long and short, here and there, but I have never done a Dialoginar.  Well, I am doing an amazing Dialoginar Series where I play an expert and explore some interesting Information Lifecycle Governance topics. In the near future you will see a YouTube advertisement in which I play a superhero jib jab bobble head and tell you all the fun facts about the Dialoginars. BTW- a bobble head is perfect role for me.  The Dialoginar is a great way to learn and have fun while doing it.  So, bring your lunch, bring your friends, bring your coworkers, but leave your bad attitude in your cubicle. A Dialoginar tastes great and it's less filling. Can I say that or will that cause a problem with my favorite Wisconsin brewer?&lt;br /&gt;   &lt;br /&gt;Topics that will be discussed in the initial Dialoginar Series are:&lt;br /&gt;&lt;br /&gt;Content Analytics Compliance refers to the text analytics process plus the ability to visually identify and explore trends, patterns, and statistically relevant facts found in various types of content spread across internal and external content sources.  &lt;br /&gt;&lt;br /&gt;Defensible Disposal – How do companies develop the policy rules to defensibly dispose of information? The only way to purge content is to dispose of it pursuant to written retention policies which take into consideration business needs, legal requirements and legal considerations like statues of limitations.&lt;br /&gt;&lt;br /&gt;Information Lifecycle Governance is a way of managing information over time with the necessary controls to advance good business practices.  ILG encompasses policies, processes, practices, and technology used to manage information throughout its life starting with creation and ending with proper disposal.&lt;br /&gt;&lt;br /&gt;These are just a few of the topics to be discussed in a series of quirky “Dialoginars” to be presented by Randy Kahn and IBM.  Prepare to be educated and entertained in a unique approach to the discussions of everything Information Governance.  Keep your eyes open for upcoming dates and times!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-3716376185620959714?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2010/12/its-dialoginar.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-6086388287223846436</guid><pubDate>Mon, 29 Nov 2010 21:03:00 +0000</pubDate><atom:updated>2011-01-28T09:40:12.931-08:00</atom:updated><title>Information Storage Governance</title><description>You can store if you believe Wendy.&lt;br /&gt;&lt;br /&gt;Attention all storage dudes and dudettes;&lt;br /&gt;&lt;br /&gt;You can keep ALL your corporate data forever, park it anywhere, even “float” it on a “Cloud”, not worry about accessing or finding it again, and the world and mostly your business will be a beautiful and productive place. Try again Storage Wendy. &lt;br /&gt;&lt;br /&gt;For our 10 Truism to decide your fate and this full blog please view it at: &lt;a href="http://searchstorage.techtarget.com/generic/0,295582,sid5_gci1526435,00.html"&gt;www.TECHTARGET.com&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;So Wendy, do you still want to fly?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6086388287223846436?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2010/11/information-storage-governance.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-4190485062245262280</guid><pubDate>Fri, 19 Nov 2010 20:07:00 +0000</pubDate><atom:updated>2010-11-19T12:11:11.707-08:00</atom:updated><title>Information management matters.</title><description>Are you sitting in your cubicle trying to justify your job and get a little budget for next year? As you contemplate your future you go the place that is most familiar. You immediately think about how much your company could save by applying retention to the mass of boxes stored on-site and off-site and getting rid of the extra boxes. Don’t waste your time—that is not really what the guys and gals who run your business care about.&lt;br /&gt;&lt;br /&gt;On a totally separate random note, I was reading the Wall Street Journal this morning and saw an article entitled “Insurers Test Data Profiles To Identify Risky Clients.”  It seem that life insurers are analyzing all the personal data being collected on-line and elsewhere to evaluate how long we will live. You see the whole life insurance business is tied to longevity. The longer we live, the more the life insurance company makes because we pay more premiums and they get to use our money longer before death.&lt;br /&gt;&lt;br /&gt;Oh. So better information management matters.  I see.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4190485062245262280?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2010/11/information-management-matters.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6791672639619957449.post-8533873084106317480</guid><pubDate>Wed, 17 Nov 2010 22:00:00 +0000</pubDate><atom:updated>2010-11-17T14:11:27.437-08:00</atom:updated><title>Free records and national security</title><description>One of the big strategic agenda items of President Obama was to make government more transparent.  One of the ways government is more transparent is by making more records of its actions accessible to the public. Of course, government always has to balance our national security against the public’s desire to know more. More about that in a minute. &lt;br /&gt;The New York Times covered the story of the Justice department’s 4 year attempt to keep a 600 page report about US governmental post war collaboration with certain Nazi’s and invitations for Nazis to come to America. The report has been written for a long time but not made public or even disclosed. So someone apparently sued to get access to the report which was eventually made available in highly redacted (blacked out) form.  &lt;br /&gt;As the WWII has been over for more than a half century, it seems rather questionable that there can be anything of a “national security” interest still in the document that requires protection. No doubt there is tons of stuff that is embarrassing, but I don’t think that is criteria for keeping something secret.&lt;br /&gt;Anyway, if our government’s invited former Nazi’s military leadership here to run missile programs or help with other military initiatives, then “transparent government” may dictate such information is disclosed, absent real national security interest requiring protection.  &lt;br /&gt;But this American says, if transparency is the desired result, absent real national security interest, then let the records be free.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-8533873084106317480?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</description><link>http://infonation.kahnconsultinginc.com/2010/11/free-records-and-national-security.html</link><author>noreply@blogger.com (Kahn Consulting, Inc.)</author><thr:total>0</thr:total></item></channel></rss>
