feat: Added documentation for OHIF-v3 (#2450)

* Added docs with new screenshots

* Added doc to architecture

* Added documentations to various extension modules

* Added more documentation to modes

* Added docs to managers

* Added docs for services

* Fixed deployment docs

* Added white labelling documentation

* Added i18n docs and measurement export

docs/latest/extensions/modules/sop-class-handler.md

@@ -1,8 +1,13 @@
 # Module: SOP Class Handler
 
-An extension can register a [SOP Class][sop-class-link] Handler Module by
-defining a `getSopClassHandlerModule` method. The [SOP Class][sop-class-link]
-Handler is a bit different from the other modules, as it doesn't provide a `1:1`
+
+## Overview
+This module defines how a specific DICOM SOP class should be processed to make a displaySet, something that can be hung in a viewport. An extension can register a [SOP Class][sop-class-link] Handler Module by defining a `getSopClassHandlerModule` method. The [SOP Class][sop-class-link].
+
+The mode chooses what SOPClassHandlers to use, so you could process a series in a different way depending on mode within the same application.
+
+
+SOPClassHandler is a bit different from the other modules, as it doesn't provide a `1:1`
 schema for UI or provide it's own components. It instead defines:
 
 - `sopClassUIDs`: an array of string SOP Class UIDs that the
@@ -14,87 +19,82 @@ A `displaySet` has the following shape:
 
 ```js
 return {
-  plugin: 'html',
-  Modality: 'SR',
-  displaySetInstanceUID: 0,
-  wadoRoot: study.getData().wadoRoot,
-  wadoUri: instance.getData().wadouri,
-  SOPInstanceUID: instance.getSOPInstanceUID(),
-  SeriesInstanceUID: series.getSeriesInstanceUID(),
-  StudyInstanceUID: study.getStudyInstanceUID(),
-  authorizationHeaders,
-};
+  Modality: 'MR',
+  displaySetInstanceUIDD
+  SeriesDate,
+  SeriesTime,
+  SeriesInstanceUID,
+  StudyInstanceUID,
+  SeriesNumber,
+  FrameRate,
+  SeriesDescription,
+  isMultiFrame,
+  numImageFrames,
+  SOPClassHandlerId,
+}
 ```
 
-Where the `plugin` key is used to influence the default `ViewportComponent` for
-rendering the `displaySet`. Additional properties are passed to the
-`ViewportComponent` and used by the default `StudyBrowser` to render
-"thumbnails" for each `displaySet`
-
 ## Example SOP Class Handler Module
 
 ```js
-const SOP_CLASS_UIDS = {
-  BASIC_TEXT_SR: '1.2.840.10008.5.1.4.1.1.88.11',
-  ENHANCED_SR: '1.2.840.10008.5.1.4.1.1.88.22',
+import ImageSet from '@ohif/core/src/classes/ImageSet';
+
+
+const sopClassDictionary = {
+  CTImageStorage: "1.2.840.10008.5.1.4.1.1.2",
+  MRImageStorage: "1.2.840.10008.5.1.4.1.1.4",
 };
 
-export default {
-  id: 'example-sop-class-handler-module',
 
-/**
- * @param {object} params
- * @param {ServicesManager} params.servicesManager
- * @param {CommandsManager} params.commandsManager
- */
-getSopClassHandlerModule({ servicesManager, commandsManager }) {
-  return {
-    id: 'OHIFDicomHtmlSopClassHandler',
-    sopClassUIDs: Object.values(SOP_CLASS_UIDS),
+// It is important to note that the used SOPClassUIDs in the modes are in the order that is specified in the array.
+const sopClassUids = [
+  sopClassDictionary.CTImageStorage,
+  sopClassDictionary.MRImageStorage,
+;
 
-    /**
-     * @param {object} series -
-     * @param {object} study -
-     * @param {object} dicomWebClient -
-     * @param {object} authorizationHeaders -
-     */
-    getDisplaySetFromSeries(series, study, dicomWebClient, authorizationHeaders) {
-      const instance = series.getFirstInstance();
+const makeDisplaySet = (instances) => {
+  const instance = instances[0];
+  const imageSet = new ImageSet(instances);
 
-      return {
-        plugin: 'html',
-        displaySetInstanceUID: 0,
-        wadoRoot: study.getData().wadoRoot,
-        wadoUri: instance.getData().wadouri,
-        SOPInstanceUID: instance.getSOPInstanceUID(),
-        SeriesInstanceUID: series.getSeriesInstanceUID(),
-        StudyInstanceUID: study.getStudyInstanceUID(),
-        authorizationHeaders,
-      };
+  imageSet.setAttributes({
+    displaySetInstanceUID: imageSet.uid,
+    SeriesDate: instance.SeriesDate,
+    SeriesTime: instance.SeriesTime,
+    SeriesInstanceUID: instance.SeriesInstanceUID,
+    StudyInstanceUID: instance.StudyInstanceUID,
+    SeriesNumber: instance.SeriesNumber,
+    FrameRate: instance.FrameTime,
+    SeriesDescription: instance.SeriesDescription,
+    Modality: instance.Modality,
+    isMultiFrame: isMultiFrame(instance),
+    numImageFrames: instances.length,
+    SOPClassHandlerId: `${id}.sopClassHandlerModule.${sopClassHandlerName}`,
+  });
+
+  return imageSet;
+};
+
+getSopClassHandlerModule = () => {
+  return [
+    {
+      name: 'stack,
+      sopClassUids,
+      getDisplaySetsFromSeries: makeDisplaySet,
     },
-  }
+  ];
 };
+
 ```
 
 ### More examples :
-
-- [Dicom-HTML SOP][dicom-html-sop]
-- [Dicom-PDF SOP][dicom-pdf-sop]
-- [Dicom-Microscopy SOP][dicom-micro-sop]
-- [Dicom-Segmentation SOP][dicom-seg-sop]
+You can find another example for this mapping between raw metadata and displaySet for
+`DICOM-SR` extension.
 
 ## `@ohif/viewer` usage
 
-We use the `sopClassHandlerModule`s in three different places:
-
-- `ViewerLocalFileData.js`
-- `ViewerRetrieveStudyData.js`
-- `StandaloneRouting.js`
-
-Each time, it is used to map study and series data to `displaySets`. It does
-this by working alongside the `StudyMetadataManager` in `@ohif/core`. That
-manager has the method `createDisplaySets` that takes an array of
-`sopClassHandlerModules`.
+We use the `sopClassHandlerModule`s in `DisplaySetService` where we
+transform instances from the raw metadata format to a OHIF displaySet format.
+You can read more about DisplaySetService here.
 
 <!-- prettier-ignore-start -->
 [sop-class-link]: http://dicom.nema.org/dicom/2013/output/chtml/part04/sect_B.5.html