# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1623252958 -7200
# Node ID bcd1a6a89280715a7f2a73243e9916266d70bfdb
# Parent  6501004571937fefe968bfb524feb8dec1ebf4e1
replace, keep and remove accept sequences in Orthanc 1.9.4

diff -r 650100457193 -r bcd1a6a89280 Sphinx/source/users/anonymization.rst
--- a/Sphinx/source/users/anonymization.rst	Thu Jun 03 21:26:40 2021 +0200
+++ b/Sphinx/source/users/anonymization.rst	Wed Jun 09 17:35:58 2021 +0200
@@ -40,7 +40,7 @@
                 "DicomVersion" : "2017c"
               }' > Anonymized.dcm
 
-Explanations:
+**Explanations:**
 
 * New UUIDs are automatically generated for the study, the series and
   the instance.
@@ -65,12 +65,21 @@
   introduced in Orthanc 1.3.0. In earlier version, the ``2008``
   standard was used. If the parameter is absent, the highest version
   that is supported by Orthanc is used.
+* ``Remove`` can also be used to provide a list of tags to be manually
+  deleted.
 
+**Important:** Starting with Orthanc 1.9.4, the ``Replace``, ``Keep``
+and ``Remove`` fields can also specify sequences, using the same
+syntax as the ``dcmodify`` command-line tool (wildcards are supported
+as well). Earlier versions were limited to top-level tags in the DICOM
+dataset. Check out the integration test ``test_modify_subsequences``
+for `examples
+<https://hg.orthanc-server.com/orthanc-tests/file/default/Tests/Tests.py>`__.
 
 **Implementation:** Internally, the setup of the anonymization
 profiles can be found in the methods ``SetupAnonymizationXXX()`` of
 the class ``Orthanc::DicomModification`` (cf. `source code
-<https://hg.orthanc-server.com/orthanc/file/tip/OrthancFramework/Sources/DicomParsing/DicomModification.cpp>`__).
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.9.3/OrthancFramework/Sources/DicomParsing/DicomModification.cpp>`__).
 
 
 Modification of a Single Instance
@@ -94,7 +103,7 @@
                 "Transcode": "1.2.840.10008.1.2.4.70"
               }' > Modified.dcm
 
-Remarks:
+**Remarks:**
 
 * The ``Remove`` array specifies the list of the tags to remove.
 * The ``Replace`` associative array specifies the substitions to be applied (cf. anonymization).
@@ -109,7 +118,7 @@
   modification to one of the ``PatientID``, ``StudyInstanceUID``,
   ``SeriesInstanceUID``, and ``SOPInstanceUID`` requires ``Force`` to
   be set to ``true``, in order to prevent any unwanted side effect.     
-
+  
 .. highlight:: json
 
 * To replace a sequence of tags, you may use this syntax:: 
@@ -140,6 +149,16 @@
       }
     }
 
+
+**Important:** Similarly to anonymization, starting with Orthanc
+1.9.4, the ``Replace``, ``Keep`` and ``Remove`` fields can also
+specify sequences, using the same syntax as the ``dcmodify``
+command-line tool (wildcards are supported as well). Earlier versions
+were limited to top-level tags in the DICOM dataset. Check out the
+integration test ``test_modify_subsequences`` for `examples
+<https://hg.orthanc-server.com/orthanc-tests/file/default/Tests/Tests.py>`__.
+
+
 .. _study-modification:
 
 Modification of Studies or Series