The agenda as discussed during the conf call on 4/1The agenda v. 0.2 as a docx file
- planning for years 3 and 4 of the grant
- mutual education on technologies that should be jointly used
Central, Desktop, Server, then how they interact
Thoughts from Tim:
- System architecture
- Desktop HIS
- Dealing with ontologies
- HISCentral and HIS central services
- Start on SourceControl, Jira, ADO.NET, etc.
- Additional data types to handle
- Progress with standards
- Planning for training and support
- Collaborative use of HIS with large tiled wall displays (a short trip to Calit2?)
- Operational discussion (what is operational and how it is validated/maintained
- HIS Website and User Group
- HIS Branding (website look, terms: HydroSeek vs Hydroseek, WaterOneFlow Web Services vs Water Data Services, Interactive Data Loader, etc.)
Have we accomplished what the standing committee suggested we do, which is to harden up our existing work? I believe documentation is part of that process. We don’t currently have instructions on how to use HIS Central. Is the rest of our documentation up to date?
When does our HIS User Liaison start at the CUAHSI office? An outcome of the KSU workshop is that people realized they knew of other groups doing similar things as HIS or potential data sources that could be part of HIS. We need a person to interact with those groups and data sources to promote more participation in HIS. We need this participation, because as you’ll notice, our list of public registered networks is dwindling. Were we once at 50, and now we’re down to 36? Part of the issue is that we’ve taken some public services offline until we assure data quality, while another part is that we just haven’t added that many services since the initial thrust with test beds. Could the HIS User Liaison handle promoting HIS with these potential new participants in the system?
I like the idea of reviewing our operational system as described below. For developmental activities, it seems like major software components to discuss are HIS Desktop, and HIS Central metadata services. We also need to figure out how the ontology fits into the Central, Server, and Desktop.
Also, what is our development strategy for upcoming software like HIS Desktop, and existing software like HydroGET? For example, the MySelect structure of HydroGET isn't fully compliant with WaterOneFlow. As the author is graduating soon, who will maintain the software and make these kinds of improvements? Do we even bother to maintain it?
9:00 Overview of System Components and Status of Documentation, Testing
- Underlying Technologies
- WaterOneFlow Web Services
- Observations Data Model
- Data Publication (ODM Service)
- Data Loader
- Scheduled Data Loader
- Controlled Vocabulary
- Required Metadata
- HIS Central Registration
- HydroTagger Ontology Mapping
- Metadata catalog harvesting and maintenance
- Downloading Log by service
- Reports for publishers (variable mapping, etc.)
- Data Publication (Hybrid Services)
- Ontology mapping
- Metadata harvesting
- Service maintenance
- HydroExcel (Tim - 5 minutes)
Note:To keep this to a two-hour block, we need to assemble the information available for each of these items in advance. The objective of this discussion to review what has been done on documentation and testing of each of these items and assigning any remaining work to a person with a due date. The objective is not to actually discuss features, performance, or changes to any of these components.