Data Management Plan (Deprecated)
Indian Lands
|
Data Set
(DS)
| Office for Coastal Management
GUID: gov.noaa.nmfs.inport:48860 | Published / External
GUID: gov.noaa.nmfs.inport:48860 | Published / External
Deprecated Version
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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:
Indian Lands
Taken From: Item
Identification | Title
1.2. Summary description of the data:
This dataset depicts feature location, selected demographics, and other associated data for American Indian Reservations, Alaska Native Villages, Federally Recognized Tribal Entities, Public Domain Allotments, and off-reservation trust lands.
Taken From: Item
Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
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?
One-time data collection
Taken From: Extents / Time
Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2005
Taken From: Extents | Time Frame
- Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -174.201359, E: -67.041677, N: 71.296549, S: 25.757695
Taken From: Extents | Geographic
Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
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.)
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
No information found
Taken From: Data Set
Information | Data Presentation Form
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.)
(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
Taken From: Acquisition
Information | Instruments, Platforms
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:
No information found
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.
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.
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:
No information found
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:
No information found
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:
No information found
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.
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?
No information found
4.2. Approximate percentage of the budget for these data devoted
to data management (specify percentage or "unknown"):
No information found
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):
(describe or provide URL of description):
Process Steps:
- 2013-10-01 00:00:00 - Source data was received directly from source. Downloadable source data is not available. Clip data to US coastal states, including Alaska. Dissolve data based on the following fields: IND_NAME (rename to name) AIANA_DESC (rename to description) ENTITY (rename to entity) ORG_CODE (rename to organization) FED_REGIST (rename to federalRecognition) REGION_NAM (rename to region) AGENCY_NAM (rename to agency) SELF_GOVER (rename to selfGovernance) COMMENTS (rename to comments) ELINK (rename to link) TREATY (rename to treaty) TRIBAL_EST (rename to establishment) GOV_TYPE (rename to government) ECON_SOURC (rename to economy) GAMING (rename to gaming) MED_FAC (rename to medicalFacilities) Perform a union to check for any overlapping polygons, identify and merge as needed. Check geometry. Reproject data into WGS84. (Citation: Indian Lands in the United States)
Taken From: Lineage | Lineage
Statement, Process Steps (Process Date/Time, Source Citation Title, Description)
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):
(describe or provide URL of description):
No information found
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.6. Type(s) of data
- 1.7. Data collection method(s)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
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):
(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?
No information found
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?
No information found
7.1.2. If there are limitations to public data access, describe
how data are protected from unauthorized access or disclosure:
None
Taken From: Access Info |
Data Access Constraints
7.2. Name of organization of facility providing data access:
No information found
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.
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:
No information found
Taken From: Data
Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
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.
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:
No information found
Taken From: Access Info |
Data Access Procedure
7.4. Approximate delay between data collection and
dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing,
indicate under what authority data access is delayed:
Taken From: Data
Management | If delay is longer than latency of automated processing, indicate under
what authority data access is delayed
Notes: This field is required if applicable.
Notes: This field is required if applicable.
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)
(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 information found
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.
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.
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):
Office for Coastal Management - Charleston, SC
Taken From: Physical
Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
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:
No information found
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
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found
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