Wave 1 & 2 Score

29%
8 / 28

Wave 1

8 / 15

Wave 2

0 / 13

Entities & Attr Score

0%
0 / 2

Entities & Attributes

0 / 2

Wave 1

53%
8 / 15
Wave 1 comprises the first set of metadata fields identified by NMFS EDM for metadata completeness.

Title

Human readable label for the InPort catalog item.

InPort: Item Identification > Title
FGDC: /metadata/idinfo/citation/citeinfo/title
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/citation/CI_Citation/title

Completion Guidance:

Since an item in InPort cannot be created without a title, all items should already have this field filled out, and the item should always receive a point.

Best Practice: The title should be human-readable and as descriptive as possible, employing terms that clearly identify the specific subject and unique contents of the record.

Abstract

A summary or description of the data described by the metadata record.

InPort: Item Identification > Abstract
FGDC: /metadata/idinfo/descript/abstract
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/abstract

Completion Guidance:

To receive a point, this field must be filled out.

Best Practice: Abstract narrative should include information on general content and features; dataset application: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations. Note: Many applications limit preliminary display to the first 150-200 characters of this field so critical distinguishing characteristics should be listed first.

Physical Location

Name of the organization or facility, city, and state where the data was located prior to archiving.
A complete physical location (organization, city, and state), or a location description, was not found. This field is required.

InPort: Physical Location > Organization, City, State, Description
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

Select the relevant organization from the list, which should also populate the City and State fields. If City and State fields are not populated for the selected organization, enter them in manually. Country is not required.

Note: If the data is sent directly to the archiving location, you can leave the Organization/City/State blank, but under the Location Description field, enter "Sent directly to archive."

To summarize, in order receive a point, you should do one of the following:
   1) Fill out Organization, City, and State.  — OR —
   2) Fill out the Location Description.

Best Practice: Enter the organization/facility where the data set is physically located, prior to archiving.

Data Presentation Form

The method in which the data are represented.
No data presentation form was found.

InPort: Data Set Information > Data Presentation Form
FGDC: /metadata/idinfo/citation/citeinfo/geoform
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/citation/CI_Citation/presentationForm

Completion Guidance:

To receive a point, a selection must be made from the dropdown list. Select "Other" if none of the provided options apply.

Best Practice: Each metadata record shall indicate the primary presentation form of the data.

Distributor / Download URL

Name of the organization or facility which is providing the access to the data, and the URL(s) where the data set may be downloaded from.
At least one distributor must be specified, as an organization, and with current effective dates; and at least one Download URL must be specified. These fields are not required if an approved access waiver exists for this data.

InPort: Support Roles > Distributor
Distribution Info > Download URL
Data Management > Is Access to the Data Limited Based on an Approved Waiver?
FGDC: /metadata/distinfo/distrib/cntinfo/
/metadata/distinfo/stdorder/digtopt/onlinopt/networka/networkr/
ISO 19115: /MI_Metadata/distributionInfo/MD_Distribution/distributor/...
/MI_Metadata/distributionInfo/MD_Distribution/transferOptions/MD_DigitalTransferOptions/onLine/CI_OnlineResource/...

Completion Guidance:

To receive a point, a Distributor must be specified under the Support Roles section. The role type should be "Distributor", and Organization and Start Date should be filled out. In addition, at least one download URL must be provided in the Distribution Info section. However, if an approved access waiver exists for this data, the Distributor and Download URL are not required. (See Data Access Limited Based on Approved Waiver? guidance below).

If the Distributing Organization is not in the Organization dropdown, please contact InPort Support to have the organization added.

Important Note #1: For distributors, an Organization must be specified (Person is optional, and in most cases, inapplicable). In addition, the dates must be in effect - i.e. the Start Date must be earlier than the current date, and the End Date must be after the current date. However, in almost all cases, End Date should be left blank, which signifies that the Support Role is in effect up to the present date, unless you are already aware that the Distributor will change on a certain date, or if you are providing a historical record of past distributors. Note, though, that in order to receive a point, at least one current Distributor must be specified.

Important Note #2: For the download URL, this field is found under the Distribution Info section. There is also a URLs section in InPort, which can be used for other related URLs, but download URLs should always be listed under the Distribution Info section. URLs that appear in the URL section will not be counted towards a point.

Best Practice: Each metadata record shall specify the organization responsible for distributing and providing access to the data. Each metadata record shall specify download URL(s) where the data set can be obtained, if applicable.

Point of Contact

Person to serve as a generic point of contact for the data.
At least one point of contact must be specified, as a person, and with current effective dates.

InPort: Support Roles > Point of Contact
FGDC: /metadata/idinfo/ptcontac/cntinfo/
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/pointOfContact/...

Completion Guidance:

To receive a point, a Point of Contact must be specified under the Support Roles. The role type should be "Point of Contact", and Person and Start Date should be filled out.

If the Point of Contact is not in the Person dropdown, please contact your Librarian to have the person added to InPort.

Important Note: For points of contact, a Person must be specified (Organization is recommended, but optional). In addition, the dates must be in effect - i.e. the Start Date must be earlier than the current date, and the End Date must be after the current date. However, in almost all cases, End Date should be left blank, which signifies that the Support Role is in effect up to the present date, unless you are already aware that the Point of Contact will change on a certain date, or if you are providing a historical record of past points of contact. Note, though, that in order to receive a point, at least one current Point of Contact must be specified.

Best Practice: The person/organization directly responsible for answering questions about a resource. This could be a person at an archive rather than the originator of the resource (described in the citation).

Data Steward

Person who is responsible for the management of the data.
At least one data steward must be specified, as a person, and with current effective dates.

InPort: Support Roles > Data Steward
FGDC: No equivalent field.
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/citation/CI_Citation/citedResponsibleParty/CI_ResponsibleParty/[CI_RoleCode='custodian']

Completion Guidance:

To receive a point, a Data Steward must be specified under the Support Roles. The role type should be "Data Steward", and Person and Start Date should be filled out.

If the Data Steward is not in the Person dropdown, please contact your Librarian to have the person added to InPort.

Important Note: For data stewards, a Person must be specified (Organization is recommended, but optional). In addition, the dates must be in effect - i.e. the Start Date must be earlier than the current date, and the End Date must be after the current date. However, in almost all cases, End Date should be left blank, which signifies that the Support Role is in effect up to the present date, unless you are already aware that the Data Steward will change on a certain date, or if you are providing a historical record of past data stewards. Note, though, that in order to receive a point, at least one current Data Steward must be specified.

Best Practice: List the current data steward of the data set. The data steward should be listed as a person, and not a group or organization.

Metadata Contact

Person who is responsible for the management of the metadata.

InPort: Support Roles > Metadata Contact
FGDC: /metadata/metainfo/metc/cntinfo/
ISO 19115: /MI_Metadata/contact/...

Completion Guidance:

To receive a point, a Metadata Contact must be specified under the Support Roles. The role type should be "Metadata Contact", and Person and Start Date should be filled out.

If the Metadata is not in the Person dropdown, please contact your Librarian to have the person added to InPort.

Important Note: For metadata contacts, a Person must be specified (Organization is also recommended). In addition, the dates must be in effect - i.e. the Start Date must be earlier than the current date, and the End Date must be after the current date. However, in almost all cases, End Date should be left blank, which signifies that the Support Role is in effect up to the present date, unless you are already aware that the Metadata Contact will change on a certain date, or if you are providing a historical record of past metadata contacts. Note, though, that in order to receive a point, at least one current Metadata Contact must be specified.

Best Practice: List the current person directly responsible for metadata creation and maintenance. The metadata contact should be listed as a person, and not a group or organization.

Geographic Area

The latitude and longitude of the rectangular region in which the data was collected, and/or a description of the geographic area in which a particular activity documented in the metadata record occurred. Include landmass info, island groups, ocean sector, etc.

InPort: Extents > Geographic Area > W°|E°|N°|S° Bounds and/or Description
FGDC: /metadata/idinfo/spdom/bounding/[west|east|south|north]bc,
   /metadata/spdom/descgeog
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/extent/EX_Extent/geographicElement/EX_GeographicBoundingBox/[west|east|south|north]Bounding[Longitude|Latitude],
   /MI_Metadata/identificationInfo/MD_DataIdentification/extent/EX_Extent/description

Completion Guidance:

To receive a point, fill out the geographic bounds, and/or the geographic area description. Geographic bounds do not apply to every Data Set, thus bounds can be empty as long as a description of the geographic area is provided.

Best Practice: Each metadata record shall indicate the geographic extent of the dataset, through bounding coordinates and/or a textual description of the geographic area.

Time Frames

The time frame(s) within which the activity described in the metadata record occurred.

InPort: Extents > Time Frames
FGDC: /metadata/idinfo/timeperd/timeinfo/
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/extent/EX_Extent/temporalElement/EX_TemporalExtent/extent/TimeInstant

Completion Guidance:

To receive a point, fill out the Time Frame Type and the Start Date. In addition, if the time frame type is Range, fill out the End Date.

Best Practice: Each metadata record shall specify the time period(s) for which the data has been collected.

Security Class

The classification level of the data.

InPort: Access Information > Security Class
FGDC: /metadata/secinfo/secclass
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/resourceConstraints/MD_SecurityConstraints/classification

Completion Guidance:

To receive a point, this field must be filled out. Note: the classifications "Top Secret", "Secret", and "Confidential" are national security classifications. For business confidential data within NOAA, use "Sensitive." Do not use "Confidential" for business confidential data.

Best Practice: Each metadata record shall provide information on access restrictions for the data set.

Data Access Constraints

For data with limitations on public access, a description of the methods by which data is protected from unauthorized access and/or disclosure.

InPort: Access Information > Data Access Constraints
FGDC: /metadata/idinfo/accconst
ISO 19115: /MI_Metadata/identificationInfo/MD_DataIdentification/resourceConstraints/MD_LegalConstraints/accessConstraints

Completion Guidance:

To receive a point, this field must be filled out. If there are no data access constraints, enter "Not Applicable".

Best Practice: Each metadata record shall specify access constraints for the data set.

Data Access Procedure

A description of the steps required to obtain access to the data.
Data Access Procedure information was not found.

InPort: Access Information > Data Access Procedure
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out.

Best Practice: Each metadata record shall specify access procedures to obtain the data set.

Lineage Process Steps

A list of the data processing steps used to generate the dataset.
Neither a Lineage Statement nor Lineage Process Steps were found.

InPort: Lineage > Lineage Statement, Process Steps
FGDC: /metadata/dataqual/lineage/procstep/...
ISO 19115: /MI_Metadata/dataQualityInfo/lineage/LI_Lineage/processStep

Completion Guidance:

To receive a point, enter the relevant process step(s), or provide relevant information in the Lineage Statement field. Note that process steps require both a Sequence Number (to indicate their order) and a Description.

Best Practice: Each metadata record shall specify the process steps used to construct the data set.

Last Modified Date

The last modification date of the metadata record.

InPort: Catalog Item Details

Completion Guidance:

This field is automatically populated when any change is made to an InPort record, thus the item should always receive a point.

Best Practice: Each metadata record shall specify its last modification date.

Wave 2

0%
0 / 13
Wave 2 comprises the second set of metadata fields identified by NMFS EDM for metadata completeness.

Instrument

The piece of equipment used to convert the signal into data.
Instrument information was not found.

InPort: Data Set > Instrument
FGDC: No equivalent field.
ISO 19115: /MI_Metadata/acquisitionInformation/MI_AcquisitionInformation/instrument/MI_Instrument

Completion Guidance:

To receive a point, this field must be filled out. If an Instrument was not used in the collection of the data, enter "Not Applicable".

Best Practice: Include information on all measuring instruments used for the data set, if applicable. This is only required for observational data, and not required for data derived from observational datasets, model inputs, etc.

Platform

The object which the Instrument or Gear is attached to.
Platform information was not found.

InPort: Data Set > Platform
FGDC: No equivalent field.
ISO 19115: /MI_Metadata/acquisitionInformation/MI_AcquisitionInformation/platform/MI_Platform

Completion Guidance:

To receive a point, this field must be filled out. If a Platform was not used in the collection of the data, enter "Not Applicable".

Best Practice: Include information on the platform used for the data set, if applicable. This is only required for observational data, and not required for data derived from observational datasets, model inputs, etc.

Physical Collection / Fishing Gear

The piece of equipment used for the purpose of catching fish or collecting physical specimens, such as water, air, or benthic sample.
Physical collection / fishing gear information was not found.

InPort: Data Set > Physical Collection / Fishing Gear
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out. If a Gear was not used in the collection of the data, enter "Not Applicable".

Best Practice: Include information on the physical collection / fishing gear used for the data set, if applicable. This is only required for observational data, and not required for data derived from observational datasets, model inputs, etc.

Quality Control Procedures Employed

A description of the quality control procedures employed by the data.
Information on quality control procedures employed was not found.

InPort: Data Quality > Quality Control Procedures Employed
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out.

Best Practice: Include information on the quality control procedures used for this data set.

Data Management Resources Identified?

Indicates if data management resources for the data have been identified.
Information on the identification of data management resources was not found.

InPort: Data Management > Have Resources for Management of these Data Been Identified?
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be answered. Note that "No" is a valid answer at this time.

Best Practice: Indicate whether or not management resources have been identified for these data.

Data Management Budget Percentage

Numeric value representing the percent of the data's budget which has been allocated towards data management.
Information on the data management resources budget was not found.

InPort: Data Management > Approx. Percentage of Budget Devoted to Data Management
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out. Use the calculation:
   100 * (the budget for data management) / (the budget for data production)
to determine the approximate percentage.

Note that "0" (zero) and "Unknown" are acceptable answers at this time.

Best Practice: Provide the approximate percentage of the budget which has been allocated towards data management. If unknown, indicate "Unknown."

Data Access Directive Compliant?

Indicate if the data complies with the NOAA Data Access Procedural Directive.
Information on NOAA Data Access Procedural Directive compliance was not found.

InPort: Data Management > Do these Data Comply with the Data Access Directive?
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be answered. Note that "No" is a valid answer at this time.

Best Practice: Indicate whether or not the data set is compliant with the Data Access Directive.

Data Access Limited Based on Approved Waiver?

Indicates if there is an approved waiver (or a waiver has been submitted) limiting the access of the data.
Information on limitations to data access based on an approved waiver was not found.

InPort: Data Management > Is Access to the Data Limited Based on an Approved Waiver?
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be answered.
Check "Yes" if there is an Approved Waiver, or if a waiver has been submitted.
Check "No" is there is no waiver, or if the submitted waiver was denied.

Best Practice: Indicate whether or not data access is limited based on an approved waiver.

Data Hosting Service Needed?

Indicates if a service is needed to host the access to the data. This information is required if a distributor has not been specified.
No information on whether a data hosting service is needed was found, and no Distributor has been specified.

InPort: Data Management > If Distributor (Data Hosting Service) is Needed, Indicate
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

This field is only required if a Distributor has not been specified (see Completion Notes for Distributor). Thus, to receive a point, either this field must be filled out, OR a distributor must be specified.

If there is not a current distributor, then the answer should be "Yes". If there is a current distributor, the answer can still be yes if the owner of the Data Set is interested in additional access options.

Best Practice: Include information on whether a data hosting service is needed for the data set.

Data Collection and Dissemination Delay

The approximate time in days from when the data were collected and the data were disseminated.
No information was found on the delay between data collection and dissemination.

InPort: Data Management > Approximate Delay Between Data Collection and Dissemination
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out. If there is no delay, enter "0 days" (zero). If the time is not known, enter "Unknown".

Best Practice: Provide the approximate delay time between data collection and dissemination.

Data Collection and Dissemination Delay Explanation

An explanation or description of the authority under which the data access is being delayed.
No explanation on the delay between data collection and dissemination was found. This field is required only if the delay between data collection and dissemination is longer than the latency of automated processing.

InPort: Data Management > If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

This field is required if applicable. Since there is no way to easily determine whether it is applicable, it is not counted in the rubric score; however, it still must be filled out if applicable.

Best Practice: If the delay between data collection and dissemination exceeds the latency of automated processing, an explanation is required to indicate under what authority access is delayed.

Archive Location

Name of the Organization or Facility which is providing data archiving.
No archive location information was found.

InPort: Data Management > Actual or Planned Long-Term Data Archive Location
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, a selection must be made from the Archive Location dropdown. In addition, if "World Data Center" or "Other" was selected, it must be specified in the free text field. Or, if "To Be Determined", "Unable to Archive", or "No Archiving Intended" was selected, the explanation must be provided.

Best Practice: Indicate the actual or planned long-term data archive location of the data set. If the archive location is World Data Center or Other, a free-text location must be provided. If the archive location is To Be Determined, Unable to Archive, or No Archiving Intended, an explanation must be provided as well.

Data Collection and Archive Delay

The approximate time in days from when the data were collected and the data were archived.
No information was found on the delay between data collection and archiving.

InPort: Data Management > Approximate Delay Between Data Collection and Archiving
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out. If there is no delay, enter "0 days" (zero). If the time is not known, enter "Unknown".

Best Practice: Provide the approximate delay time between data collection and archiving.

Data Protection Plan

A description of how the data be protected from accidental or malicious modification or deletion. Include discussion of data backup, disaster recovery/contingency planning, and off-site data storage relevant to the data collection.
No information was found on the data protection plan.

InPort: Data Management > How Will the Data be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?
FGDC: No equivalent field.
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, this field must be filled out.

Best Practice: Provide a data protection plan description. Explain how the data will be protected from accidental or malicious modification or deletion, prior to receipt by the archive.

Entities & Attributes

0%
0 / 2
The Entity & Attribute section comprises the fields identified by NMFS EDM for metadata completeness for a data set's entities and attributes at the data set level.

Child Entity Exists?

A child entity associated with the Data Set.
No child entities were found.

InPort: Item Identification (for a child catalog item of type "Entity") > Title
FGDC: /metadata/eainfo/...
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, the data set must have at least one child entity.

Note: Entity information is not specified in the Data Set. Create a child item of type "Entity".

Best Practice: Each table should be represented by a child entity item.

Data Attributes

Attribute(s) of the entity associated with the data.
No attributes were found on one or more of the tabular child entities of this data set.

InPort: Data Attributes (for a child catalog item of type "Entity") > Name
FGDC: /metadata/eainfo/detailed/attr/attrdef
ISO 19115: No equivalent field.

Completion Guidance:

To receive a point, a child entity which has a tabular Entity Type ("Data Table", "Data View", or "Spreadsheet") must have at least one attribute.

Note: Attribute information is not specified in the Data Set. Go to the Data Attributes section of child entities.

Best Practice: If a child entity is tabular, there should be at least one Data Attribute.