I am looking for any guidelines or documented best practices for archiving old or out of date wiki content. We want to keep it in our OnDemand environment, but want to minimize storage, minimize confusion by eliminating it from searches, etc.
Any tips or links would be appreciated.
This is a great write up on the topic: http://sivupoluilla.fi/2011/08/managing-content-in-confluence-archiving-and-retention-policies/
Please note that it rather focuses on keeping the content fresh than minimizing the storage space requirements.
The other problem is that the Archiving Plugin suggested in that article is not currently available at OnDemand, only in in-house hosted Confluence instances.
One thing you could do is restrict the outdated spaces/pages to a select few users, or no users at all. This would remove the content from search results but leave it there for an administrator to access if they needed to.
This would have no impact on storage size, though. Content would have to be deleted outright to decrease the storage footprint.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG