[Go-essp-tech] Publication, versioning and notification

[martin.juckes at stfc.ac.uk]

Hi,

I have the impression that we won't be able to avoid some confusion so long as we are dealing with an evolving archive. In practise, user A and B are likely to have tens of thousands of files, and may be dealing with data derived from the files by their colleagues or support staff rather than the original files. 

We will have a simpler situation when we tag a version of the archive as the static "IPCC_DDC" version. 

Is it possible to create other tagged versions? E.g. tag the archive on the 1st of each month (or quarter), and then make it possible for users to download data from the tagged version? This would make collaborative work easier: people from different institutes would be able to access a particular collection of files without worrying about intermediate updates. It would also make it possible for people giving presentations to communicate to the audience what version of the data they had used, whereas listing file versions or dataset versions is never going to work in an oral presentation.   I guess this would be a gateway issue rather than a publisher issue.

cheers,
Martin


-----Original Message-----
From: go-essp-tech-bounces at ucar.edu on behalf of Luca Cinquini
Sent: Fri 26/02/2010 13:47
To: Pascoe, Stephen (STFC,RAL,SSTD)
Cc: go-essp-tech at ucar.edu
Subject: Re: [Go-essp-tech] Publication, versioning and notification
 
Hi Stephen,
it's good to think of all possible scenarios...

It seems to me like in this case:
o) it would make more sense to change the propose notification system  
to operate on datasets, not single files
o) in any case, when the two users compare the plots for variable V1,  
the first thing they should do is exchange information about which  
file versions they are using - and they would find they have different  
versions. If instead they'd rather exchange information about dataset  
versions, they can do that too, and they would still find they are  
using different versions.

thanks, Luca

On Feb 26, 2010, at 4:50 AM, <stephen.pascoe at stfc.ac.uk> <stephen.pascoe at stfc.ac.uk 
 > wrote:

> Another issue with changing the publication granularity.
>
> Will users be notified about changes to files, atomic-datasets or  
> realm-datasets?  I think Gavin has said in the past that users will  
> be emailed when *files* change.  Consider the scenario:
>
>  1. A realm-dataset DS1 is published at version v1.
>  2. User A downloads variable V1 from DS1.
>  3. User B downloads all of DS1.
>  4. An error is found in variable V2 of DS1.
>  5. The files for V2 are replaced and DS1 is republished as version  
> v2.
>  6. User B is notified that some files have changed in DS1.
>  7. User A is *not* notified because he never downloaded the files  
> that changed.
>  8. User A & B collaborate discussing the data from DS1 v1.  THEY  
> HAVE DIFFERENT FILES!
>
> If this is how the system is supposed to work it's going to be very  
> confusing.
>
> S.
>
> ---
> Stephen Pascoe  +44 (0)1235 445980
> British Atmospheric Data Centre
> Rutherford Appleton Laboratory
>
>
> -- 
> Scanned by iCritical.
>
>
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech


-- 
Scanned by iCritical.