---------- Forwarded message ----------
From: Paula S. Fratantoni <pfratant@mercury.wh.whoi.edu>
Date: Thu, Apr 7, 2011 at 9:26 AM
Subject: Re: automated submission
To: Jonathan Blythe <Jonathan.Blythe@noaa.gov>
Cc: Maureen Taylor <mtaylor@mercury.wh.whoi.edu>, James.Reagan@noaa.gov, Jon Hare <Jon.Hare@noaa.gov>


Hi Jonathan,

Thanks for getting back to me.

(1) Grabbing files from the existing ftp site in the existing format is 
certainly the easiest option for us.  This is the most up to date site 
for our processed data.  As cruises get processed and loaded into our 
oracle database, these ascii files are posted to that ftp-site.  Maureen 
has said that she will be able to routinely post a metadata file for the 
posted cruises similar to the one that she has provided to Jim for the 
subset of cruises that he is working with in WOD.

(2) My immediate concern is that all of the NEFSC survey data processed to 
date are submitted and publicly available through NODC.  I don't want 
lingering logistics having to do with an automated submission protocol to 
delay this process.  It certainly is easiest for us if you can simply grab 
the files that are there and compare with what is already in NODC to produce 
a complete and up to date dataset.  Is this what Jim is doing now?  Or is he 
only working with an earlier subset of the data?  What can we do to make this 
happen now?  Do we need to spool an up-to-date metadata file identifying the 
cruise name and gear type deployed for each station/survey in the database?

(3) In the future, I'm sure, with Maureen's help, that we can design a table 
of contents that can be used by NODC to routinely check for new files posted 
to the ftp site.

Thanks for you help,

Paula
