The Lifecycle of a Signal

Summary

The journey of a signal within the GSE can be thought of in terms of a sequence of events referred to as reports.

The first report for a signal is most often sent by a GSE member either via the api or by uploading a CSV file and is classified with a status of new. This report is made available in near real time for other GSE members to retrieve for analysis and use in their own platforms.

Following a new report for a signal, a number of follow up feedback reports can be created for this signal which are either sent from GSE members using the Feedback API or using the online feedback function. Feedback reports are also generated internally by the GSE.

Feedback reports are classified with 3 distinct types:

• Enrichment Feedback - These reports add extra data or context to a signal. The GSE itself generates Enrichment Feedback reports for certain classes of signal shortly after receipt of a new report and other users are also able to submit Enrichment Feedback reports to add additional data or context to signals.
• Action Feedback - These reports are sent from other GSE users to confirm that they have taken some sort of action on a signal. This could be for example that they have executed a take down or blocked something at their end.
• No Action Feedback - These reports are sent from other GSE users to proactively confirm that they took no action on a signal. This might be for example that there was no evidence of an issue at their end or they felt it was a false positive or inaccurate signal.

Signal Lifecycle

The following diagram summarises the key reports which make up the typical lifecycle for a signal in the GSE.