1. Sharing models as social objects through HydroShare
Jonathan L. Goodalla, Mohamed M. Morsya , Anthony M. Castronovab, Pabitra Dashc, Venkatesh Merwaded, Jeffrey M. Sadlera, Jeffery Horsburghc, and David G. Tarbotonc
aUniversity of Virginia, Charlottesville, VA
bCUAHSI, Medford, MA
cUtah State University, Logan, UT
dPurdue University, West Lafayette, IN

2. It is time consuming and complicated to build hydrologic models
Introduction
It is time consuming and complicated to build hydrologic models
Improved methods and tools for sharing these models with appropriate metadata are needed to …
foster reproducibility of other’s work
encourage reuse and extensions of models
A challenge is how to achieve model sharing given the diversity of hydrologic models.
2 models gear shift to model share

3. Why metadata framework for describing and sharing models are needed?
We have reached a point of complexity that necessitates methods and tools for organizing existing resources.
Think of not just the software required to execute models, but also the many model applications that have been performed using these model software.
A metadata framework is required to support discovery, sharing, access and reuse of the model and its associated datasets.

4. HydroShare
HydroShare is a web-based collaborative system with the goal of:
sharing
accessing
discovering
The metadata framework developed here is being used for sharing model resources within HydroShare, but could have other applications too.
hydrologic data and models

5. Examples of efforts done to develop a Earth science model metadata
CSDMS developed certain metadata for several Earth surface dynamics model programs.
es-doc developed tools to describe Earth system models. These tools are based on the Common Information Model (CIM) standard. CIM is a metadata standard specific to describing Earth system models.

6. System design
Model concepts and relationship
In this work, a computational model is represented as two key concepts:
model program: the software for executing a model simulation and generating outputs.
model instance: the input files required to execute a specific model program.
A model instance is executed by a model program.

7. System design
Model resources metadata analysis
Model Program

8. Allow for additional model specific metadata fields
System design
Model resources metadata analysis
Model Instances
Can be implemented by ANY model instance
Allow for additional model specific metadata fields

9. System design
Model resources metadata analysis
Generic Model Instance

10. System design
Model resources metadata analysis
SWAT model instance

11. Example Use Case
We completed a model-based study of an urban watershed in Columbia, SC
The study focused on distributed LID stormwater infrastructure as a flood mitigation strategy and the study was published in the Journal of Hydrologic Engineering.
We wish to share the model instances created through our study through HydroShare.
This will allow others to more easily verify, repeat, and expand on our study.

12. Example Use Case
Step 1: Identify HydroShare Resources

13. Example use case Step 2: Create New Resources in HydroShare
Modeling resources available on

14. Model program specific metadata page in edit mode
Example use case
Step 3: Enter metadata for new Model Program resource
A model program resource stores the software for the specific version of SWMM used in the study.
Only need to complete this step if the model program resource is
not already within HydroShare
Model program specific metadata page in edit mode

15. Example use case
Step 4: Enter metadata for new Model Instance resources
Only these two additional metadata fields (beyond Dublin Core) are required for a Generic Model Instance
Model instance specific metadata page in edit mode

16. Example use case
Step 4: Enter metadata for new Model Instance resources
A Model Instance resource can have spatial and temporal coverage metadata as defined in Dublin Core
Model instance coverage metadata page in edit mode

17. Metadata Capture

18. Metadata Capture

19. Model Instance for Rocky Branch simulation
Metadata Capture
Model Instance for Rocky Branch simulation
Morsy, M. (2015). Rocky Branch watershed simulation, HydroShare, 

20. Metadata Capture

21. Metadata Capture

22. Model Program for EPA-SWMM 5
Metadata Capture
Model Program for EPA-SWMM 5
Rossman, L., T. Schade, D. Sullivan, R. Dickinson, C. Chan, E. Burgess (2016). Storm Water Management Model (SWMM), Version with Low Impact Development (LID) Controls,  accessed 6/2/2016, replicated in HydroShare at:

23. Metadata Capture

24. Metadata Capture

25. Metadata Capture
Executed By relation to link the Model Instance with the Model Program used for execution

26. SWAT model instances can be shared with the 3rd party SWATShare
HydroShare to SWATShare

27. Metadata is compatibility between HydroShare and SWATShare

28. Summary
We present a model metadata framework for general to specific model metadata capture to support the wide range of models used within the hydrology community.
The metadata framework is built from general standards including RDF, Dublin Core, and BagIt that allows the resources to be more easily shared within and outside of the discipline.
We show how having standard resource descriptions enables interoperability between cyberinfrastructure systems (e.g., HydroShare and SWATShare).
Providing the right balance between minimal and rich metadata is a challenge and will require an iterative process.

29. Next steps
New functionality to automate metadata extraction when a resource is uploaded.
Expanding metadata framework for more specific model instance resource types. Ideally allow 3rd party developers an easy path for adding their own specific model instance resource types.
Providing server-side execution of model instances directly through the HydroShare user interface and potentially through the HydroShare API.

30. Thank You
Contact info:
Jon Goodall,
Associate Professor
Department of Civil and Environmental Engineering
Department of Computer Science, by courtesy
University of Virginia, USA