OSS Knowledge Management
Background Timeline
December 2018
Request for Information:
Strategic Plan for
Scientific Data and
Computing
Feedback on:
2019
SMD’s Strategy for Data Management and Computing for Groundbreaking Science
Goal to Develop and Implement Capabilities to Enable Open Science including the recommendation to develop and implement a centralized data discovery and access capability.
August 2018
NASA Archives Processing
and Data Exploitation Workshop
Discussion on needs including:
October 2018
Workshop on Maximizing
the Scientific Return of
NASA Data
Discussion on:
Slide courtesy Kaylin Bugbee
3
Goal 1: Develop and Implement Capabilities to Enable Open Science | Goal 2: Continuous Evolution of Data and Computing Systems | Goal 3: Harness the Community and Strategic Partnerships for Innovation | |||
1.1 | Develop and implement a consistent open data and software policy tailored for SMD | 2.1 | Establish standardized approaches for all new missions and sponsored research that encourage the adoption of advanced techniques | 3.1 | Develop community of practice and standards group |
1.2 | Upgrade capabilities at existing archives to support machine readable data access using open formats and data services | 2.2 | Integrate investment decisions in High-End Computing with the strategic needs of the research communities | 3.2 | Partner with academic, commercial, governmental and international organizations |
1.3 | Develop and implement a SMD data catalog to support discovery and access to complex scientific data across divisions | 2.3 | Invest in capabilities to use commercial cloud environments for open science | 3.3 | Promote opportunities for continuous learning as the field evolves through collaboration |
1.4 | Increase transparency into how science data are being used through a free and open unified journal server | 2.4 | Invest in the tools and training necessary to enable breakthrough science through application of AI/ML | | |
SMD Strategy for Data Management and Computing for Groundbreaking Science 2019-2024
✔
✔
✔
✔
✔
✔
Morning agenda – setting the stage for collaboration
Open data and open science guidelines
28 September 2022
NASA Open Source Science Data Repositories Workshop
Mark A. Parsons
https://orcid.org/0000-0002-7723-0950
mark.parsons@uah.edu�@chutneyboy
University of Alabama in Huntsville
Why
“The basic irony of standards is the simple fact that there is no standard way to create a standard, nor is there even a standard definition of ‘standard’.”
- Andy Russel and Lee Vinsel, NYT, 2019-02-16
A Policy-Driven Vision
SPD-41a:
III.B.a SMD-funded data should follow the FAIR Guiding Principles for scientific data management and stewardship.
III.C.a When released, SMD-funded software should follow best practices in the relevant open source and research communities.
A Pragmatic Mission (to start)
Help make NASA’s science discovery systems work better.
Help SMD repositories meet the new demands of open science.
Who
All y’all!
What — Objectives
Establish an SMD-wide ‘standards’ guidelines process to help implement the NASA Information Policy:
How — Principles
Very Important Slide!
Explicit “community standards” referenced
Scope: Where on the spectrum below?
Figure based on the work of Peter Pulsifer, Carleton University, Ottawa, Canada
Scope: Where on the spectrum below?
“Guidelines”
Reviewed Existing Processes, including
Seeking a balance of control and flexibility
1a. Identify Need
2. Assess issue and current standards adopted
3. Prepare work proposal
4. (public?) Review proposal
5. Assemble team and do work
6. Propose guideline & implementation (RFC)
8. Public review
7. Policy and/or Technical review
9. Publish final RFC
1b. Identify Champion(s)
Elevate issues as needed
10. Publish summary guideline
go?
A Draft Process
DOIs for data citation as a test case
SPD-41a requires NASA data to be citable “using a persistent identifier”. But which identifier and how?
So we
Who
Guideline Background and Context
Guideline description (section H)
Some lessons learned
Friction is inevitable and necessary
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
SPASE
SPASE
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
Figure based on Yarmey and Baker (2013). https://doi.org/10.2218/ijdc.v8i1.252
Working at multiple scales
— glocally —
builds knowledge and interconnection to address shared problems.
?
?
“Standardization is dynamic, not static; it means not to stand still, but to move forward together.”
1920’s motto for the Engineering Standards Committee (precursor to ANSI)
Created by Manuel Waelder, Noun Project
Thank You
Contact me at mark.parsons@uah.com @chutneyboy
Organizing Breakouts
Session ideas:
Session voting:
Instructions to Breakouts
Start the afternoon in breakouts and then come together to report before next session
5 min: Identify helpers
10 min: Clarify the general issue
20 min: Break it down
25 min: Identify approaches to a solution
5 min: Synthesize and prepare to report back