<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hello
Karl,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’d
just like to clarify a point about your step one: some modelling centres may
want to distribute output from CMIP5 experiments which cannot easily be made
CMOR2 compliant and therefore will not be in our CMIP5 archive – but they
the may nevertheless choose to use ESG software to publish this data (I’m
not sure of the ESG terminology here, but it would be a distinct archive). I
discussed this with Bryan yesterday, and he was adamant that “CMIP5 data”
should only refer to CMOR2 compliant data. My concern is that
if we don’t have a clear and comprehensible way of referring to “output
from CMIP5 experiments which is not CMOR2 compliant” it will be hard to
stop modellers from referring to their data as “CMIP5 data”. So, I
suggest calling this data “CMIP5 raw data”, and recommending that
if it is published through ESG it should be with a reduced DRS consisting of:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>CMIP5_raw/<institute>/<model>/<whatever
suits your local group>.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The
driver for this concern is the fact that the CMIP5 data request does not,
despite the extensive consultation, include all output for forcing of regional
models that some groups want. So, this additional output will (or is likely to
be) be produced and distributed by at least DKRZ and IPSL. There are two factors
which might block the preferred route of making it CMOR2 compliant: (1) justifying
the data transformation effort when it is not part of the WCRP request and (2)
getting the variables into tables so that creation of CMOR2 compliant data is possible.
<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If we
end up distributing raw model output within the IS-ENES project, would you
object to us calling it “CMIP5_raw”? <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Martin<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><b><font size=2
color=black face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext;font-weight:bold'>From:</span></font></b><font
size=2 color=black face=Tahoma><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:windowtext'>
go-essp-tech-bounces@ucar.edu [mailto:go-essp-tech-bounces@ucar.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Karl Taylor<br>
<b><span style='font-weight:bold'>Sent:</span></b> 15 March 2010 22:14<br>
<b><span style='font-weight:bold'>To:</span></b> go-essp-tech@ucar.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [Go-essp-tech]
Publication, versioning and notification<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>Dear all,<br>
<br>
I'll try here to summarize my understanding of how data will get published and
replicated as part of ESG. If my summary is accurate, there are a number
of items we'll need to address soon, which I'll come back to at the end of this
email.<br>
<br>
Consider the following simplified case:<br>
<br>
1. Model A produces precipitation and temperature data for a 100-year
simulation. This will be considered the entire "output".<br>
2. CMIP5 requests that only temperature data be archived, and this
temperature data then constitutes the entire "requested" model
output.<br>
3. The ESG federation has agreed that the last 20 years of temperature
data will be replicated at the archival gateways (PCMDI, BADC, DKRZ, ...).<br>
<br>
Thus, the "replicated" output is a subset of the
"requested" output, which is a subset of the
"output". Note that in what follows I assume there is no good
reason to separate "requested" from "output". The
"replicated" output, however, needs to be treated someone separately
because of the issues having to do with quality control, versioning and
replication.<br>
<br>
As I understand it, one possible route by which data will appear on ESG is as
follows:<br>
<br>
1. Modeling group A publishes all its "output" on an ESG
node. This requires writing the output files into directories,
determining which data will be part of the official replicated subset and which
will not, collecting files into ESG datasets, and assigning version numbers to
files and to datasets. <br>
<br>
1a) files are initially placed in directories following the DRS specifications,
without assigning a version number. Thus, they are placed directly in the
<ensemble member> directory. Here is the DRS directory
structure: ...../ </span></font><<i><span style='font-style:italic'>activity</span></i>>/<<i><span
style='font-style:italic'>product</span></i>>/<<i><span style='font-style:
italic'>institute</span></i>>/<<i><span style='font-style:italic'>model</span></i>>/<<i><span
style='font-style:italic'>experiment</span></i>>/<<i><span
style='font-style:italic'>frequency</span></i>>/<<i><span
style='font-style:italic'>modeling realm</span></i>>/<<i><span
style='font-style:italic'>variable name</span></i>>/<<i><span
style='font-style:italic'>ensemble member</span></i>>/<br>
1b) ESG decides whether any of the files are supposed to replace earlier
versions and assigns a version number to each file. It also moves any
replaced or withdrawn files down one level into directories named by the
version of the files they contain. Thus, both the latest versions of files and
directories containing earlier versions of the files will appear under <<i><span
style='font-style:italic'>ensemble member</span></i>>.<br>
1c) ESG decides whether any portion of the data in each file is included in the
officially called for replicated set. [The code has not yet been written
that can make this decision.] If it finds any data in the
"replicated" category, ESG creates a parallel directory (under the
"requested" directory as called for by the current DRS, but perhaps
this should be changed to "replicated"). ESG creates a link
from the new directory to the file itself under "output" (i.e., to
the file or files containing temperature data that falls within the specified
20-year period.<br>
1d) Assuming publication at the "realm" level, the ESG publisher is
executed on the "output" side of the directory tree, yielding a
single dataset containing all the temperature and precipitation data.
Note, that publication at the "realm" level means all variables from
a single realization of a simulation will be in the same ESG dataset.
[The different members of an ensemble will appear in separate ESG
datasets.] <br>
1e) The ESG publisher will then act on the "links" in the
"replicated" side of the directory tree, and publish a dataset
containing only temperature data from 20 years (plus perhaps any additional
years that might be included as part of the needed files). Thus, the
replicated data will be found either under the "replicated" dataset
or the original "output" dataset (along with additional data stored
there).<br>
<br>
2. Modeling group A sends all of its temperature data to PCMDI (because PCMDI
plans to archive as much of the requested data as it can). <br>
<br>
3. PCMDI publishes the data it receives, following a similar procedure as
in 1a-e above, but of course the realm dataset will only include temperature
data. The "replicated" dataset, on the other hand should be
identical to the one published by Modeling Group A on its own node.<br>
<br>
4. The data is sent to other archival gateways (e.g., BADC and DKRZ) who
might choose only to archive the "replicated" subset. They
might place their files directly in the "replicated" side of the
directory tree (and omit the "output" side of the tree). <br>
<br>
Questions:<br>
<br>
1. How we can make sure that the version numbers assigned by the
publishers at the different nodes/gateways are the same across the federation?<br>
<br>
2. Isn't there an easier way to do all of this?<br>
<br>
3. When a user looks for data, he is more likely to find what he needs by
searching "output" not "replicated" (since
"output" is more complete). In fact I'm not sure the typical
user will care what portion of the data has been replicated. What are the
advantages to the user of requiring that some defined subset of the data be
replicated. Is it in the DOI assignment?<br>
<br>
I've run out of time for now, but I think we still have envisioned how this is
going to work end to end. Also, the requirements of the
"search" capability and the "notification" service still
seem quite vague to me. It seems to me we need to get the specifications
down on paper soon.<br>
<br>
Best regards,<br>
Karl<br>
<br>
<br>
<br>
<br>
Hi Karl, <br>
this is a VERY good use case, and thinking about it can
really help clarify how the system will or should work, even for me. It might
be worth discussing this with the go-essp list just to make sure everybody is
on the same page. I'm cc'ing Eric too because he is working on wget scripts
right these days... <br>
<br>
That said, I think the use case is flawed, because, as it stands, it involves
partial replicas of datasets, a thing that we said we wouldn't support. To be
specific, the only way that the modeling center can only ship one file to PCMDI
is that the output stream is split into 2 datasets: "requested" and
"full" (or whatever), contrary to assumption 4) below. <br>
<br>
So, if we assume that the "full" dataset is composed of two files,
and the "requested" dataset of 1 file, the following happens: <br>
<br>
o The modeling center publishes the full dataset onto its data node and to the
PCMDI gateway <br>
o The "requested" dataset is replicated to PCMDI, and published to
the PCMDI datanode and the PCMDI gateway <br>
o The PCMDI gateway exposes both datasets in the search interface. The 2
datasets share all the same DRS facets (model, experiment, time frequency,...)
except perhaps a facet called "product" that has the two possible
values "Full CMIP5 output" and "Core CMIP5 output". To be
distinguishable, the two datasets must come with a name/description that
specify their time extent, and/or their product type. We could also harvest the
overall time information and display it, if it can be helpful. <br>
o So when users 1, 2, 3 below make a search, 2 results will be returned: by
inspecting the results descriptions, they will realize that all the original
data is available from the modeling center, and only a subset of it from PCMDI.
Depending on what they want, they will make their dataset selection, click a
button, and obtain a files listing which contains all the files for that
particular dataset. At this point they can still presumably deselect any files
they don't want (perhaps based on the total size displayed) before asking for a
wget script to be generated. <br>
<br>
In summary, I think the system fully supports this use case provided the two
datasets are identified as distinct at the time of publication. <br>
<br>
Also, let me add a few comments. This is a simple use case because there is
only one gateway serving two datanodes. In this case, the gateway knows exactly
which files are present at each data node. If the user (1, 2 or 3) was going to
select BOTH datasets in the search results and ask for the files, a single web
page would be presented that contains all the files from the two datasets.
Since some of the files share the same name, the gateway can either present two
options for download, or maybe make an authoritative decision and present one
only. <br>
<br>
More complicated is the case where the modeling center publishes the
"full" dataset to BADC (for example), and the "requested"
dataset is replicated to the PCMDI data node and published to the PCMDI
gateway. In this case, the PCMDI gateway knows about two datasets, but only the
files of its datanode, and similarly the BADC gateway knows about two datasets,
but only the files of the modeling center. In this scenario, it's very
important that the two datasets be accurately described so that the user can
make the proper selection, after which the listing of files is presented. If
the user were to select both datasets, he would be presented with two sets of
files, and two wget scripts to download them. Probably the worst that can
happen in this case is that if the user doesn't pay attention to the file
listing, he'll download the files twice. <br>
<br>
I hope this helps in understanding - Bob, Eric please speak up if you think I
got any of this wrong. <br>
<br>
thanks, Luca <br>
<br>
<br>
<br>
On Mar 6, 2010, at 11:31 AM, Karl Taylor wrote: <br>
<br>
Hi Bob and Luca, <br>
<br>
I'm trying to get a feel for what to expect from a user's perspective out of a
federated ESG, assuming only what software will be in place at the time of the
first release. Consider the following simple federated archive, involving
just two partners -- a modeling center hosting a data node and PCMDI hosting a
data node and a portal (i.e., a gateway). <br>
<br>
1. Suppose the archive is tiny and comprises only two files: one file
with precipitation data for years 1-100 of a single simulation, and the other
years 101-200 from the same simulations. <br>
<br>
2. Suppose the modeling center responsible for the simulation publishes
the data (years 1-200) on its node, and then sends a copy of only the 2nd file
(years 101-200) to PCMDI, which subsequently publishes it on the PCMDI node. <br>
<br>
3. The ESG portal at PCMDI knows about both nodes. <br>
<br>
4. Suppose that there is no special designation associated with any of
the data (e.g., we have not defined a "requested" or
"replicated" subset). <br>
<br>
I presume the gateway will see 2 different datasets. Could you please
tell me whether the gateway will be aware of all the information found in the
catalogs at both nodes, or only a subset of the information? (And will
the gateway have to retrieve this information from each node whenever it is
needed by a user, or will the gateway already have a copy?) In
particular will the gateway be able to access (locally?): <br>
a) the full list of files at each node? <br>
b) what time period the data covers in each node? <br>
<br>
Could you also tell me what information/scripts each of the following users
will receive from ESG that will allow him to get the data he wants? <br>
User 1: <br>
This user wants to download all precipitation data available in the
archive. How will he know he should download his data from the original
node, rather than from PCMDI? <br>
<br>
User 2: <br>
This user wants to download only years 1-100 of the data. How will he
know he should download his data from the original node, rather than from
PCMDI? <br>
<br>
'User 3: <br>
This user wants to download only years 101-200 of the data. How will he
know that he can get his data from either site? <br>
<br>
The answers to these questions may help guide us in setting priorities beyond
the first release. <br>
thanks, <br>
Karl <br>
<br>
On 26-Feb-10 5:47 AM, Luca Cinquini wrote: <o:p></o:p></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>Hi Stephen, <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>it's good to
think of all possible scenarios...<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>It seems to
me like in this case:<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>o) it would
make more sense to change the propose notification system to operate on
datasets, not single files<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>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.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>thanks, Luca<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>On Feb 26,
2010, at 4:50 AM, <<a href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>>
<<a href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>>
wrote:<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Another
issue with changing the publication granularity.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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:</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 1.
A realm-dataset DS1 is published at version v1.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 2.
User A downloads variable V1 from DS1.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 3.
User B downloads all of DS1.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 4.
An error is found in variable V2 of DS1.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 5.
The files for V2 are replaced and DS1 is republished as version v2.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 6.
User B is notified that some files have changed in DS1.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 7.
User A is *not* notified because he never downloaded the files that changed.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 8.
User A & B collaborate discussing the data from DS1 v1. THEY HAVE
DIFFERENT FILES!</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>If
this is how the system is supposed to work it's going to be very
confusing.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>S.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>---</span></font><o:p></o:p></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Stephen
Pascoe +44 (0)1235 445980</span></font><o:p></o:p></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>British
Atmospheric Data Centre</span></font><o:p></o:p></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Rutherford
Appleton Laboratory</span></font><o:p></o:p></p>
<div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 color=black face="Times New Roman"><span style='font-size:12.0pt'>--
<br>
Scanned by iCritical. <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'>_______________________________________________<br>
GO-ESSP-TECH mailing list<br>
<a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br>
<a href="http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<pre><font size=2 color=black face="Courier New"><span style='font-size:10.0pt'><o:p> </o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'><o:p> </o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'>_______________________________________________<o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'>GO-ESSP-TECH mailing list<o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
href="http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'> <o:p></o:p></span></font></pre>
<p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>