<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
Gentle-people, <br>
<br>
This is what the catalogs are for.<br>
There is too much filesystem talk. The filesystem can only do so
much for us.<br>
There is semantic knowledge that is trying to be captured in a
relatively rigid tree structure.<br>
We must out 'outside of the box', I feel we are abusing the
filesystem and trying to do gymnastics with it that we don't need to
do. The answer is not with the filesystem. The answer is the
catalogs and using them appropriately. We need to stop hedging our
bets against the system we are building and actually use it to our
benefit (the reason why we made it). The filesystem is a red
herring.<br>
<br>
just my $0.02<br>
<br>
I should pull out the email I wrote in November of 2009 describing
the catalog as the needed lingua fraca of this endeavor.<br>
<br>
-Cassandra.<br>
<br>
On 9/19/11 9:00 AM, Kettleborough, Jamie wrote:
<blockquote
cite="mid:E51EDFEBF10BE44BB4BDAF5FC2F024B90FB7F6F5@EXXMAIL02.desktop.frd.metoffice.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19120">
<div dir="ltr" align="left"><span class="822044715-19092011"><font
color="#0000ff" face="Arial" size="2">Hello Karl, everyone,</font></span></div>
<br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255);
padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div><font face="Times New Roman">For replicating the latest
version, I agree that your alternate structure poses
difficulties (but it seems like there must be a way to
smartly determine whether the file you already have a file
and simply need to move it, rather than bring it over
again). </font><font color="#0000ff" face="Arial" size="2"><span
class="822044715-19092011"> </span></font></div>
<div><font color="#0000ff" face="Arial" size="2"><span
class="822044715-19092011"></span></font> </div>
</blockquote>
<div dir="ltr"><span class="822044715-19092011"><font face="Arial"><font
color="#0000ff" size="2">Doesn't every user (not just the
replication system) have this problem: they want to know
what files
<!--[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]-->have changed (or not changed) at a new
publication version. No one wants to be using band width
or storage space to fetch and store files they already
have. How is a user expected to know what has really
changed? Estani mentions check sums - OK, but I don't
think all nodes expose them (is this right?). You may try
to infer from modification dates (not sure, I haven't look
at them that closely). You may try to infer from the
TRACKING_ID - but I'm not sure how reliable this is (I can
imagine scenarios where different files share the same
TRACKING_ID - e.g. if they have been modified with an nco
tool).</font></font></span></div>
<div dir="ltr"><span class="822044715-19092011"></span> </div>
<div dir="ltr"><span class="822044715-19092011"><font
color="#0000ff" face="Arial" size="2">Is there a recommended
method for users to understand what *files* have actually
changed when a new publication version appears?</font></span></div>
<div dir="ltr"><span class="822044715-19092011"></span> </div>
<div dir="ltr"><span class="822044715-19092011"><font
color="#0000ff" face="Arial" size="2">Thanks,</font></span></div>
<div dir="ltr"><span class="822044715-19092011"></span> </div>
<div dir="ltr"><span class="822044715-19092011"><font
color="#0000ff" face="Arial" size="2">Jamie</font></span></div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gavin M. Bell
Lawrence Livermore National Labs
--
"Never mistake a clear view for a short distance."
-Paul Saffo
(GPG Key - <a class="moz-txt-link-freetext" href="http://rainbow.llnl.gov/dist/keys/gavin.asc">http://rainbow.llnl.gov/dist/keys/gavin.asc</a>)
A796 CE39 9C31 68A4 52A7 1F6B 66B7 B250 21D5 6D3E
</pre>
</body>
</html>