跳到正文

Field Note Input Spec · v0.6

真实 field note 输入规范 — 16+5 字段 + 7 validation rules + manual 5-step 流程

Field Note Input Specification

v0.6 完整 field note 输入规范。仅 schema + 流程设计,不实装实际输入管道。
边界声明 · STRICT

本期仅文档化 input spec。不实装:input UI · backend API · auto-validator 脚本 · auto-pipeline。所有实装由 P5-E 完成。

StatusTotal FieldsRequiredOptionalv0.6 NewValidation Rules

Input Pipeline Status

Current Status

DESIGN_ONLY — v0.6 only documents this schema.

Supported Input Methods (by design)

MethodDescriptionv0.6 StatusFuture Implementation
manual_markdown_file Fieldworker drafts in MD with YAML frontmatter, commits to /data/field_notes/incoming/ RECOMMENDED P5-E pipeline script
json_form_submission Web form posts JSON to /api/field_notes PLANNED P5-E
csv_batch_import Batch CSV import for migration / bulk operations PLANNED P5-E

Manual Method · 5-Step Workflow

  1. Step 1: Fieldworker drafts note in Markdown with YAML frontmatter matching this schema.
  2. Step 2: Fieldworker or curator commits note to /data/field_notes/incoming/ folder.
  3. Step 3: Pipeline script (P5-E only) validates schema, validates place_id, validates citation_ids.
  4. Step 4: On success, note moves to /data/field_notes.json and gets linked to workspace + research_questions.
  5. Step 5: v0.6+ site rebuilds; note appears on /field-notes/ page.

Required Fields · 7

FieldTypeFormatNote

Optional Fields · 9

FieldTypeNote

v0.6 New Fields · 5

FieldTypeNote

Validation Rules · 7

  1. Unique ID: field_note_id must be globally unique across all field_notes.json records.
  2. Valid Place: place_id must exist in places.json (canonical, no place- prefix).
  3. Citation Format: all linked_citation_ids must match SHUGE:p<post_id>:<page_seq> format and exist in citations.json.
  4. Optional IDs: linked_evidence_card_ids and research_question_ids are optional, but if present must exist.
  5. Enum Status: verification_status must be one of 4 enum values (UNVERIFIED / VERIFIED / CONTRADICTED / NEEDS_REVIEW).
  6. Photo Count: photos_count must be integer ≥0; actual photos not stored in v0.6.
  7. WGS84 Range: gps_lat/gps_lng must be valid WGS84 lat/lng range if provided.

YAML Frontmatter Example

---
field_note_id: FN-20261001-001
place_id: beijing
date: '2026-10-01'
location_text: 北京市东城区故宫博物院 太和殿前檐柱
gps_lat: 39.9163
gps_lng: 116.3972
weather: 晴
photos_count: 12
recording_count: 1
fieldworker_name: 张三
linked_citation_ids:
  - SHUGE:p44159:100
  - SHUGE:p44159:200
linked_research_question_ids:
  - rq-ws2-001
verification_status: VERIFIED
tags:
  - pillar-measurement
  - d-equals-2c
---

# 太和殿前檐柱测量

实测太和殿前檐柱直径约 0.6m,柱顶石正心面直径约 0.3m...

v0.6 Boundary

不做的事
  • ❌ 不实装输入 UI 表单
  • ❌ 不实装 backend API endpoint
  • ❌ 不实装 auto-validator 脚本
  • ❌ 不实装 auto-pipeline (incoming/ → field_notes.json)
  • ❌ 不存实际照片文件
  • ❌ 不实装 GPS auto-collection

Further Reading