<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx</link><description>Now that we've given you an overview information management policies in Office SharePoint Server 2007, we can (finally) dive into one of the most important records management features controlled via policies -- expiration. As mentioned in the last few</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#653159</link><pubDate>Sat, 01 Jul 2006 07:43:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:653159</guid><dc:creator>DLV</dc:creator><description>Dear Ethan Gur-esh,&lt;br&gt;&lt;br&gt;First I wish to congratulate you and your team for bringing Records Management out of the closet and into the mainstream by the effect of Microsoft joining the cause and also for making your thoughts and principles related to RIM to the passionate masses via the web blog.&lt;br&gt;&lt;br&gt;In your latest posting you state - Perform an automated “action”: For many types of content, disposition can be fully automated. For example, the item can be deleted from the system without any human involvement. &lt;br&gt;&lt;br&gt;I have a major problem with this concept. WHY? Because disposition requirements may change or need to be updated over time, an automated disposition process may cause legal, moral or historical implications. In my RIM world I would always, and without exception requires a manual process so that I can receive a document of what is to be disposition so I can have senior management sign off on the action. It is not my decision to disposition certain data at a certain times but a corporate one [as an RIM manager I may be delegated the authority to advise on the disposition process but I would never sign off personally due to legal implications if I made the incorrect decision]. Senior executive level and possibly the legal department need to sanction an action not the RIM system or the RIM manager.&lt;br&gt;&lt;br&gt;On a second matter: The promotion of classification as a desirable process has been highlighted on several occasions in the blog postings but to date no specifics. Will you be addressing the matter soon? I vote with you in your statement - Because we believe classification is a critical component to the success of any records management system, we’ve enabled a number of other features like record filing and reporting, that help process your records or help you identify if anything is out of policy. - I would go further and state that without a Business Classification Scheme - BCS in place no and I mean NO [in the strongest terms] RIM system can be successful.&lt;br&gt;&lt;br&gt;Third matter: I see no mention of ISO 15489 pars one and two in any of your blog posts. What is Microsoft’s position in the support or otherwise to the International Bible for RIM in its product offerings? ISO 15489 to my knowledge is now available in Italian, French, and German and of course English plus I understand it is being translated for Russian &amp;amp; Chinese. ARMA of the USA and Canada are supporters of the standard so it would be of interest that the Microsoft offerings are at least cognisant of the principles and guidelines espoused in ISO 15489.&lt;br&gt;&lt;br&gt;My 2 cents worth!&lt;br&gt;&lt;br&gt;Laurie Varendorff ARMA&lt;br&gt;</description></item><item><title>re: Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#654787</link><pubDate>Mon, 03 Jul 2006 04:06:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:654787</guid><dc:creator>Hef</dc:creator><description>I'll respond to Laurie's 1st point. &amp;nbsp;In a post-Enron world legitimate disposal of records at the 1st opportunity is a way to reduce the costs and risks associated with discovery. Retaining records for other than legal purposes such as cultural or historical interest becomes an active pursuit rather than the default. &amp;nbsp;Where possible, automatic disposal is essential to deal with the very large volumes of electronic documents that may occur. &amp;nbsp;Unnecessary retention creates a litigative risk that most companies will avoid. &amp;nbsp;Changes that affect disposal will need to be reflected in the disposal system, and a feature I would like to see is a workflow for reviewing disposal classes. &amp;nbsp;There is also a metadata issue with disposal - the legislative basis of a disposal class needs to be in the metadata, to allow tracking changes in the legal environment. &amp;nbsp;&lt;br&gt;&lt;br&gt;Of course, organizational policies may be needed to set who approves the disposal actions when the system is implemented and maintained, but it would seem to me that automatic disposal would lead to a significant productivity gains, although my experience in government is that this would be hard to justify on an ROI basis, as disposal action on physical records tends only to be taken when it becomes a major problem due to storage overflow or a significant legal action, and is otherwise not resourced.&lt;br&gt;&lt;br&gt;As an example, on government agency I worked for handled 40,000 emails per hour (Not counting emails that were spam filtered). &amp;nbsp;Now, using a rough guess as to how many were records (1% seems reasonable, but it could vary) that's 400 emails per hour which should be captured as records. &amp;nbsp;Assume an 8 hour day (more like 10 in that organization), 3200 a day, assuming 250 working days per year that's 800,000 per annum. &amp;nbsp;I don't even want to think about listing these in anything other than an electronic form, and the sooner that volume is reduced the better, as that 800,000 becomes a rich hunting ground for lawyers during discovery, the media during Freedom of Information requests, and a tremendous burden in terms of indexing. And in all likelihood, most will never be referred to after a month or two.&lt;br&gt;&lt;br&gt;During discovery records are assigned a hold - disposal should cease with the discovery order. &amp;nbsp;A possibility is to stream records for disposal into 2 streams, the 1st being those that have never been accessed, and the 2nd those with some level of access. &amp;nbsp;That would highlight those that are more likely to be of some significance, and perhaps should be the subject of further review. &amp;nbsp;All of this is possible, provided the metadata design is decent and logs are available. &amp;nbsp;When volumes are high automation is essential, otherwise we end up with organizations staffed with 5% records staff. &amp;nbsp;&lt;br&gt;&lt;br&gt;Cheers&lt;br&gt;Hef&lt;br&gt;pcheffNOSPAM@internode.on.net</description></item><item><title>re: Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#663959</link><pubDate>Thu, 13 Jul 2006 04:54:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:663959</guid><dc:creator>recman</dc:creator><description>&lt;P&gt;@ DLV: &lt;BR&gt;&lt;BR&gt;Laurie, &lt;BR&gt;&lt;BR&gt;Firstly, thank you for your warm congratulations on our product and our blog... it's always great for our team to hear. &lt;/P&gt;
&lt;P&gt;Regarding your questions/feedback: &lt;BR&gt;&lt;BR&gt;1. About "automated disposition": I completely agree that in many circumstances automated disposition isn't appropriate, and I apologize if this posting didn't adequately stress that. It's exactly for that reason that we've enabled our expiration policies to use human-centric workflow processes to manage record disposition, in addition to the automated approach. And of course, in all cases a RIM program's dispositions must always be sanctioned by the appropriate executives &amp;amp; legal departments. &lt;BR&gt;&lt;BR&gt;2. Classification: We will be getting into the details of classification soon (beyond what we've already discussed with Content Types). We know that community is waiting to hear more about classification, but we've got many concepts to cover in the overall story of RIM in Office 2007 and want to adequately cover each before moving onto the next. But please stay tuned! :) &lt;BR&gt;&lt;BR&gt;3. About ISO 15489: While we haven't mentioned it directly on this blog yet, we're very much aware of and in favor of ISO 15489. Having an ISO-ratified standard for records management practices was an important event in the discipline of records management, and we certainly took the principles &amp;amp; best practices of that standard into account when designing Office 2007. It's my hope that as we continue to talk about RIM in Office 2007 that it becomes evident how the functionality in our product aligns with ISO 15489. (So again, please stay tuned!) &lt;BR&gt;&lt;BR&gt;Thanks, &lt;BR&gt;- Ethan Gur-esh, Program Manager&lt;/P&gt;</description></item><item><title>re: Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#663965</link><pubDate>Thu, 13 Jul 2006 05:01:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:663965</guid><dc:creator>recman</dc:creator><description>@ Hef:&lt;br&gt;&lt;br&gt;Thanks for the comment/response! I couldn't have made the case for automated disposition in a RIM program better myself. :)&lt;br&gt;&lt;br&gt;- Ethan Gur-esh, Program Manager </description></item><item><title>2007 MOSS Resource Links (Microsoft Office SharePoint Server)</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#687693</link><pubDate>Thu, 03 Aug 2006 19:11:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:687693</guid><dc:creator>The Boiler Room - Mark Kruger, SharePoint MVP</dc:creator><description>Here is an assortment of various 2007 Microsoft Office SharePoint Server Documentation / Reference Materials...</description></item><item><title>Sharepoint 2007: Document/Records Management resource list V0.1</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#733122</link><pubDate>Thu, 31 Aug 2006 11:14:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:733122</guid><dc:creator>Arno Nel 2.0</dc:creator><description>Planning Plan document management Chapter overview: Plan document management What is document management?</description></item><item><title>Physical Records Management in the 2007 Office system</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#793076</link><pubDate>Thu, 05 Oct 2006 11:00:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:793076</guid><dc:creator>Microsoft Records Management Team Blog</dc:creator><description>&lt;p&gt;So far in this blog, we’ve talked directly about electronic records – the files created in document authoring&lt;/p&gt;
</description></item><item><title>E-mail Records Management, Part 3: E-mail Retention</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#1485975</link><pubDate>Thu, 18 Jan 2007 03:56:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1485975</guid><dc:creator>Microsoft Records Management Team Blog</dc:creator><description>&lt;p&gt;In my previous post , I described how organizations can define a set of e-mail classifications (i.e.&lt;/p&gt;
</description></item><item><title>Sharepoint 2007 Document and Records Management resource List (update)</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#5263866</link><pubDate>Wed, 03 Oct 2007 18:17:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5263866</guid><dc:creator>Mirrored Blogs</dc:creator><description>&lt;p&gt;Document and Records Management Definition Document Management According to Wikipedia : &amp;amp;quot;A document&lt;/p&gt;
</description></item><item><title>2007 MOSS Resource Links (Microsoft Office SharePoint Server)</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#6151774</link><pubDate>Mon, 12 Nov 2007 23:46:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6151774</guid><dc:creator>The Boiler Room - Mark Kruger, Microsoft SharePoint MVP</dc:creator><description>&lt;p&gt;2007 MOSS Resource Links (Microsoft Office SharePoint Server) Here is an assortment of various 2007 Microsoft&lt;/p&gt;
</description></item><item><title>Sharepoint 2007 Document and Records Management resource List (update)</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#8783794</link><pubDate>Mon, 28 Jul 2008 14:29:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8783794</guid><dc:creator>Arno Nel 2.0</dc:creator><description>&lt;p&gt;Document and Records Management Definition Document Management According to Wikipedia : &amp;amp;quot;A document&lt;/p&gt;
</description></item><item><title> Microsoft Records Management Team Blog Records Management Feature | Paid Surveys</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#9654670</link><pubDate>Fri, 29 May 2009 19:48:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9654670</guid><dc:creator> Microsoft Records Management Team Blog Records Management Feature | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?title=microsoft-records-management-team-blog-records-management-feature-2"&gt;http://paidsurveyshub.info/story.php?title=microsoft-records-management-team-blog-records-management-feature-2&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Microsoft Records Management Team Blog Records Management Feature | fix my credit</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#9763990</link><pubDate>Wed, 17 Jun 2009 04:43:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9763990</guid><dc:creator> Microsoft Records Management Team Blog Records Management Feature | fix my credit</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://fixmycrediteasily.info/story.php?id=12007"&gt;http://fixmycrediteasily.info/story.php?id=12007&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Microsoft Records Management Team Blog Records Management Feature | alternative dating</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#9767586</link><pubDate>Wed, 17 Jun 2009 10:13:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9767586</guid><dc:creator> Microsoft Records Management Team Blog Records Management Feature | alternative dating</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://topalternativedating.info/story.php?id=13788"&gt;http://topalternativedating.info/story.php?id=13788&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Records Management Feature: Expiration Policies</title><link>http://blogs.msdn.com/recman/archive/2006/06/29/651347.aspx#9942202</link><pubDate>Wed, 30 Dec 2009 08:14:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9942202</guid><dc:creator>Hussein Ahmad</dc:creator><description>&lt;p&gt;after expiration, the disposition approival triggers.&lt;/p&gt;
&lt;p&gt;what happens when i select &amp;quot;retain this item&amp;quot;. would this renew the expiration policy again, so lets say if it is a year, then this will renew the item with 1 more year ?&lt;/p&gt;
</description></item></channel></rss>