Why your case size may be significantly smaller than your original ZIP upload after reclaiming space.
Issue: You uploaded a large ZIP file (For example, 90GB) to GoldFynch, and after processing and reclaiming space, the total case size is significantly smaller (For example, under 25GB). This seems counterintuitive if you expected the processed data to be somewhat larger than the original compressed files. You want to confirm that all your data was successfully imported.
Resolution: The difference in size between your original production ZIP file and the final storage footprint in your GoldFynch case is expected and completely normal. This is due to how GoldFynch processes and stores data, focusing on efficiency and cost-effectiveness for your eDiscovery needs.
Here's a breakdown of why this occurs:
1. Multiple Representations in Production ZIP Files:
A common practice in eDiscovery production is to include multiple versions of the same document within a single ZIP file. These often include:
Issue: You uploaded a large ZIP file (For example, 90GB) to GoldFynch, and after processing and reclaiming space, the total case size is significantly smaller (For example, under 25GB). This seems counterintuitive if you expected the processed data to be somewhat larger than the original compressed files. You want to confirm that all your data was successfully imported.
Resolution: The difference in size between your original production ZIP file and the final storage footprint in your GoldFynch case is expected and completely normal. This is due to how GoldFynch processes and stores data, focusing on efficiency and cost-effectiveness for your eDiscovery needs.
Here's a breakdown of why this occurs:
1. Multiple Representations in Production ZIP Files:
A common practice in eDiscovery production is to include multiple versions of the same document within a single ZIP file. These often include:
- The original native file: This is the original document in its native application format (for example, .docx, .xlsx, .msg, .pdf).
- An imaged version of the document: This is typically a rendered image of the document, such as a PDF, TIFF, or JPEG, often used for review or stamping.
- A text file with extracted or OCR text: This file contains the searchable text extracted from the document, or text generated through Optical Character Recognition (OCR) if the original was an image-only document.
2. GoldFynch's Chargeable Storage Calculation:
When importing data, the chargeable size is based on the following:
When importing data, the chargeable size is based on the following:
- Native File (if available): If a native file is present for a document, GoldFynch primarily charges for the size of this native file. This is because the native file is the most complete and authentic representation of the document.
- Total Size of Images (if no native is provided): In cases where no native file is provided, or if the document is natively an image (for example, a scanned document), GoldFynch will calculate the chargeable size based on the total size of the images (PDF, TIFF, or JPEG).
3. Reclaiming Space:
The "Reclaim Space" feature specifically targets the removal of redundant data that was part of the initial upload, such as:
The "Reclaim Space" feature specifically targets the removal of redundant data that was part of the initial upload, such as:
- The original compressed ZIP file: Once the contents are extracted and processed, the original ZIP container file itself is no longer needed for data access within GoldFynch and can be removed.
- Load files: These are often included in productions to help import data into other review platforms but are not directly consumed by GoldFynch for the core document content.
For more information on using the Reclaim Space feature, please see here.