-
Notifications
You must be signed in to change notification settings - Fork 235
Query Retrieve with Series Metadata
The test is to verify that Retrieve Cache is used when query/retrieve is being done from a Nearline storage even after
the series metadata is accumulated. This means that object(s) are first copied to the retrieve cache from nearline
and then sent to destination. In addition to that, the json file(s) of the object(s) in the updated series-metadata
zip
files should now also contain the reference to retrieve-cache
storage.
Note : It is assumed here, that purging of instance records is not enabled.
- Go to
Configuration
page of Archive UI,Devices
tab and editdcm4chee-arc
device.Edit extension
ofDevice Extension
, nextEdit extension
ofArchive Device
and then toAttributes
section. - Ensure that one does NOT have any values set for fields
Purge Instance Records Delay
andPurge Instance Records Polling Interval
andPurge Instance Records
andSave
.
In addition to basic configuration done for retrieve cache, below configuration is needed to enable the accumulation of series metadata feature.
- Go to
Configuration
page,Devices
tab and editdcm4chee-arc
device.Edit extension
ofDevice Extension
, nextEdit extension
ofArchive Device
. Create a newChild Object
forseries-metadata
asStorage Descriptor
with values as shown below. - Go back to
Attributes
section ofArchive Device
and ensure that one has values set for fieldsSeries Metadata Storage ID
,Aggregate Series Metadata Delay
andUpdate Series Metadata Polling Interval
andSave
.
One may
-
create a LDIF file (e.g.):
dn: dcmStorageID=series-metadata,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org dcmProperty: pathFormat={now,date,yyyy/MM/dd}/{0020000D,hash}/{0020000E,hash}/{now,date,HHmmss}.zip dcmProperty: checkMountFile=NO_MOUNT objectClass: dcmStorage dcmStorageID: series-metadata dcmURI: ${jboss.server.data.url}/series-metadata/ dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org changetype: modify add: dcmSeriesMetadataStorageID dcmSeriesMetadataStorageID: series-metadata dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org changetype: modify add: dcmSeriesMetadataDelay dcmSeriesMetadataDelay: PT1M dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org changetype: modify add: dcmSeriesMetadataPollingInterval dcmSeriesMetadataPollingInterval: PT1M dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org changetype: modify add: dcmSeriesMetadataFetchSize dcmSeriesMetadataFetchSize: 10
One may refer to Archive Device and Storage Descriptor to understand the description of attributes.
Refer ISO-8601 Duration format for more know-how on Durations.
Go to the Control tab on Configuration page in archive UI and reload the configuration.
- Perform test steps 1-3 and the corresponding verifications.
- In addition, verify the size, path and ID of series metadata storage in the private attributes
Series Metadata Storage ID
,Series Metadata Storage Path
andSeries Metadata Storage Object Size
on Series/Object level. - Also, verify that
Storage ID (77771050)
in the object's json file inseries-metadata.zip
has value asretrieve-cache
.
DCM4CHEE 5 Documentation