dcm4chee
  1. dcm4chee
  2. DCMEE-252

Allow Move requests to specified AE destination without overwrite of DB content

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: DICOM
    • Labels:
      None

      Description

      A feature to allow Move requests to a specificed AE destination that would not overwrite instance content from the DB.

      Currently, when an instance is received the instance dataset attributes are saved in the INSTANCE ATTR column of the DB. However, if the same image is received again... the DB forces coercion of some fields (for example: Rescale Intercept) and thus the second received instance gets the same attributes.

      I ran in to this when a modality was sending images twice- the first time the instance was send with wrong rescale value, the second time it was correct, but the rescale was coerced to the first received instance value.

      It would be nice to somehow send these instances to a particular destination where the coercion would not happen (no overwite).

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Gunter Zeilinger
            Reporter:
            scott shannon
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development