<!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="#ffffff" text="#000000">
<font face="Times New Roman">I agree with Stephen's last paragraph
below.<br>
<br>
Karl<br>
</font><br>
On 3/4/11 1:31 AM, <a class="moz-txt-link-abbreviated" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B52106A235@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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:0cm;
margin-bottom:.0001pt;
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;}
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.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Stephane and everyone,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal">> CMOR2 enforces model names to be
lowercase, so there should be no issue here, except if one
admits that avoiding the use of CMOR2 is a<o:p></o:p></p>
<p class="MsoNormal">> way to get more visibility by using an
uppercase model name<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">We have data from MOHC that has been through
CMOR2 with mixed-case model names in the metadata and file
names. Since MOHC did the processing I can't vouch
precisely for the method used (maybe Mark wishes to comment)
but as far as I know CMOR2 supports mixed-case model names.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Case sensitivity in DRS components has been a
tricky issue in the design of the whole system and we've
never really converged on a consistent approach. The DRS
document has always been very clear that model names are
mixed case, as a result drslib supports mixed-case model
names. The publisher, by contrast, has usually been
configured to use lower-case model names, however Bob and I
have agreed that publishers can configure mixed-case models
into the publisher configuration.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Other than the obvious bug of prefixing "model_"
to the name, I think the case sensitivity should be retained
from what ever is published. BADC datasets are consistently
named in mixed case in the THREDDS catalogs, filenames and
NetCDF metadata.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Stephen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">Stephen
Pascoe +44 (0)1235 445980<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">Centre of
Environmental Data Archival<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">STFC
Rutherford Appleton Laboratory, Harwell Oxford, Didcot
OX11 0QX, UK<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;" lang="EN-US">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;" lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a class="moz-txt-link-freetext" href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>] <b>On Behalf Of
</b>Stéphane Senesi<br>
<b>Sent:</b> 04 March 2011 08:01<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] error in "Model"
name(s)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Karl Taylor wrote, On 03/03/2011 18:10: <o:p></o:p></p>
<p class="MsoNormal">Thanks, Nate.<br>
<br>
One other item, which may already be ticketed, but wanted to
make sure:<br>
<br>
Except on the home gateway, the model names under search
category "Model" appear all in lower case with a prefix of
"model_". For example, on PCMDI's gateway, the model
published at BADC is listed as "model_hadgem2-es", but it
should appear just as it appears at the BADC gateway:
"HadGEM2-ES"<o:p></o:p></p>
<p class="MsoNormal"><br>
Hi, all<br>
<br>
CMOR2 enforces model names to be lowercase, so there should be
no issue here, except if one admits that avoiding the use of
CMOR2 is a way to get more visibility by using an uppercase
model name<br>
<br>
(Sorry if the same is said at <a moz-do-not-send="true"
href="https://vets.development.ucar.edu/jira/browse/GTWY-2058">
https://vets.development.ucar.edu/jira/browse/GTWY-2058</a>;
I do not have access to this site)<br>
<br>
Regards<br>
S<br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
thanks,<br>
Karl<br>
<br>
<br>
On 3/2/11 7:01 PM, Nathan Wilhelmi wrote: <o:p></o:p></p>
<p class="MsoNormal">Hi Karl,<br>
<br>
Thanks for the feedback, a couple of inline comments.<br>
<br>
On 03/02/2011 06:47 PM, Karl Taylor wrote: <o:p></o:p></p>
<p class="MsoNormal">Dear all,<br>
<br>
I hope that the following two items can be implemented soon:<br>
<br>
1. Users should be able to ask ESG to display only datasets
they have permission to download:<br>
<br>
Without this, a "CMIP5 commercial" user will have to subselect
(point and click on!) only the models they are allowed to
download, and they will have to consult an external table to
figure out which tables those are. If they don't do this,
when they go to download the files they will be asked if they
want to join the "CMIP5 research" group, and I don't want them
to do this if they are going to use the data for commercial
purposes. We're asking a lot of users to expect them to
jump through lots of hoops to honor the "terms of use".<o:p></o:p></p>
<p class="MsoNormal">I have added a JIRA ticket for this one: <a
moz-do-not-send="true"
href="https://vets.development.ucar.edu/jira/browse/GTWY-2182">
https://vets.development.ucar.edu/jira/browse/GTWY-2182</a><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
Similarly lots of CMIP5 data is already published (and visible
via ESG), but hasn't been released for download. Users who
want to download CMIP5 data will have to eliminate one by one
all the models that are not yet public before downloading, and
it is not obvious which models those are. This is a pain.<br>
<br>
2. I noticed that the institute information is lost when a
gateway harvests datasets from another gateway (at least it
doesn't appear in the "Search Categories"). If you look at
the institutes listed at BADC, you find MOHC, but the same
datasets listed at PCMDI or NASA JPL don't include the
institute information under "Search Categories".
<o:p></o:p></p>
<p class="MsoNormal">We already have this one logged here: <a
moz-do-not-send="true"
href="https://vets.development.ucar.edu/jira/browse/GTWY-2058">
https://vets.development.ucar.edu/jira/browse/GTWY-2058</a><br>
<br>
Thanks!<br>
<br>
-Nate<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
Best regards,<br>
Karl<br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><o:p> </o:p></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Stéphane Sénési<o:p></o:p></pre>
<pre>Ingénieur - équipe Assemblage du Système Terre<o:p></o:p></pre>
<pre>Centre National de Recherches Météorologiques<o:p></o:p></pre>
<pre>Groupe de Météorologie à Grande Echelle et Climat<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CNRM/GMGEC/ASTER<o:p></o:p></pre>
<pre>42 Av Coriolis<o:p></o:p></pre>
<pre>F-31057 Toulouse Cedex 1<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>+33.5.61.07.99.31 (Fax :....9610)<o:p></o:p></pre>
</div>
<br>
<p>-- <br>
Scanned by iCritical.
</p>
<br>
</blockquote>
</body>
</html>