Back to Details

sf-datacloud-harmonize

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

sf-datacloud-harmonize: Data Cloud Harmonize Phase

sf-datacloud-harmonize: Data Cloud 协调阶段

Use this skill when the user needs schema harmonization and unification work: DMOs, field mappings, relationships, identity resolution, unified profiles, data graphs, or universal ID lookup.
当用户需要架构协调与统一工作时使用此技能：DMO、字段映射、关系、身份解析、统一档案、数据图谱或通用ID查询。

When This Skill Owns the Task

此技能负责的任务场景

Use 
sf-datacloud-harmonize
when the work involves:
  • sf data360 dmo *
  • sf data360 identity-resolution *
  • sf data360 data-graph *
  • sf data360 profile *
  • sf data360 universal-id lookup
Delegate elsewhere when the user is:
  • still ingesting streams or building DLOs → sf-datacloud-prepare
  • working on segment logic or calculated insights → sf-datacloud-segment
  • running SQL, describe, or search-index workflows → sf-datacloud-retrieve
当工作涉及以下内容时，使用
sf-datacloud-harmonize
：
  • sf data360 dmo *
  • sf data360 identity-resolution *
  • sf data360 data-graph *
  • sf data360 profile *
  • sf data360 universal-id lookup
当用户进行以下操作时，转交至其他技能：
  • 仍在摄取流或构建DLO → sf-datacloud-prepare
  • 处理细分逻辑或计算洞察 → sf-datacloud-segment
  • 运行SQL、描述或搜索索引工作流 → sf-datacloud-retrieve

Required Context to Gather First

首先需要收集的必要上下文

Ask for or infer:
  • source DLO and target DMO names
  • whether the task is schema creation, mapping, IR, or graph-related
  • target org alias
  • whether a ruleset already exists
  • the user’s desired unified entity model
询问或推断：
  • 源DLO和目标DMO名称
  • 任务是架构创建、映射、身份解析（IR）还是图谱相关工作
  • 目标组织别名
  • 是否已存在规则集
  • 用户期望的统一实体模型

Core Operating Rules

核心操作规则

  • Inspect DMO schema before creating mappings.
  • Run the shared readiness classifier before mutating harmonization assets: 
    node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
    .
  • Prefer 
    dmo list --all
    when browsing the catalog, but use first-page 
    dmo list
    for fast readiness checks.
  • Use 
    query describe
    or 
    dmo get --json
    instead of inventing unsupported describe flows.
  • Treat identity resolution runs as asynchronous and verify results after execution.
  • Keep unified-profile work separate from STDM/session tracing work.
  • 创建映射前检查DMO架构。
  • 修改协调资产前运行共享就绪分类器：
    node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
    。
  • 浏览目录时优先使用
    dmo list --all
    ，但快速就绪检查时使用第一页的
    dmo list
    。
  • 使用
    query describe
    或
    dmo get --json
    代替自定义不支持的描述流程。
  • 将身份解析运行视为异步操作，执行后验证结果。
  • 将统一档案工作与STDM/会话追踪工作分开处理。

Recommended Workflow

推荐工作流程

1. Classify readiness for harmonize work

1. 分类协调工作的就绪状态

bash
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
bash
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json

2. Inspect the catalog

2. 检查目录

bash
sf data360 dmo list --all -o <org> 2>/dev/null
sf data360 identity-resolution list -o <org> 2>/dev/null
bash
sf data360 dmo list --all -o <org> 2>/dev/null
sf data360 identity-resolution list -o <org> 2>/dev/null

3. Inspect schema before mapping

3. 映射前检查架构

bash
sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
sf data360 dmo get -o <org> --name ssot__Individual__dlm --json 2>/dev/null
bash
sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
sf data360 dmo get -o <org> --name ssot__Individual__dlm --json 2>/dev/null

4. Create or review mappings intentionally

4. 有意创建或审核映射

bash
sf data360 dmo mapping-list -o <org> --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
sf data360 dmo map-to-canonical -o <org> --dlo Contact_Home__dll --dmo ssot__Individual__dlm --dry-run 2>/dev/null
bash
sf data360 dmo mapping-list -o <org> --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
sf data360 dmo map-to-canonical -o <org> --dlo Contact_Home__dll --dmo ssot__Individual__dlm --dry-run 2>/dev/null

5. Run IR only after mappings are trustworthy

5. 仅在映射可信后运行身份解析

bash
sf data360 identity-resolution create -o <org> -f ir-ruleset.json 2>/dev/null
sf data360 identity-resolution run -o <org> --name Main 2>/dev/null
bash
sf data360 identity-resolution create -o <org> -f ir-ruleset.json 2>/dev/null
sf data360 identity-resolution run -o <org> --name Main 2>/dev/null

High-Signal Gotchas

关键注意事项

  • dmo list
    should usually use 
    --all
    .
  • Use 
    query describe
    or 
    dmo get --json
    ; there is no 
    dmo describe
    command.
  • Mapping and related commands can be sensitive to API-version differences.
  • Unified DMO names are ruleset-specific rather than generic.
  • Data graph definitions are sensitive to field selection and relationship shape.
  • If 
    dmo list
    works but 
    identity-resolution list
    is gated, treat that as a phase-specific gap rather than a full Data Cloud outage.
  • dmo list
    通常应使用
    --all
    参数。
  • 使用
    query describe
    或
    dmo get --json
    ；不存在
    dmo describe
    命令。
  • 映射及相关命令对API版本差异敏感。
  • 统一DMO名称是特定于规则集的，而非通用名称。
  • 数据图谱定义对字段选择和关系结构敏感。
  • 如果
    dmo list
    可用但
    identity-resolution list
    受限，将其视为阶段特定的缺口而非完整的Data Cloud故障。

Output Format

输出格式

text
Harmonize task: <dmo / mapping / relationship / ir / data-graph>
Source/target: <dlo → dmo or ruleset/graph names>
Target org: <alias>
Artifacts: <json files / commands>
Verification: <passed / partial / blocked>
Next step: <segment / retrieve / follow-up>
text
Harmonize task: <dmo / mapping / relationship / ir / data-graph>
Source/target: <dlo → dmo or ruleset/graph names>
Target org: <alias>
Artifacts: <json files / commands>
Verification: <passed / partial / blocked>
Next step: <segment / retrieve / follow-up>

References

参考资料

  • README.md
  • ../sf-datacloud/assets/definitions/dmo.template.json
  • ../sf-datacloud/assets/definitions/mapping.template.json
  • ../sf-datacloud/assets/definitions/relationship.template.json
  • ../sf-datacloud/assets/definitions/identity-resolution.template.json
  • ../sf-datacloud/assets/definitions/data-graph.template.json
  • ../sf-datacloud/references/feature-readiness.md
  • README.md
  • ../sf-datacloud/assets/definitions/dmo.template.json
  • ../sf-datacloud/assets/definitions/mapping.template.json
  • ../sf-datacloud/assets/definitions/relationship.template.json
  • ../sf-datacloud/assets/definitions/identity-resolution.template.json
  • ../sf-datacloud/assets/definitions/data-graph.template.json
  • ../sf-datacloud/references/feature-readiness.md