<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Many thanks Don,</p>
<p><br>
</p>
<p>I'm lucky enough to have the time now I'm 80% retired and have a strong interest in ships. I've even started contributing to the shipspotting site and am building a network of contacts around the world who are even more passionate about ships than I am.
This is the sort of work that nobody in their right mind would fund, but I find it fun and think has benefit to the community.</p>
<p><br>
</p>
<p>My strategy is to put effort into bringing the quality of the metadata in the ICES system through research using multiple internet sources to as high a standard as possible, including synchronising with the metadata in our server. When I get there, I should
have over 70% of the codes in the ICES system in which I have confidence in both the names and the attributes. Marilynn is also QCing the changes I suggest, including cross-checking periods of activity against data holdings.</p>
<p><br>
</p>
<p>I would hope that you would be able to trust this work and ingest the results into your system without needing a lot of resource. The remaining 30% are where the knotty problems and the need for resources lie, but I think that even if we sweep these under
the carpet we will have taken a massive step forward towards a coherent international resource. </p>
<p><br>
</p>
<p>Cheers, Roy.</p>
<p><br>
</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in the office. All vocabulary queries should be sent to enquiries@bodc.ac.uk. Please also use this e-mail
if your requirement is urgent.</p>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Donald W. Collins <donald.collins@noaa.gov><br>
<b>Sent:</b> 15 December 2015 20:17<br>
<b>To:</b> Lowry, Roy K.; platforms@mailman.nerc-liv.ac.uk; NODC.Services@noaa.gov<br>
<b>Subject:</b> Re: [Platforms] US Navy Pennants and Ship Names</font>
<div> </div>
</div>
<div>Hi, Roy, et al,<br>
See inline comments below...<br>
<br>
<div class="moz-cite-prefix">On 12/13/15 12:34 PM, Lowry, Roy K. wrote:<br>
</div>
<blockquote type="cite">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>Dear All,</p>
<p><br>
</p>
<p>I am currently in the process of adding attributes for several hundred US Navy Vessels into the ICES system as a part of the synchronisation of the ICES list with the C17 list in NVS. </p>
<p><br>
</p>
<p>This work has raised a couple of issues:</p>
<p><br>
</p>
<p>1) Pennants. US Navy practice is to only carry the numeric portion of the pennant on the hull but this is prefixed by an alphanumeric classification in all references to the pennant. For example, USS Nimitz has '68' painted on her hull, but has the classification
'CVN' to indicate that she is a nuclear-powered aircraft carrier. However, the syntax used for pennant references varies between sources. Wikipedia hyphenates the two parts, such as 'CVN-68', but what I would regard as more naval sources such as UK Admiralty
naval callsign lists and ship Facebook pages (e.g. <a href="https://www.facebook.com/cvn68" id="LPlnk19082"></a><a class="moz-txt-link-freetext" href="https://www.facebook.com/cvn68">https://www.facebook.com/cvn68</a>), use a space such as 'CVN 68'. I am currently
following the navies and standardising on spaces, but before I get too far down the path (I've put 30-40 into the system so far) does anybody have strong reasons for a hyphen to be included.<br>
</p>
<br>
</div>
</blockquote>
In addition to relatively authoritative self-managed sources (e.g., the USS Nimitz facebook page), I noticed that other 'authoritative sources', such as compendia published by Jane's (e.g., Jane's Fighting Ships), use a space as the separator not a hyphen.
I agree with your approach and would follow the convention established in more authoritative and curated sources than Wikipedia and not use a hyphen. I will alert you if I am able to find a US Navy source that says otherwise.<br>
<br>
<blockquote type="cite">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>2) Whoever set up the US Navy codes in ICES in the 1990s was fond of brevity and certainly didn't approve of writing out Christian names in full when these were a part of the ship name. For example the ship widely listed as Forrest Sherman is 'F. Sherman'.
This has been the cause of a significant number of alerts put on the ICES system by Frank Sejer. I am systematically working through ship class lists (e.g. Forrest Sherman destroyers) which makes this contradiction glaringly obvious. <span style="font-size:12pt">I
strongly feel that the names should be expanded to match the published class lists and am therefore putting name change proposals into the ICES system. I am also proposing removal of titles from names to the title attribute (e.g. USS Normandy to Normandy).
Does anybody disagree?</span></p>
<p><span style="font-size:12pt"><br>
</span></p>
</div>
</blockquote>
As noted, there was a now-abandoned practice in the late-1990s and early-2000s to insert 'USS' into the name field for US Navy vessels. I've been slowly updating these entries to separate USS from the Name. I agree with making this change and to making any
other necessary changes to update names as necessary. However, be advised that the staff time allocated in US NCEI (former NODC) for managing this information is minimal, so there will be delays in getting the US NCEI information to match ICES.<br>
Cheers, <br>
Don Collins
<blockquote type="cite">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><span style="font-size:12pt"></span></p>
<p><span style="font-size:12pt">Cheers, Roy.</span></p>
<p><br>
</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in the office. All vocabulary queries should be sent to
<a class="moz-txt-link-abbreviated" href="mailto:enquiries@bodc.ac.uk">enquiries@bodc.ac.uk</a>. Please also use this e-mail if your requirement is urgent.</p>
</div>
</div>
</div>
<hr>
<small>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</small>.
<hr>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre>_______________________________________________
Platforms mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Platforms@mailman.nerc-liv.ac.uk">Platforms@mailman.nerc-liv.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms">http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<hr>
<small>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</small>.
<hr>
</body>
</html>