comparison NEWS @ 5656:a3c244090f67 find-refactoring

integration mainline->find-refactoring
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 06 Jun 2024 13:24:04 +0200
parents 3f13db27b399 5e99cf9eebcf
children 301212a3fa08
comparison
equal deleted inserted replaced
5641:3f13db27b399 5656:a3c244090f67
1 Pending changes in the mainline 1 Pending changes in the mainline
2 =============================== 2 ===============================
3
4 * TODO-FIND: complete the list of updated routes:
5 /studies?expand and sibbling routes now also return "Metadata" (if the DB implements 'extended-api-v1')
6
7
8 Version 1.12.4 (2024-06-05)
9 ===========================
3 10
4 REST API 11 REST API
5 -------- 12 --------
6 13
7 * API version upgraded to 24 14 * API version upgraded to 24
8 * Added "MaximumPatientCount" in /system 15 * Added "MaximumPatientCount" in /system
9 * Added a new "LimitToThisLevelMainDicomTags" field in the payload of 16 * Added a new "LimitToThisLevelMainDicomTags" field in the payload of
10 /patients|studies|series/instances/../reconstruct to speed up the reconstruction 17 /patients|studies|series/instances/../reconstruct to speed up the reconstruction
11 in case you just want to update the MainDicomTags of that resource level only 18 in case you just want to update the MainDicomTags of that resource level only
12 e.g. after you have updated the 'ExtraMainDicomTags' for this level. 19 (e.g., after you have updated the "ExtraMainDicomTags" for this level)
13 * The "requestedTags" GET argument was deprecated in favor of "requested-tags". 20 * The "requestedTags" GET argument is deprecated in favor of "requested-tags"
14 * Fixed broken /instances/../tags route after the calling 21 * Added "?whole" option to "/instances/{id}/tags" to access tags stored after pixel data
15 /studies/../reconstruct when changing the "IngestTranscoding". 22
16 * TODO-FIND: complete the list of updated routes: 23 Plugins
17 /studies?expand and sibbling routes now also return "Metadata" (if the DB implements 'extended-api-v1') 24 -------
18 25
19 Plugins 26 * Multitenant DICOM plugin: added support for locales.
20 -------
21
22 * Multitenant DICOM plugin: added support for locales
23 * Housekeeper plugin: 27 * Housekeeper plugin:
24 - Added an option "LimitMainDicomTagsReconstructLevel" 28 - Added an option "LimitMainDicomTagsReconstructLevel"
25 (allowed values: "Patient", "Study", "Series", "Instance"). This can greatly speed 29 (allowed values: "Patient", "Study", "Series", "Instance"). This can greatly speed
26 up the housekeeper process e.g. if you have only update the Study level ExtraMainDicomTags. 30 up the housekeeper process, e.g. if you have only update the Study level ExtraMainDicomTags.
27 - Fixed broken /instances/../tags route after running the Housekeeper 31 - Fixed broken /instances/../tags route after running the Housekeeper
28 after having changed the "IngestTranscoding". 32 after having changed the "IngestTranscoding".
29 * SDK: added OrthancPluginLogMessage() that is a new primitive for 33 * SDK: added OrthancPluginLogMessage() as a new primitive for plugins
30 plugins to log messages. This new primitive will display the plugin 34 to log messages. This new primitive will display the plugin name,
31 name, the plugin file name, and the plugin line number in the 35 the plugin file name, and the plugin line number in the logs. If
32 logs. If they are not using the LOG() facilities provided by the 36 they are not using the LOG() facilities provided by the
33 OrthancFramework, plugins should now use ORTHANC_PLUGINS_LOG_INFO(), 37 OrthancFramework, plugins should now use ORTHANC_PLUGINS_LOG_INFO(),
34 ORTHANC_PLUGINS_LOG_WARNING(), and ORTHANC_PLUGINS_LOG_ERROR(). 38 ORTHANC_PLUGINS_LOG_WARNING(), and ORTHANC_PLUGINS_LOG_ERROR().
35 39
36 Maintenance 40 Maintenance
37 ----------- 41 -----------
38 42
39 * C-Find queries: 43 * C-Find queries:
40 - In C-Find queries including GenericGroupLength tags, Orthanc was still 44 - In C-Find queries including "GenericGroupLength" tags, Orthanc was still
41 extracting these tags from the storage although they were already ignored 45 extracting these tags from the storage although they were already ignored
42 and not returned in the response. 46 and not returned in the response.
43 They are now removed from the query earlier to avoid this disk access that 47 They are now removed from the query earlier to avoid this disk access that
44 could slow down the response time. Note that this seems to happen mainly 48 could slow down the response time. Note that this seems to happen mainly
45 when the query originates from some GE devices (AWS). 49 when the query originates from some GE devices (AWS).
46 - TimezoneOffsetFromUTC is now ignored for matching. 50 - "TimezoneOffsetFromUTC" is now ignored for matching.
47 * The 0x0111 DIMSE Status is now considered as a warning instead of an error 51 * The 0x0111 DIMSE Status is now considered as a warning instead of an error
48 when received as a response to a C-Store. 52 when received as a response to a C-Store.
49 See https://discourse.orthanc-server.org/t/ignore-dimse-status-0x0111-when-sending-partial-duplicate-studies/4555/3 53 See https://discourse.orthanc-server.org/t/ignore-dimse-status-0x0111-when-sending-partial-duplicate-studies/4555/3
50 * Removed potential PHI from the logs when Orthanc encounters an error while 54 * Removed potential PHI from the logs when Orthanc encounters an error while
51 creating a ZIP archive. 55 creating a ZIP archive.
52 * Monitoring of stable resources now also takes into consideration the 56 * Monitoring of stable resources now also takes into consideration the
53 resource type, not only the resource identifier identifier. 57 resource type, not only the resource identifier identifier.
54 * DICOM TLS: 58 * DICOM TLS:
55 - In prior versions, when "DicomTlsRemoteCertificateRequired" was set to false, Orthanc 59 - In prior versions, when "DicomTlsRemoteCertificateRequired" was set to false, Orthanc
56 was still sending a client certificate request during the TLS handshake but was not triggering 60 was still sending a client certificate request during the TLS handshake but was not
57 and error if the client certificate was not trusted (equivalent to the --verify-peer-cert DCMTK option) 61 triggering and error if the client certificate was not trusted (equivalent to the
58 From this version, if this option is set to false, Orthanc will not send a 62 "--verify-peer-cert" DCMTK option). Starting with Orthanc 1.12.4, if this option is
59 client certificate request during the TLS handshake anymore (equivalent to the --ignore-peer-cert 63 set to "false", Orthanc will not send a client certificate request during the TLS
60 DCMTK option). 64 handshake anymore (equivalent to the "--ignore-peer-cert" DCMTK option).
61 - When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false, 65 - When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false,
62 Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided. 66 Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided.
67 - New configuration options:
68 - "DicomTlsMinimumProtocolVersion" to select the minimum TLS protocol version
69 - "DicomTlsCiphersAccepted" to fine tune the list of accepted ciphers
70 * Fixed broken /instances/../tags route after calling of
71 /studies/../reconstruct after having changed the "IngestTranscoding".
63 * Upgraded dependencies for static builds: 72 * Upgraded dependencies for static builds:
64 - boost 1.85.0 73 - boost 1.85.0
65 74
66 75
67 Version 1.12.3 (2024-01-31) 76 Version 1.12.3 (2024-01-31)