<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 92.4pt 72.0pt 92.4pt;}
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 lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>Hello Karl,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I think the following changes are what is needed –
I’m happy to put them into the document and circulate the result for
approval if you send me the latest version in word. I don't think this affects
what modelling groups are doing, since, if they archive in the DRS, everything
they archive will be in the 'full' section of the directory tree and it will be
up to the data node managers to create the 'requested' section.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><span style='background:yellow;mso-highlight:yellow'>In
section 2.1</span>: Modify the atomic dataset definition: <o:p></o:p></p>
<p class=MsoPlainText><i>The collection of data that is output from a single
model run and <o:p></o:p></i></p>
<p class=MsoPlainText><i>characterized by sharing a single activity, <u>activity
component</u>, institute, model, <o:p></o:p></i></p>
<p class=MsoPlainText><i>experiment/scenario, data frequency, modeling-realm,
variable name, <o:p></o:p></i></p>
<p class=MsoPlainText><i>local ensemble member, and version. <o:p></o:p></i></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>I’m not sure about the terminology “activity
component”, but it is reasonably descriptive.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>In the following paragraph, change `first six' to `first
seven' and add 'activity component' to the list. <o:p></o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><span style='background:yellow;mso-highlight:yellow'>In
section 2.2</span>: Insert an `activity component' definition after the
'activity' definition: <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Activity component <o:p></o:p></b></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>The DRS will distinguish between 'full' and 'requested'
atomic datasets. The 'full' component <o:p></o:p></p>
<p class=MsoPlainText>will contain all the data archived, while the 'requested'
component will contain only <o:p></o:p></p>
<p class=MsoPlainText>those sections of the data in the PCMDI CMIP5 data
request. The atomic datasets within <o:p></o:p></p>
<p class=MsoPlainText>the 'requested' component will thus either be subsets of
those 'full' component or identical <o:p></o:p></p>
<p class=MsoPlainText>to them when only the requested data is archived. <o:p></o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><span style='background:yellow;mso-highlight:yellow'>In
section 3.1</span>: insert `/<category>' after '/<activity>/', and
similar changes to <o:p></o:p></p>
<p class=MsoPlainText>other URLs in this section. <o:p></o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><span style='background:yellow;mso-highlight:yellow'>In
section 3.2</span>: as above.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><span style='background:yellow;mso-highlight:yellow'>Add
a new section 3.4:</span><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>3.4 Replication<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>A subset of the data will be replicated at PCMDI, BADC
and DKRZ. This subset will consist of a selection of complete atomic datasets
from the “requested” activity component.<o:p></o:p></p>
<div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;
padding:0cm 0cm 1.0pt 0cm'>
<p class=MsoPlainText style='border:none;padding:0cm'><o:p> </o:p></p>
</div>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Cheers,<o:p></o:p></p>
<p class=MsoPlainText>Martin<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>-----Original Message-----</span><o:p></o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>From: Pascoe, Stephen
(STFC,RAL,SSTD)</span><o:p></o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>Sent: 07 January 2010 12:05</span><o:p></o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>To: Juckes, Martin (STFC,RAL,SSTD);
Karl Taylor</span><o:p></o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>Cc: go-essp-tech@ucar.edu</span><o:p></o:p></p>
<p class=MsoPlainText>> <span lang=EN-US>Subject: Updating the DRS document</span><o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Hi Martin and Karl,<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> I am keen that the recent discussions on DRS aren't
forgotten in the<o:p></o:p></p>
<p class=MsoPlainText>> rush to implement. Therefore I would like to
see the DRS document<o:p></o:p></p>
<p class=MsoPlainText>> updated with the following:<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> 1. Product/Category Component.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> As agreed in the versioning telco<o:p></o:p></p>
<p class=MsoPlainText>> (http://proj.badc.rl.ac.uk/go-essp/wiki/CMIP5/Meetings/telco091208)
we<o:p></o:p></p>
<p class=MsoPlainText>> need an extra component in the DRS to distinguish
between requested<o:p></o:p></p>
<p class=MsoPlainText>> and unrequested atomic datasets. I think the
proposal was for a<o:p></o:p></p>
<p class=MsoPlainText>> category between Activity and Institute with a the
value "full" or<o:p></o:p></p>
<p class=MsoPlainText>> "requested". I like the term
"Product" for this component but I think<o:p></o:p></p>
<p class=MsoPlainText>> various names were discussed.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> 2. Hostname Component in URLs.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> I believe this needs to be replaced by a host
prefix, thus allowing<o:p></o:p></p>
<p class=MsoPlainText>> some site-specific path elements to preceed the
activity component.<o:p></o:p></p>
<p class=MsoPlainText>> Knowing how the datanode software is designed I
think it is too<o:p></o:p></p>
<p class=MsoPlainText>> restrictive to insist the first element after the
hostname is Activity<o:p></o:p></p>
<p class=MsoPlainText>> because in reality multiple services will be running
on a datanode.<o:p></o:p></p>
<p class=MsoPlainText>> One could keep the current scheme with virtual hosts
and redirects but<o:p></o:p></p>
<p class=MsoPlainText>> it seems unnecessary.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> 3. Section 3.3 Filenames.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> There is no version number in the filename
convention: Shouldn't there<o:p></o:p></p>
<p class=MsoPlainText>> be? A recent comment from Sylvia suggested the
ESG metadata display<o:p></o:p></p>
<p class=MsoPlainText>> will depend on this naming scheme so I would like to
see more detail<o:p></o:p></p>
<p class=MsoPlainText>> here. Is the temporal_subset element manditory
for all files in the<o:p></o:p></p>
<p class=MsoPlainText>> system?<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> I am happy to help with preparing a new draft if you
wish.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Thanks,<o:p></o:p></p>
<p class=MsoPlainText>> Stephen.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
</div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>