Create DICOMweb compatible version of the comments API
The primary Orthanc comments API (refer to #28 (closed)) utilizes Orthanc's internal UIDs to make it consistent with the rest of the Orthanc interface. To integrate with OHIF, however, endpoints which are compatible with DICOM UIDs are needed.
Development tasks:
-
Research the DICOMweb specification and propose compatible URL structures for comments endpoints - Refer to DICOMweb Standard for an overview of the standard. We should focus on the JSON implementation (while changing our implementation and data schema as little as possible).
-
Adapt the primary endpoints so that it is possible to provide management and REST endpoints for the new components. - Primary goal: code re-use. Ideally, all that is needed is a mixin method which can be used to translate a DICOM UID (taken from the URL) to an Orthanc UID.
- Within existing Orthanc comments views, we should look at adapting the
get_comment
method.
Architectural notes:
- The view should throw a
ResourceDoesNotExist
error if either the DICOM series UID or comment UID is invalid. - The comment UID should remain the same as the primary interface. For extension models where we aren't seeking broader compatibility, I don't think we need to deal with more an a single identifier.