Open a remote study in the editing workspace
Pull an archived study into the ordinary editor, whole or scoped to the series you pick, with its origin recorded.
Desktop app only, 1.6.0 or newerdcmage pro
Problem
Correcting one instance of a study and sending it back would leave the archive holding a study whose instances disagree with each other. A study-level correction has to be made against the whole study.
But not every retrieval is a correction. Pulling four hundred instances to read the metadata of two is a long wait for nothing, and over DIMSE and DICOMweb a correction goes back as a new study rather than replacing the original.
Steps
-
Open a study from the search results. dcmage retrieves every instance the archive reports for that study (not the first one, not the ones currently displayed) and parses them through the same loader that handles local files. This is the one-click path and the one a correction needs. While the instances arrive, the button counts them (Retrieving 12 of 40…), and Cancel beside it stops the retrieval. A cancelled open leaves your workspace as it was.
-
Or open part of it. Series… on the result row lists what the study holds and what each series would cost to retrieve. Tick the ones you want and choose Open selected series.
-
Work in the ordinary editor. The tag editor, the undo timeline, the viewport tools, and the files tree behave exactly as they do for a study you opened from disk.
-
Check the provenance badge in the top bar. It names the archive the open study came from and how many instances are here.
When you hold part of a study
A notice at the open tells you how much of the study is here, and the badge keeps telling you: it reads held of total rather than a single count, in the colour dcmage uses for anything modified.
The notice also names two consequences. Sending a correction back to the archive is refused until the whole study is open: the correction is written into every instance, including the ones you never retrieved, so a correction compiled from part of a study cannot show you what the rest would lose. Reopening the study whole lifts the refusal. And a local export carries only the instances you have; nothing is lost at the archive.
The count is what the workspace holds, not what was asked for. An instance that arrived but could not be parsed counts as missing, exactly like one you never requested.
So does an instance the archive would not return. dcmage asks for a failed instance a second time, and if that fails too it opens the rest of the study and the notice says how many instances could not be retrieved. If none arrive at all, nothing opens and you see the archive’s error instead.
Result
The archived study is open in the normal editing workspace (all of it, or the series you chose) and its origin, which archive, which resource, and how much of the study is here, is recorded and visible for as long as that study is the one you are editing.
When you move on
Close the session or load a local file, and the badge is gone: a local study is never shown as though it came from the archive.