Search Help Show/Hide Menu

Data Management Plan

DMP Template v2.0.1 (2015-01-01)

Please provide the following information, and submit to the NOAA DM Plan Repository.

Reference to Master DM Plan (if applicable)

As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
Students Collaborating to Undertake Tracking Efforts for Sturgeon(SCUTES)
1.2. Summary description of the data:

Students Collaborating to Undertake Tracking Efforts for Sturgeon (SCUTES) is a collaboration between NOAA Fisheries, sturgeon researchers, and teachers/educators in an effort to learn more about Atlantic and shortnose sturgeon and promote sturgeon conservation. In order to learn more about the movement of sturgeon, we collaborate with researchers by providing them with some of the acoustic tags that are either inserted or attached to the sturgeon.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
Ongoing series of measurements
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2003 to Present
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:

The data included in the SCUTES database is based on where SCUTES sturgeon researchers have conducted tagging and tracking studies (i.e., the location of acoustic arrays), as well as which tracking data researchers voluntarily submit in addition to those associated with the acoustic tags that NOAA Fisheries provided. All geographical data included in the SCUTES database has been collected from within the geographical area occupied by shortnose and Atlantic sturgeon. The “geographical area occupied by a species” is defined as: “the geographical area which may general be delineated around the species’ occurrences, as determined by the Secretary (i.e., range). Such areas may include those areas used throughout all or part of the species’ life cycle, even if not used on a regular basis (e.g., migratory corridors, seasonal habitats, habitats used periodically, but not solely by vagrant individuals)” (81 FR 7413). For both Atlantic and shortnose sturgeon, geographic data reflects only aquatic habitat.

Based on our review of the literature and other available data, we concluded that Atlantic sturgeon: Typically occur in marine waters within the 50 m depth contour, but also occur in deeper marine waters; occur in many coastal sounds and bays from the Maine/Canada border to Cape Canaveral, Florida; and occur in tidally-affected rivers along the coast. Similarly, shortnose sturgeon: Typically occur in the slower moving riverine waters or nearshore marine waters along the coast from the St. John River in Canada to the St. Johns River in Florida. As previously stated, the location of acoustic arrays is at the discretion of SCUTES sturgeon researcher. The data currently included in the SCUTES database spans from Maine to Virginia, however future data can be generated in any of the geographic areas described above.

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Table (digital)
1.7. Data collection method(s):
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
Edith E Carson
Taken From: Support Roles (Metadata Contact) | Person
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
edith.carson@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
978-282-8490
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

3. Responsible Party for Data Management

Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.

3.1. Name:
Edith E Carson
Taken From: Support Roles (Data Steward) | Person
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

5. Data Lineage and Quality

NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Lineage Statement:
he SCUTES Coordinator will collect the latest tracking data annually from the sturgeon researchers that are partnered with the SCUTES program. The SCUTES Coordinator will then process and upload the new data into the Oracle database. The Oracle database is only accessible to NOAA Fisheries staff, so the SCUTES Coordinator will be responsible for downloading the data when an educator expresses interest in “adopting” a sturgeon. This process involves selecting a tagged fish from a river of the teacher/educator’s choosing, applying filters to remove irrelevant content (e.g., researcher’s name, station name, soak time) from the data, and downloading the data in a readable format (e.g., Excel, PDF) according to the teacher/educator’s request. The tracking data is then sent to the teacher/educator reminding them that this data is for educational purposes only.

Process Steps:

  • N/A (Citation: N/A)
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):

The SCUTES Coordinator will collect the latest tracking data annually from the sturgeon researchers that are partnered with the SCUTES program. The SCUTES Coordinator will then process and upload the new data into the Oracle database. The Oracle database is only accessible to NOAA Fisheries staff, so the SCUTES Coordinator will be responsible for downloading the data when an educator expresses interest in “adopting” a sturgeon. This process involves selecting a tagged fish from a river of the teacher/educator’s choosing, applying filters to remove irrelevant content (e.g., researcher’s name, station name, soak time) from the data, and downloading the data in a readable format (e.g., Excel, PDF) according to the teacher/educator’s request. The tracking data is then sent to the teacher/educator reminding them that this data is for educational purposes only.

6. Data Documentation

The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 1.7. Data collection method(s)
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

7. Data Access

NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.

7.1. Do these data comply with the Data Access directive?
Yes
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
Yes
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

SCUTES sturgeon researchers share the tracking data from acoustic tags that NOAA Fisheries provides with the understanding that the tracking information is used by the SCUTES program for the sole purpose of providing teachers/educators with data sets for the “Adopt a Sturgeon” program and that the distribution of the data will not threaten researchers’ proprietary interests (e.g., research publication).

7.2. Name of organization of facility providing data access:
Taken From: Support Roles (Distributor) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
7.2.1. If data hosting service is needed, please indicate:
N/A
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

Informal Data Sharing Agreement: Once a year, the researchers will share the tracking data from the

acoustic tags that NOAA Fisheries provided. At their discretion, they may share with us the tracking data

from other tags in addition to the NOAA fisheries tags. NOAA Fisheries has an informal agreement with

the SCUTES sturgeon researchers that the tracking information is used by the SCUTES program for the

sole purpose of providing teachers/educators with data sets for the “Adopt a Sturgeon” program and

that the distribution of the data will not threaten researchers’ proprietary interests (e.g., research

publication).

7.4. Approximate delay between data collection and dissemination:
Unknown
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

8. Data Preservation and Protection

The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.

8.1. Actual or planned long-term data archive location:
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
NO_ARCHIVING_INTENDED
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Greater Atlantic Regional Fisheries Office - Gloucester, MA
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
N/A
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

Processed data is uploaded into the Oracle database. Data is also protected from accidental or malicious modification or deletion by maintaining a data backup (i.e., Excel spreadsheet) of the raw tracking data that has been submitted by SCUTES sturgeon researchers on an internal network (i.e., GARFO H:drive). Additionally, individual sturgeon researchers store and maintain all data associated with their work at their respective institutions/organizations.

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank