Export Triggered Rejection of Objects with Data Retention Expired

Overview

One may choose to reject objects with Data Retention Expired reason automatically once the objects have been exported to the desired destination. This is useful together with Move Expired Studies before Rejection wherein it may be necessary to first move or export the objects to a destination before rejecting them.

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 move/export the objects of expired studies/series once the expiration date has been reached.
• For Reject Entity for Data Retention Expiry field, select True and Save.

Using LDAP

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

    version: 1
    dn: cn=RejectAfterExport,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    dcmExporterID: RejectAfterExport
    objectClass: dcmExporter
    dcmQueueName: Export1
    dcmURI: dicom:BACKUP_ARCHIVE_AE
    dicomAETitle: DCM4CHEE
    dcmRejectForDataRetentionExpiry: true

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

• One may use the Archive UI to trigger the export of objects using the Queued Exporter option.
• In Monitoring page Export tab, verify if the export was successful.
• On Studies page, you can see that the exported study is no longer available on querying it.