*****************************************************************
Journal for accession number:  0128138
Created on:                    2015-05-18 04:11:47 UTC
By:                            Automated Ingest Agent

Source: NOAA Office of Response and Restoration (OR&R)

Data were collected as part of the Natural Resources Damage Assessment
(NRDA) and were subject to a separate set of more formal protocols for data
collection, processing, and chain-of-custody than was the case for the
Response data.  NCDDC was selected to process the NRDA CTD data, using a
protocol that was agreed to by NOAA and BP (note: this was different in many
respects from the Response CTD processing protocol). Raw data and
configuration files were downloaded by NCDDC from a secure OR&R FTP server;
processed; and uploaded back to the OR&R server. OR&R (specifically, OR&R
contractors Sirius) submitted the data for archival by uploading to NODC's
anonymous FTP.

Some cruises were exclusively NRDA, and some cruises combined NRDA and
Response activities. In the latter case, there should already be an
accession that contains the Response data for that cruise. The decision was
made to create new, separate accessions to contain the NRDA data rather than
add the NRDA data to the existing Response accession, in order to ensure
that users could easily separate the two. The result will be that that there
may be two accessions for the same DWH cruise, one designated for Response
data and the other for NRDA data.

Actions: An automated process copied the data files into the data/0-data
directory of this accession. Sample locations were determined by extracting
information from the global header of each netCDF file. Other descriptive
information was automatically extracted from the data files and used to
characterize this accession.

Spreadsheets in Microsoft Excel format were converted to comma-separated-value
(CSV) text files.

about/
This directory contains files generated by NODC with ancillary information
about the data submission.

0128138_lonlat.txt -
  Contains bounding coordinates for data sample locations derived from
  netCDF files.

0128138_map.jpg -
  Map of bounding rectangle of sample data locations.

2012_06_01_WATER_CTD_Processing_Plan_LAsignature1-1_redacted3.pdf -
  A high-level overview of the CTD processing appproach.

NODC_CTD_Processing_SOPs_PROCESSING_EDITS.pdf -
  Standard Operating Procedure for CTD processing.

data/0-data/
This directory contains data transmitted to NODC's FTP server by OR&R. The data is arranged in a series of subdirectories as follows:

JackFitzCruise2Leg1/Bin_Averaged_Val/
  This subdirectory contains bin-averaged, validated data compiled into cruise-level netCDF files.

JackFitzCruise2Leg1/Raw_Originator_Files/
  This subdirectory contains the raw CTD data files.

JackFitzCruise2Leg1/Station_Level Processed_Unval
  This subdirectory contains station-level data files that result from Seabird CTD processing software, prior to being converted to netCDF and validated.

JackFitzCruise2Leg1/Station_Level Processed_Val
  This subdirectory contains validated, station-level data files in netCDF format.

data/1-data/
This directory contains files that were converted by NODC from their
originally submitted format under the 0-data/ directory to an archival
format.

*.csv - 
  Comma-separated-value (CSV) files that NODC converted from the Microsoft 
  Excel files in 0-data/. There may be one or more CSV files for each spreadsheet.