The Model Catalogue is a web product that complements eWater Source (and . The primary role of Model Catalogue is to provide a community space for organisations in the water modelling industry to share Source water models with the rest of the water modelling community.

Model Definitions and Model Artefacts

The Model Catalogue only stores model definitions (or simply definition). A model definition contains inform about the model. It includes core information such as the models:

A model definition is just a reference to the model artefacts. The model artefacts are the physical files that comprise a complete functional water model. They typically include the following files:

• Project files (eg rsproj)
• Plugins
• Water Modelling Software (exe and dll files)
• Input data (eg.csv)

The model artefacts themselves are stored in the /wiki/spaces/EI/pages/52563693. 

Organisations

Model definitions are owned by organisations. An individual model definition is owned by one and only one organisation. Model definitions are not directly owned by an individual user, 

A

Membership

All users of the Model Catalogue need to be registered in the system. Membership is currently by invitation only. There is no anonymous access.

Providers and Consumers

Consumers always have access to publicly available model definitions. However, by default they do not automatically have access to the model artefacts. Currently, access to the Model Datastore from the Model Catalogue is a manual offline process managed by the organisation that owns the 

Workflow

Organisations create a model definition. The model definition contains models that, enhance it with additional metadata and (optionally) publish the model to other users. The other users can then discover the model definition

It can be accessed via catalogue.ewater.org.au.

The following is a description of the typical workflow users experience:

1. A provider creates a model definition (aka registers) a model that their organisation owns in the Model Catalogue. The model definition contains core information about the model (eg. repository, scenario, changes, versions, maps).
2. A consumer (not from the same organisation) can then find the model definition in the catalogue by using various tools (maps, searching and filtering)
3. External Modellers can then request access to models that they wish to have access to.
4. Internal Modellers can approve or reject requests to access their models.
5. External Modellers, once approved, can then access the model files
6. External Modellers can review the model and provide feed back to the Internal Modeller.
7. Internal modellers can incorporate the feedback into their models to make for better decision making.

Troubleshooting and FAQs

If you have further questions please contact us or visit our online service desk.