Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/orthanc-storage.rst @ 577:7d27154e70f9
cheatsheet and full openapi
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 30 Dec 2020 07:55:12 +0100 |
parents | 090cc988c35e |
children | eaa6cdfa7ba6 |
comparison
equal
deleted
inserted
replaced
576:28a09c734c90 | 577:7d27154e70f9 |
---|---|
9 **By default** (i.e. if no database plugin such as :ref:`PostgreSQL | 9 **By default** (i.e. if no database plugin such as :ref:`PostgreSQL |
10 <postgresql>` or :ref:`MySQL <mysql>` is used), Orthanc stores all the | 10 <postgresql>` or :ref:`MySQL <mysql>` is used), Orthanc stores all the |
11 DICOM files it receives in a folder called ``OrthancStorage`` on the | 11 DICOM files it receives in a folder called ``OrthancStorage`` on the |
12 filesystem. Orthanc also associates each incoming DICOM file with a | 12 filesystem. Orthanc also associates each incoming DICOM file with a |
13 JSON file that summarizes all its DICOM tags, which speeds up | 13 JSON file that summarizes all its DICOM tags, which speeds up |
14 subsequent processing by avoiding a costly DICOM parsing. | 14 subsequent processing by avoiding a costly DICOM parsing (these |
15 summaries are refered to as ``DICOM-as-JSON`` :ref:`attachments | |
16 <metadata>`). | |
15 | 17 |
16 More generally, the ``OrthancStorage`` folder contains a set of | 18 More generally, the ``OrthancStorage`` folder contains a set of |
17 so-called **attachments**, that may correspond to either a DICOM file, | 19 so-called **attachments**, that may correspond to either a DICOM file, |
18 a JSON file, or any user-defined file. Internally, each attachment is | 20 a JSON file, or any user-defined file. Internally, each attachment is |
19 automatically associated with an `universally unique identifier (UUID) | 21 automatically associated with an `universally unique identifier (UUID) |