EEGLE Data Policy

EEGLE Data Policy
last revised 12/21/97

The EEGLE Data Policy will follow the procedures set forth by the GLOBEC Data Policy and summarized by the CoOP Data Policy. Please read these data policies and follow their guidelines. Below are some preliminary thoughts about the EEGLE Data Policy.

Data Exchange and Dissemination:
- Following each cruise, the Chief Scientist will submit the Cruise Operations Log to the EEGLE Data Manager.
- Data/Measurements which do not involve lengthy analyses, will be submitted to the EEGLE Data Manager within 6 months after collection (end of cruise).
- All other measurements and results of analyses will be submitted to the EEGLE Data Manager within 1 year after collection.
- Data will be available to EEGLE PI's ONLY for 2 years after all data collection is complete (Fall, 2000).
- After 2 years, data will be publicly available (Fall, 2002).
- PI's must apply to the CoOP Steering Committee for exceptions.
Metadata:
Metadata (location, time, units, accuracy, precision, method of collection, method of analysis or processing, sensor calibration, name of analyst or operator, etc) must accompany each data submission.
Cruise Operations Log:
A Cruise Operations Log will be kept by the Chief Scientist of each cruise and will record all activities. Each activity (defined as "anything put over the side") will be a separate line in the log, and will contain the following:
1. Op Number, consisting of the following:
  1. Ship ID (S=Shenehon, L=Laurentian, G=Lake Guardian, N=Neeskay, C=Cyclops, U=USCG vessel, etc)
  2. Year (4 digits)
  3. Julian Day (3 digits). Julian Day 1 is Jan 1, 0000 GMT - 2359 GMT
  4. Daily Task Number (2 digits), starting at 01 each julian day
2. Sample Time (GMT)
3. Station ID
4. Lat (degrees and decimal minutes)
5. Lon (degrees and decimal minutes)
6. Activity (see possible Activity Codes below)
7. Name of PI associated with the task
8. Name or Initials of person making the entry (usually the Chief Scientist)
Examples of entries might be:
```
               Time                                                Entered
    OP#       (GMT)    STA      LAT       LON    Activity     PI       By
-------------------------------------------------------------------------
S1997273.01    1510    T26   42 58.99  86 14.20   TRP-D       Eadie   MBL
S1997273.02.1  1530    T26   42 58.99  86 14.20     CTD    Johengen    TJ
S1997273.02.2  1540    T26   42 58.99  86 14.20     CTD       Eadie   MBL
S1997273.03    1630    T26   42 58.99  86 14.20     WAT       Eadie   MBL
S1997273.04S   1730    M15   42 30.00  86 20.00     PSS Vanderploeg    JL
S1997273.04E   1930   M110   42 30.00  86 30.00     PSS Vanderploeg    JL
S1997274.01    0350    T26   42 58.99  86 14.20   TRP-R       Eadie   MBL
-------------------------------------------------------------------------
```
Each ship should have its own Cruise OP Log.
Following each cruise, the Cruise Operations Log will be submitted by the Chief Scientist to the Data Manager. The Data Manager will then make it available on the web and will generate a detailed map of activities for that cruise.
Notes for Cruise OP Logs:
1. Instrument Deployments and Retrievals (e.g., Sediment traps, current meters) should have different OP Nos (corresponding to the DOY). However, the data generated by the instrument should be associated with the Deployment Op No.
2. For continuous measurements (e.g., PSS, LV-TSM), record the start time/lat/lon upon start of tow as well as the end time/lat/lon upon completion of tow. They should have the same OP No., with an "S" appended for start of tow and a "E" for end of tow.
3. For multiple activities at station (eg attaching a thermistor to a current meter deployment), use different Op Nos or append an ".1",".2",etc to the single Op No.
4. Be careful not to overlap Op Nos. Each ship should have unique Op Nos corresponding to the DOY and task number. If the current task is not the first of the day, be sure to find out the Op No of the previous task. This can easily be accomplished by using a single Cruise Log for each ship, where each activity (and Op No) is listed on a line in the log.

Activity Codes:

The following is a partial/preliminary list of activity codes to be used in the Cruise Operations Log:

Activity Codes:

BS      (Benthic Sampler)                 PCB-AIR (PCB - air sample, continuous)
BSLED   (Benthic sled)                    PCB-WAT (PCB - water sample)
BL-SIS  (Benthic Layer - Surface Interface Sampler)
CM-D    (current meter - deployment)      PNET    (Vertical phytoplankton tow)
CM-R    (current meter - retrieval)       PSS     (Plankton Survey System, continuous)
CORE-B  (sediment core - box)             PSS-CTD (vertical PSS CTD)
CORE-G  (sediment core - gravity)         ROV     (ROV, continuous)
CORE-S  (sediment core - sectioned)       TH-D    (thermistor string - deployment)
CTD     (vertical CTD cast)               TH-R    (thermistor string - retrieval)
CTD-C   (horizontal CTD, continuous)      TRAWL   (bottom fish trawl - continuous)
CTD-PRO (vertical CTD-like Hyrolab in situ profiler)
CTD-PSS (vertical CTD using PSS)          TRAN-D  (transmissometer - deployment)
DRF-D   (drifter - deployment)            TRAN-R  (transmissometer - retrieval)
DRF-R   (drifter - retrieval)             TRI-D   (Tripod - deployment)
LI      (light or optics profile)         TRI-R   (Tripod - retrieval)
LT-D    (Lagrangian trap - deployment)    TRP-D   (sediment trap - deployment)
LT-R    (Lagrangian trap - retrieval)     TRP-R   (sediment trap - retrieval)
LV-TSM  (large volume TSM)                WAT     (water sample = Niskin)
SIZE-TSM (Particle size Profiler)         WAT-TOW (horizontal Water Sample - continuous)
PONAR   (Ponar grab)                      WS-D    (Water Sampler - deployment)
METB-D  (Met Buoy - Deployment)           WS-R    (Water Sampler - retrieval)
                                          ZNET    (vertical zooplankton net tow)
                                          ZNET-LIVE (vert. zoop. net tow - LIVE)

Station Log Sheets:
Station Log sheets could be used to document tasks, or group of tasks, performed while at station during the cruise. The Station Log sheet should contain one or more OP #s to help identify specific time and location of sample/deployment/tow. These sheets could be developed by the PI (more specific) or by the data manager (more generic). See example. If a station log sheet is used, a copy should be submitted to the Data manager following the cruise. The station log sheets should contain some or all of the following:
1. Cruise Operations Log Number (see OP # above)
2. Cruise Name. (see below)
3. Ship Name (Lake Guardian, Laurentian, Shenehon, etc)
4. Year/Julian Day. Julian Day 1 is Jan 1, 0000 GMT - 2359 GMT
5. Station ID
6. Lat/Lon
7. Site & Task Description
8. Sample Depth/ID
9. Time of Sample/Cast/Tow/Core. All times should by in GMT
Cruise Names:
Cruise names will consist of 3 parts. The first part will be 3 or 4 characters identifying the type of cruise (e.g. surv=Survey, proc=Process, lagr=Lagrangian, moor=Mooring, rov=ROV). The second part will be the 4-digit year. The third part will be the 3-digit day of year (DOY), corresponding to the 1st day of the cruise. Examples:
```
      surv-1998-068  =  Survey Cruise, March 9, 1998
      proc-1998-081  =  Process Cruise, March 22, 1998
      lagr-1998-094  =  Lagrangian Cruise, April 4, 1998
       rov-1998-121  =  ROV Cruise, May 1, 1998
```
Data Organization:
Data can be accessed via the EEGLE web site. The data will be organized as follows:
- By Data Type
- By Year
- By Cruise
- By Station
- By Project No.
Data Archival:
- World Wide Web
- Durable media (CD-ROM)
- NOAA archives (NODC, NGDC)

EEGLE Homepage

Greg Lang, EEGLE Web Manager, gregory.lang@noaa.gov

EEGLE Data Policylast revised 12/21/97

Data Exchange and Dissemination:

Metadata:

Cruise Operations Log:

Activity Codes:

Station Log Sheets:

Cruise Names:

Data Organization:

Data Archival:

EEGLE Data Policy
last revised 12/21/97