MLML RDC Moss Landing Marine Laboratories Regional Data Center

MLML RDC Moss Landing Marine Laboratories Regional Data Center Project Registration Template Documentation Updated July 15, 2014

Table of Contents INTRODUCTION...5 MLML RDC PROJECT TEMPLATE...5 PROJECT SUBMISSION STEPS...6 MLML RDC PROJECT TABLES...7 PR OJECT TEMPLATE TABLES...8 AGENCY TAB LE...... 8 STATIONS TABLE...10 P ROGRAM TABLE...16 PARENT PROJECT TABLE...17 PROJECT TAB LE......19 QAPP TABLE...22 SAMPLING PROTOCOL TABLE...23 COLLECTIONDEVICE_FIELDRESLOOKUP TABLE...25 MLML RDC Project Registration Template Documentation revised 7/15/14 2 of 25

List of Acronyms CEDEN California Environmental Data Exchange Network MLML RDC SWAMP Moss Landing Marine Laboratory Regional Data Center Surface Water Ambient Monitoring Program MLML RDC Project Registration Template Documentation revised 7/15/14 3 of 25

List of Terms Controlled Vocabulary Data Checker Lists Primary Key Data Type Controlled vocabulary refers to codes and associated definitions maintained within the MLML RDC to ensure comparability between and among data sets. Current controlled vocabulary can be found at: http://205.155.75.83/ceden_checker/lists.php Web-based automated tool that assists data submitters in examining their data sets against the required lists, formats and business rules. Controlled vocabularies are maintained within the MLML RDC database as ' Lists' and are managed by the MLML RDC to maintain comparability between RDCs and throughout data sets available through CEDEN. Contact the MLML RDC to add new codes to lists. Uniquely identifies each row in a table and is comprised of a set of columns. No two distinct rows in a table can have the same combination of column values. Required for record uniqueness. Refers to the type of format required for a specific column heading in templates. Data type examples include: integer (whole numbers), text, date and time, and decimal. MLML RDC Project Registration Template Documentation revised 7/15/14 4 of 25

Introduction This document is designed to provide guidance on reporting requirements for electronic data to be entered in the Moss Landing Marine Laboratories Regional Data Center (MLML RDC). Detailed below are definitions of data elements within the MLML RDC Project Registration template. Please review the entire Project Registration Guidance Document prior to filling out or submitting the MLML RDC Project Registration template. If you have any questions regarding these guidelines, contact the MLML RDC Help Desk for assistance. MLML RDC Project Registration Template The project registration template has been developed to aid data generators with new projects to compile the information needed to initially create project specific codes including Agency, Station, Collection Device, QAPP, Sampling Protocol, Program and Project. The Project code is used to reference all of a user's data and allows users to link various data types from within the MLML RDC database. The information supplied in the template is used by the MLML RDC to create new codes in the database that are essential for data comparability and will allow the user to add associated data to the MLML RDC database. It is helpful to provide this needed information at the start of the project for data entry. Once the information is compiled, contact the MLML RDC Help Desk to have the individual codes created. The MLML RDC will contact you once your information has been reviewed to discuss and/or provide you with your specific programmatic codes. MLML RDC Project Registration Template Documentation revised 7/15/14 5 of 25

Project Registration Submission Steps To submit project registration information to the MLML RDC, start with the Project Registration Template. In this template you will find the eight data tables (each in a separate worksheet) required for submitting project registration data. This file can be named at the discretion of the user; however, the Excel sheet tabs MUST be named Agency, Stations, Program, ParentProject, Project, QAPP, SamplingProtocol and CollectionDevice_FieldRes respectively. MLML RDC Project Registration Template Documentation revised 7/15/14 6 of 25

MLML RDC Project Registration Tables Below describes what is included and submission requirements for each of the eight tables in the MLML RDC Project Registration Template: 1. Agency a. Holds information about the sampling agency b. Required only for new agencies that are not currently in the database 2. Stations a. Holds information about sample site and GIS information b. Required only for new stations that are not currently in the database 3. Program a. Holds information about the program b. Required only for new programs that are not currently in the database 4. ParentProject a. Holds information about the parent project b. Required only for new parent projects that are not currently in the database 5. Project a. Holds information about the project b. Required only for new projects that are not currently in the database 6. QAPP a. Holds information about the QAPP b. Required only for new QAPPs that are not currently in the database 7. SamplingProtocol a. Holds information about the sampling protocol b. Required only for new sampling protocols that are not currently in the database 8. CollectionDevice_FieldRes a. Holds information about the collection device and associated analytes b. Required only for new collection devices that are not currently in the database The guidelines in the following sections will assist you in getting your data into the MLML RDC Project Registration tables. Once you have completed the template, visit the CalDUCS website to check and submit your data using the online data checker. The online data submission process includes specific checks on your data to ensure both data integrity and comparability with other data sets. Once the information is compiled, contact the MLML RDC Help Desk to have the individual codes created or for any specific data questions. The MLML RDC will contact you once your information has been reviewed to discuss and/or provide you with your specific programmatic codes. MLML RDC Project Registration Template Documentation revised 7/15/14 7 of 25

Project Registration Template Data Tables Agency Table PURPOSE: The agency table contains information about the agency. It is important to fill out as much information as possible. This table is only required for new stations not within the database and can be submitted prior to collecting any field data. Utilize the Agency list within MLML RDC's Controlled Vocabulary to view all current agencies within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: AgencyCode AgencyName None on this worksheet Not Required Columns: AgencyDescr Agency Comments AgencyType1 AgencyType2 AgencyType3 PrimaryContact StreetAddress City State Zip Email Telephone Fax WebAddress MLML RDC Project Registration Template Documentation revised 7/15/14 8 of 25

AGENCY TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION AgencyCode* Text Yes 20 Agency Unique code referencing the Agency AgencyName* Text Yes 255 Agency Name of the Agency AgencyDescr Text No 255 Description of the Agency Active Boolean No 1 Utility column used to limit list values in forms and queries AgencyComments Text No 255 Comments related to the Agency AgencyType1 Text No 50 Used in queries and forms to limit output to a subset of results AgencyType2 Text No 50 Used in queries and forms to limit output to a subset of results Used in queries and forms to AgencyType3 Text No 50 limit output to a subset of results Primary contact person for the PrimaryContact Text No 50 Agency StreetAddress Text No 50 Street address of the Agency Full name of the nearest town, city, or community where the Agency is located City Text No 255 State where the Agency is located; from State Text No 2 VariableCodes Zip Text No 10 Zip Code of the Agency Email Text No 50 Email address of the Agency Primary Contact Telephone Text No 25 Telephone number of the Agency Primary Contact Fax Text No 25 Fax number of the Agency Primary Contact WebAddress Text No 75 Web site of the Agency MLML RDC Project Registration Template Documentation revised 7/15/14 9 of 25

Stations Table PURPOSE: The stations table contains information about the station/sample site and GIS information. It is important to fill out as much information as possible. This table is only required for new stations not within the database and can be submitted prior to collecting any field data. Utilize the Station list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: StationSource StationCode StationName StationAgency CoordinateNumber TargetLatitude TargetLongitude SWRCBWatTypeCode Datum CoordinateSource LocalWaterbody State MLML RDC Project Registration Template Documentation revised 7/15/14 10 of 25

Not Required Columns: StationDescr CalWater_2004_HUNAME StationComments GageStationID EventType1 UpstreamArea EventType2 HBASA2_1995_NHCODE EventType3 NHD_24k_v2_GNIS_Name GeometryShape NHD_24k_v2_ReachCode DirectionsToStation NHD_24k_v2_HUC_12 AddDate NHD_24k_v2_Hu_12_Name Elevation NHD_100k_GNIS_Name UnitElevation NHD_100k_ReachCode StationDetailVerBy NHD_Plus_CatchmentComID StationDetailVerDate Ecoregion_1987_Level3* StationDetailComments IBI_NorthCoast_2005_WithinPolygon* LocalWaterShed IBI_SoCal_2005_WithinPolygon* Counties_2004_COUNTY StationGISVerBy CalWater_2004_RB StationGISVerDate CalWater_2004_CALWNUM StationGISVerComments * Not required unless station has accompanying bioassessment data. ADDITIONAL RESOURCES: When populating the stations table one can utilize additional resources provided by the Surface Water Ambient Monitoring Program (SWAMP). SWAMP has compiled and summarized many fields that are desired to fully describe the location of your station on the following website: http://swamp.mpsl.mlml.calstate.edu/resources-and-downloads/database-managementsystems/swamp-25-database/templates-25/gis-shapefile-layers. The SWAMP website has compiled GIS layers for CalWater, Counties, Ecoregion, IBI, HBASA and NHD. If one does not have access to GIS mapping software SWAMP has provided maps for data providers to visually map their stations for the IBI and Ecoregion layers. Contact your Regional Data Center if you have any questions regarding information found on this website. MLML RDC Project Registration Template Documentation revised 7/15/14 11 of 25

STATIONS TABLE STRUCTURE: * Primary Key, required for record uniqueness. ^ Not required unless station has accompanying bioassessment data. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION StationSource Text Yes 50 Agency or Project Agency or project that submitted the station. StationCode* Text Yes 25 StationName* Text Yes 100 Station Station A code representing the StationName and site and should be unique within a study design. Represents a unique sampling site in a sampling design. A single waterbody may have multiple stations. Station name must be unique for all stations. StationDescr Text No 255 Description of the StationCode. StationAgency Text Yes 20 StationComments Text No 255 EventType1 Text No 20 EventType2 Text No 20 EventType3 Text No 20 GeometryShape Text No 50 Agency Event Event Event Variable Code Represents the agency that created the station and is responsible for any updates or modifications to the station. Only the agency listed here can modify the information for this station. Default value equals Not Recorded if unknown. Any pertinent comments regarding the station and/or station area. Represents what type of sampling events will or have occurred at a station, i.e. water quality, tissue or bioassessment sampling. Represents what type of sampling events will or have occurred at a station, i.e. water quality, tissue or bioassessment sampling. Represents what type of sampling events will or have occurred at a station, i.e. water quality, tissue or bioassessment sampling. Physical shape of the Station. Example values are Line, Point, or Polygon. MLML RDC Project Registration Template Documentation revised 7/15/14 12 of 25

PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION DirectionsToStation Text No 255 A general description of how to get to the station using streets, landmarks, etc. AddDate Date/ Time No Date the StationCode was added. Format as dd/mmm/yyyy CoordinateNumber Integer Yes Number of the coordinate recorded at a Station; e.g. 1 for Points (target and actual coordinates), 1 and 2 for Lines. Default value equals 1 if unknown. TargetLatitude TargetLongitude Decimal Yes Decimal Yes Represents the targeted latitude for the sample site in decimal degrees with 5 decimal places. Represents the targeted longitude for the sample site in decimal degrees with 5 decimal places (must be negative). Datum Text Desired 10 CoordinateSource Text Desired 50 Variable Code Variable Code Represents the associated model of the Earth from which reference points are used to calculate position measurements. GPS Devices commonly use Datums such as NAD83 and WGS84. Default value equals NR if unknown Describes how the coordinate was measured. For example, if measurement was taken from a map or GPS. Default value equals NR if unknown Elevation Decimal No Elevation at which the sample was taken. UnitElevation Text No 2 StationDetailVerBy Text No 100 Variable Codes Unit of the Elevation measurement. Agency or person who performed the verification of the station detail information. StationDetailVerDate Date/ Time No Date the station detail information was verified. StationDetailComments Text No 255 Comments related to the station detail information. MLML RDC Project Registration Template Documentation revised 7/15/14 13 of 25

PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION LocalWatershed Text No 50 LocalWaterbody Text Desired 50 State Text Desired 2 Counties_2004_County Text No 50 SWRCBWatTypeCode Text Yes 10 CalWater_2004_RB Integer No 1 CalWater_2004_CALWNUM Text No 12 CalWater_2004_HUNAME Text No 35 GageStationID Text No 50 Variable Codes WBType Local watershed of the station as supplied by data user. Local waterbody of the station as supplied by data user. State in which the station was surveyed. Default = CA County in which the station was surveyed. Unique code assigned by the state for the appropriate waterbody type. Default value equals NR if unknown Regional Board ID Number from the CalWater 2.2.1 2004 GIS layer. This layer can be retrieved from: https://projects.atlas.ca.gov/frs/downl oad.php/676/calw221_e00.zip Watershed ID Number from the CalWater 2.2.1 2004 GIS layer. Hydrologic Unit Name from the CalWater 2.2.1 2004 GIS layer. Identifier for USGS Gage station located at the Station location. UpstreamArea Decimal No Area (measured in km2) upstream that drains to the sampling point. HBASA2_1995_NHCODE Text No 6 NHD_24k_v2_GNIS_Name Text No 65 NHD_24k_v2_ReachCode Text No 14 NHDCODE from Teale HBASA watershed GIS layer. This layer can be retrieved from: https://projects.atlas.ca.gov/frs/downl oad.php/389/hbasa2-1997_shp.zip Official federal Geographic Names Information System (GNIS) name of stream from the NHD high-resolution GIS layer. This layer can be retrieved from: http://nhd.usgs.gov/data.html 14-digit ReachCode ID Number for streams from NHD high-resolution GIS layer. MLML RDC Project Registration Template Documentation revised 7/15/14 14 of 25

PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION NHD_24k_v2_HUC_12 Text No 12 NHD_24k_v2_Hu_12_Name Text No 120 NHD_100k_GNIS_Name Text No 120 NHD_100k_ReachCode Text No 14 NHD_Plus_CatchmentComID Text No 50 Ecoregion_1987_Level3 Text No^ 5 12-digit Hydrologic Unit ID for NHD watershed polygon (WBD) from NHD high-resolution GIS layer. Name of 12-digit Hydrologic Unit for NHD watershed polygon (WBD) from NHD high-resolution GIS layer. Official federal Geographic Names Information System (GNIS) name of stream from the NHD mediumresolution GIS layer. This layer can be retrieved from: http://nhd.usgs.gov/data.html 14-digit ReachCode ID Number for streams from NHD mediumresolution GIS layer. Represents the common identifier of an NHD Flowline for the catchment polygon. EPA Ecoregion Level III name (US_L3NAME). This layer can be retrieved from: ftp://ftp.epa.gov/wed/ecoregions/ca/ IBI_NorthCoast_ 2005_WithinPolygon IBI_SoCal_ 2005_WithinPolygon TRUE/ FALSE No^ TRUE/ FALSE No^ True if the Station is located within the IBI North Coast 2005 polygon. False if otherwise. True if the Station is located within the IBI Southern California 2005 polygon. False if otherwise. StationGISVerBy Text No 100 Agency or person who performed the verification of the GIS station information. StationGISVerDate Date/ Time No Date the GIS station information was verified. StationGISVerComments Text No 255 Comments related to the GIS station information verification. MLML RDC Project Registration Template Documentation revised 7/15/14 15 of 25

Program Table PURPOSE: The program table contains information about the program. It is important to fill out as much information as possible. This table is only required for new programs not within the database and can be submitted prior to collecting any field data. Utilize the Program list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: ProgramCode ProgramName None on this worksheet Not Required Columns: ProgramDescr ProgramWebAddress ProgramComments PROGRAM TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION ProgramCode* Text Yes 50 Program Unique code referencing the Program ProgramName* Text Yes 50 Program Name of the Program ProgramDescr Text No 255 Description of the Program ProgramWebAddress Text No 75 Web site of the Program; e.g. Link to RMP, Bight03 web sites ProgramComments Text No 255 Comments related to the Program MLML RDC Project Registration Template Documentation revised 7/15/14 16 of 25

Parent Project Table PURPOSE: The parent project table contains information about the parent project. It is important to fill out as much information as possible. This table is only required for new parent projects not within the database and can be submitted prior to collecting any field data. Utilize the ParentProject list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: ProgramCode ParentProjectCode ParentProjectName AgencyCode None on this worksheet Not Required Columns: ParentProjectDescr ParentProjectSummary RWQCBCoverage StartDate ParentProjectWebAddress ParentProjectManager ParentProjectComments MLML RDC Project Registration Template Documentation revised 7/15/14 17 of 25

PARENT PROJECT TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION ProgramCode Text Yes 50 Program Foreign key reference to Program table ParentProjectCode* Text Yes 50 ParentProject Unique code referencing the ParentProject ParentProjectName* Text Yes 50 ParentProject Name of the ParentProject ParentProjectDescr Text No 255 Description of the ParentProject ParentProjectSummary Text No 255 A brief summary of the ParentProject, for display on the web RWQCBCoverage Text No 10 Identification of the SWRCB regional area(s) where sampling occurs for ParentProject; e.g. RWB4 or RWB8 or Statewide StartDate Date No 8 Date the ParentProject started ParentProjectWebAddress Text No 75 Web site of the ParentProject ParentProjectManager Text No 100 Manager of the ParentProject AgencyCode Text Yes 20 Agency associated with the ParentProject Manager; Foreign key reference to Agency table Comments related to the ParentProjectComments Text No 255 ParentProject MLML RDC Project Registration Template Documentation revised 7/15/14 18 of 25

Project Table PURPOSE: The project table contains information about the project. It is important to fill out as much information as possible. This table is only required for new projects not within the database and can be submitted prior to collecting any field data. Utilize the Project list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: ParentProjectCode ProjectCode ProjectName AgencyCode None on this worksheet Not Required Columns: ProjectDescr ProjectType1 ProjectType2 ProjectType3 ProjectCategory QAPPName StartDate Duration Purpose ProjectManager ProjectLead Telephone Email Address1 Address2 City State Zip LeadAgencyWebAddress DQOlevel ExternalFileName ProjectComments Finalized PublicRelease MLML RDC Project Registration Template Documentation revised 7/15/14 19 of 25

PROJECT TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION ParentProjectCode Text Yes 50 ParentProject Foreign key reference to ParentProject table Project Unique code referencing the ProjectCode* Text Yes 25 project ProjectName* Text Yes 50 Project Name of the Project ProjectDescr Text No 255 Description of the Project ProjectType1 Text No 20 Used in queries and forms to limit output to a subset of results ProjectType2 Text No 20 Used in queries and forms to limit output to a subset of results ProjectType3 Text No 20 Used in queries and forms to limit output to a subset of results ProjectCategory Text No 50 Category of Project; e.g. Ambient Monitoring, Bioassessment or Bioaccumulation QAPPName Text Yes 100 Name of the QAPP StartDate Date No 8 Date the Project was started Duration Text No 150 Duration of the Project Purpose Text No 255 Purpose of the Project ProjectManager Text No 100 Manager of the Project ProjectLead Text No 100 Lead person of the Project Telephone Text No 20 Phone number of the Project Lead Email address of the Project Email Text No 150 Lead Address1 Text No 255 Address of the Project Lead Address2 Text No 255 Address of the Project Lead City Text No 255 Full name of the nearest town, city, or community of the Project Lead State of the Project Lead; State Text No 2 from VariableCodes Zip Text No 10 Zip Code of the Project Lead LeadAgencyWebAddress Text No 255 Web site of the Lead Agency Agency associated with the ProjectLead; Foreign key reference to Agency AgencyCode Text No 20 table MLML RDC Project Registration Template Documentation revised 7/15/14 20 of 25

PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION DQOlevel Text No 255 Tiered usage level that project Data Quality Objectives fall under ExternalFileName Text No 255 Name of the External File associated with the project Comments related to the ProjectComments Text No 255 Project Finalized Boolean No 1 Used to indicate that a Project is finalized PublicRelease Boolean No 1 Used to restrict data from being migrated to the web; e.g. a "no" value signifies that data is not to be presented on the web MLML RDC Project Registration Template Documentation revised 7/15/14 21 of 25

QAPP Table PURPOSE: The QAPP table contains information about the QAPP. It is important to fill out as much information as possible. This table is only required for new QAPPs not within the database and can be submitted prior to collecting any field data. Utilize the QAPP list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: QAPPName None on this worksheet Not Required Columns: QAPPDescr QAPPComments QAPP TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION QAPPName* Text Yes 100 QAPP Name of the QAPP QAPPDescr Text No 255 Description of the QAPP QAPPComments Text No 255 Comments related to the QAPP MLML RDC Project Registration Template Documentation revised 7/15/14 22 of 25

Sampling Protocol Table PURPOSE: The sampling protocol table contains information about the sampling protocol. It is important to fill out as much information as possible. This table is only required for new sampling protocols not within the database and can be submitted prior to collecting any field data. Utilize the Protocol list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: ProtocolCode ProtocolName None on this worksheet Not Required Columns: ProtocolDescr ProtocolType1 ProtocolType2 ProtocolType3 SAMPLING PROTOCOL TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION ProtocolCode* Text Yes 20 Protocol Unique code referencing the Protocol which is a set of methods, methodology and/or specifications used ProtocolName* Text Yes 50 Protocol Name of the Protocol ProtocolDescr Text No 255 Description of the Protocol ProtocolType1 Text No 25 Used in queries and forms to limit output to a subset of results MLML RDC Project Registration Template Documentation revised 7/15/14 23 of 25

PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION ProtocolType2 Text No 25 Used in queries and forms to limit output to a subset of results ProtocolType3 Text No 25 Used in queries and forms to limit output to a subset of results MLML RDC Project Registration Template Documentation revised 7/15/14 24 of 25

CollectionDevice_FieldRes Table PURPOSE: The CollectionDevice_FieldRes table contains information about the collection device and associated analytes. It is important to fill out as much information as possible. This table is only required for new collection devices not within the database and can be submitted prior to collecting any field data. Utilize the CollectionDevice list and FieldResEquip list within MLML RDC's Controlled Vocabulary to view all current stations within the MLML RDC. Please see the above section for data submission steps. COLUMN REQUIREMENTS: Columns within the MLML RDC Project Registration Template tables are either considered 1) required, 2) desired or 3) not required. Required columns must be filled out in order for data to be accepted by the MLML RDC. Desired columns are strongly encouraged and should be filled in whenever possible. Not required columns include additional information that aid in data usability. Individual column requirements are listed below: Required Columns: Desired Columns: CollectionDeviceName AnalyteName Not Required Columns: CollectionDeviceDescr SerialNumber CollectionDeviceComments COLLECTIONDEVICE_FIELDRESLOOKUP TABLE STRUCTURE: * Primary Key, required for record uniqueness. PROJECT TEMPLATE HEADER TYPE REQUIRED SIZE LOOKUP LIST DEFINITION CollectionDeviceName* Text Yes 50 CollectionDevice Unique name of the CollectionDevice CollectionDeviceDescr Text No 255 Generic description of the Collecti on Device used for web display SerialNumber Text No 30 Serial number of the CollectionDevice CollectionDeviceComments Text No 255 Comments related to the CollectionDevice AnalyteName Text Desired 255 Analyte Foreign key reference to Analyte table MLML RDC Project Registration Template Documentation revised 7/15/14 25 of 25