Soliciting Community Feedback on the NOAA OneStop Data Discovery and Access Framework Project

Abstract/Agenda: 

The NOAA OneStop Data Discovery and Access Framework Project was initialized in FY15 and is now working rapidly to improve discovery and access to NOAA's data. This session will feature a combination of presentations and discussions led by OneStop Projects teams (for example, the Architecture Team and the Metadata Team), designed to both inform the ESIP community and solicit feedback on progress to date.

Notes: 

Feedback: goo.gl/forms/6c54aH7S1e

 

Kenneth Casey, OneStop Project Manager

  1. OneStop is a result new policy and regulatory environment, including the US Open Data Policy.
  2. OneStop is meant to improve discovery and access of NOAA data.
  3. Big Earth Data Initiative and Big Data Partnerships overlap with OneStop to improve access.
  4. OneStop’s approach will:
    1. Modernize high-priority data.
    2. Improve data infrastructure
    3. Release software
  5. Case Study of the Current to OneStop interface
    1. User-centric
    2. Dynamic
    3. Visual
  6. OneStop was conceptualized in May 2015 and initiated in Q4 FY2015. Received funding in end of FY2015 and has received funding for Q1 2016.
  7. OneStop will have a GUI, but there will be multiple other groups that can access data at every level and will utilize Agile design.
  8. Question: How will NOAA improve dataset relevance ranking?
    1. Currently using solar/lucine style.  Data stewardship maturity, user evaluations, web services, and metadata rubric ranking will help with relevance rankings under OneStop.
    2. Potential collaboration à NASA currently has a a relevancy working group.
    3. How are the consequences tracked (i.e. usage tracking, links to publications, etc.)?  Its on the radar, but may not be included in this project time period.  NOAA library has done some analysis and can be included in relevancy ranking.
    4. How could re-usable interfaces be used across agencies? A lot of interest in it. 18F may be working on a playbook regarding this.

 

David Fischman, OneStop Architecture Team Lead

  1. Components of OneStop will be modular and compartmental, so system can evolved with other NOAA initiatives and make improvements over time.
  2. Agile development is based on user stories to develop discrete functional requirements, which are tested iteratively.
  3. The search engine will use Elasticsearch, locally hosted at each of the three NOAA centers.
    1. Elasticsearch is also used by ESRI and NASA.
  4. Graph database is being explored to represent metadata.

 

John Relph, OneStop IT Team Lead

  1. NOAA will modernize data from tape.
  2. OneStop will procure a storage solution, with the help of OSGS.
    1. Scalable up to multiple PBs
    2. Low cost to own
    3. Compatible with existing IT infrastructure
    4. Reasonable performance
  3. OneStop will be connected to NCEI systems via standard protocols (e.g. ISCIS, NFS).
  4. Question: Is there an alignment between big data initiatives and OneStop?
    1. Timelines didn’t fit with using cloud services currently, though relationships exist with cloud providers.  Datasets that are currently in the cloud will be able to be taken advantage of and will hopefully move in that direction further down the line.

 

Nancy Ritchey, OneStop Metadata Team Lead

  1. Metadata will initially be limited to NCEI and CLASS.
  2. OneStop metadata practices draft has been developed and NOAA will be looking for feedback on practices in the future.
  3. NoSQL will be used for graph database and granular level metadata.
  4. Web Accessible Folders will support harvesting by externals and indexing to catalogue services.
  5. EMMA is already used to assess completeness and standardization of metadata.
  6. Question: How will maturity matrices be applied to ranking?
    1. Depending on
  7. Question: Is there any user modeling to identify the intent of the users?
    1. This won’t be occurring.  Though some simple user intent may be able to be designed into the user account management (ex. operational users who want real-time data).
Citation:
Soliciting Community Feedback on the NOAA OneStop Data Discovery and Access Framework Project; Winter Meeting 2016. ESIP Commons , September 2015
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 823296 bytes) in /code/includes/database/database.inc on line 2278