To work on/with this project, you will need to get a copy of the files in the repository. You do this using git.
If you are completely new to git and GitHub, there are are a number of online resources, but a good place to start for this project is Using Git in the GitHub Docs.
To get your local copy (aka, clone) of this repository, do the following:
- Set up Git.
- Choose a directory where you want to have your local copy of this repository.
- Clone the repository
In limited scenarios, you can add or edit files on GitHub, but in general you will need to use Git to manage your changes and share them to the repository. An example of contributing to an existing repository is given in those documents.
The steps there are:
- Clone the repository and change into the directory.
- Create a new branch for your changes.
- Switch to the new branch.
- Make whatever changes are needed.
- Add the changes to the branch.
- Commit the changes.
- Push the branch to GitHub.
Documentation is stored in the docs
directory.
You can do this either with a local clone, or by creating and editing files directly in the browser.
For details on working in the browser, see
Note: When you are done with your edits, under Commit Changes you should edit the commit message, and then choose "Create a new branch for this commit and start a pull request"
Create new documents as Markdown files (a file with a .md
extension) in the docs
directory.
Use the GitHub Markdown
format to make sure they display correctly on the site.
Images should be placed in the docs/images
directory, and can be included in a markdown document.
More detail on writing documentation on GitHub is available under Writing on GitHub in the GitHub Get Started docs.
To add or modify Word documents, you will need to follow the Git workflow above.
To add a document
- Create and switch to a new branch with a descriptive name for the addition.
- Place your document in the
docs
directory of this repository. - Add the document with git, commit the changes, and push the branch.
To modify a document in a branch
- Checkout the branch
- Open the word document from the docs directory in your clone, and save your work
- Add the document with git, commit the changes, and push the branch.
Each form set is broken out into individual instruments for each form. For instance, the Down Syndrome module has five forms and the corresponding directory structure is
forms/ds
├── a1d
├── b1d
├── b2d
├── c1d
└── d1d
where each directory contains the exported instrument for the form.
Before adding or updating a new instrument, create a new branch with an appropriate name using Git. For instance, to add the initial A1D form for the Down Syndrome module, we could use
git checkout -b add-initial-ds-a1d
To export an individual instrument in REDCap
-
For the instrument you want to export, click the
Choose action
dropdown next to the instrument,and select
Download instrument ZIP
.
This will save the downloaded file to the default location for your browser and OS settings.
On a Mac with the default settings, the file will be unzipped and saved in your Downloads
directory with a name corresponding to the instrument name (e.g., Downloads/FormA1dParticipantHe_2022-05-27_0749
).
On a Windows machine, you will likely have to unzip the file using the File Manager.
In this case, to move the file into the repository
- Make sure there is a directory for your instrument.
For A1D of Down Syndrome module, this should be a directory
forms/ds/a1d
. All of these should already exist for most projects, but if not you can create the directory. If you aren't sure how, please ask. - Copy the file into the instrument directory.
For A1D, the command on a Mac would be
cp ~/Downloads/FormA1dParticipantHe_2022-05-27_0749/*.* forms/ds/a1d
- Commit your changes and then push the branch to GitHub.