| Kevin Crowston | crowston | 0 | 12 years 3 months ago |
| Biblio | Innovation in academic-industry partnerships: Measuring the challenges to effective performance | crowston | 0 | 12 years 5 months ago |
| Data Management Best Practice | A separate field with specified values may be used to provide additional information about the measured data value | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Provide elevation in meters. | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Make sure that all location information in a file uses the same coordinate system | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Provide latitude and longitude with south latitude and west longitude recorded as negative values | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Spatial coordinates should be reported in decimal degrees format to at least 4 (preferably 5 or 6) significant digits past the decimal point. | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | both the begin time and end time should be reported in both local and UTC time | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Use 24-hour notation | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Dates: yyyy-mm-dd or yyyymmdd | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Consistent formats are particularly important for dates, times, and spatial coordinates. | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | use only letters, numerals, and underscores in the parameter name | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | use consistent capitalization (not temp, Temp, and TEMP) | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Use commonly accepted parameter names | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | To ensure that documentation can be read well into the future requires that it be in a stable non-proprietary format. | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Provide Data Set Documentation and Metadata | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Assign Descriptive Data Set Titles | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Define the Quality of Your Data | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Perform Basic Quality Assurance | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Assign Descriptive File Names | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Data that are provided in a proprietary software format must include documentation of the software specifications | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | If the data files were created with custom code, provide a software program to enable the user to read the files | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Avoid using generic file extensions | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | select a consistent format that can be read well into the future and is independent of changes in applications | crowston | 0 | 13 years 2 weeks ago |
| Data Management Best Practice | Use Consistent File Structure and Stable File Formats For Tabular and Image Data | crowston | 0 | 13 years 2 weeks ago |
