From 96709b6e303d3cfd0d5942ed587892906e4c845d Mon Sep 17 00:00:00 2001
From: Nico-AP <Nico-AP@users.noreply.github.com>
Date: Mon, 4 Dec 2023 07:13:48 +0000
Subject: [PATCH] deploy: 0af697f792dfdac97074d52b61eebdacfb0036d2

---
 ddm/main/for_researchers.html | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

diff --git a/ddm/main/for_researchers.html b/ddm/main/for_researchers.html
index 30078fa8..fed64192 100644
--- a/ddm/main/for_researchers.html
+++ b/ddm/main/for_researchers.html
@@ -597,8 +597,15 @@ <h5 id="_configure_donation_blueprint"><a class="anchor" href="#_configure_donat
 <dt class="hdlist1">Expected fields</dt>
 <dd>
 <p>The fields that must be contained in the donated file. If a file does not contain
-one or more of the fields defined here, it will not be accepted as a donation.
-Put the field names in double quotes (") and separate them with commas ("Field A", "Field B").</p>
+<strong>all</strong> fields defined here, it will not be accepted as a donation.<br>
+Put the field names in double quotes (") and separate them with commas ("Field A", "Field B").
+You can also use regular expressions (regex) to match expected fields - for this, you
+must enable the <code>expected field regex matching</code> option (see below).</p>
+</dd>
+<dt class="hdlist1">Expected field regex matching</dt>
+<dd>
+<p>Select if you use a regex expression in the <code>Expected fields</code>
+setting.</p>
 </dd>
 <dt class="hdlist1">Expected File Format</dt>
 <dd>
@@ -613,7 +620,7 @@ <h6 id="_json_specific_settings"><a class="anchor" href="#_json_specific_setting
 <dt class="hdlist1">Extraction Root</dt>
 <dd>
 <p>Indicates on which level of the files' data structure information
-should be extractet. If you want to extract information contained on the first
+should be extracted. If you want to extract information contained on the first
 level (e.g., <code>{'field to be extracted': value}</code>, you can leave this field empty.
 If you want to extract data located on a higher level, then you would provide
 the path to the parent field of the data you want to extract (e.g., if your json
@@ -658,7 +665,12 @@ <h5 id="_extraction_rules"><a class="anchor" href="#_extraction_rules"></a>Extra
 </dd>
 <dt class="hdlist1">Field</dt>
 <dd>
-<p>The field to which the rule will be applied.</p>
+<p>The field to which the rule will be applied. This can either be a "normal" string or a
+regular expression (regex). If the latter is the case, you must also select <code>regex field</code> (see below).</p>
+</dd>
+<dt class="hdlist1">Regex field</dt>
+<dd>
+<p>Select if you use a regex expression in the <code>Field</code> setting of this rule.</p>
 </dd>
 <dt class="hdlist1">Extraction Operator</dt>
 <dd>