http://tfs.mayo.edu/tfs/MayoClinic/HSR/_git/personal-Moore-m088378?path=%2FExAC_Example.md&version=GBmaster&fullScreen=true&_a=contents

Comments with markdown
- denote auto-generated sections vs user's manually produced sections
[//]: # (BEGIN-section-1)

Automated sections
Semi-automated (create stubs)
User-generated


Put markdown in TFS-Git to allow anyone to change it and we can pull automatically for latest.
- Have one main owner per catalog - they are responsible for changes, handling feedback from users


- Drupal plugin for pulling in markdown


------------------------------------------------
Locations:
  - main:  TFS-Git  (edit from here)
  - Push to:
     - Drupal
     - Catalog directories
  - bior_catalog_markdown cmd would push to git??


------------------------------------------------
Sections:

Title

Purpose

Citations

IMPORTANT:

New:
- Info from Re-interpretation (new vs removed vs changed keys)

Technical Specifications:

Content Details:

FAQ - manual section of important info, but not necessarily new or critical info

Licenses - can we automated the download of licenses?


------------------------------------------------
Where to host it:


------------------------------------------------
Pics
  - Could link directly from publication



------------------------------------------------
Cmd:
bior_catalog_markdown
#bior_document_catalog

-d <CATALOG_PATH>
    - Output dir:
         Ex: $CTG/markdown/dbSNP_142_GRCh37.md
-p  --previous-markdown [PREVIOUS_MARKDOWN_FILE]
	- will have to crawl md file to find images and copy relative images.  
	- Throw error if links not found (not just images)
    - Add warning 
-o --output [OUTPUT_DIR]
    - By default, if not specified, create "markdown" subdir and add files there
TEMPLATE: Default to one in the toolkit

