customSoftware | description | Describe any custom software or code developed or used, and/or any web tools being developed as part of the project. |
---|
source | If the custom software or code can be accessed via an online repository, provide a link. |
---|
webToolMaintenanceAndSupport | If a web tool is developed as part of the project, is there a strategy for the ongoing support and maintenance of the web tool after the project is complete? If so, briefly describe it. |
---|
languages | Identify the computing language/framework that was used (e.g., Java, .Net, Ruby, Rails, SQL, etc.) |
---|
restrictions | Identify any limitations on access or reuse. |
---|
environment | Identify the operating system environment (e.g., Windows, Linux, MacOS X, etc.) |
---|
name | [Name of Software or Other Need] |
---|
|
---|
dataProduct | metadata | Identify the metadata standard that will be used to describe the data and products (FGDC, ISO, EML, etc.) |
---|
exclusiveUse | Project data and associated products should be available publicly at the end of the project. If a request to limit access for a period of time after project completion is needed, please identify the length of time and the reason for the extension. (Request cannot be more than one year.) |
---|
description | Describe the information that will be produced, including its characteristics, temporal scope and scale, and geographic scope and scale, when available. |
---|
repository | In addition to the NCCWSC repository (ScienceBase), identify any other repositories where you plan to share your data. |
---|
dataLifespan | At some point, datasets may be archived. Choose one of the following options to indicate how long you anticipate this data will be of value to other researchers. Less than 5 years, 5-10 years, 10-20 years, 20-50 years, 50+ years. |
---|
qualityChecks | Identify the procedural steps for ensuring data quality during the project. |
---|
citation | Specify how the project’s data should be cited. |
---|
format | Identify the formats in which the data will be generated, maintained, and made available. |
---|
restrictions | Identify any limitations on access or reuse (e.g., sensitive data, restricted data, software with license restrictions, etc.) and provide justification for restriction. Provide citation or documentation describing limitations if due to policies or legal reasons. |
---|
backupAndStorage | Describe the approach for backup and storage of the information associated with the research project during the project. |
---|
dataManagementResources | Describe the proposal resources allocated for data management activities for the data products as a level of effort, total dollars allocated, or as a percentage of the total project’s cost. Resources could include people’s time or proposal funding. |
---|
volumeEstimate | Estimate the volume of information generated: megabyte (MB), GB, TB, or PB. |
---|
dataProcessing | Describe data processing steps or provide a scientific workflow you plan to use to manipulate the data, as appropriate. |
---|
name | [Name of Data Product] |
---|
doi | Provide a digital object identifier (DOI)/link to the project when available publicly. |
---|
|
---|
existingInput | fees | Identify any fees associated with acquiring the data. |
---|
description | Describe the information that will be used, including its characteristics, temporal scope and scale, and geographic scope and scale, when available. |
---|
source | Identify the source for the data; include a link and digital object identifier (DOI) if available. |
---|
qualityChecks | Identify the procedural steps used to evaluate the existing data, including verification, validation, and an assessment of usability. |
---|
citation | Provide citation for data product. If the data product can be found online, provide a URL. |
---|
format | Identify the formats in which the data are maintained and made available. |
---|
restrictions | Identify any limitations on access or reuse (e.g., sensitive data, restricted data, software with license restrictions, etc.) and provide justification for restriction. Provide citation or documentation describing limitations if due to policies or legal reasons. |
---|
backupAndStorage | Describe the approach for backup and storage of the information associated with the research project during the project. |
---|
volumeEstimate | Estimate the volume of information that will be generated: megabyte (MB), GB, TB, or PB. |
---|
dataProcessing | Describe any data processing steps or provide a scientific workflow you plan to use to manipulate the data, as appropriate. |
---|
name | [Enter Name of Existing Collection] |
---|
|
---|
history | 2023-04-14 09:03:04 MDT: phase Approved DMP
|
---|
model | modelVersion | Identify the version of model used. |
---|
description | Provide a brief description of the model and its purpose. |
---|
source | Provide a link or a source for the model. |
---|
modelInputs | Enter the types of input data required for driving, calibrating, or validating the model. For proposals, summary information is all that is needed. For funded projects, these should be described in detail in the existing or new collection, data inputs section. |
---|
calibrationDetails | Briefly describe the calibration/validation approach being taken. |
---|
modelOutputs | Enter the types of output data the model will produce. For proposals, summary information is all that is needed. For funded projects, provide more details as known. If the model output is a generated dataset that is a project deliverable, describe it in detail in the data product section. |
---|
name | [Name of Model] |
---|
|
---|
newInput | metadata | Identify the metadata standard that will be used to describe the document (FGDC, ISO, EML, etc.) |
---|
exclusiveUse | Project data and associated products should be available publicly at the end of the project. If a request to limit access for a period of time after project completion is needed, please identify the length of time and the reason for the extension. (Request cannot be more than one year.) |
---|
description | Describe the information that will be collected, including its characteristics, temporal scope and scale, and geographic scope and scale, when available. |
---|
repository | In addition to the NCCWSC repository (ScienceBase), identify any other repositories where you plan to share your data. Indicate if data will be integrated into an existing collection or offered as a new collection. |
---|
dataLifespan | At some point, datasets may be archived. Choose one of the following options to indicate how long you anticipate this data will be of value to other researchers. Less than 5 years, 5-10 years, 10-20 years, 20-50 years, 50+ years. |
---|
qualityChecks | Identify the procedural steps for ensuring data quality. |
---|
protocols | Identify any standard protocols or methodologies that will be used to collect the data, if available. |
---|
citation | Specify how the project’s data should be cited. |
---|
format | Identify the formats in which the data will be generated, maintained, and made available. |
---|
restrictions | Identify any limitations on access or reuse (e.g., sensitive data, restricted data, software with license restrictions, etc.) and provide justification for restriction. Provide citation or documentation describing limitations if due to policies or legal reasons. |
---|
backupAndStorage | Describe the approach for backup and storage of the information associated with the research project during the project. |
---|
dataManagementResources | Describe the proposal resources allocated for data management activities for the new data collected as a level of effort, total dollars allocated, or as a percentage of the total project’s cost. Resources could include people’s time or proposal funding. |
---|
volumeEstimate | Estimate the volume of information generated: megabyte (MB), GB, TB, or PB. |
---|
dataProcessing | Describe data processing steps or provide a scientific workflow you plan to use to manipulate the data, as appropriate. |
---|
name | [Provide a brief name to describe new data collection] |
---|
doi | Provide a digital object identifier (DOI)/link to the data when available publicly. |
---|
|
---|
phase | Approved DMP |
---|
templateName | NCCWSC DMP v3 |
---|