Folders
=======
downloads   -> /data/projects/glygen/downloads/
generated   -> /data/projects/glygen/generated/
misc        -> /data/projects/glygen/generated/misc/ 
unreviewed  -> /data/projects/glygen/generated/datasets/unreviewed
reviewed    -> /data/projects/glygen/generated/datasets/reviewed

Making new dataset
=====================
    a)  Edit misc/dataset_masterlist.json to enter information about
        your new dataset
    
    b)  Create a folder structure under the downloads folder
        downloads/$resource/$release/ to house downloaded input files
        for your new dataset, where the variable $resource represents
        the resource from which your input data was downloaded and 
        $release is for the release (if release is unknown, use yyyy_mm_dd
        of the download date)

    c)  Use the following commands to create symbolic link under 
        downloads/$resource to point to the most current release
        
        $ cd downloads/$resource
        $ ln -s $release current

    d)  Use the following commands to give write access to every member
        in the glygen user group (where $username is your ssh user name)
        
        $ chown -R $username:glygen downloads/$resource 
        $ chmod -R 775 downloads/$resource

    e)  If the resource from which you downloaded data needs to be 
        cross referenced, edit misc/database_url_templates.csv to 
        enter relevant information

    f)  Create a ticket for data lead in the project, with detailed information
        on how the new dataset files needs to be created from the downloaed
        input files, giving the list of output field names (structure of the file)

    g)  Once the datset file created, use the BCO editor to create BCO that 
        describes the new dataset file. Make sure you use the correct file 
        name for the dataset when entering it in the BCO editor.

Peforming QC
============
Follow README file (/software/glygen/qc/README) on how to perform QC steps