[Go-essp-tech] Publishing dataset with option --update

[Kettleborough, Jamie]

Hello,

Isn't one way of dealing with this is simply to publish the whole
dataset (old files and additional files) at a new version.  In fact I
thought that was the 'policy' - but I could have misunderstood.

Jamie 

> -----Original Message-----
> From: go-essp-tech-bounces at ucar.edu 
> [mailto:go-essp-tech-bounces at ucar.edu] On Behalf Of Serguei Nikonov
> Sent: 20 December 2011 17:12
> To: Drach, Bob
> Cc: go-essp-tech at ucar.edu
> Subject: [Go-essp-tech] Publishing dataset with option --update
> 
> Hi Bob,
> 
> I needed to add some missed variables to existing dataset and 
> I found in esgpublish command an option --update. When I 
> tried it I've got normal message like
> INFO       2011-12-20 11:21:00,893 Publishing: 
> cmip5.output1.NOAA-GFDL.GFDL-CM3.historical.mon.atmos.Amon.r1i
1p1, parent = pcmdi.GFDL
> INFO       2011-12-20 11:21:07,564   Result: PROCESSING
> INFO       2011-12-20 11:21:11,209   Result: PROCESSING
> ....
> 
> but nothing happened on gateway - new variables are not 
> there. The files corresponding to these variables are in 
> database and in THREDDS catalog but apparently were not 
> published on gateway.
> 
> I used command line
> esgpublish --update --keep-version --map <map_file> --project 
> cmip5 --noscan --publish.
> 
> Should map file be of some specific format to make it works 
> in mode I need?
> 
> Thanks,
> Sergey Nikonov
> GFDL
> 
> 
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>