What the data for this category looks like
Data for glass intelligent due diligence reports comes primarily from production plant outgoing quality inspection sheets, third-party testing institution reports, and project bidding technical requirement documents. Update frequency varies by document type:
- Outgoing quality inspection sheets update with each production batch
- Third-party testing reports update with each inspection batch
- Project documents update with bidding adjustments
Most documents are structured tables, while some are mixed-format technical documents. Core fields include batch number, nominal thickness, visible light transmittance, bending strength, and test date. Units include millimeters (mm), megapascals (MPa), and others. No unified fixed format template exists.
How These Characteristics Impact Document Parsing and Chunking
The multi-structured table format of glass due diligence documents requires the parsing process to accurately identify merged cells, cross-page tables, and similar scenarios to avoid field misalignment. Mixed-format documents require support for both text block and table block parsing logic, rather than relying solely on plain text parsing rules.
Core metadata such as batch number and test date must be bound to their corresponding parameters. Chunking must not split content that has cross-field associations. Parameter fields differ across glass types. Chunking must retain contextual links for parameters of the same type, to avoid mixing parameters of insulated glass and monolithic glass. Documents containing multiple batches of data must be split by batch to prevent cross-batch parameter confusion.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
PARSE_TABLE_ENABLED | Enabled | Glass due diligence documents are mostly structured tables, and the original table structure and field associations must be preserved |
CHUNK_MAX_SIZE | 800-1200 characters | Glass parameters are mostly short fields. This length avoids splitting parameters from the same batch while controlling the data volume per chunk |
PARSE_FILE_TIMEOUT_SECONDS | 120 seconds | Large multi-batch test reports take longer to parse. This value covers parsing needs for most scenarios |
UPLOAD_FILE_MAX_SIZE | 500 MB | Single-batch glass quality inspection reports may include multiple test images. This value supports conventional file uploads |
TABLE_CHUNK_SPLIT_STRATEGY | Preserve context by row groups | Glass parameters are arranged by batch. This retains multi-row table data from the same batch to avoid cross-chunk splitting |
ENABLE_METADATA_EXTRACTION | Enabled | Metadata such as batch number and test date are core due diligence information, and must be accurately extracted and associated with corresponding chunks |
The parameter values provided on this page are common starting points for configuration setup. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Issue: No table file upload entry is visible in the interface, making it impossible to directly import CSV/Excel documents with glass parameters. Cause: The
TABLE_PARSE_UPLOAD_ENABLEconfiguration is not enabled in the knowledge base settings, or this entry is not available in the current version. - Issue: Calling the
create_file_collectionAPI to upload glass parameter files returns a400 Bad Requesterror with the prompt "No valid table data detected". Cause: ThePARSE_TABLE_ENABLEDconfiguration is not enabled, or the uploaded file format does not match the preset parsing rules. - Issue: After uploading a large glass test report, the vectorization task takes excessive time and progress stalls. Cause:
CHUNK_MAX_SIZEis set too large, leading to high per-chunk data volume and increased subsequent vectorization calculation load.
How to Verify Proper Configuration
- Upload a CSV file containing single-batch glass parameters, and check that the parsing result retains all fields completely without misalignment or loss.
- Upload a mixed-format document with multiple batches of data, and confirm that chunking splits content by batch, with parameters from the same batch not split across chunks.
- Upload a glass test report larger than 100 MB, and verify that the parsing task completes within the preset
PARSE_FILE_TIMEOUT_SECONDSduration. - View the metadata list in the knowledge base, and confirm that core fields such as batch number and test date have been correctly extracted and linked to their corresponding chunks.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.