Closed alexandroidii closed 3 years ago
Incidents are what will be submitted by the end users.
As incidents start to show patterns, for example, the same industry type, bribe type, and region could be turned into a scenario that has details on common ways to resolve the issue properly, as well as a list of incidents that match that same scenario.
Scenarios would be created by the reviewers as they spot the patterns.
The Resist document is a tool with example scenarios but the list of scenarios will grow as new types incidents start reoccurring.
We need to see if there are other fields that need to be added to a scenario.
It's been a while since we set this up, but maybe we should get a confirmation on the difference between the incident and the scenario.
From what I remember, the Incident is something that actually happened, and a scenario is a fictitious example used more for training then reporting. Seems like lots of fields if not all fields would over lap. If they do, should there not just be 1 type which you can mark as a training scenario? Or mark it as good material to learn from?