Export Triggered Deletion of Objects from Storage - dcm4che/dcm4chee-arc-light GitHub Wiki

Overview

Export triggered deletion of objects from a storage is helpful when one wants to replace or backup a storage system, effectively deleting them from the old storage system once they are available on the new storage system.

Configuration

Using Archive UI

  • Go to Menu->Configuration, then on Devices page, Edit the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive device. In its Child Objects select the Exporter Descriptor which shall be used to export the objects from old storage system to the new storage system.
  • For Delete Study From Storage ID field, select the old storage system ID and Save.

Using LDAP

One may either create a LDIF file (e.g.):

    version: 1
    dn: cn=CopyToNewStorage,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    dcmExporterID: CopyToNewStorage
    objectClass: dcmExporter
    dcmQueueName: Export5
    dcmURI: storage:newStorageID
    dicomAETitle: DCM4CHEE
    dcmDeleteStudyFromStorageID: oldStorageID

and import it to the LDAP Server by using the ldapmodify command line utility.

One may refer to Exporter Descriptor to understand the description of attributes.

Go to the Control tab on Configuration page in archive UI and reload the configuration.

Testing

  • Use RESTful service Export Matching Studies by setting the query parameter storageID=oldStorageID. The path parameter {exporterID} shall be the Exporter that was created above.
  • Once the export of objects from old to new storage systems has been completed, you can see info in the server logs which stating Successfully marked objects of Study[uid={}] at {} for deletion.
  • Alternatively you may also verify in the study table in database. The storage_ids column, which previously contained also the old storage ID, now does not have old storage ID anymore.
⚠️ **GitHub.com Fallback** ⚠️