Article Overview
The Harmony to Image Artist integration enables the transfer of imaging data and associated metadata, including results, analysis files, and assay definitions, from Harmony into Image Artist for downstream analysis and visualization. This article highlights the practical differences between Harmony 5.2 and Harmony 5.3 when integrating with Image Artist.
Summary
Harmony 5.3 uses a simplified, push-based integration model with updated authentication and storage technologies. Harmony 5.2 uses a bidirectional transfer model that requires additional firewall and network connectivity considerations.
Key Differences:
| Area | Harmony 5.2 | Harmony 5.3 |
|---|---|---|
| Transfer Model | Bidirectional communication between Harmony and Image Artist | Unidirectional push from Harmony to Image Artist |
| Data Transfer | Harmony sends XML metadata and references to TIF files stored in ODA; Image Artist retrieves image data via HTTP | Harmony uses the Gemma client to push data directly to Image Artist |
| Screen Visibility | Users can view all screens associated with users in the same Image Artist group | Users can only view screens they own |
| Storage Architecture | ODA-based storage | Harmony Store using PostgreSQL and OpenSearch |
| Authentication | Standard Harmony user accounts | Keycloak authentication |
| File Naming | TIF filenames are not human-readable and depend on XML context | Human-readable Harmony Archive naming |
| User Interface | Legacy Columbus-labelled workflow | Updated Image Artist-aligned workflow |
Harmony 5.3 allows the reimport of Harmony Store data exported from Image Artist 1.5 and above.
See also:
Image Artist: Communication Pathways and Firewall Requirements for Harmony 5.3
Image Artist: Communication Pathways and Firewall Requirements for Harmony 5.2 and Earlier
Comments
0 comments
Article is closed for comments.