http://www.endusersharepoint.com/STP/ SharePoint QA en Fri, 28 Aug 2009 05:18:40 +0000 http://www.endusersharepoint.com/STP/topic/versioning-content-approval-archiving#post-7034 Mon, 25 May 2009 23:09:29 +0000 laura67 7034@http://www.endusersharepoint.com/STP/ <p>I don't know the answer to that off the top of my head. I recommend trying it out in a test doc library, so you'll know exactly what happens.</p> <p>Laura </p> http://www.endusersharepoint.com/STP/topic/versioning-content-approval-archiving#post-7026 Mon, 25 May 2009 04:54:39 +0000 genet 7026@http://www.endusersharepoint.com/STP/ <p>Thanks for the good advice! I have a further related question :</p> <p>We have content approval set on all the document libraries that have major and minor versioning activated. However, people are not always taking the trouble to publish a major version, with the result that a lot of the documents are "Draft" when they should be "Approved".<br /> If I were now to set the versioning to say keep 5 major versions and drafts for 5 major versions, what would happen to these Draft documents? Would they be lost because they are not major versions?</p> <p>Hope my question makes sense! </p> http://www.endusersharepoint.com/STP/topic/versioning-content-approval-archiving#post-6476 Fri, 08 May 2009 15:24:54 +0000 laura67 6476@http://www.endusersharepoint.com/STP/ <p>If you have MOSS, there's a feature called "Information management policy settings" on each library, that has an "Enable Expiration" feature that you can enable. This can be used not only to just delete items when they expire, but instead, you can create a SPD workflow that physically moves the documents, and set this policy to run that workflow to move the documents to a central storage place once they've been in there a certain amount of time.<br /> Oh, and I recommend setting the versioning to a finite number of versions, instead of just infinite (blank).</p> <p>Laura Rogers<br /> <a href="http://spinsiders.com/laurar" rel="nofollow">http://spinsiders.com/laurar</a> </p> http://www.endusersharepoint.com/STP/topic/versioning-content-approval-archiving#post-6451 Fri, 08 May 2009 08:24:33 +0000 eric 6451@http://www.endusersharepoint.com/STP/ <p>That is correct about versioning, each version is a separate document. COntent approval doesn't add any additional storage, it's just a means of forcing an approver group to sign off on the document before it's visable to all.</p> <p>Archiving will take care of itself if you trim down the number of versions it keeps, older versions get deleted automatically when the version cap is reached. </p> http://www.endusersharepoint.com/STP/topic/versioning-content-approval-archiving#post-6450 Fri, 08 May 2009 06:14:44 +0000 genet 6450@http://www.endusersharepoint.com/STP/ <p>I have recently heard that Versioning takes up a lot of space because each version is saved as a separate document - is this true, and does Content Approval also somehow take up more space?</p> <p>Related question : should we be looking at some sort of archiving solution if we do want to have versioning on most of our document libraries? </p>