Best Practices for Archiving Old Wiki Content

[Ed Schriger]

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.

[Midori · Accepted solution]

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.

[Darin - Opus Guard]

@Ed Schriger following up here as this is a good topic and still relevant. In terms of best practices, I wrote some content in our knowledge base around the importance of information governance. It's a worth while read. The importance of information governance 

In Confluence Cloud there's no longer the ability to set global retention policies, however, many apps have come to Atlassian Marketplace including Content Retention Manager for Confluence as a means to make it easy to declutter, save space, and remain compliant (ISO/SOC2) by having a means to enforce data retention policies. Also of note, in Confluence Cloud archived content still counts against your storage limits, and in terms of compliance with information governance, content is still considered discoverable until fully purged. 

[SimonS]

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