You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
Hi Ed,
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.
-Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.