It may sound counter-intuitive, but it would allow complex 2-phase processes like:
Source: https://community.atlassian.com/t5/Confluence-questions/Solution-for-automated-trash-purging/qaq-p/689230
We'd love to see a config option to enable the archive plugin to run on archived spaces, for the purposes of trashing content.
Context: As we considered our options for cleaning up dupe data, we checked if we would be able to run a separate configuration only on archived spaces, to trash their content after an even longer period of time passed; thus, eventually removing the complication of duplicate content and data overflow. With this method, content would also go through en entire lifecycle (creation > archive > deletion) rather than living on in perpetuity. Since our use case is essentially focused on an intranet, our archive spaces won't be deleted since they represent historical data for primarily evergreen subjects like "departments", not transient subject matter like a company event. So, having the ability to automate not only the archival of content but the eventual deletion as well would be of huge value, especially for instances of our size and rate of growth/scale.
Totally agree!!! That is what we intend to do
@Midori: Any idea when something like this might be implemented?
After running the archiving plug-in successfully for several years, we now have over 50% of the content in archive spaces, and we're looking for a way to free resources and programmatically remove anything that's been sitting in the archive for too long.
We would also very much welcome this possibility.
Can you already tell us, if this feature will be coming anytime soon? This would be a critical feature for our company as well.
This is really helpfuol.
We have around 500 spaces in our instance. And when applied, it creates another 500 spaces with respective archived pages. we want to delete these pages if not moved / viewed for 1 year.
One additional vote for getting this added to Data Center.
Voting for this to apply to data center!
As a customer who cannot move to cloud for data security reasons, I'm voting for this to apply to data center as well. PLEASE!
I think yes. It's a feature we need because of the DSGVO in Germany.
Hey,
are there any news in regards to this topic.
Our legal team is pushing as due to data protection reasons outdated content should not stored longer than 3 years.
Otherwise we might need to start deleting content manually and that is definitely not a fun task.
Best regards
Rebecca
Hi Aron, yes it is the same as in the description, and in the first comment.
Same as Martin, we're running Data Center Version. We have to clean up the archive spaces by deleting old content and this feature would be very helpful.
UPDATE: We have released the Better Content Archiving app's cloud version just a few weeks ago. It addresses many points criticized in the Data Center version, including also this one.
(Our plan is that, if there is interest, we will back-port the most valuable changes from the Cloud version to the Data Center one.)
In the cloud version we implemented a new concept called automations. It is a general(ized) batch processing mechanism for contents. It can be used for auto-archiving, also for auto-deleting contents, and we plan to add further actions in the future.
In a nutshell, an automation is defined by a schedule (when to execute it?), a CQL query (on what contents?) and an action (what to do with those?):
Automation schemes can contain multiple automations and can be applied to any space, including archive spaces, too!
All in all, it means you can:
Do you realize how powerful this can be?
Another additional vote for this feature on Data Center. Thank you for your efforts!
Also another vote to have this feature on Data Center
Voting for this to apply to data center! Thank you!
+1, it would be really important to us
+1
+1
Such a feature would be great (Data Center)!
+1 for this request!
The logical conclusion of keeping a large archive for many organizations is eventual deletion of content. This serves to complete many organizational policies around document retention and deletion. Bumping this up in priority would be absolutely a value add for my org.
We're in the same boat. We archive with the Archive Strategy of "Move", but after some time, once it's clear no one needs the archived content, it should be safe to delete.
It could be as simple as being able to enable the archiving configuration on archive spaces and then applying a different archive strategy.
Hi Stella and All,
Yes, this is planned for a future release, but it's not currently prioritized, as the product team is focusing on different new features.
There is also no confirmed release date, but we will be communicating here as soon as we have any updates!
Please keep watching this space and leaving new comments if any ideas come up, as we are monitoring this topic in the meantime.
Thanks for all your patience and support!
@Midori, is this feature planned in the future?
We would also need it.
We not only need to be able to delete archived content after a period of years to clear space, but for legal/regulatory reasons as well.
Martin, Jan, Paula, Erkan, is your use case the same as suggested by others? (Like intentionally disposing information from archive spaces after a certain period.)
Hey all,
I can agree with all the above comments. This would be a great feature to have.
Are there any news yet if a release is planned in the near future?
Side note: do you guys know the recipe implementing the "Permanently Delete" strategy?
I understand that it may not be precisely what you look for, but I think this idea is not widely known and is practical for certain use cases.
29 Comments