Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/features.rst @ 838:6afc236cd60a
dicom-web & main-dicom-tags
author | Alain Mazy <am@osimis.io> |
---|---|
date | Thu, 05 May 2022 12:27:09 +0200 |
parents | 66ff2f30afcc |
children | c29ac12e3160 |
comparison
equal
deleted
inserted
replaced
837:66ff2f30afcc | 838:6afc236cd60a |
---|---|
149 SCU, which normally matches the AET of Orthanc (for DICOM protocol). | 149 SCU, which normally matches the AET of Orthanc (for DICOM protocol). |
150 * ``HttpUsername`` (new in Orthanc 1.4.0): The username that created | 150 * ``HttpUsername`` (new in Orthanc 1.4.0): The username that created |
151 the instance (for REST API). | 151 the instance (for REST API). |
152 * ``PixelDataOffset`` (new in Orthanc 1.9.1): Offset (in bytes) of the | 152 * ``PixelDataOffset`` (new in Orthanc 1.9.1): Offset (in bytes) of the |
153 Pixel Data DICOM tag in the DICOM file, if available. | 153 Pixel Data DICOM tag in the DICOM file, if available. |
154 | 154 * ``MainDicomTagsSignature`` (new in Orthanc 1.11.0 - not released yet): |
155 The list of :ref:`MainDicomTags <main-dicom-tags>` that have been | |
156 saved in DB for this resource. | |
155 | 157 |
156 Metadata listed above are set privately by the Orthanc core. They are | 158 Metadata listed above are set privately by the Orthanc core. They are |
157 **read-only** from the perspective of the end user, as Orthanc | 159 **read-only** from the perspective of the end user, as Orthanc |
158 internally relies on them. | 160 internally relies on them. |
159 | 161 |
184 | 186 |
185 Metadata associated with one DICOM resource can be accessed through | 187 Metadata associated with one DICOM resource can be accessed through |
186 the :ref:`REST API <rest>`, for instance:: | 188 the :ref:`REST API <rest>`, for instance:: |
187 | 189 |
188 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata | 190 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata |
191 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata?expand | |
189 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata/RemoteAet | 192 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata/RemoteAet |
190 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata/SampleMetaData1 | 193 $ curl http://localhost:8042/instances/cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e/metadata/SampleMetaData1 |
191 | 194 |
192 User-defined metadata can be modified by issuing a HTTP PUT against | 195 User-defined metadata can be modified by issuing a HTTP PUT against |
193 the REST API:: | 196 the REST API:: |