录取数据 = 志愿填报的硬核。 本地只有院校层次/批次;真正的录取分/位次/等位分来自雨来平台(接入中)。
Admission data is the hard core of 志愿. Locally we hold only school tier/batch; the real 录取分/位次/等位分 come from the 雨来 platform (integration pending).
我们手里有什么 / What we actually hold
中文。
- 本地(
school_index_sample.json,2347 校):985 / 211 / 双一流标志 + 录取批次(本科一批/二批…)。这是层次信号,不是分数——能判断”这是不是好学校/什么档次”,不能告诉你”今年多少分能上”。 - 雨来平台(权威层,接入中):
录取分(分省/分年/分专业)、等位分(跨年份可比,目前云南)、专业判别。这才是”多少分、什么位次、能不能冲”的数据。
诚实现状:雨来 API 已上线但我们的 key 被拒(401 INVALID_API_KEY),所以分数维度暂未流通——游戏在没有分数时回退到层次信号 + 定性。拿到有效生产 key 即接通。接入设计见 yulai-integration。
English.
- Local (
school_index_sample.json, 2347 schools):985 / 211 / 双一流flags + admission batch. This is a tier signal, not a score — it tells you “is this a strong school / what bracket,” not “what score gets in this year.” - 雨来 platform (authoritative tier, integrating):
录取分(by province/year/major),等位分(cross-year-comparable, currently Yunnan),专业判别. This is the “what score, what rank, can I reach it” data.
Honest status: the 雨来 API is live but our key is rejected (401 INVALID_API_KEY), so the score dimension isn’t flowing yet — the game falls back to the tier signal + qualitative when scores are absent. It connects the moment we get a valid production key. Integration design: yulai-integration.
怎么被用 / How it’s used
中文。 调查员取数顺序(source tier):雨来(录取分/等位分)→ 本地层次/批次 → 网络检索 → 定性。分数缺失时绝不编造,退回层次或定性表述。
English. Investigator fetch order (source tier): 雨来 (scores/等位分) → local tier/batch → web search → qualitative. When a score is missing it’s never fabricated — fall back to tier or a qualitative statement.
Related
data-overview · yulai-integration · data-schools-majors · investigator