Is there a threshold requirement for compliance, think I read that.

This is from the list of activities that require a plan:

A comprehensive listing of all activity codes that generally require applicants to submit a Data Management and Sharing Plan. Read funding opportunities carefully – requirements may differ from general activity code applicability for a small number of opportunities

Maybe we should add the bold part

this was at the bottom of our slides

we will want to update this section too

do we want to provide more info about data sizes in general?

This is a good way to show hutch folks that "prototyping" model of work is great!

Here is a link about this: https://grants.nih.gov/grants/policy/nihgps/HTML5/section_8/8.5_special_award_conditions_and_remedies_for_noncompliance__special_award_conditions_and_enforcement_actions_.htm

from @vortexing on slack:

The link to the DMS policy FAQ link listed here https://hutchdatascience.org/NIH_Data_Sharing/faq.html is broken.
Perhaps it should be https://sharing.nih.gov/faqs#/data-management-and-sharing-policy.htm?

Follow the Wiki instructions here for details on how to complete the items in this issue.

The following files need to be edited to get this new course started!

Files that need edited upon creating a new course.

• README.md - Fill in all the { }.
• index.Rmd - title: should be updated.
• 01-intro.Rmd - replace the information there with information pertinent to this new course.
• 02-chapter_of_course.Rmd - This Rmd has examples of how to set things up, if you don't need it as a reference, it can be deleted.

Files that need to be edited upon adding each new chapter (including upon creating a new course):

• _bookdown.yml - The list of Rmd files that need to be rendered needs to be updated. See instructions.
• book.bib - any citations need to be added. See instructions.

Picking a style

See more about customizing style on this page in the guide.
By default this course template will use the jhudsl data science lab style. However, you can customize and switch this to another style set.

Using a style set

Read more about the style sets here.

• On a new branch, copy the style-sets/<set-name>/index.Rmd and style-sets/<set-name>/_output.yml to the top of the repository to overwrite the default index.Rmd and _output.yml.
• Copy over all the files in the style-sets/<set-name>/copy-to-assets to the assets folder in the top of the repository.
• Create a pull request with these changes, and double check the rendered preview to make sure that the style is what you are looking for.

Files that need to be edited upon adding new packages that the book's code uses:

• docker/Dockerfile needs to have the new package added so it will be installed. See instructions.
• The code chunk in index.Rmd should be edited to add the new package.

Sandy shared that there are new example DMS plans from teh NIH that we should refer to in the guide:

https://sharing.nih.gov/data-management-and-sharing-policy/planning-and-budgeting-for-data-management-and-sharing/writing-a-data-management-and-sharing-plan#sample-plans

I'll also put them on the NIH page on our site too.

We are interested in at least pointing out concerns that people should think about.

• many clinical considerations for sharing data

  • people need to be careful with de-identification and should ideally work with an expert

• in terms of raw vs cleaned data -what level of effort/funding/resources should be used to make data easy for someone to use the data from scratch, since slightly processed data while less convenient takes up less space/uses less resources

• what quality threshold is really needed to share data?

  • what are the consequences of sharing poor-quality data?
  • what are the consequences of not sharing data that is of reasonable quality that someone decided was poor quality?

References got moved to after session info section... need to fix that

https://sharing.nih.gov/data-management-and-sharing-policy/sharing-scientific-data/generalist-repositories

https://sharing.nih.gov/data-management-and-sharing-policy/sharing-scientific-data/repositories-for-sharing-scientific-data

Thanks @vortexing !

chapter 2. needs filled in

The Data Types that might be good to organize some portion of this course by or present suggestions for that are most interesting to the Hutch like include:

1. Genomics data: gene expression - GEO, Gtex, variant data (with - clinvar - or without - dbSNP - clinical connections, structural variations - dbVar, sequence data in general)
2. Imaging data (likely not of human body parts during clinical care, but of things through microscopes or animal imaging). (??http://www.cellimagelibrary.org/pages/about ??)
3. Flow cytometry data ??
4. Proteomic data (PDC?)
5. clinical trials data (clintrial.gov)
6. medical imaging data?

Others for sure but these seem to be a start that include a couple of particularly easy and some hard examples.

To help users report issues or areas of improvement for your course, you should provide a clear method of feedback for your users to route their concerns through.

See these instructions for suggestions on how to add a feedback method for this course.

OK so I know now that renewals need to comply but what about no cost extensions during the transition. I don't think a grant that was funded before Jan 25 2023 needs to comply if the extension is after this date but idk for sure

Jeff wanted us to add info about how NIH doesn't have specific expectations and knows that they will learn from this process

Jeff said he didn't see the review process section - so he suggested adding this

Just thinking about what Jeff said about this in basecamp

Need to add a disclaimer about people at institutes that are part of this (including Hutch) need to use specific templates

"I would just add that there has not really been a consensus on where to put metabolomics data - something like GenBank would dramatically change the landscape for metabolomics data sharing"

@ehumph thought it would look better if the book was at the top

DMPTool A web-accessible, form-based tool for drafting Data Management Plans that contains guidelines for most funders. JHU Data Services offers additional guidance available through this link.
SPARC A resource for tracking, comparing, and understanding current U.S. federal funder research data sharing policies.
Sherpa Juliet A searchable database and single focal point of up-to-date information concerning funders’ policies and their requirements on open access, publication and data archiving.
Council on Government Relations, NIH Data Management and Sharing Policy Matrix Provides additional instruction related to the NIH requirements

I'm not sure if @ehumph asked about this already.

@vortexing are you good with your linkedin being used for the author section?

We should see if Sandy is cool with us linking to the fredhutch team page.

The original template: https://github.com/jhudsl/OTTR_Template is always a work in progress.
We are working on adding more features and smoothing out bugs as we go.

If you want to receive updates from the original template to your course template, you will need to enroll this repository to the template updates by adding it to the sync.yml file.

• Follow these instructions to enroll your course repository to receive these updates.

• Ensure that you have followed these instructions to add the jhudsl-robot as a collaborator to your repository.

see slack fhdasl

use:
<div class = "question">
Question
</div>

We will want to add the path images to each section when we are done.

Can probably add more graphics to the course

https://nexus.od.nih.gov/all/2023/01/10/dms-plan-tip-leave-the-hypertext-at-home/

Add no hyperlinks to main messages

Per Jeff's request on slack

https://www.cos.io/blog/new-osf-metadata-to-support-data-sharing-policy-compliance

https://www.cos.io/blog/how-osf-meets-desirable-characteristics-for-data-repositories

Came across this today

Sansone S-A, McQuilton P, Rocca-Serra P, Gonzalez-Beltran A, Izzo M, Lister AL, Thurston M (2019) FAIRsharing as a community approach to standards, repositories and policies. Nat Biotechnol 37(4):358–367

https://www.cos.io/blog/new-osf-metadata-to-support-data-sharing-policy-compliance
https://www.cos.io/blog/how-osf-meets-desirable-characteristics-for-data-repositories

For more information on these settings see instructions in the getting started GitHub wiki pages.

• This course repository is set to public.

• Add the jhudsl-robot as a collaborator to your repository..

• GH_PAT has been set up as a GitHub secret

• GitHub pages is turned on

  • Go to Settings > Pages. Underneath Source, choose main for the branch and select the docs folder. Then click Save.
  • Check Enforce HTTPS.

• Github secret GH_PAT has been set
  Name: GH_PAT
value: A personal access token following these instructions.
  Underneath Select scopes, check both repo and workflow.
  Then copy the PAT and save as the value.

• Set branch protections settings

  • main branch has been set up:
    • Require pull request reviews before merging box is checked.
    • Require status checks to pass before merging box is checked.
      • Underneath that Require branches to be up to date before merging box is checked.
  • Click Save at the bottom of the page!

• Customize GitHub actions for what you will need in this course.

Moving this from the automatic issue - since we did everything else

Just wondering how this was set up and how to manage that

    can we source some average `fcs` file sizes? I can post a message in the slack.

Originally posted by @avahoffman in #34 (comment)

A response from Slack:

In our lab it varies by project but usually 1-50 MB each, with the averages ranging from 2 - 20MB

do we want to add this to the footer or to each image or somewhere else?

At the beginning of the chapter, there is this snippet:

The following outline several key questions:

Is my research exempt from the policy?
Does my research generate scientific data? If yes, you will need to submit a DMS Plan.
When do I need to share my data?
Can I elect to not share data? The short answer is yes. However, you must still justify this choice in a submitted DMS Plan.

Might be helpful to make each question a link to the subsection that addresses the answer.