Skip to main content area
Future of News Work
Syracuse University School of Information Studies
FNW menu
PI
Papers
You are here
Home
»
crowston
Error message
The page style have not been saved, because your browser do not accept cookies.
Primary tabs
View
Publications
Track
(active tab)
crowston
Type
Title
Author
Replies
Last updated
Data Management Best Practice
If a shorthand notation is reported in the data file, the complete units should be spelled out in the documentation
crowston
0
12 years 11 months ago
Data Management Best Practice
Definitions of flag codes should be included in the accompanying data set documentation.
crowston
0
12 years 11 months ago
Data Management Best Practice
Codes should not be parameter specific but should be consistent across parameters and data files.
crowston
0
12 years 11 months ago
Data Management Best Practice
be aware of, and document, any changes in the coding scheme
crowston
0
12 years 11 months ago
Data Management Best Practice
Within each data set, choose a format for each parameter, explain the format in the documentation, and use that format throughout the data set.
crowston
0
12 years 11 months ago
Data Management Best Practice
units of reported parameters need to be explicitly stated in the data file and in the documentation
crowston
0
12 years 11 months ago
Data Management Best Practice
have names that describe the contents and are standardized across files, data sets, and the project
crowston
0
12 years 11 months ago
Data Management Best Practice
Define the Contents of Your Data Files
crowston
0
12 years 11 months ago
Data Management Best Practice
inquire about integration and interoperability opportunities for archived data and related data products to maximize data reuse
crowston
0
12 years 11 months ago
Data Management Best Practice
data, processing codes, and documentation at all stages of development be routinely copied and backed up on secure and retrievable media
crowston
0
12 years 11 months ago
Data Management Best Practice
Keep copies of your raw data as collected or as received, before any processing has been done.
crowston
0
12 years 11 months ago
Data Management Best Practice
it is also important to be able to tell what data were used for the synthesis or model data
crowston
0
12 years 11 months ago
Data Management Best Practice
proper attribution of the source data be included with the derived product
crowston
0
12 years 11 months ago
Data Management Best Practice
users want to know where your data have been before they were archived
crowston
0
12 years 11 months ago
Data Management Best Practice
determine the likely final destination and likely mode of dissemination of your data
crowston
0
12 years 11 months ago
Data Management Best Practice
consider the potential user community, the final data archive, and the certain Web accessibility of your data
crowston
0
12 years 11 months ago
Data Management Best Practice
to reduce the level of effort required to prepare data for sharing.
crowston
0
12 years 11 months ago
Data Management Best Practice
Create, manage, and document your data storage system
crowston
0
12 years 11 months ago
Data Management Best Practice
Create a data dictionary
crowston
0
12 years 11 months ago
Data Management Best Practice
Assign descriptive file names
crowston
0
12 years 11 months ago
Data Management Best Practice
Use consistent codes
crowston
0
12 years 11 months ago
Data Management Best Practice
Maintain consistent data typing
crowston
0
12 years 11 months ago
Data Management Best Practice
Separate data values from annotations
crowston
0
12 years 11 months ago
Data Management Best Practice
Provide version information for use and discovery
crowston
0
12 years 11 months ago
Data Management Best Practice
Provide identifier for dataset used
crowston
0
12 years 11 months ago
Pages
« first
‹ previous
…
14
15
16
17
18
19
20
21
22
…
next ›
last »
Text Size
Increase
Decrease
Normal
Current Size:
100%
Page Style
Black/White
White/Black
Yellow/Blue
Standard
Current Style:
Standard