Summary: | DICOMweb metadata resource reads all instances | ||
---|---|---|---|
Product: | Orthanc | Reporter: | Sébastien Jodogne <s.jodogne> |
Component: | Plugin - DICOMweb | Assignee: | Sébastien Jodogne <s.jodogne> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | --- | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All |
Description
Sébastien Jodogne
2020-06-29 15:16:23 CEST
[BitBucket user: Sébastien Jodogne] [BitBucket date: 2019-12-24.11:07:39] This issue is under active discussion on the forum: https://groups.google.com/d/msg/orthanc-users/y1N5zOFVk0M/wal0jtwpBgAJ [BitBucket user: Sébastien Jodogne] [BitBucket date: 2020-02-17.15:36:25] This is fixed by the following changeset: https://hg.orthanc-server.com/orthanc-dicomweb/changeset/27001924c4564a517f1a4c6dacc3453a629aff04 This is documented in the Orthanc Book: https://book.orthanc-server.com/plugins/dicomweb.html#server-related-options [BitBucket user: Sébastien Jodogne] [BitBucket date: 2020-02-17.15:51:43] Besides the new options “StudiesMetadata“ and “SeriesMetadata”, the forthcoming DICOMweb plugin 1.1 does not access the “DICOM-as-JSON” attachments anymore. This divides by two the number of access to the storage area, even if the new options are set to “Full”. Here is a status in the number of accesses to the storage area in the various configurations: ```plaintext Test command (this is the VIX dataset): $ curl http://localhost:8042/dicom-web/studies/2.16.840.1.113669.632.20.1211.10000315526/metadata DICOMweb plugin 1.0: $ ./Orthanc Configuration.json --verbose 2>&1 | grep 'Reading attachment' | wc -l 500 DICOMweb plugin mainline, with "StudiesMetadata" equal to "Full": $ ./Orthanc Configuration.json --verbose 2>&1 | grep 'Reading attachment' | wc -l 250 DICOMweb plugin mainline, with "StudiesMetadata" equal to "MainDicomTags" (only uses the Orthanc index): $ ./Orthanc Configuration.json --verbose 2>&1 | grep 'Reading attachment' | wc -l 0 ``` |