What the data for this category looks like
Energy storage financing daily report data comes from public energy project financing announcements, local energy regulatory disclosure platforms, and bank credit disclosure documents. The reports update daily with the latest disclosed financing project information. Each document is a structured financing project entry, containing fields including project entity name, energy storage installed capacity, financing amount, credit institution, and announcement date. Energy storage installed capacity uses megawatt-hours (MWh) or kilowatts (kW) as units. Financing amount uses ten thousand yuan or hundred million yuan as units. Each record includes an original announcement link as a traceability field.
What constraints these characteristics impose on deployment and upgrade
Daily updated data sources require precise scheduled pull cycle configuration to avoid data lag or duplicate pulls. Structured field unit validation requires preset unit conversion rules for capacity and amount during deployment to prevent data parsing errors. A new record type field requirement demands compatibility with old data structures during upgrade, to avoid loss of historical project data. Deduplication logic for traceability links needs separate configuration to prevent duplicate import of the same financing project entry, and ensure accurate deduplication.
How to Configure Settings
| Configuration Key | Recommended Value | Rationale |
|---|---|---|
FETCH_INTERVAL_MINUTES | 1440 minutes | Aligns with the daily update rhythm of the energy storage financing daily report data source, avoids duplicate pulling of same-day announcements |
PARSE_UNIT_WHITELIST | ["MWh", "kW", "ten thousand yuan", "hundred million yuan"] | Matches standard field units for energy storage financing projects, filters abnormal parsing results from non-standard units |
DUPLICATE_REMOVE_KEY | ["announcement link"] | Identifies and removes duplicate imported financing project entries via unique traceability links |
PARSE_TIMEOUT_SECONDS | 600 seconds | Adapts to parsing of original financing announcements with long text, avoids timeout interruptions caused by excessive content length |
OLD_STRUCTURE_COMPATIBLE | Enabled | Retains legacy field mapping rules during upgrade, compatible with previously imported energy storage financing project data |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Configuration Errors
- Symptom: Docker container status is up, but accessing port 3000 shows a database connection failure. Logs display
MongoConnectionError. Cause:MONGO_INITDB_ROOT_USERNAMEandMONGO_INITDB_ROOT_PASSWORDenvironment variables are not correctly configured, or the local MongoDB service has not opened corresponding port permissions. - Symptom: After starting the local development server, the model configuration page cannot be accessed. The interface prompts that the model service entry was not found. Cause: The associated model proxy service is not started, or the
ONEAPI_API_BASEenvironment variable is not configured to point to the local model service address. - Symptom: After adding a custom model in version 4.8.22, an index build error
ModelConfigNotFoundis reported, or the API key configuration entry cannot be found. Cause: The corresponding model's key is not filled in theMODEL_API_KEYSmodule of the system configuration page, or the service is not restarted to load new configuration items.
How to Confirm Configuration is Successful
- Run the scheduled pull task, check whether the latest daily energy storage financing project data is successfully imported. Verify that the number of imported entries matches the number disclosed by the data source.
- Randomly select imported project entries, check whether field units comply with the preset whitelist rules, with no abnormal unit parsing results.
- Restart the service, check whether historically imported project data is retained in the database, with no missing fields or structural changes.
- Access the model configuration page, confirm that API keys for custom models can be normally added and saved, with no configuration error prompts.
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.