Skip to content

cr625/data-sharing-directory

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Contributing to the directory

To add a new entry to one of the following categories: Standards, Tools, or Community Initiatives (or to edit an existing entry), begin by forking the repository to create your own copy of the directory, adding (or editing) the entry, committing your additions/changes, and submitting a pull request to the original repository.

  1. Sign into your GitHub account. If you don't have one, here's how to set one up

  2. Fork the repository using the button at the upper right. The fork button looks like this:
    Fork button

    You have just created a copy of the directory for your personal use. The changes you make here will not be final until you have submitted them as a pull request, and the pull request has been merged into the origin repository by a repo maintainer. More on pull requests below. After forking, the URL for your repository should look something like the following: github.com/[your-user-name]/data-sharing-directory/tree/gh-pages

    And the title of the directory at the top of your page should be: [your-user-name]/data-sharing-directory

  3. In your forked directory, navigate to the ‘initiatives’, 'standards', or ‘tools’ directory and open the sub-folder named ‘data’. You will see a list of files, one for each entry.

    To add a new item, click ‘Add file’ (in the upper right-hand area, as shown above in Figure 2), and select ‘add new file’.

    Give your file a descriptive name, using lowercase letters and hyphens instead of spaces, and give it a .yml file extension. (Ex: creative-commons.yml).

    YAML is a data serialization language. If you are unfamiliar with YAML syntax, refer to the files in the _templates directory official YAML sample file

    Use the following format to create the code for your new entry:

---
title: Vivli - Center for Global Clinical Research Data
sub_categories:
  - Licensing
  - Informational resources
started: 2013
founded_by: The Multi-Regional Clinical Trials Center of Brigham and
Women’s Hospital and Harvard (MRCT Center)
current_url: https://vivli.org
goals: Help researchers share and access data from clinical trials.
Serve as a searchable repository for contributors and users, and
provides tools, examples, and guidelines that facilitate the creation
of data sharing agreements for sensitive and restricted information.
status:
type:
  - tool
  - initiative
---

NOTE – Important! If your text contains any colons, delete or replace them with another character or :. Colons in text results in an error in the code and the new file will not be added.

  1. To make changes to an entry, open the file and click the pencil in the upper right-hand area to edit, following formatting instructions as above. It is helpful to turn on ‘Soft wrap’, which appears on the right as soon as you open a file for editing. This allows you to see all the text without scrolling to the right.

    More than one sub-category or type can be included for any entry, i.e. a resource may be both a standard and a tool. If you include more than one, enter each on a separate line, indented with a preceding ‘–‘. If there is only one, enter it on the same line after the colon.

    Types are standards, tools, and community initiatives.

    Sub-category options include Rights, Licensing, Metadata, Ontologies, and Informational Resources [this may be changed or expanded].

  2. After you have created your new file or made any edits, scroll down and click the green ‘commit changes’ button. This saves your work.

  3. Press the pull request button when it appears:
    Button to create pull request

    You will then see the discussion page we will use when reviewing your request. That’s it, you’re entry has been submitted. If you don’t have or don’t want a GitHub account, feel free to submit your entry to [email protected]

Releases

No releases published

Packages

No packages published

Languages

  • HTML 89.0%
  • SCSS 11.0%