<config>
can occur repeatedly for different projects or work steps in order to be able to perform different actions within different workflows. The elements <namepart>
are decisive for the generation of the file names.project
<config>
is to apply. The name of the project is used here. This parameter can occur several times per <config>
block.step
<config>
should apply. The name of the workflow step is used here. This parameter can occur several times per <config>
block.startValue
counter
should start.namepart
static
), use variables from Goobi (variable
) and generate a counter. The number of digits defined is crucial for generating the counter (counter
). For example, the value 00000
would generate five-digit numbers with any leading zeros. The components of the file name defined in this way are concatenated together for naming purposes and then supplemented by the actual file extension to name the file.<namepart>
are evaluated, assigned the appropriate values for the counter and variables from Goobi workflow and then linked together. The file names created in this way are now applied to all the relevant directories in the Goobi process and are supplemented with the correct file name extensions (e.g. .tif
).barcode
within the file name, it will also be named according to the naming scheme. However, the value 0
is set as counter here.