crowston

TypeTitleAuthorRepliesLast updated
Data Management Best Practiceuse consistent capitalization (not temp, Temp, and TEMP) crowston011 years 11 months ago
Data Management Best PracticeUse commonly accepted parameter names crowston011 years 11 months ago
Data Management Best PracticeTo ensure that documentation can be read well into the future requires that it be in a stable non-proprietary format. crowston011 years 11 months ago
Data Management Best PracticeProvide Data Set Documentation and Metadata crowston011 years 11 months ago
Data Management Best PracticeAssign Descriptive Data Set Titles crowston011 years 11 months ago
Data Management Best PracticeDefine the Quality of Your Data crowston011 years 11 months ago
Data Management Best PracticePerform Basic Quality Assurance crowston011 years 11 months ago
Data Management Best PracticeAssign Descriptive File Names crowston011 years 11 months ago
Data Management Best PracticeData that are provided in a proprietary software format must include documentation of the software specifications crowston011 years 11 months ago
Data Management Best PracticeIf the data files were created with custom code, provide a software program to enable the user to read the files crowston011 years 11 months ago
Data Management Best PracticeAvoid using generic file extensions crowston011 years 11 months ago
Data Management Best Practiceselect a consistent format that can be read well into the future and is independent of changes in applications crowston011 years 11 months ago
Data Management Best PracticeUse Consistent File Structure and Stable File Formats For Tabular and Image Data crowston011 years 11 months ago
Data Management Best PracticeIf you are collecting many observations of several different types of measurements at a site, place each type of measurement in a separate data file. crowston011 years 11 months ago
Data Management Best PracticeKeep Similar Information Together crowston011 years 11 months ago
Data Management Best PracticeConsistently use the same missing value notations for numeric and text/character fields in the data file. crowston011 years 11 months ago
Data Management Best Practicespecify the standard source for units in your data set crowston011 years 11 months ago
Data Management Best PracticeIf a shorthand notation is reported in the data file, the complete units should be spelled out in the documentation crowston011 years 11 months ago
Data Management Best PracticeDefinitions of flag codes should be included in the accompanying data set documentation. crowston011 years 11 months ago
Data Management Best PracticeCodes should not be parameter specific but should be consistent across parameters and data files. crowston011 years 11 months ago
Data Management Best Practicebe aware of, and document, any changes in the coding scheme crowston011 years 11 months ago
Data Management Best PracticeWithin each data set, choose a format for each parameter, explain the format in the documentation, and use that format throughout the data set. crowston011 years 11 months ago
Data Management Best Practiceunits of reported parameters need to be explicitly stated in the data file and in the documentation crowston011 years 11 months ago
Data Management Best Practicehave names that describe the contents and are standardized across files, data sets, and the project crowston011 years 11 months ago
Data Management Best PracticeDefine the Contents of Your Data Files crowston011 years 11 months ago

Pages