86
EARTHCUBE COMMUNITY UPDATES Monthly Webinar November 22, 2013 Organized by the EarthCube Test Enterprise Governance Project

EarthCube Monthly Community Webinar- Nov. 22, 2013

Embed Size (px)

DESCRIPTION

This webinar features project overviews of all EarthCube Awards (Building Blocks, Research Coordination Networks, Conceptual Designs, and Test Governance), followed by a call for involvement, and a Q&A session. Agenda: EarthCube Awards – Project Overviews 1.. EarthCube Web Services (Building Block) 2. EC3: Earth-Centered Community for Cyberinfrastructure (RCN) 3. GeoSoft (Building Block) 4. Specifying and Implementing ODSIP (Building Block) 5. A Broker Framework for Next Generation Geoscience (BCube) (Building Block) 6. Integrating Discrete and Continuous Data (Building Block) 7. EAGER: Collaborative Research (Building Block) 8. A Cognitive Computer Infrastructure for Geoscience (Building Block) 9. Earth System Bridge (Building Block) 10. CINERGI – Community Inventory of EC Resources for Geoscience Interoperability (BB) 11. Building a Sediment Experimentalist Network (RCN) 12. C4P: Collaboration and Cyberinfrastructure for Paleogeosciences (RCN) 13. Developing a Data-Oriented Human-centric Enterprise for Architecture (CD) 14. Enterprise Architecture for Transformative Research and Collaboration (CD) 15. EC Test Enterprise Governance: An Agile Approach (Test Governance) A Call for Involvement!

Citation preview

  • 1.EARTHCUBE COMMUNITY UPDATES Monthly Webinar November 22, 2013 Organized by the EarthCube Test Enterprise Governance Project

2. Webinar Agenda EarthCube Awards Project Overviews EarthCube Web Services (Building Block) EC3: Earth-Centered Community for Cyberinfrastructure (RCN) GeoSoft (Building Block) Specifying and Implementing ODSIP (Building Block) A Broker Framework for Next Generation Geoscience (BCube) (Building Block) Integrating Discrete and Continuous Data (Building Block) EAGER: Collaborative Research (Building Block) A Cognitive Computer Infrastructure for Geoscience (Building Block) Earth System Bridge (Building Block) CINERGI Community Inventory of EC Resources for Geoscience Interoperability (BB) Building a Sediment Experimentalist Network (RCN) C4P: Collaboration and Cyberinfrastructure for Paleogeosciences (RCN) Developing a Data-Oriented Human-centric Enterprise for Architecture (CD) Enterprise Architecture for Transformative Research and Collaboration (CD) EC Test Enterprise Governance: An Agile Approach (Test Governance) A Call for Involvement! 3. EarthCube Web Services Building Block By Tim Ahern Director of Data Services, IRIS IRIS, CUAHSI, IEDA @ LDEO, UNAVCO, Unidata, GPlates-Caltech, RAMADDA 4. OverviewThe objective of the Web Services Building Block is to provide access to scientific data from a variety of domains using relatively simple service interfaces. These interfaces will be as consistent as possible and service as data sources to the Brokering Building Block. The are intended to assist in data discovery, access, and usability across multiple domains. 5. EarthCube Building Block Partners RAMADDALong Tail DataGGPNEON IRISUTEP Gravity Inter Magnet Structural GeologyUNAVCONGDC WSBBCUAHSISDSCCaltech GPlatesOOI Columbia IEDABCubeUnidataCINE RGYWOVODAT 6. Strategy Goal: Create web services that are as uniform as possible and support the most fundamental space-time discovery and access criteria. Two solutions depending on data type: 1. Simple Web ServicesREST-like services offering data in cross-domain formats (text, NetCDF) with common or similar query parameters and patterns.2.3.RAMADDAAn existing data management system that will be extended to support simple web service access.Simple Clients Another benefit is that the envisioned simple services enable simple clients to be developed by scientists 7. There is no better place to have these conversations than in the field EC3Earth-Centered Communication for Cyberinfrastructure: Challenges of field Yosemite/Owens Valley Summer 2014 field trip: data collection, management, and integration Why Concentrate on Field-baseddisciplines of the Geosciences? Initiate relationships andcollaborations challenges field-based to between with regards Common set of geoscientists and computer digitizing our data and making those data Summer 2015 field trip: TBA scientists available through community databases. Applications to participate in fieldtrips:Steering Committee Membership: Richard Allmendinger, Cornell U; Jim Bowring, College of Form available in Chan, U of Utah; Amy Ellwein, Rocky Mountain Bio Charleston; Marjorie December, 2013 Deadline: provides essential information Lab; Yolanda Gil, U of Southern CA; Paul Harnik, Franklin and Marshall College; Eric FieldworkTBA Kirby, Penn State U; Ali Kooshesh, Sonoma State U; Matty Mookerjee, Sonoma State U; Rick about the long-term Inc; Terry Pavlis, theTexas, El Paso; Shanan Morrison, Comprehend Systems history of U of Earths Peters, U of Wisc, Madison; Bala Ravikumar, Sonoma State U; Paul Selden, U of atmosphere, oceans, and tectonic cycles. Kansas; Thomas Shipley, Temple U; Frank Spear, Rensselaer Poly. Inst; Basil Tikoff, U of Wisc, Madison; Douglas Walker, U of Kansas; Mike Williams, U of Mass., Amherst 8. Software Stewardship for Geosciences Principal Investigators:NSF ICER-1343800geosoft.earthcube.orgChristopher J. DuffyDepartment of Civil and Environmental Engineering, Penn State UniversityYolanda GilInformation Sciences Institute, University of Southern California Department of Computer Science, University of Southern CaliforniaJames D. HerbslebInstitute for Software Research, Carnegie Mellon UniversityChris A. MattmannNASA Jet Propulsion Laboratory Department of Computer Science, University of Southern CaliforniaScott D. PeckhamDepartment of Hydrologic Sciences, University of ColoradoErin RobinsonFoundation for Earth Science 9. The Importance of Geosciences Software EarthCube aims to enable scientists solve challenging problems that span diverse geoscience domains This requires not only data sharing but new forms of knowledge sharing The focus of our project is on helping scientists to share knowledge concerning the software they develop 10. Problems: Software Cost Scientists and engineers spend more than 60% of their time just preparing the data for model input or data-model comparison (NASA A40)Common Motifs in Scientific Workflows: An Empirical Analysis. Garijo, D.; Alper, P.; Belhajjame, K.; Corcho, O.; Gil, Y.; and Goble, C. Future Generation Computer Systems, 2013. 11. Problems: Reproducibility 12. The Importance of Geosciences Software The focus of our project is on helping scientists to share knowledge concerning the software they develop Software implements models (ecology, hydrology, climate,...) Embodies very sophisticated knowledge about those models Other software implements data reformatting, QC, etc. Estimated to take 60-80% of effort in most research projects There are repositories of model software (CSDMS, CGI, ESMF,) There are no shared repositories for other geosciences software 13. GeoSoft: Software Stewardship for Geosciences An on-line community for sharing knowledge about geosciences software Intelligent assistance to describe new software: how to use it appropriately, what kinds of data, how it relates to other software Sophisticated search capabilities to find software for their needs Interactive advice on open source software, forming successful developer communities, and other software sharing topics Project involves: geoscientists, social scientists expert in on-line communities, and computer scientists expert in knowledge capture, open source software, and software reuse 14. ODSIP: The Open Data-Services Invocation Protocol Building Blocks for EarthCube Dave Fulker (OPeNDAP, Inc), PI November-2013 15. OPeNDAP Mission: Reduce Data-Usage Impedance 16. Data Access as a Service In the ideal, WebServices building blocks Distance (users to data) does not matter 17. But Distance Does Matter... When combined with factors such as Large data volumes 18. Large Volumes May Be OK With services for creating subsets (OPeNDAPs forte since ~1994) 19. But Subsetting May Be Insufficient Especially for multi-instrument, x-disciplinary studies Users require data that (prior to delivery) have been transformed 20. ODSIP Building Blocks: Data acquisition protocol + rich algebra of preretrieval ops Statistical summarization Binning Remapping Feature extraction ... 21. Summary: theODSIP Project Will Develop a service-invocation paradigm Extend the well-used OPeNDAP protocol Offer an algebra of pre-retrieval operationsPrototype its use in 3 (hard!) geo contexts Climate-model downscaling - native-Hawaiian use Storm surge prediction - coastal NC emergencies SST front analysis/synthesis - from satellite imagesEngage the EarthCube community... 22. BCubeBrokering Building Blocks for EarthCube 1st EarthCube Community Webinar 23. Project Goals Demonstrate both a process and a technology for addressing critical needs of EarthCube A process for understanding and working with scientists and educators while developing infrastructure To develop cyberinfrastructure components that ease the discovery, understanding, use and reuse of data and knowledge 24. Technical Facets of BCube Advance brokering capabilities Mediating new types of resources, including real time data, model components, and workflows Enhancing semantic mediation capabilities Developing public APIs to broker components Establish a testbed in the cloud For purposes of test and evaluation Build and test interfaces with major data repositories Demonstrate ability to find new data and knowledge resources by crawling the web 25. Social Science Facets of BCube Develop innovative methods to capture data practices and needs, and then incorporate these into broker development in an iterative, continuous (i.e. agile) development cycle Observe scientists as they execute scenarios Interview project scientists and developers 26. Educational Facets of BCube Explore ways in which brokering can enhance learning and improve access to data and models by novices Exploit capabilities of broker to interface with social networks Foster interest among early career scientists in cyberinfrastructure development and utilization 27. BCube Organizational Structure 28. http://dx.doi.org/10.7265/N59C6VBCLearn more about our vision for EarthCube 29. Stay Informed! Subscribe to: [email protected] [email protected] [email protected] by visiting https://nsidc.org/mailman/listinfo and bookmark http://nsidc.org/bcube (coming soon) 30. EarthCube Building Blocks: Integrating Discrete and Continuous DataDavid Maidment, Dan Ames, Alva Couch, Ethan Davis EarthCube Community Webinar, Nov 22, 2013 31. Hydrologic domain: Discrete Spatial Objects ObservationsGIS Discrete observations Features In situ sensors E.g. : Waterflow, Streamflow, Discharge 32. Atmospheric Science Domain: Continuous space-time arrays Arrays of multi-dimensional data Coverages Satellite observations E.g. Precipitation maps, Remote Sensing Rain flux, Soil moisture grids, Wind direction/magnitude/elevationClimate 33. Digital BarriersObservations and Time SeriesClimate Observations and GridsGeographic Information Systems (GIS)Remote Sensing 34. Breaking Down Digital Barriers Cataloging and discovery Common Data/Information Model Data access web services, data encodings Data access, analysis, and visualization applications/tools Outreach to the community 35. Leveraging Semantics and Linked Data for Geoscience Data Sharing and Discovery A wide spectrum of maturing methods and tools, collectively characterized as Semantic Web Technologies, enables machines to complete tasks automatically. For the Geosciences, Semantic Web Technologies will vastly improve the integration, analysis and dissemination of research data and results. This EarthCube project will conduct exploratory research applying state-of-the-art Semantic Web Technologies to support data representation, discovery, analysis, sharing and integration of datasets from the global oceans, and related resources including meeting abstracts and library holdings. 36. Leveraging Semantics and Linked Data for Geoscience Data Sharing and Discovery A key contribution will be semantically-enabled cyberinfrastructure components capable of automated data integration across distributed repositories. Woods Hole Oceanographic Institution Cynthia Chandler Lisa Raymond Adam Shepherd Peter Wiebe Lamont-Doherty Earth Observatory Robert Arko Suzanne CarbotteUniversity of Maryland, Baltimore County Tim Finin Tom Narock Wright State University Pascal Hitzler Michelle Cheatham Adila Krisnadhi 37. Peters File 38. Earth System Bridge An NSF funded EarthCube Building Block Scott Peckham, CU-Boulder, PI Co-PIs Cecilia Deluca (NOAA, CIRES), David Gochis (NCAR), Rocky Dunlap (GA Tech), Anna Kelbert (OSU), Gary Egbert (OSU), Eunseo Choi (Memphis), Jennifer Arrigo (CUAHSI) 39. The Science Goal: Improving Environmental Modeling Predictions Mission-Driven agenciesproviding predictions Efficient data and computational enterprise Information to protect life and property Bridging the Gap to Enable Research-to-Operations Operations-to-Research Academic Enterprise Geoscientists advancingthe science Computer scientists advancing the technology Scientific inquiry and hypothesis testing 40. Building the Bridge Framework Definition Language (FDL) Metadata specification Application Architecture Protocols for interaction Mechanics and ImplementationBuild a series of bridges Semantic Frameworksnew services to improve the integration of inter-agency, fourdimensional databases with more heterogeneous academic databases 41. Initial Groups for Demonstration ESMF- Earth System Modeling Framework NUOPC - National Unified Operational Prediction Capability Layer to enhance interoperability FEDERAL CSDMS - Community ACADEMICSurface Dynamics Modeling System Pyre -Python Framework for Coupling CIG Models CUAHSI data services NCAR/UCAR resources WRF CESM CSS-Wx 42. Community Inventory of EarthCube Resources for Geoscience Interoperability dataset discovery is the most often cited issue in executive summaries on the EarthCube web site 43. Goals Inventory of EarthCube information resources datasets, catalogs, vocabularies, information models, services, process models, etc. resources for interoperability links between resources, people, publications, models, etc. cross domain data applications and collaborations community contribution to resource descriptions. 44. Inventory resource scope Activity Person Organization CommunityVocabulary Record Collection CrosswalkSoftware Model WorkflowRepository FacilitySpecification 45. Starting Point: Queries Is there a defined information exchange for topic X Find example implementations of specification X Find resources with subject X (theme, geographic area...) Find datasets with subject Y using query concept expansion Find people who have worked in Domain X, dataset Y, location L Find repositories that will accept my data Find resources annotated by person X Find geographic region having data of type Z Find datasets that contain property X 46. Approach Build on http://connections.earthcube.org Compile metadata for as many resources as we can (collect recommendations at AGU, harvest existing catalogs) Expose through simple search interface Use off the shelf technology: Geoportal, ISO metadata, CSW Make it accessible through EarthCube.org 47. Then add features Links to organizations, researchers, other systems Validation Services Deep registration of datasets/databases Data search capabilities Quality/interop readiness assessment Annotation system 48. Development Team San Diego Supercomputer Center/UCSD Ilya Zaslavsky, DavidValentine, Tom Whitenack Amarnath Gupta, Jeff Grethe (NIF project) Lamont /Columbia Univ./IEDA Kerstin Lehnert, Leslie HsuArizona Geological Survey Stephen RichardUniversity of Chicago Tanu MalikOpen Geospatial Consortium Luis BermudezCommunity Partners Anthony Aufdenkampe: Critical Zone Observatories Shanan Peters: stratigraphy Bernhard Peucker-Ehrenbrink: Global River Observatories RCN projects that plan to organize community resources Test Enterprise Governance Building Blocks projects working on web services, brokering solutions Agencies International 49. RCN: Building a Sediment Experimentalist Network (SEN)Wonsuck Kim (UT Austin) Leslie Hsu (LDEO) Brandon McElroy (U Wyoming) Raleigh Martin (UCLA)meanders channels deltasripplesfloodsmountains 50. Motivation: Sediment experiment data and facilitiesincreasing and improving rapidly, but the rate of science communication, data discovery, and data re-use is not keeping pace.Goal: More accessible data, guidelines, and procedures,leading to better-equipped investigators. Archived, re-usable data for our own and other related research communities.EarthCube RCN: Building a Sediment Experimentalist Network 51. Component1 SENKnowledge Base (SEN-KB): a centralized place for sharing knowledge and data a data repository leveraging and building on the existing National Center for Earth-surface Dynamics (NCED) Data Repository synthesizes research activities of experimentalists by continuously aggregating existing and newly-collected experimental data. make data discoverable to those outside our immediate community e.g. modelers and field geomorphologistsEarthCube RCN: Building a Sediment Experimentalist Network58 52. Component2 SENEducation and Data Standards (SEN-ED): developing and promoting guidelines workshops, special sessions, the NCED Summer Institute educate data management and experimental techniques facilitate development of suggested guidelines for data and metadata management and disseminate those to end users.EarthCube RCN: Building a Sediment Experimentalist Network59 53. Component3 SENExperimental Collaboratories (SEN-EC): a new form of research collaboration in our community: broadcast physical laboratory experiments and interact with colleagues through a webinar system. foster greater communication among experimentalists and promote collaborations within and beyond the Earth-surface science community regardless of physical location.EarthCube RCN: Building a Sediment Experimentalist Network60 54. EarthCube RCN: Cyberinfrastructure for Paleobioscience (C4P)Goals Build new partnerships and collaborations among geoscientists and technologists Survey and catalog existing resources Build community around cyberscience & paleogeoinformatics Advance development of common standards and semantic frameworks, working closely with biological community 55. EarthCube RCN: Cyberinfrastructure for Paleobioscience (C4P) Steering CommitteeLehnert, Kerstin IEDA, Columbia University Anderson, David M. NOAA, National Climatic Data Center Fils, Douglas Consortium for Ocean Leadership Jenkins, Chris University of Colorado at Boulder Lenhardt, Christopher Renaissance Computing Institute Noren, Anders University of Minnesota Olszewski, Thomas Texas A&M University Smith, Dena University of Colorado at Boulder Uhen, Mark George Mason University Williams, Jack University of Wisconsin-MadisonC4P 56. Challenge: Much fossil data is dark i.e. not easily accessibleNeotoma DB www.neotomadb.orgC4P 57. Challenge: Many informatic efforts, little coordination or interoperability among efforts VertNet Neotoma DBPaleobio. DB MorphobankNeptuneIEDAiDigBioDigimorphMacro-StratTMITree of LifeC4P 58. Planned RCN Activities Cataloging existing cyberinfrastructure resources in the paleobiological sciences Webinar series featuring other EarthCube projects and related geo- & bioinformatic activities (coming soon) Workshops: Paleobioinformatics (May/June 2014) Geochronology Synthesis Town Halls & Early Career Symposia at GSA, AGU, ESIP Social Media: Twitter, EarthCube Website, etc.C4P 59. EarthCube Conceptual Design: Developing a DataOriented Human-Centric Enterprise Architecture for EarthCube Chaowei Yang*, Chen Xu*, and Carol Meyer October 15, 2013 * George Mason University Federation of Earth Science Information Parterns 60. Project Objective This project seeks to design a conceptual architecture that can bring geoscientists, computing scientists, and social scientists together to collaborate on networks of data, technology, applications, business models, and stakeholders. 1. Design a data-oriented CI for achieving the goal of EarthCube as a knowledge management system and CI that integrates all geosciences data to transform the conduct of geoscience research and education. 2. Have geoscientists and domain experts at the center and facilitate them to communicate and collaborate using multiple layers of technology and information to achieve the sharing of data/information/knowledge. 61. Three-Layer Architecture Layer 2: InformationLayer 3: KnowledgeLayer 1: Model 62. EarthCube Architecture Report Template (TBD) VOLUME 1VOLUME 2Vision for EarthCube 1.1 Fit for Purpose Architecture 1.2 Goals and Objectives 2. Framework Overview 2.1 EarthCube Architecture Framework Defined 2.2 Purpose and Scope 3. Domains of Architecture (Strategic, Capability, and Solution) 4. Principles of Federation 4.1 FEAF, TOGAF, Zachman, and DoDAF 4.2 EarthCube Enterprise Architecture Overview 5. Customer Requirements 5.1 Support of Key Processes 5.2 The Program Tier 5.3 The Enterprise Tiers (Component, Research Projects, and Geoscience Domains) 6. Methodologies 6.1 Methodology Based Approach to Architecture 6.2 System Component, Package, Deployment Diagrams 7. Presentation 7.1 EarthCube Enterprise Architecture Notional Structure 7.2 Generated Views (Reports) 8. Data Focus 8.1 Core Architecture Data Model (CADM) 8.2 Exchange Standard: XML Schema Definitions (XSDs) 9. Process Performance Engineering & Metrics 9.1 Performance Engineering in Process Improvement 9.2 Metrics for Use in Testing Process Improvement 10. Analytics 10.1 Modeling and Simulation 10.2 Executable Architectures 11. Architecture Planning 11.1 Organizing the Architecture Effort 11.2 Architecture Management 12. Configuration Management (CM, Not Instantiated Architectures) 13.1 Configuration Control Board (CCB) 13.2 CADM (EarthCube Architecture Data Model) 13.3 Generic Process Models 13.4 EarthCube Enterprise Architecture Framework1. Operations Architecture 1.1 Capabilities/Metrics 1.2 Process 1.3 Information Flow 1.4 Data Descriptions 1.5 Roles 2. Technology Architecture 2.1 Systems, Applications, Services, Interfaces 2.2 Infrastructure (Networks, CES, Computing, Spectrum) 2.3 Standards (DISR, profiles) 2.4 Data Exchange 3. Net-Centric Architecture Description 3.1 Net-Centric Perspective 3.2 Backward Compatibility with Legacy Architectures 3.3 Point to Point Connections 3.4 Support for SOA1.VOLUME 3 1.EarthCube Enterprise Architecture Metamodel APPENDICIES (Applies to all 3 Volumes): A. GLOSSARY B. ACRONYMS C. REFERENCES D. TRANSITION FROM DODAF V1.0/1.5 TO V2.0 63. EarthCube Conceptual Design: Enterprise Architecture for Transformative Research and Collaboration Across the Geosciences A socio-technical system of systems: Based on Technology components to support social network research computation data management. Technology-enabled feedback between users cultivates an emergent, self-organizing system 64. Approach Challenge: adoption of research enterprise to 21st century technology Larger community, new communicationchannels, more information Issues are mostly reshaping social networks and attitudesParadigm: Emergent, Self-organizing system Requires more direct interaction between agents in the system 65. Feedback loop People Models DataResourcesUsageActivitiesLog Analysis RecommendationsImpactPublication Discussion Data use Data revision Annotation 66. Design Incorporate emerging social technology in research enterprise Klout, PeerIndex, Academia.com, Mendeley, Google Scholar,LinkedIn, ResearchGateMetrics for impact, recommendations Integrate with recognized cyberinfrastructure components: Catalogs, data services, repositories, standards 67. Development Team San Diego Supercomputer Center/UCSD: Ilya Zaslavsky, Amarnath Gupta, David Valentine Arizona Geological Survey: Stephen Richard University of Chicago: Tanu MalikAdvisory Team of Large Information System Architects USGS Academic Data Centers National Research Facility Geoscientists Social organization experts Mendeley OGC IBM Microsoft Elsevier ESRI 68. EarthCube Test Enterprise Governance: An Agile Approach M. Lee Allison, PI Rachael Black, Anna Katz, Kate Krestchmann, Kim Patten, & Genevieve Pearthree November 5, 2013 69. EARTHCUBE ENTERPRISE TEST GOVERNANCE An agile approach to design a system that catalyzes the field and works for you How do we bring your tools, standards, and skills into EarthCube? 70. STAKEHOLDER ENGAGEMENT (YEAR 1): CROWDSOURCING 71. Governance timeline Year 1 Stakeholders (Assembly) governance ideas, testingIntegrate stakeholder concepts crowdsourceSynthesize and recommend to NSFGovernance timeline Year 2 Establish Test GovernanceFacilitate convergence on system design, data standardsEvaluate results: basis for long term governance 72. STAKEHOLDER ENGAGEMENT (YEAR 1): EARTHCUBE ASSEMBLY Industry & FOSS: Instrumentation, Software, and Technology DevelopersEarthCube PortfolioResearch Science CommunitiesEnd-User Communities & Workshop ParticipantsData Facilities & UsersIT/CS/ Information Scientists Professional SocietiesAssembly Advisory Council(10-12 members) 73. Executive BranchAn unbiased, objective process to get your input and propose a solutionTest Governance Project SecretariatLegislative BodyAssembly & Assembly Advisory Council 74. EARTHCUBE.ORG The Public Site PortalEarthcube.orgThe WorkspaceThe Workspace 75. A CALL FOR YOUR INVOLVEMENT Virtual Town Hall: November 22, 11:30 EST Upcoming community workshops: Jan March 2014 All Hands Meeting, June 24-26, 2014, Washington, DC Crowdsourcing: Virtual table-top gaming exercises Feedback on governance models Social Media Twitter, Facebook www.earthcube.org