Replication verification from filesystem to Postgres

Skip to first unread message

Oct 5, 2016, 9:04:11 PM10/5/16
to Orthanc Users

I am attempting to migrate my filesystem based DICOM store and index into Postgres. I am using the supplied ImportDicomFiles python script to walk through the directories. However a number are failing for some reason or another, I would say roughly half.

Is there any way of just re-sending the failed studies? I think the reason they are failing is the sheer volume I am trying to transmit.

Is there any way of verifying that all the instances on the file system have made it into the database?

Ben Ganley

Sébastien Jodogne

Oct 6, 2016, 10:14:41 AM10/6/16
to Orthanc Users,

The first part of your question is answered in the following FAQ:

"Orthanc also associates each incoming DICOM file with a JSON file that summarizes all its DICOM tags, which speeds up subsequent processing by avoiding a costly DICOM parsing." This explains why your "OrthancStorange" folder contains twice more files than the number of instances that are stored by your Orthanc server.

You can certainly verify that all the instances have been properly replicated by creating a script (e.g. in Python) that makes use of the REST API of Orthanc:

In a nutshell, the script would iterate over all the DICOM instances of your "Source" Orthanc server, and check whether the "Target" server contains each of them. You could also test whether their MD5 hash matches (cf. the "http://localhost:8042/instances/{...}/attachments/dicom/md5" URI).


Oct 6, 2016, 2:57:32 PM10/6/16
to Orthanc Users,
Ahh okay, so when the ImportDicomFiles scripts finished running I checked the totals and saw that exactly half of the studies succeeded. This makes sense as above you have said that half the files are JSON.

Perhaps it is worth noting this in
in the direct access to the filesystem section? So people expect half to fail in this instance?
Or perhaps modify the ImportDicomFiles to run
import json
except ValueError:
//Post this file as it is not JSON.
This would add a lot of overhead to this script but there may be a better way of doing it.

Sébastien Jodogne

Oct 7, 2016, 2:13:07 AM10/7/16
to Orthanc Users,
Thanks for this interesting suggestion! I have just updated the Orthanc Book accordingly:

I will not modify the default to keep it as straightforward and generic as possible. Obviously, it is quite easy to fine-tune it to serve one's needs.

Also, don't forget that a standalone GitHub repository is opened to store such user contributions, feel free to issue pull requests therein:

Reply all
Reply to author
0 new messages