2018 Outline

2017 Status

  • Define requirements and success criteria
    • We did not get much engagement from our critical requirements group to date (Packard Foundation, COS)
    • Defining requirements with what we have to date
      • Web Upgrade Stakeholders
        • Foundation and Board Members
        • Policy Makers and Resource Managers
        • Researchers (External)
        • Researchers (Internal)
        • Engineers
        • Aquarium, Public, Students
        • Teachers
        • Media
        • Tech Transfer Partners
        • Marine Operations
      • Existing Infrastructure (meetings)
      • Current Projects
  • Export pathways
    • Researching other groups and their access methods
      • ERDDAP
      • THREDDS
      • REST
      • OGC
  • Define architectures
    • Researching architectures:
      • Met with OOI CI
      • Telecon with AGU Data Management and Assessment Services
      • Renewable Natrual Resources Foundation - Congress on Harnessing Big Data for the Environment
      • Blue Tech Week San Diego
        • Big Data, Data Analytics, OceanGIS and Maritime Cyber Security
      • Elastic Search Training
      • HADOOP Workshop
      • Messaging Architecture discussions
      • Lamba Architecture Research
      • Big Table research
      • Map Reduce research
    • Auth0 for authentication
    • FSWatch indexing
    • Isilon EMC Common Event Enabler
  • Data And Description Protocols
    • REST Design Guide
    • JSON Format Guide
    • Markdown and MKDocs for documentation
    • Swagger for API Docs
  • Catalog
    • Research concepts
      • ERDDAP
      • THREDDS
      • Elasticsearch
      • Internal systems design (see appendix)
  • Modeling
    • Research
      • OGC
      • UNIDATA
      • OceanSITES
      • Our internal systems (see appendix)
    • Activity/Resource model
  • Policy definition
    • Lack of engagement

2018 Proposed

  • 3 Categories:
    • Development: 75%
    • Use: 25%
    • Transfer: 0%
  • Research
    • Got uninimous feedback that we need to understand our requirements
    • We are not there due to difficultly in articulating requirements (thus lack of engagement)
    • Have some from our own internal ideas, but as discovered, much different than what the outside is looking for
      • ESP as an example
    • We are proposing to do work that will push the requirements definition from the top down (from our stakeholders)
  • Development
    • We are going to be 'building rocks' starting with MT, ITD, and Accounting as our proxy to the Foundation and other external stakeholders.
    • Focus our efforts on the concepts of articulating ROI at first.
    • Start with idea of interactive map (talk about prototype work to date)
    • Iterate with ideas from our proxy group.
    • If making good progress, target an interactive demonstration with the Board (and thus some foundation) through DOEST/Board meeting
    • Iterations with be with prototypes
      • Prototypes will integrate ideas from existing developments that are out there (research existing systems)
      • Continue modeling work to support prototype development
    • Continue research of existing architectures and technologies for data storage
    • Catalog development (i.e. bottom up) will continue but under CANON, ITS and ESP projects where requirements are better understood.
  • Deliverables
    • Prototypes that test ideas and foster dicussions to target requirements gathering
    • Prototype for external interaction to get feedback
    • Requirements that can then be used to create a roadmap to stitch bottom up work with top down work
  • Milestones
    • What iteration schedules do we want here?
    • DOEST to expand stakeholder base
  • Tasks and Labor:
    • ?
  • Budget:
    • Currently have $23K left
    • 2017 activities and carrover:
    • 2018 Projections
    • 2018 request
  • Data Storage Requirements:
    • Money for hosting services
  • Data Availability