(Data) better data organization (maybe use girder)

[cchriste]

Currently...

• different versions only work with data
• config.yaml doesn't specify version
• datasets in /usr/sci/projects/dSpaceX disorganized and redundant
• no documentation explaining which data corresponds with what build(s)

[cchriste]

Many of these issues have been resolved:

• data is much better organized
• organization is documented with READMEs in /usr/sci/projects/dSpaceX and /usr/sci/data/dSpaceX
• dates have been added to these READMEs indicating which version (master branch) of dSpaceX required

Standing challenges:

• consider using girder to handle multiple versions of data
• consider partitioning data so that portions of a datasets such as config.yamls can be updated independently