Input for the ESS Data Archive (ESS-DIVE)
The new DOE Environmental Systems Science data archive, ESS-DIVE, is currently under development at the Lawrence Berkeley National Laboratory. The ESS-DIVE team is requesting input to better understand the data archiving needs of the DOE TES or SBR projects and SFA programs. Please help us by completing this form below to the extent possible. If you have any questions regarding this questionnaire or ESS-DIVE, contact us at ess-dive-support@lbl.gov.
GENERAL PROJECT/SFA PROGRAM INFORMATION
Name: *
Your answer
E-mail:
Your answer
Role: *
Project Title/SFA Program Name *
Your answer
Project/SFA Program Website URL
Your answer
CURRENT PROJECT/SFA PROGRAM DATA STORAGE SYSTEM
Please describe your current project/program data storage system(s). *
Your answer
Identify the point of contact for the individual(s) managing your system(s). *
Your answer
What volumes of data are currently stored in each of your systems? What is the volume and frequency with which data are added to each system? *
Your answer
What data collection and reporting/metadata standards, if any, does your project/program use (e.g. netCDF, FGDC, ISO, etc.)? *
Your answer
Please check the metadata you have for your datasets;
Do you currently collect streaming data in some form and if so, please explain. *
Your answer
Have DOI's already been assigned to some of your data? *
If you have "Data Use Terms" defined (e.g. free, fair use) provide a definition or a link to the terms. *
Your answer
Do you manage versioning, and if so, what is the frequency of new data products generated? *
Your answer
What do you consider to be the biggest threat to your current data management lifecycle?
Your answer
Additional notes or comments
Your answer
ESS-DIVE PREFERENCES
How do you expect to use ESS-DIVE? *
Your answer
What would you suggest ESS-DIVE provide to the community? What would be the most critical resource needed from ESS-DIVE?
Your answer
Types of data you would like to store or mirror in ESS-DIVE (select all that apply)?
What is your project's timeframe for archiving mission-critical data in ESS-DIVE?
Do you have data that you want to store in ESS-DIVE that cannot be made public? *
If yes, briefly explain which datasets cannot be made public, and why. *
Your answer
What is the approximate data volume (in GB) your project/program would like to archive in ESS-DIVE in the next year?
Your answer
What is the approximate number of datasets, variables, and if applicable, value-added products your project/program would like to archive in ESS-DIVE in the next year?
Your answer
Are there modes of aggregating or grouping the data that your community would prefer (e.g., individual archived files possess one daily value and are served as annual/monthly in a separate file)?
Your answer
What would be the most effective ways for ESS-DIVE to communicate with the community?
Your answer
Additional notes or comments
Your answer
ESS-DIVE Community mailing list opt-out?
Submit
Never submit passwords through Google Forms.
This form was created inside of Berkeley Lab (Univ of California).