As different client has different data archival standards, we need to create archival process for various clients. In AEM, since the content goes into the repository, anything that comes inside the repo becomes a data that is moved across environments. Moreover, we need to have a process for content editors for moving archived content to some other tree or space and to keeping the content tree clean and only with needed content.
It will be great if you can support an archival strategy OOTB. The features I look for in this feature is
1. Easy to manage from authoring experience
2. Reduced to a small size
3. It should be outside the repository so that we don't need to move that as content in the repo.
4. We should be able to search through the metadata
5. We should be able to retrieve the content with some action.