知识卡片
元数据系统:单一系统还是多个协作系统
元数据系统用来记录『我们在做什么』,最低限度要追踪已有的特征定义及其在各模型中的版本。多数组织起步时不做、日后追悔;常见错误是长出多套各自为政的系统。作者给出两条路线:单一系统便于跨子系统关联、简化分析,但 schema 难一次定对、需不断加列回填;多套协作系统解耦、故障隔离,代价是跨系统 join 困难,需共享唯一标识或再建 meta-metadata 系统。原则:需求简单明确时优先单一系统,领域快速发展时选多套,且元数据系统绝不能处在训练或服务的实时路径上。数据集、特征、标签与流水线各有应记录要素,如来源、责任人、版本日期、使用限制与置信度。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 元数据系统
原书出处 · 1 处
- Feature and Training Data · 查看原书依据
Our choices for a metadata system are relatively simple: One system Build one system to track metadata from all of these sources. This makes it simple to make correlations across multiple subsystems, simplifying analysis and reporting. Such a large system is difficult to get right from a data schema perspective. We will be constantly adding columns when we discover data we would like to keep track of (and backfilling those col
参考来源
- 位置:《Reliable Machine Learning》第04章《Feature and Training Data》(源文件:extracted/Reliable Machine Learning/_epub-src/OEBPS/ch04.xhtml)
- 结论依据:原文明确阐述该主题,并给出定义、实践或反例。
- 原始内容:Our choices for a metadata system are relatively simple: One system Build one system to track metadata from all of these sources. This makes it simple to make correlations across multiple subsystems, simplifying analysis and reporting. Such a large system is difficult to get right from a data schema perspective. We will be constantly adding columns when we discover data we would like to keep track of (and backfilling those col