Skip to content

tradman/guide-to-n3c-v1

 
 

Repository files navigation

The Researcher's Guide to N3C

The Researcher's Guide to N3C: A National Resource for Analyzing Real-World Health Data is designed to guide research with the National COVID Cohort Collaborative (N3C).

The rendered booked is accessible through either of these urls:

Contributing Content

The N3C and its domain teams are healthiest when assimilating contributions from reseachers of different skills (e.g., clinicians & informaticians), specialties (e.g., endocrinology & gerontology), programming languages (e.g., Python, R, & SQL) and experiences (e.g., students & PIs).

Accordingly, the guide-to-n3c-v1 repository welcomes input from you.

If you see a small mistake or unclear language, we invite you to inform us in a new issue or to edit the source and submitting a pull request. When an editor reviews and accepts your change, the website will be updated within minutes.

If you have an idea for something more substantial such as a chapter or section, please start a new issue and the N3C Educational Committee will coordinate with you where it fits best.

Platform

As the chapters are being written, talk to the chapter's Lead Author to learn if it's being written in GitHub or Google Docs. Eventually all Google Docs chapters will be translated to Markdown. Once a chapter has been finally converted to Markdown...

To make small changes like spelling corrections, we recommend editing the source directly in GitHub. It handles the details without your knowledge (like starting a fork and prompting your pull request). From the appropriate page of the book, click on the "Edit this page " button and type your change in the GitHub editor.

Substantial edits and writing are better accommodated by a text editor on your local machine that can preview the rendered content as you type. We suggest Visual Studio Code or RStudio.

You don't have to understand the rest to contribute, but for those interested:

  • The majority of this book is written in a collection of Markdown documents and assembled by the Quarto.

  • After your change is pushed to GitHub, a GitHub Action spawns a small VM that (a) collects all the Markdown documents, (b) calls Quarto/Pandoc to convert them to html, and (c) moves the rendered html files to the "gh-pages" branch.

  • GitHub Pages serves the contents of the gh-pages branch to anyone with a browser.

Assets

Funding

The N3C is supported by NIH National Center for Advancing Translational Sciences (NCATS).

Versioning and Build Status

Zenodo releases: DOI

GitHub Actions: Build Book

Packages

No packages published

Languages

  • TeX 51.3%
  • JavaScript 31.7%
  • Lua 13.2%
  • SCSS 2.6%
  • Other 1.2%