Summary
The content comparison tab of the version comparison view (/:repo/compare-versions) is currently only available for sources. It needs to be extended to collections for v3 MVP.
Context
Collection owners need to review what changed between two versions of their collection as part of the Update Collection workflow — seeing which concepts/mappings were added, changed, or retired. Without a collection-level content comparison, this review must be done manually (e.g., via spreadsheet or screenshots, as is currently done for CL → PIH review).
Andy Kanter confirmed this as a required workflow during a demo on 2026-05-20: when a new source version is released, the collection owner needs to see the concept-level diff before deciding whether to accept the update.
Scope
In scope: The content comparison tab — the concept/mapping diff view showing what was added, changed, or retired between two versions.
Out of scope / already working: The metadata and JSON comparison tabs are not the concern here.
Acceptance Criteria
- The content comparison tab is accessible from the Versions tab of a collection
- Users can select two collection versions (or a version vs. HEAD) and see a diff of concepts and mappings
- The view shows: concepts only in version A, concepts only in version B, concepts in both with changes
- Consistent with existing source version comparison behavior
Related
Summary
The content comparison tab of the version comparison view (
/:repo/compare-versions) is currently only available for sources. It needs to be extended to collections for v3 MVP.Context
Collection owners need to review what changed between two versions of their collection as part of the Update Collection workflow — seeing which concepts/mappings were added, changed, or retired. Without a collection-level content comparison, this review must be done manually (e.g., via spreadsheet or screenshots, as is currently done for CL → PIH review).
Andy Kanter confirmed this as a required workflow during a demo on 2026-05-20: when a new source version is released, the collection owner needs to see the concept-level diff before deciding whether to accept the update.
Scope
In scope: The content comparison tab — the concept/mapping diff view showing what was added, changed, or retired between two versions.
Out of scope / already working: The metadata and JSON comparison tabs are not the concern here.
Acceptance Criteria
Related
ocl_issues#185303_workflows/update-collection-source-version.mdin the TBv3 knowledge base