Frequently-Asked Questions about Metadata

How many metadata records do I need?

In general, you should supply one metadata record per project if you expect to produce one dataset. However, more metadata records might be needed if several data files are submitted and are not consistently related to each other. Examples include:

Per cruise metadata, like ctd, bottle or nutrient information.
Example: CTD data collected on a Healy cruise (HLY0701) [XML]
Gridded data: model forecast, satellite product. If the data structure and format is consistent from data submission to data submission, then this only needs to be described once. However, if processing changes, additional data lineage will need to be updated.
Example: AMSR-E/Aqua Daily 12.5 km Sea Ice Concentration [XML]
Databases of information. If datasets are incrementally added into a larger database system that BSIERP will harvest.
Example: AFSC Ichthyoplankton Information System [XML]
Two different datasets that use two different spatial references. Since there is no way to define both spatial references in the XML metadata record, two separate records will be required to define each dataset.

What does this data set describe?

How should this data set be cited? | dataset title, date of publication, publisher and contact information
What geographic area does the data set cover?
- West_Bounding_Coordinate: -100.00000
- East_Bounding_Coordinate: 100.00000
- North_Bounding_Coordinate: 90.00000
- South_Bounding_Coordinate: 0
- Description_of_Geographic_Extent (short description of the geographic areal domain of the data set)
- What does it look like? (graphic depiction of study area)
Does the data set describe conditions during a particular time period?
- Several options are available for defining a time, set of times, or a time range. Typical use is to use a range of dates and then click Add to define start and end date and/or time.
- Currentness: describe how these times were determined
What is the general form of this data set?
- Geospatial_Data_Presentation_Form: presentation of cited material
How are geographic features stored?
- Single word description of spatial refrences in the dataset. Can be one of Point, Vector or Raster. Ex: XBT/CTD casts may be considered Point locations, cruise track lines are composed of connected points (to form Lines/Vectors) and Raster is typically used for gridded datasets (model output, satellite, etc). If the dataset does not strictly conform to any of these types, provide an Indirect Spatial Reference instead.
- What geographic coordinate system is used?
How are geographic features described?

Define variables and/or column names for the dataset. This section will probably be the hardest to complete. As you define entity and attribute information, you may find that you actually need to create multiple metadata records if information between files/columns are found to be incompatible.
NOTE: Attributes or Domain Values that you define are saved only if they are attached or linked to corresponding Entity Types and Attributes. Failure to do so will result in loss of definitions.
Entering multiple Entity Types: You can construct one entity type that represents a superset of NetCDF variables or Excel/CSV columns or tables in a database. If you only have a handful of files or database tables that you wish to describe individually, please use one Entity Type per file or database table. The Attributes and Domain Values will still be a superset of the handful of files or database tables. More detailed instructions on how to attach or link items may be found here:

Who produced the data set?

Formal authors, digital compilers, and editors

Why was the data set created?

Describe the purpose of collecting the data.

How was the data set created?

From what previous works were the data drawn?
How were the data generated, processed, and modified?
What similar or related data should the user be aware of?

How reliable are the data; what problems remain?

Explanation of the fidelity of relationships in the dataset and tests used. The report can reference more extensive descriptions in other documents. If creating a Logical Consistency Report is not logical, use the default "not applicable."
Information about omissions, selection criteria, generalizations, definitions used, and other rules used to derive the data set. The report can reference more extensive descriptions in other documents.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: Restrictions on accessing or obtaining the data set
Use_Constraints: Restrictions on using the data set after access is granted

Who distributes the data set?
- Name and contact information
What's the catalog number I need to order this data set?
- Identifier by which distributer knows the data set
What legal disclaimers am I supposed to read?
How can I download or order the data?
- Availability in digital form; fees and terms for data retrieval

Who wrote the metadata?

Last modification date
Author contact information
Metadata standard (e.g., FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata (FGDC-STD-001.1-1999)

What other elements are required by Data Management?

These other elements are required by the USGS (mp) metadata parser program and are not necessarily required for production of the FAQ. However, the information will be presented in the full HTML representation of the metadata record.

Identification:Basic Info:Status

Select an item in Progress.
Select an item in Updating or you may type in something more appropriate.

Identification:Keywords

Theme:Add: Multiple themes may be added. In support of the Integrated Ocean Observing System, a Thesaurus that can be added is "IOOS Core Variables". The first keyword must indicate the version of the standard. Followed by one or more of the fixed vocabulary for the standard.
IOOS Core Variables: Bathymetry, Bottom Character, Contaminants, Dissolved Nutrients, Dissolved O2, Fish Abundance, Fish Species, Heat flux, Ice Distribution, Ocean color, Optical properties, Pathogens, Phytoplankton species, Salinity, Sea Level, Surface Currents, Surface Waves, Temperature, Zooplankton abundance, Zooplankton species