<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Times New Roman">Dear all,<br>
<br>
If we guard against "replicas" appearing in ESG that have a
different checksum from the original</font>, then the same QC
status should apply to all replicas and it shouldn't matter which
one we point to as having passed a given QC level. <br>
<br>
This seems to be another argument to add checksums to all datasets
as soon as we can. Once this happens, wouldn't that mean that the
current gateways are adequate?<br>
<br>
cheers,<br>
Karl<br>
<br>
On 11/10/11 7:15 AM, Bryan Lawrence wrote:
<blockquote cite="mid:201111101515.47919.bryan.lawrence@ncas.ac.uk"
type="cite">
<pre wrap="">
Martin has been quite vociferous (quite rightly) in personal email to me that as far as QC goes, the dataset which gets through QC2 will *not* be the original dataset - we have no control over the original dataset's permanence and/or immutability.
This raises some interesting issues about the role of ESGF ... and it's interaction with the data owner and the publication process which is governed by DKRZ as the Publisher (and in the future probably multiple publication processes and multiple Publishers). The correct analogy here, as I said on an earlier email today, is to consider the original dataset as a preprint, of a Published dataset (at QC level 3).
Incidentally, this disctinction might offer us a possible (distinct) future for two different types of gateways into ESGF: the Published datasets view (which makes pre-eminent the QC'd copy) and the published view (which makes pre-eminenent whatever someone sticks on a data node).
But meanwhile, I think we can live with what you proposed, as long as the QC status of the replicas is clearly visible - and the DOI points to a landing page that somehow prioritises those versions, which would be trivial if your page was organised in the same way (prioritising the replicants of QC level 3, then replicants of QC level 2, and then originals).
Cheers
Bryan
</pre>
<blockquote type="cite">
<pre wrap="">Hi Stephen,
On 11/10/2011 05:23 AM, <a class="moz-txt-link-abbreviated" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Eric,
Replicas are beginning to show up in CMIP5 and this is exposing some
gaps in what Gateway 1.x can do. I know you are reimplementing replica
support in Gateway 2.0 so I'd like to raise these issues now.
We need to be able to publish a replica to the same Gateway that hosts
the original. I can't imagine this being possible with Gateway 1.x since
the URL <a class="moz-txt-link-freetext" href="http://">http://</a><GATEWAY>/dataset/<dataset-id>.html only points to one
dataset on that Gateway. Either that page needs to link to the original
and all replicas for that dataset or we need separate URLs for each
replica/original, or both.
</pre>
</blockquote>
<pre wrap="">
The current direction for the implementation would be to have a 1 page
for the original dataset and have that page list where replicas are
located.
If there are use cases for the other options we should get those identified.
Thanks!
-Nate
</pre>
<blockquote type="cite">
<pre wrap="">
Is this part of your design for Gateway 2.0's replica support?
Thanks,
Stephen.
---
Stephen Pascoe +44 (0)1235 445980
Centre of Environmental Data Archival
STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK
--
Scanned by iCritical.
_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<pre wrap="">
--
Bryan Lawrence
University of Reading: Professor of Weather and Climate Computing.
National Centre for Atmospheric Science: Director of Models and Data.
STFC: Director of the Centre for Environmental Data Archival.
Ph: +44 118 3786507 or 1235 445012; Web:home.badc.rl.ac.uk/lawrence
_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
</body>
</html>