Data Management In The Lab Lynn Yarmey National

Data Management In The Lab Lynn Yarmey National Snow and Ice Data Center Version 1. 0 Review Date

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Overview • Why are lab Data Management policies important? • Common Language – Data Stages • Lab policies you should have (and be using) • File Naming • Versioning • Infrastructure practices

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Lab Data Management Policies • Reduce confusion, lost work when students graduate • Reduce ramp-up time for new students or lab staff • Help easily re-create figures from old papers, etc. • Help all members of a lab quickly find critical data • Increase awareness of Data Management issues • Are a great start towards metadata creation and meeting NSF requirements

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Data Stages • Raw • Organized • Standardized • Transformed • Processed • Quality Controlled • Analyzed • Summarized • Presented/Published • Archived Use data stages as a common foundation for lab policies and practices

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Data Stages • Raw • Organized • Standardized • Transformed • Processed • Quality Controlled • Analyzed • Summarized • Presented/Published • Archived Does everyone in your lab understand agree on what these terms mean?

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 File Naming Conventions Done Right Make file names unique! Include (as appropriate): - Project name or acronym - Study title - Location - Data type - Researcher initials - Date (YYYYMMDD for easy sorting) - Data stage (see previous slides) - Version number - File type DO – Use underscores or dashes. DO NOT – Use spaces or special chars. WRITE DOWN conventions for your lab and save to a shared space. For more info - https: //www. dataone. org/content/assign-descriptive-file-names

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Versioning • A very personal practice • But lab policies can help • Version at each data stage • Common version identification ex. ‘x. y’ = ‘major. minor’ - Communicate with your lab/research group and agree on a file naming convention that includes a versioning system. - WRITE IT DOWN and save to a shared space.

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Infrastructure Practices • Again, often very personal • Again too - lab policies can help • Agreed-upon file organization framework • Submitting data to lab infrastructure at each stage using common file naming conventions

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 References and Resources • Data. One File Naming Guide • Versioning Guidelines documentation, etc) (for software but also apply to data,

Module Template: Subtitle; Version 1. 0, Reviewed 9/15/11 Other Relevant Modules • Documentation and Metadata section • Data Management Plans section