Dataset metadata v1.0.0

	A	B	C	D	E	F
1	Dataset metadata	v1.0.0
2	Metadata fields			User input	Required	Descriptions
3	Project ID				Y
4	Experiment ID				Y
5	Data type [controlled vocabulary]				Y	dosing' 'cast' 'bottle' 'flow_thru' 'pigment' 'marine_snow_catcher' 'mooring' 'drifter' 'airborne' 'auv' 'usv' 'experimental' 'sediment_trap' 'taxonomy' 'sediment' 'model_output' 'socioeconomic' 'net_tow'
6	Data Submitter [controlled vocabulary]	Name			Y	Full name of the principal investigator (Firstname Middlename Lastname).
7		Institution			Y	Affiliated institution of the principal investigator (e.g., Woods Hole Oceanographic Institution).
8		Road address				Street and number of the affiliated institution of the person submitting data
9		City				Name of the City, e.g., Seattle
10		State or province				State or Province, e.g., Washington
11		Zip code				Zip code, e.g., 98115
12		Country				Name of the country, e.g., U.S.A.
13		Phone				Phone number of the principal investigator.
14		Email				Email address of the principal investigator.
15		Researcher ID	ID			Identification number of the researcher
16		Researcher ID	ID type (ORCID, Researcher ID, etc.)			Type of the researcher identification, e.g., ORCID, Researcher ID, etc.
17	Author list for data citation				Y	Author list in the format of Lastname1, Firstname1 Middlename1; Lastname2, Firstname2 Middlename2; ...
18	Dataset title				Y	A brief descriptive sentence that summarizes the content of a data set. Here is one example: "Dissolved inorganic carbon, total alkalinity, pH, temperature, salinity and other variables collected from profile and discrete sample observations using CTD, Niskin bottle, and other instruments from R/V Wecoma in the U.S. West Coast California Current System during the 2011 West Coast Ocean Acidification Cruise (WCOA2011) from 2011-08-12 to 2011-08-30"
19	Dataset description (Abstract)				Y	The abstract of a dataset is a brief summary that provides an overview of the dataset's content, purpose, and scope. It is used to provide context and background information to users who are interested in using the dataset. An abstract may include information such as the dataset's source, how the data was collected or generated, the variables or attributes included in the dataset, and any limitations or restrictions on the use of the data. It may also include information on how the data can be accessed or used.
20	Data license [controlled vocabulary]					NOAA intramural PIs are required to use "CC0-1.0" (universal public domain dedication), while non-NOAA PIs have the option of either choosing "CC0-1.0" or "CC-BY-4.0" (international license). For more info, refer to: https://www.nauticalcharts.noaa.gov/data/data-licensing.html.
21	Fair data use request					A statement from the data producer regarding how this dataset should be used.
22	Data product type [controlled vocabulary]				Y	One of the three choices: (a) Originally collected dataset (e.g., a dataset collected from a research cruise or laboratory experiment), (b) Data compilation product (e.g., SOCAT, GLODAP), or (c) Derived product (e.g., gridded products, or model output). This piece information will be used to put the search results into categories within the data access portal.
23	QC flag scheme					Describe what the quality control flags stand for, e.g., 2 = good value, 3 = questionable value, 4 = bad value.
24	Platform info (repeatable)	Platform type [controlled vocabulary]			Y	Controlled vocabularies for the types of the platform: https://www.ncei.noaa.gov/access/ocean-carbon-acidification-data-system/vocabularies/platform-types.html.
25		Platform name				Name of the observing platform, e.g., RV Ronald Brown, Saildrone#0132, Mooring_First_Landing, etc.
26		Platform ID (synonymous with glider ID, cruise ID)				A unique name assigned to oceanographic assets such as buoys, moorings, floats, drifters, towed vehicles like the Scanfish or StingRay. This is synonymous with the BCO-DMO “platform” parameter (https://www.bco-dmo.org/parameter/932), NERC “platform type” term (https://vocab.nerc.ac.uk/collection/W06/current/CLSS0001/), and the “platform_id” term within the Climate and Forecast (CF) metadata conventions (https://cfconventions.org/Data/cf-standard-names/current/build/cf-standard-name-table.html). e.g., ICES platform code (e.g., 33RO).
27		Platform owner				Institution that owns the platform.
28		Platform country				Country to which the platform belongs.
29	calibration_files				Y	A comma-separated list (no spaces) of supplementary file names containing coefficients and techniques used to calibrate the instruments used in data collection. The named files can be found within the relevant documents folder accompanying the submitted data files.
30	start_date				Y	The earliest date data in the file were collected (in YYYY-MM-DD), in UTC.
31	end_date				Y	The latest date data in the file were collected (in YYYY-MM-DD), in UTC.
32	start_time				Y	The earliest date time in the file were collected (in HH:MM:SS), in UTC.
33	end_time				Y	The latest date time in the file were collected (in HH:MM:SS), in UTC.
34	north_latitude (in decimal degrees)				Y
35	south_latitude (in decimal degrees)				Y
36	east_longitude (in decimal degrees)				Y
37	west_longitude (in decimal degrees)				Y
38	Filenames of data				Y	Filenames of data associated with this metadata sheet
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100