Files
frontend-miniapp/static/guide-data/README.md
lyf c146beba9e 对齐讲解业务单元静态数据口径
- 刷新讲解静态数据包并保留完整 outline 树
- 按后台顶层业务单元口径归并讲解点统计
- 更新讲解静态数据刷新操作文档

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 02:05:02 +08:00

43 lines
1.2 KiB
Markdown

# Guide Static Data
This directory contains the production guide/explain static package exported from
the Dameng `NATURE_SGS` schema.
Generated files:
- `manifest.json`
- `halls.json`
- `outlines.json`
- `guide-stops.json`
- `exhibits.json`
- `guide-contents.json`
- `pois.json`
- `indexes.json`
- `poi-bridge.json`
Re-export:
```bash
python scripts/export-guide-static-data.py
```
Operational runbook for SSH tunnel export and explain-business refresh:
- `docs/Data/explain-static-data-refresh-runbook.md`
Optional arguments:
```bash
python scripts/export-guide-static-data.py --config <application-local.yaml> --output static/guide-data --nav-assets static/nav-assets/<nav-package>
```
Frontend mode:
- Default: `VITE_GUIDE_CONTENT_SOURCE_MODE=static`
- Future API mode: `VITE_GUIDE_CONTENT_SOURCE_MODE=remote`
- Explicit development demo mode only: `VITE_GUIDE_CONTENT_SOURCE_MODE=mock`
The static package preserves original database IDs and relationship fields.
`poi-bridge.json` maps SGS guide/explain POI references to the active nav-assets POI IDs.
Confirmed exhibit/stop/content POI mappings are used as exact locations; hall mappings are used as hall-level fallback locations when exhibit-level POI data is missing.