Orphan Files: What Are They and How to Manage Them

Orphan data (GB) refers to the total file size of items that still exist in the images folder but are no longer associated with a document in the case or workspace.

When Orphan Data Occurs

Orphan data can be created in several ways:

• Documents are deleted from the case, but the associated natives, images, or text are not permanently removed during the delete job.
• Files created during an overlay are not named correctly and cannot be linked back to a document in the case.
• DOC IDs do not match the native file, text file, or image file stored in the repository.
• Errors during processing or ingestion leave files behind.

Best Practices to Minimize Orphan Data

To reduce the amount of orphan data in a case, ensure that:

• The RTL images repository contains accurate file names.
• Files no longer linked to a record are permanently deleted.

After ingesting documents, it is also a best practice to check for suppressed files:

• Only retain suppressed files if you may need to unsuppress them in the future.
• If retention is not required, clear out the suppressed folder on the CLT to reduce leftover data.

Repository Maintenance

As part of routine cleanup, check the following directories on the CLT after ingestion or import jobs finish:

• Export
• Import
• Ingest
• Ingest_temp
• Suppressed
• Upload

Clearing out unnecessary files ensures no excess data is left behind and keeps your repository healthy.