What the data for this category looks like
Coke research report data primarily comes from daily reports on coke futures exchanges, monthly reports from the China Coking Industry Association, special research reports from securities firms, and weekly reports from spot traders. Update cadence varies by type: spot-related data is updated daily, industry reports are released monthly, and securities firm research reports are updated in response to industry policies and supply-demand changes. Most documents are in PDF format, containing supply-demand analysis, price trends, production area and port data. Core fields include coke ex-factory price (unit: yuan/ton), port inventory (unit: 10,000 tons), production capacity scale (unit: 10,000 tons/year). Some documents include comparative tables of indicators across different production areas.
What constraints do these characteristics impose on the document parsing and chunking link
Different source documents have significant format differences. Text extraction from editable PDFs can result in messy layout. Scanned documents require an additional OCR process, which increases the complexity of the parsing link. Short-cycle spot data updated daily and long monthly reports are mixed during import. During chunking, short data segments and long-text analysis must be distinguished to avoid incorrect merging of cross-type content. Core numeric fields are tightly bound to their units. During chunking, the association between fields and units must be retained to prevent unit misalignment after splitting. Research reports often contain cross-chapter supply-demand linkage data. The chunking logic must retain contextual associations to avoid breaking critical logical chains.
How to set the configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
PARSE_OCR_ENABLE | Auto-detect | Coke research reports include editable text and scanned tables. Auto-detect can adapt to mixed-format documents and reduce manual configuration costs |
PARSE_TABLE_MODE | Retain original cell structure | Price and inventory tables in coke research reports require complete retention of the correspondence between fields and values, to avoid data misalignment when tables are split |
CHUNK_SIZE | 800–1200 characters | Coke research reports include short-cycle data segments and long-cycle analysis. This range balances contextual completeness and retrieval accuracy |
CHUNK_OVERLAP | 100–150 characters | Prevents linkage data across chunks from being split, ensuring contextual coherence of supply-demand logic |
PARSE_FILE_TIMEOUT_SECONDS | 120 seconds | OCR and table parsing for long documents take significant time. This duration covers parsing requirements for most coke research reports |
UPLOAD_FILE_MAX_SIZE | 500 MB | Some monthly coke research report collections have large file sizes. This threshold is compatible with most bulk upload scenarios |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require specific analysis. It is recommended to test on your own samples before finalizing settings.
Three common mistakes
- A 400 status code is returned when calling the image parsing workflow API. Cause: The binary stream of the
filefield or form parameter format is not correctly carried, and the input parameter specifications of the document parsing module are not matched. - Price values and units appear separated in the parsed chunked results. Cause: The configuration to retain cell structure for
PARSE_TABLE_MODEis not enabled, causing field and unit misalignment during table splitting. - Parsing results are empty when attempting to parse audio or video attachments included with coke research reports. Cause: The current document parsing module does not support audio and video file formats, and cannot extract text content from them.
How to confirm the configuration is correct
- Upload a scanned coke research report, check if the parsed text contains complete recognized content, and confirm that the OCR configuration status meets business requirements.
- Upload a research report containing a price table, check if the chunked results retain the binding relationship between fields and values, and confirm that the table parsing configuration matches the business scenario.
- Push research report files through an external system, check if the knowledge base automatically generates corresponding chunked data, and confirm that the automatic parsing trigger logic complies with configuration requirements.
- Upload a single research report with a volume within the business upper limit, check if parsing completes within the preset duration, and confirm that the timeout configuration adapts to the current document size.
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.