1. Faceted Search for Hydrologic Data Discovery Alex Bedig Alva Couch Tufts University, Medford, MA

2. Overview of Relevant Architecture Source: http://www.cuahsi.org/his

3. “Ontology” A collection of terms along with a set of relationships between terms. In our case, main relationship is hierarchical: “is a subconcept of”. Provides a mapping between user notions of data, and data as it is found in HIS Central.

4. Discovery in HydroDesktop Source: HydroDesktop

5. Procedure of Discovery in HydroDesktop 1.Specify spatial and temporal dimensions. 2.Choose terms from the “Hydrosphere” variable name ontology. 3.Click search, wait… for results… usually.

6. April 15, 2011 Usability Study CUAHSI Ontology Startree

7. Use Case 1: No Matching Series User’s selections return no series, no feedback suggesting which constraints could be relaxed. ISSUE: Search should occur in multiple steps, informing the user of where data exists in each step. SOLUTION:

8. Use Case 2: No Familiar Terms User is unfamiliar with the terms provided in the variable-name ontology, leading to low confidence in search results. ISSUE: Search should allow for multiple representations of the same canonical names, eliminate options based upon known terms, and present only options for which data is available. SOLUTION:

9. Use Case 3: Too Many Results User’s search returns a large number of results; filtering any further requires download of results for client-side manipulation. ISSUE: Exposing multiple dimensions of metadata in the search interface allows for more precise search, reducing download time and selection procedures. SOLUTION:

10. Demo! SOAP Endpoint: http://cuahsi.eecs.tufts.edu/FacetedSearch/MultiFacetedHISSvc.svc?wsdl http://cuahsi.eecs.tufts.edu/FacetedSearch/MultiFacetedHISSvc.svc?wsdl Prototype Services Demonstrated: GetAllOntologyElements GetTypedOntologyElementsGivenConstraints ConductFacetedSearch

11. Conclusions Faceted search of HIS Central improves the user experience by: – Eliminating “wasted” time in which a search returns no data. – Allowing multiple metadata dimensions to be specified. – Allowing multiple ontological representations of vocabulary. – Moving towards the use of multiple vocabularies. Thus increasing the likelihood that a user finds relevant data.

12. Conclusions Faceted search requires some rethinking of HIS central, including – Services that return whether series exist for a query. – Support for multi-dimensional queries. – A need for speed that may justify supercomputing solutions.