Determine requirements for Sonador CLI library
Much of the systems integration with Sonador will need to happen outside of the Sonador codebase and within ETL (such as AirFlow) or discrete analytic tools. For this reason, Sonador needs a strong client library (and an associated set of CLI tools).
Identified needs:
-
Utilize an access ID and secret to connect to Sonador and retrieve a session token from the oAuth2 token endpoint. -
Implement a "servers" endpoint that can be used to retrieve the list of Orthanc instances associated with Soandor. #8 (closed) -
Integrate DICOMweb client that is able to connect to a designated server and query available studies (and their associated metadata). sonador-client#4 (closed) -
Create an upload
command capable of taking a stack of DICOM folders and sending them to the Orthanc instance. sonador-client#2 (closed) -
Create a download
command capable of retrieving a patient, study, or sequence and pulling it back to the client. sonador-client#3 (closed)
This is a tracking issue for discussion and monitoring the ongoing development of the client.