DDM: Create Blueprint

General Settings

Name For internal use (e.g., "watch_history")

Associated File Uploader The File Uploader through which the related file will be uploaded

Display Settings

Configure what participants see on the donation interface

Display name Title of the Blueprint shown to participants (e.g., "Watch History").

Description Explains to participants what data is extracted (e.g., "Videos you watched and when")

Display order Controls display order in Blueprint list. Lower = first.

Data Extraction Configuration

File Identification

Files are identified by their path in the zip file. For example, if the file is some_data.json at the root of the zip, enter some_data.json as the file path.

You can use regex patterns or define multiple paths, which are tried in priority order (lower numbers first; useful if the filename may not always be the same).

Filepath	Is regex	Priority	Remove
No file paths added

The uploader extracts all file paths from the uploaded zip and tries to match them against your specified path(s).

Matching works from the right: data.json will match both root/data.json and root/some-folder/data.json, selecting the first match. Be specific enough to avoid unintended matches.

If a match is found, the uploader validates the file content and extracts the data.

If no match is found, it tries the next path you defined, or displays an information message to the participant that the file could not be found in the uploaded zip-file.

Regex matching

Mark a file path as is regex to use regex patterns. For example, /specific folder/.*\.json$ matches both /specific folder/my_data.json and /specific folder/meine_daten.json — useful when filenames vary based on account settings.

For single file uploads, the participant will upload a single file – file identification is therefore not necessary.

File Validation

Configure how an identified file is validated

Expected file format

Csv delimiter The character that separates values in the CSV (e.g., , ; or \t for tab). If left empty, the delimiter is inferred automatically.

Record/entry separator The character(s) that separate one entry from the next in the file — for example, a blank line or a single line break. Use \n for a line break, or \n\n for a blank line between entries.

Field separator The character sequence that separates individual fields within a single record (e.g., a line break if each field is on its own line). Use \n for a line break.

Key-value separator The character that separates a field's name from its value within a line (e.g., : in Name: John, or = in name=John).

Skip header lines How many lines to skip at the beginning of the TXT-file.

Skip footer lines How many lines to skip at the end of the TXT-file.

Ignore blank lines

Trim whitespace Whether to trim whitespace around records/entries and key-value pairs.

Expected fields Comma-separated, in double quotes: "Field A", "Field B"

Expected fields use regex matching

When a file has been identified, it is validated in order:

Format correct: The file matches the expected file format.
Fields present: The file contains all expected fields.

If any step fails, no data is extracted and the participant sees an error explaining what went wrong.

Data Extraction

Configure what data will be collected

You can configure the data extraction once you have created the Blueprint.

Advanced Settings

Backup for If set, this blueprint is used as a fallback when the referenced blueprint's parser fails to extract data (either because it does not find the expected file or because it encounters an error).

Backup priority If a Blueprint has multiple backups, backup blueprints with lower priority values are tried first when the main blueprint's parser fails.