Mercurial > hg > orthanc-book
changeset 622:debcf6b6d070
dicom-as-json is now deprecated
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Fri, 26 Feb 2021 10:03:21 +0100 |
parents | 05a5a7369126 |
children | b6ac092360ab |
files | Sphinx/source/faq/features.rst Sphinx/source/faq/orthanc-storage.rst |
diffstat | 2 files changed, 17 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/faq/features.rst Fri Feb 26 09:00:27 2021 +0100 +++ b/Sphinx/source/faq/features.rst Fri Feb 26 10:03:21 2021 +0100 @@ -234,11 +234,21 @@ ``OrthancPluginSetGlobalProperty()``) are therefore kindly invited to complete the **central registry** below: -* ``Attachment 1`` is used by the core of Orthanc to store DICOM instances -* ``Attachment 2`` was used by Orthanc <= 1.9.0 to cache the :ref:`DICOM-as-JSON information <orthanc-storage>` -* ``Attachment 3`` is used since Orthanc 1.9.1 to store the DICOM instance, until the ``Pixel Data (7fe0,0010)`` tag, - if global configuration option ``StorageCompression`` is ``true``, or if the storage area plugin doesn't support - range reads +* ``Attachment 1`` is used by the core of Orthanc to store the DICOM + file associated with one instance. +* ``Attachment 2`` was used by Orthanc <= 1.9.0 to cache the so-called + ``DICOM-as-JSON`` information (as returned by the + ``/instances/.../tags`` URI in the :ref:`REST API <rest>`) in order + to speed up subsequent requests to the same URI. This attachment is + not automatically generated anymore starting with Orthanc 1.9.1, in + order to improve performance (creating two files for each DICOM + instance has a cost) and consistency (if the DICOM dictionary gets + modified in the future). +* ``Attachment 3`` is used since Orthanc 1.9.1 to store the DICOM + instance until the ``Pixel Data (7fe0,0010)`` tag, if the global + configuration option ``StorageCompression`` is ``true``, or if the + storage area plugin doesn't support range reads. This allows to + avoid downloading the full DICOM instance if not necessary. * ``Attachment 9997`` is used by the :ref:`Osimis WebViewer plugin <osimis_webviewer>` to store series information. * ``Attachment 9998`` is used by the :ref:`Osimis WebViewer plugin <osimis_webviewer>` to store instance information. * ``Attachment 9999`` is used by the :ref:`Osimis WebViewer plugin <osimis_webviewer>` to store annotations.
--- a/Sphinx/source/faq/orthanc-storage.rst Fri Feb 26 09:00:27 2021 +0100 +++ b/Sphinx/source/faq/orthanc-storage.rst Fri Feb 26 10:03:21 2021 +0100 @@ -9,13 +9,9 @@ **By default** (i.e. if no database plugin such as :ref:`PostgreSQL <postgresql>` or :ref:`MySQL <mysql>` is used), Orthanc stores all the DICOM files it receives in a folder called ``OrthancStorage`` on the -filesystem. 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 (these -summaries are refered to as ``DICOM-as-JSON`` :ref:`attachments -<metadata>`). +filesystem. -More generally, the ``OrthancStorage`` folder contains a set of +More precisely, the ``OrthancStorage`` folder contains a set of so-called **attachments**, that may correspond to either a DICOM file, a JSON file, or any user-defined file. Internally, each attachment is automatically associated with an `universally unique identifier (UUID)