Keeping websites well organised and fast is very important. Also, for many organisations, keeping records of what was shown on any site at any specific time is a legal requirement. Jentla retains archive copies of site content centrally on the Jentla Manager, where it can't affect site performance, and removes unwanted or old content from the sites.

As the original content resides on the manager, archiving can all be controlled centrally.

By setting parameters in the configuration page that specifies the amount of time objects should be unused before they are archived from the database and removed, you can tailor Jentla to your individual archiving requirements.

The criteria for individual archiving parameters continues to grow more granular. An example of this asset split might be:

• Published Articles 700 days
• Submitted Articles100 days
• Draft Articles 60 days
• Images 350 days
• Flash 250 days
• Videos 200 days

With the format as: Videos 200 days<destination><confirmationy/n>

• If an object has a wait interval of 0 days, then archiving is turned off for that type of object.
• If all values are set to 0, then archiving is turned off and the archiving process is never run.
• Destination: The destination field defines where that particular object should be archived to, prior to deletion.
• Confirmation: The confirmation flag for each object defines whether it requires confirmation prior to deletion.

To extend this functionality, adding sites, sections and categories to this criteria is currently under development.