The Scenarios tab contains the set of scenario definitions contained in the model definition. It allows users to know what scenarios are contained in the underlying model and their purpose artefacts.
Definitions
A scenario definition has is a unique name and description of a scenario contained within in the underlying water software model. For example, an simple example may be for scenarios "Wet", "Average", "Dry".
TODO: Screen shot of these models
A scenario definition is specific to the model defintion that contains it. They are not shared accross model definitions. Multiple model definitons may contain the same scenario individual scenarios but they are treated completely separate in the Model Catalogue.
A scenario definition is a loose concept in the Model Catalogue. The Model Catalogue does not restrict the scope, purpose or context of the scenario it refers to. A water modeller is free to define a scenario as they think appropriate.
The Model Catalogue may contain all or only some of the scenario definitions of the scenarios contained in the underlying software model. A scenario definition is a loose concept in Providers are free to choose if only a subset of the models are published into the Model Catalogue. It may represent
Furthermore, a scenario definition may refer to a wide varierty of physicall physically different model artefacts. This is because a water modeller may choose to physically represent a scenario in modelling software maybe physically represented in a wide variety ways A scenario definition has a unique name and description. These may include:
- Scenario Input Sets
- Separate project files
- Different parameter sets defined in a scripts.
- A Input set properties provided to the command line runner.
- Any combination of the above.
A water modeller may choose to represent a scenario in any one of this menas. The This loose definition exists to allow water modellers the flexibility to irrespective of how they are
The model definitions are managed manually by the provider. There is not (currently) any automated process inspection of the model artefacts to determine any scenarios that are contain within them. The onus is on providers to ensure that the scenario definitons are represented accurately in the Model Catalogue.
Usage
Consumers
Consumers can . They can use use this information to determine if the model defintion contains scenarios use the Scenarios tab to discover information about the scenarios, assess whethe they that are of interest to them, and then to potentially (optionally) request access to the model artefacts.
This tab is read only for consumers.
Providers
Providers use the Scenarios tab to manage scenarios contained in the model. They can add(ie createadd/edit/delete scenarios) the current models scenario definitions.
The button 
will prompt the providers to a pop up window to add sceneariosscenarios. Providers can edit existing scenarios by clicking on the 
and the 
button will copy the guid of the scenario to the clipboard.
TODO: Add screenshot of creating, editing, deleting etc.
To delete a scenario simply click the 
button.
...