This windows allows to edit an Early Warning Alert (EWA) definition for a Plasmid Typing. Unlike the Early Warning Alerts for cgMLST the plasmid EWAs are defined for a Typing, and not for a Project.

The alert can be activated or deactivated using the checkbox. The EWAs are triggered when the pipeline is used to create new Samples.

Metadata Criteria

It is possible to define metadata limit criteria for the alert. If multiple limits are defined they will be linked by the AND operator.

• Limit to same location: The hit sample must have the same location as the query sample. If this limit is used the option match if missing is set by default. Thereby an alert is triggered even if the query and/or hit sample location field is empty. If this option is deselected no alert is reported if the query and/or hit sample location field is empty. The Country of Isolation or the City of Isolation can be defined as location field.
• Limit to date: The date of the hit sample must match within a given time period (days, weeks, months, or years) with the date of the query sample. If this limit is used, the option match if missing is set by default. Thereby an alert is triggered even if the query and/or hit sample date field is empty. The Collection Date or Created for the sample entry creation date can be defined as date field.
• Limit to same value in fields: Other database fields than location and/or date fields that must match can be selected here. If this limit is used, the option match if missing is deselected by default. Thereby no alert is reported if the query and/or hit user defined fields is empty.
• Limit by tags: Only query samples with the defined tag(s) will initiate the alert search and only similar samples that fulfill the tag criteria will be reported as hit samples. If multiple tags are selected, they will be linked by the AND operator.

Hint: The EWA searches are performed directly after a new sample is processed and stored. Therefore, the metadata (location, date, user defined fields, and tags) must be entered in advance (e.g., by spreadsheet import of metadata, pipeline tags, and/or spec files) if they should be effective as limiting criteria in the EWA.