<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0cm; FONT-SIZE: 12pt; MARGIN-RIGHT: 0cm
}
P.MsoAcetate {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
LI.MsoAcetate {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
DIV.MsoAcetate {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.EmailStyle21 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
.MsoChpDefault {
FONT-SIZE: 10pt
}
DIV.WordSection1 {
}
</style>
<meta name="GENERATOR" content="MSHTML 9.00.8112.16476">
<style id="owaTempEditStyle"></style><style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body lang="EN-GB" vlink="purple" link="blue" ocsi="x">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: x-small" DanaPrelude="1">
<div>Hi Marilynn,</div>
<div> </div>
<div>It is quite clear that this is a classic case of 'multiple hull' syndrome, and as you have suggested to Mathieu the usual and safest solution would be to abandon 18CN with a 'multiple hull conflict' label and set up two new codes. This, of course, requires
all data coded 18CN to be recoded with one or other of the new codes.</div>
<div> </div>
<div>Mathieu is arguing that 18CN be allocated to Calanus II, with a new code set up for the original Calanus. This would require just the pre-1991 data to be recoded, which would seem like less work. However, the risk with this approach is that if 18CN has
been used for pre-1991 Calanus data or metadata by somebody outside the 'informed circle' of ICES, NODC and Mathieu then those references will be explicitly pointed at the wrong Calanus.
</div>
<div><font face="tahoma"></font> </div>
<div><font face="tahoma">Consequently, I would support your recommendation. That way, any 'wild' 18CN references will point at an entry that clearly describes the conflict and allow appropriate corrective action to be taken at any stage in the future.</font></div>
<div><font face="tahoma"></font> </div>
<div><font face="tahoma">Cheers, Roy.</font></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma"></font> </div>
<div style="DIRECTION: ltr" id="divRpF319619">
<hr tabindex="-1">
<font color="#000000" size="2" face="Tahoma"><b>From:</b> Accessions [accessions@ices.dk]<br>
<b>Sent:</b> 18 April 2013 17:17<br>
<b>To:</b> Lowry, Roy K.<br>
<b>Subject:</b> In case you want to join the discussion.... Canada - Calanus and Calanus II RE: Request for platform code description change<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Hi Roy,</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">In case you want to join the discussion, you should read the first emails.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Cheers,</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Marilynn</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt" lang="EN-US">From:</span></b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt" lang="EN-US"> Accessions
<br>
<b>Sent:</b> 18 April 2013 14:21<br>
<b>To:</b> 'Ouellet, Mathieu'<br>
<b>Cc:</b> 'Donald Collins - NOAA Federal'<br>
<b>Subject:</b> Canada - Calanus and Calanus II RE: Request for platform code description change</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Dear Mathieu and Don,</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Just when I thought we had resolved this conflict, I found data associated with the 18CN code for the old Calanus from 1967-1976.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">18CN has been on the ICES list at least since 1996 (probably 1993). 2006 is the date that the list went into the Platform program. In 1996, NOAA and ICES
were aligned, therefore I believe the change to Calanus II came in the years when ICES and NOAA parted company. Don, can you see in your system when the “Calanus” was changed to the Calanus II?</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">This needs to be resolved with a “multiple hull” code. I will designate 18CN as Multiple hulls and create new codes for Calanus and Calanus II which are
linked to the 18CN code.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Best regards,</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Marilynn</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt" lang="EN-US">From:</span></b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt" lang="EN-US"> Ouellet, Mathieu [<a href="mailto:Mathieu.Ouellet@dfo-mpo.gc.ca">mailto:Mathieu.Ouellet@dfo-mpo.gc.ca</a>]
<br>
<b>Sent:</b> 17 April 2013 20:16<br>
<b>To:</b> Accessions<br>
<b>Cc:</b> Donald Collins - NOAA Federal<br>
<b>Subject:</b> Request for platform code description change</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Hello</span> </p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Since my request is<i> not</i> for a<i> new</i> platform code, I did not use the only request form.</span>
</p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">I noticed that the code 18CN has been created in 2006 for a Canadian ship named "CALANUS". The name is incomplete and therefore ambiguous. The full ship name is "CALANUS II", could you please
update it ? It is a medium-sized vessel that is multi-taskable to fishery and oceanographic missions, as well as geological and hydrographic surveys, built in 1991.
</span><a href="http://www.marinfo.gc.ca/en/flotte/calanusii.asp" target="_blank"><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">http://www.marinfo.gc.ca/en/flotte/calanusii.asp</span></a><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">
</span></p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">The problem with the current name, "CALANUS", is that it is the name of a 15 m research vessel built in 1948. I don't think it is still used; it doesn't look in very good shape:
</span><a href="http://www.flickr.com/photos/24968234@N02/7593900356/lightbox/" target="_blank"><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">http://www.flickr.com/photos/24968234@N02/7593900356/lightbox/</span></a><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">
</span></p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Nevertheless we have historical data collected by the "first" CALANUS and more recent data collected by the CALANUS II and we need not confuse them.</span></p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Thanks</span>
</p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Best Regards</span>
</p>
<p><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Mathieu Ouellet</span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">613-990-8570</span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><a href="mailto:mathieu.ouellet@dfo-mpo.gc.ca">mathieu.ouellet@dfo-mpo.gc.ca</a></span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Gestion des données scientifiques intégrées | Integrated Science Data Management</span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Pêches et Océans | Fisheries and Oceans Canada</span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">12W091, 200 Kent Ottawa, ON K1A 0E6</span>
<br>
<span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Gouvernement du Canada | Government of Canada</span>
</p>
<div style="TEXT-ALIGN: center" class="MsoNormal" align="center">
<hr align="center" size="2" width="100%">
</div>
<p style="TEXT-ALIGN: center" class="MsoNormal" align="center"><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Denne mail er blevet scannet af
</span><a href="http://www.comendo.com" target="_blank"><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">http://www.comendo.com</span></a><span style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> og indeholder ikke virus!</span></p>
<div>
<div style="TEXT-ALIGN: center" class="MsoNormal" align="center">
<hr align="center" size="2" width="100%">
</div>
</div>
</div>
</div>
<script id="dstb-id" language="javascript">if(typeof(dstb)!= "undefined"){ dstb();}</script></div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt
from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.<br>
</font>
</body>
</html>