OSS population

CherrelleTucker · May 23, 2024 · 2859384 · 2859384
1 parent 14b301f
commit 2859384
Show file tree

Hide file tree

Showing 4 changed files with 121 additions and 5 deletions.
diff --git a/_tabs/Home.md b/_tabs/Home.md
@@ -1,5 +1,4 @@
 ---
-
 layout: post
 permalink: /
 toc: true
@@ -13,8 +12,7 @@ _This graphic originated 2022ish and does need updating. Using for website draft
 <div align="center">
 
    <!-- markdownlint-disable-next-line -->
-   <h1> Welcome to the Satellite Needs Working Group Management Office!</h1>
-
+   <h1>Welcome to the Satellite Needs Working Group Management Office!</h1> 
 </div>
 
 ## What do we produce?

diff --git a/_tabs/Open Source Science.md b/_tabs/Open Source Science.md
@@ -28,6 +28,116 @@ toc: true
 
 </div>
 
+**F**indable
+**A**ccessible
+**I**nteroperable
+**R**eusable
+
+## Open Source Data Management Plan (OSDMP)
+
+_In keeping with the [NASA Plan for Increasing Access to Results of Federally Funded Research](https://smd-cms.nasa.gov/wp-content/uploads/2023/05/NASA_Plan_for_increasing_access_to_results_of_federally_funded_research1.pdf) the [SMD Strategy for Data Management and Computing for Ground Breaking Science 2019-2024](https://smd-cms.nasa.gov/wp-content/uploads/2023/06/SDMWG_Full_Document_v3.pdf), and [SPD-41A](https://science.nasa.gov/researchers/science-data/science-information-policy/), SMD's Scientific Information Policy, which was updated late in 2022, most proposers to ROSES-2023 must provide an "Open Science and Data Management Plan", (formerly called the Data Management Plan) or an explanation of why one is not necessary given the nature of the work proposed. This Open Science and Data Management Plan (OSDMP) must address how publications, data, and software will be made available, see below and the [SMD Open-Source Science Guidance] at https://science.nasa.gov/oss-guidance for more detail and examples._
+
+Solution Project Teams should have the following in their OSDMP:
+
+### Open Data
+
+- [ ] **What:** "A description of data types, volume, formats, and (where relevant) standards”;
+- [ ] **When**: “A description of the schedule for data archiving and sharing;”
+- [ ] **Where**: “A description of the intended repositories for archived data, including mechanisms for public access and distribution;”
+- [ ] **How**: “A discussion of how the plan enables long-term preservation of data;”
+- [ ] **Who**: “A discussion of roles and responsibilities of team members in accomplishing the OSDMP. If funds are required for data management activities, these should be covered in the normal budget and budget justification sections of the proposal.”
+
+### Open Software
+- [ ] Acknowledge that “software needed to validate the scientific conclusions of a peer-reviewed publication resulting from an award, e.g., data underlying figures, maps, and tables in a publication must be made available at the time of publication.” Include:
+    - Expected software types
+    - Repositories and timeline for sharing software
+    - Description of software that are exempt from software sharing requirements
+- [ ] Acknowledge that “the remaining scientifically useful software must be made available at the end of the award’”
+- [ ] Acknowledge that “publicly available software projects developed under the grant must include a code of conduct and guidelines for contributors and when released, have a digital persistent identifier, such as a Digital Object Identifier, associated with it to support citation.”
+- [ ] Acknowledge that “software should be released with an open, permissive license such as Apache 2.0, BSD 3-Clause “Revised” License, or MIT License. Any limitations to sharing the software should be described as part of the SMP.”
+
+### Open Publications
+- [ ]  Acknowledge that the “as-accepted manuscript or the version of record of peer-reviewed publications must be made publicly available at the time of publication. 
+
+Note: There are two options for how to comply with this requirement: 
+- (1) the manuscript is individually uploaded to NASA PubSpace by the time of publication or 
+- (2) It is published in a journal that makes it openly available at the time of publication and also it is indexed by either CHORUS or ADS”
+
+## Open Data
+
+### Considerations:
+- What is the nature of the data I am collecting or creating?
+- How can the data be safely stored?
+- Who can access the data without manipulating it (view-only)?  
+- Who can access the data AND manipulate the data?
+- Is my data understandable for others to use?
+- Is my data in an accessible format that makes it easy for others to work with? 
+- Is the data format widely used in my community?
+- Does the data format I've chosen have adequate metadata support in my community?
+- Are the tools needed to read the data format readily available in my community?
+- Is my data easy to find?
+- How private or open should my data be?
+    - What does my supervisor or Principal Investigator say?
+    - What does my grant/contract say?
+    - What does my organization say?
+    - What does my funding agency say?
+    - If I am planning to publish, what does the publisher say?
+<br>
+
+### Document Attributes:
+
+| Description      | Full documentation |
+| Quality          | Storage            |
+| Backup           | Access             |
+| Sharing          | Re-use             |
+| Preservation     | Archival           |
+| Responsibilities | Resources          |
+
+### Deposit Locations
+
+The following are examples of data repositories that can be used to host open data. Inclusion on this site does not indicate endorsement. 
+
+- [4TU.Centre for Research Data](https://data.4tu.nl/): Data repository
+- GitHub
+- [Re3data](https://www.re3data.org/): Registry of Research Data Repositories 
+- [CoreTrustSeal](https://www.coretrustseal.org/): offers to any interested data repository a core level certification based on the Core Trustworthy Data Repositories Requirements.  This universal catalogue of requirements reflects the core characteristics of trustworthy data repositories.
+
+### Data Preservation
+
+Consider:
+- Type of data created
+- Level of sensitivity
+- Will future work or publications use it as a base
+is the data unique?
+- Is it easy to replicate the data?
+are the costs of replication disproportionately high?
+- Is there a formal obligation to preserve data for the longer term?
+- Who is responsible for the management of data preservation?
+
+Tip: Data Management Costing Tool
+A group at the Delft University of Technology has developed a [costing tool that allows a rough estimation of FTE resources](https://forms.gle/8mUXX3TWTr85eyK47).
+
+
+## Open Sofware
+
+_Research software includes various components like source code, algorithms, scripts, workflows, and executables created during or for research. It does not cover software like operating systems, libraries, dependencies, and packages that are used in research but weren't specifically developed for it. Research software should have persistent identifiers, be stored in repositories, be properly cited, and described with metadata. It is unique because it is executable, evolves with versioning, and depends on a specific development system._
+
+|FAIR Data vs FAIR Software    |
+| :--------------------------------------------------- | :--------------- |
+|Focus is on actions taken at the **end of archiving** | Requires **ongoing action** from the start of the project,<br> such as in code documentation and modularization |
+
+
+## Open Publications
+
+## Open Meetings
+
+- Meeting Notice
+- Meeting Notes
+- Meeting Outcomes
+- Document Hosting
+
+## Algorithm Theoretical Basis Documents (ATBD)
+
 
 ## Further Reading
 
@@ -37,6 +147,8 @@ toc: true
 - [Desirable Characteristics of Data Repositories for Federally Funded Research, 2022 May](https://repository.si.edu/bitstream/handle/10088/113528/Desirable%20Characteristics%20of%20Data%20Repositories.pdf)
 <br>
 
+- [ROSES Open Science and Data Management Plan](ROSES Open Science and Data Management Plan)
+
 - [TOPS](https://nasa.github.io/Transform-to-Open-Science/)
 
 [SNWG OSS Quick Win Strategy.pptx](https://docs.google.com/presentation/d/1Nk8whKqDxwkjko5W0T7l2Ed1kLpvuxQ-/edit?usp=sharing&ouid=106604293755679367477&rtpof=true&sd=true)

diff --git a/_tabs/Part 2: Implementation.md b/_tabs/Part 2: Implementation.md
@@ -32,7 +32,9 @@ While the SNWG MO Program Plan governs the overall process and actions of the SN
 
 Key parts of the SNWG MO Program Plan for the purposes of the Project Implementation Teams are:
 
+- 2.3.2.1 Enabling Open Science
 - 5.1.2 Requirements on the SNWG Solution Projects
+- 5.1.2.1 Open Source Science Requirements
 - 6.2 Solution Project Implementation Collaborations
 - 6.3 SNWG MO SEP Collaborations
 - **12.2 Solution Project Lifecycle**

diff --git a/_tabs/Resources.md b/_tabs/Resources.md
@@ -16,6 +16,10 @@ toc: true
 ## Document Links
 - [SNWG MO Program Plan pdf](https://drive.google.com/file/d/1xe-rrKjwZZ7p0w39umL7nPdjCXmWwkUW/view?usp=sharing)
 
-## Presentation Links
+## Templates
+
+[OSDMP Template](https://docs.google.com/document/d/1Q1bwUlnPS4LqSHUAkyBwHSsLtUTDizMvbf8oNSOlTtk/edit#heading=h.bga6f4my90jo)
+
 
-## Partnering Organizations
+
+## Presentation Links