From marilynn at ices.dk  Fri Dec  5 12:01:11 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Fri, 5 Dec 2008 13:01:11 +0100
Subject: [Platforms] Estonia Salme
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDB9@coral.ices.local>

Dear Platform Group, 
A request has come in for a code for the Estonian vessel Salme.

Suggested code: ESSA
<name>Salme</name> <callsign>ES2408</callsign> <platformclass>Fishing vessel</platformclass> <title>R/V</title> <IMO>7431337</IMO> <previousname>Neshamar</previousname> 
<notes>Built 1974 Port of registry: Roomassaare Previous names: After 1 Jan. 1974 named Dana Bank,  after 1 Jan. 1976 named Amasteinur, after 1 Jan. 1994 named Neshamar, after 1 Jan. 1999 named Salme</notes>

Lloyds information: www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=357981

This suggestion will need confirmation by NOAA.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081205/6fe3d82a/attachment.html 

From marilynn at ices.dk  Fri Dec  5 13:37:14 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Fri, 5 Dec 2008 14:37:14 +0100
Subject: [Platforms] Fram III
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDBC@coral.ices.local>

Dear Platform Group, 

A request has come in for a code for the UK vessel Fram III.

Suggested code:  74FU
<name>Fram III</name> <platformclass>fishing vessel</platformclass> <Pennant>BRD1</pennant> <commissioned>1990</commissioned> <notes>Small vessel chartered for FRS Marine Laboratory work in Lochs Shieldaig and Torridon'. RSS No. B11324; length 11.7m; gross tonnage 11.27</notes>

This suggestion will need confirmation by NOAA.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081205/71e17ced/attachment.html 

From rkl at bodc.ac.uk  Mon Dec  8 11:48:49 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Mon, 08 Dec 2008 11:48:49 +0000
Subject: [Platforms] Estonia Salme
Message-ID: <s93d09c7.073@wpo.nerc.ac.uk>

Hi Marilynn,

The platformclass (fishing vessel) and title (R/V) seem to contradict each other.  Is she actually a research vessel - which includes fishery research vessels or a ship that spends most of her time fishing commercially, but is sometimes chartered for research work?

Cheers, Roy. 

>>> Marilynn S?rensen <marilynn at ices.dk> 12/5/2008 12:01 pm >>>
Dear Platform Group, 
A request has come in for a code for the Estonian vessel Salme.

Suggested code: ESSA
<name>Salme</name> <callsign>ES2408</callsign> <platformclass>Fishing vessel</platformclass> <title>R/V</title> <IMO>7431337</IMO> <previousname>Neshamar</previousname> 
<notes>Built 1974 Port of registry: Roomassaare Previous names: After 1 Jan. 1974 named Dana Bank,  after 1 Jan. 1976 named Amasteinur, after 1 Jan. 1994 named Neshamar, after 1 Jan. 1999 named Salme</notes>

Lloyds information: www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=357981 

This suggestion will need confirmation by NOAA.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 




From marilynn at ices.dk  Wed Dec 10 17:27:30 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Wed, 10 Dec 2008 18:27:30 +0100
Subject: [Platforms] USA Katahdin
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDD9@coral.ices.local>

Dear Platform Group, 

A request has come in for a code for USA vessel Katahdin.

Suggested code: 33H0
<name>Katahdin</name> <callsign>WUY7620</callsign> <platformclass>fishing vessel</platformclass> <IMO> 8813881</IMO> <notes>built 1988, renamed to Misty Dawn, WOD code 9661</notes>

This suggestion will need confirmation by NOAA because of new code suggestion. Don, also note call sign change - found on http://e-ships.net/index/M13.shtml. 

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081210/e35e80e3/attachment.html 

From marilynn at ices.dk  Wed Dec 10 17:41:36 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Wed, 10 Dec 2008 18:41:36 +0100
Subject: [Platforms] USA Great Pacific
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDDA@coral.ices.local>

Dear Platform Group, 

A request has come in for a code for the USA vessel Great Pacific.

Suggested code: 324J
<name>Great Pacific</name> <flag>USA</flag> <callsign>WQZ2898</callsign> <platformclass>Fishing Vessel</platformclass> <IMO>7947506</IMO>  <notes>built 1979, WOD code 9658, MMSI 367 332000</notes>
Lloyds: http://www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=396327 - IMO absent in Lloyds

This suggestion has been agreed with NOAA.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081210/07a18dec/attachment.html 

From marilynn at ices.dk  Wed Dec 10 17:50:39 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Wed, 10 Dec 2008 18:50:39 +0100
Subject: [Platforms] USA Isabel S.
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDDB@coral.ices.local>

Dear Platform Group, 

A request has come in for a code for the USA vessel Isabel S.

Suggested code: 327N
<name>Isabel S.</name><platformclass>fishing vessel</platformclass>  <notes>WOD code 9665, 91 foot offshore fishing vessel based in New Bedford, MA</notes>

Link: http://www.crenvironmental.com/Isabel.htm

This suggestion has been agreed with NOAA.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081210/5c8cb0bc/attachment.html 

From marilynn at ices.dk  Wed Dec 10 17:57:42 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Wed, 10 Dec 2008 18:57:42 +0100
Subject: [Platforms] USA Nordic Pride
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDDC@coral.ices.local>

Dear Platform Group, 
A request has come in for a code for the USA vessel Nordic Pride.

Suggested code: 32YE
<name>Nordic Pride</name> <platformclass>fishing vessel</platformclass> <IMO>8719554</IMO> <notes>WOD code 9666, Built 1987, Length overall 31m</notes>

Lloyds: http://www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=269080

This suggestion will need confirmation by NOAA because of added information.

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081210/9fe37b93/attachment.html 

From rkl at bodc.ac.uk  Thu Dec 11 08:07:26 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Thu, 11 Dec 2008 08:07:26 +0000
Subject: [Platforms] USA Katahdin
Message-ID: <s940ca64.035@wpo.nerc.ac.uk>

Hi Marilynn/Don,

It would be extremely helpful to have an approximate date when she was renamed to Misty Dawn.

Cheers, Roy.

>>> Marilynn S?rensen <marilynn at ices.dk> 12/10/2008 5:27 pm >>>
Dear Platform Group, 

A request has come in for a code for USA vessel Katahdin.

Suggested code: 33H0
<name>Katahdin</name> <callsign>WUY7620</callsign> <platformclass>fishing vessel</platformclass> <IMO> 8813881</IMO> <notes>built 1988, renamed to Misty Dawn, WOD code 9661</notes>

This suggestion will need confirmation by NOAA because of new code suggestion. Don, also note call sign change - found on http://e-ships.net/index/M13.shtml. 

Cheers,
Marilynn
---------------------------------------------------------- 
Marilynn S?rensen 
Data Manager 
International Council for the Exploration of the Sea 
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
Denmark 
Direct tel: +45 33 38 67 20 




From NeilH at ices.dk  Mon Dec  8 13:56:37 2008
From: NeilH at ices.dk (Neil Holdsworth)
Date: Mon, 8 Dec 2008 14:56:37 +0100
Subject: [Platforms] Platform code requests (Ship codes) - improving the
	process
Message-ID: <4BA05716CBB9C24C911E746FE1A3B1279E0A80@coral.ices.local>

Dear platform group,

 

There are a number of shortcomings with the current platform code assignment process, some of these are technical in nature and some are related to workflow processes and traceability of actions. The ICES Data Centre has been investigating ways in which we can improve the situation, both for you as users of the platform code process and for us as administrators of the platform codes.

 

Attached is a new web application and database that we intend to build and implement at the beginning of 2009. The purpose of the new system is:

-          Place the whole workflow process (from request, to acceptance, to assigment) on the web

-          Allow management and administration to take place in one application

-          Allow all ship requests/amendments to be handled in a standard way, in one place

-          Give users an online report of status on requests as well as views of all the history behind a specific platform code or request

-          Give users more power to update requests with additional information

-          Capture all communication and amendments in an automated audit trail through the application

-          Expolit web services etc. to automate request updates

 

The ICES Data Centre would ask that you take a look at the attached document and return with comments to Lee Martin <mailto:lmartin at ices.dk>  by Friday 19th December. After this point we will be building and testing this application with a view to launching it in early 2009. It is important that you are aware of this development as it will mean in the future we only accept platform requests through this process and according to the minumum criteria as described in the document. 

 

We hope this initiative will lead to a better management of platform codes and a clear management process for all involved. Thank you and we look forward to hearing from you.

 

Neil.

 

Neil Holdsworth
Head of Data Centre
International Council for the Exploration of the Sea 

Email: neil at ices.dk <mailto:neil at ices.dk> 

Web: www.ices.dk <http://www.ices.dk/> 

Tel: +45 3338 6718 

Fax: +45 3393 4215

H.C. Andersens Boulevard 44-46
1553 Copenhagen V. Denmark

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081208/53f10061/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Requests Database Utility - Requirements Specification (Phase	1 only) Final.doc
Type: application/msword
Size: 543232 bytes
Desc: Requests Database Utility - Requirements Specification
	(Phase 1 only) Final.doc
Url : http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081208/53f10061/attachment-0001.doc 

From marilynn at ices.dk  Mon Dec 15 11:52:54 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Mon, 15 Dec 2008 12:52:54 +0100
Subject: [Platforms] Platform code requests (Ship codes) - improving
	theprocess
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BDEF@coral.ices.local>

Dear platform group,

There are a number of shortcomings with the current platform code assignment process, some of these are technical in nature and some are related to workflow processes and traceability of actions. The ICES Data Centre has been investigating ways in which we can improve the situation, both for you as users of the platform code process and for us as administrators of the platform codes.

 

We intend to build and implement a new web application and database at the beginning of 2009. The purpose of the new system is:

-          Place the whole workflow process (from request, to acceptance, to assigment) on the web

-          Allow management and administration to take place in one application

-          Allow all ship requests/amendments to be handled in a standard way, in one place

-          Give users an online report of status on requests as well as views of all the history behind a specific platform code or request

-          Give users more power to update requests with additional information

-          Capture all communication and amendments in an automated audit trail through the application

-          Expolit web services etc. to automate request updates

 

The ICES Data Centre would ask that you take a look at the document at http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20(Phase%201%20only)%20Final.doc <http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20(Phase%201%20only)%20Final.doc>   and return with comments to Lee Martin <mailto:lmartin at ices.dk>  by Friday 19th December. After this point we will be building and testing this application with a view to launching it in early 2009. It is important that you are aware of this development as it will mean in the future we only accept platform requests through this process and according to the minumum criteria as described in the document. 

 

We hope this initiative will lead to a better management of platform codes and a clear management process for all involved. Thank you and we look forward to hearing from you.

 

Neil.

 

Neil Holdsworth
Head of Data Centre
International Council for the Exploration of the Sea 

Email: neil at ices.dk <mailto:neil at ices.dk> 

Web: www.ices.dk <http://www.ices.dk/> 

Tel: +45 3338 6718 

Fax: +45 3393 4215

H.C. Andersens Boulevard 44-46
1553 Copenhagen V. Denmark

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081215/6417249e/attachment.html 

From Donald.Collins at noaa.gov  Tue Dec 16 18:31:37 2008
From: Donald.Collins at noaa.gov (Donald Collins)
Date: Tue, 16 Dec 2008 13:31:37 -0500
Subject: [Platforms] Estonia Salme
In-Reply-To: <4BA05716CBB9C24C911E746FE1A3B12708BDB9@coral.ices.local>
References: <4BA05716CBB9C24C911E746FE1A3B12708BDB9@coral.ices.local>
Message-ID: <4947F409.4010108@noaa.gov>

All,
NOAA confirms platform code ESSA for the Estonian vessel Salme.
Cheers,
Don

Marilynn S?rensen wrote:
> Dear Platform Group,
> A request has come in for a code for the Estonian vessel Salme.
> 
> Suggested code:*** ESSA*
> <name>Salme</name> <callsign>ES2408</callsign> <platformclass>Fishing 
> vessel</platformclass> <title>R/V</title> <IMO>7431337</IMO> 
> <previousname>Neshamar</previousname>
> 
> <notes>Built 1974 Port of registry: Roomassaare Previous names: After 1 
> Jan. 1974 named Dana Bank,  after 1 Jan. 1976 named Amasteinur, after 1 
> Jan. 1994 named Neshamar, after 1 Jan. 1999 named Salme</notes>
> 
> Lloyds information: 
> ___www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=357981_ 
> <file://www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=357981>
> 
> This suggestion will need confirmation by NOAA.
> 
> Cheers,
> Marilynn
> ----------------------------------------------------------
> Marilynn S?rensen
> Data Manager
> International Council for the Exploration of the Sea
> H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
> Denmark
> Direct tel: +45 33 38 67 20
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Platforms mailing list
> Platforms at mailman.nerc-liv.ac.uk
> http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

-- 
Donald W. Collins
Oceanographer
National Oceanographic Data Center
NOAA/NESDIS/NODC E/OC1
SSMC3 Fourth Floor
1315 East West Highway
Silver Spring MD 20910-3282
Donald.Collins at noaa.gov
http://www.nodc.noaa.gov
Telephone: 301.713.3272 xtn 154
Fax: 301.713.3302


From Donald.Collins at noaa.gov  Tue Dec 16 18:38:49 2008
From: Donald.Collins at noaa.gov (Donald Collins)
Date: Tue, 16 Dec 2008 13:38:49 -0500
Subject: [Platforms] Fram III
In-Reply-To: <4BA05716CBB9C24C911E746FE1A3B12708BDBC@coral.ices.local>
References: <4BA05716CBB9C24C911E746FE1A3B12708BDBC@coral.ices.local>
Message-ID: <4947F5B9.4040601@noaa.gov>

All,
NOAA confirms platform code 74FU for the UK vessel Fram III.
Cheers,
Don

Marilynn S?rensen wrote:
> Dear Platform Group,
> 
> A request has come in for a code for the* UK* vessel*** Fram III*.
> 
> Suggested code:***  74FU*
> <name>***Fram III*</name> <platformclass>fishing vessel</platformclass> 
> <Pennant>BRD1</pennant> <commissioned>1990</commissioned> <notes>Small 
> vessel chartered for FRS Marine Laboratory work in Lochs Shieldaig and 
> Torridon'. RSS No. B11324; length 11.7m; gross tonnage 11.27</notes>
> 
> This suggestion will need confirmation by NOAA.
> 
> Cheers,
> Marilynn
> ----------------------------------------------------------
> Marilynn S?rensen
> Data Manager
> International Council for the Exploration of the Sea
> H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
> Denmark
> Direct tel: +45 33 38 67 20
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Platforms mailing list
> Platforms at mailman.nerc-liv.ac.uk
> http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

-- 
Donald W. Collins
Oceanographer
National Oceanographic Data Center
NOAA/NESDIS/NODC E/OC1
SSMC3 Fourth Floor
1315 East West Highway
Silver Spring MD 20910-3282
Donald.Collins at noaa.gov
http://www.nodc.noaa.gov
Telephone: 301.713.3272 xtn 154
Fax: 301.713.3302


From Donald.Collins at noaa.gov  Tue Dec 16 20:42:09 2008
From: Donald.Collins at noaa.gov (Donald Collins)
Date: Tue, 16 Dec 2008 15:42:09 -0500
Subject: [Platforms] USA Katahdin
In-Reply-To: <s940ca64.035@wpo.nerc.ac.uk>
References: <s940ca64.035@wpo.nerc.ac.uk>
Message-ID: <494812A1.5000808@noaa.gov>


Roy Lowry wrote:
> Hi Marilynn/Don,
> 
> It would be extremely helpful to have an approximate date when she was renamed to Misty Dawn.

It appears that 'Katahdin' may have been renamed to 'Misty Dawn' ca. Dec 
2005 (see 
http://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=2770596)

> 
> Cheers, Roy.
> 
>>>> Marilynn S?rensen <marilynn at ices.dk> 12/10/2008 5:27 pm >>>
> Dear Platform Group, 
> 
> A request has come in for a code for USA vessel Katahdin.
> 
> Suggested code: 33H0
NODC platform code 33HO is currently in use for 'HORIZON ENTERPRISE':

<name>HORIZON ENTERPRISE</name>
<callsign>KRGB</callsign>
<platformclass>ship</platformclass>
<IMO>7617905</IMO>
<previousname>SEA-LAND ENTERPRISE</previousname>
<notes>WOD code 8880; SEAS participating vessel; hull number 4651; built 
1980 by Bethlehem Steel Corp.; see 
http://www.st.nmfs.noaa.gov/pls/webpls/cgv_pkg.vessel_id_list?vessel_id_in=623168</notes>

------------

Now, back to 'Katahdin'...

New suggested code: 323I
<name>Katahdin</name>
<callsign>WUY7620</callsign>
<platformclass>fishing vessel</platformclass>
<IMO> 8813881</IMO>
<notes>WOD code 9661; built 1988 by Duckworth Steel Boats, Inc., Tarpon 
Springs FL; 199 tons; renamed to 'Misty Dawn' by December 2005; see 
http://e-ships.net/index/M13.shtml</notes>

> <name>Katahdin</name> <callsign>WUY7620</callsign> <platformclass>fishing vessel</platformclass> <IMO> 8813881</IMO> <notes>built 1988, renamed to Misty Dawn possibly in December 2005, WOD code 9661</notes>
> 
> This suggestion will need confirmation by NOAA because of new code suggestion. Don, also note call sign change - found on http://e-ships.net/index/M13.shtml. 
> 
Sorry for the digression, but I hope this will help us reconcile our 
respective tables. Thanks,
Don

> Cheers,
> Marilynn
> ---------------------------------------------------------- 
> Marilynn S?rensen 
> Data Manager 
> International Council for the Exploration of the Sea 
> H.C. Andersens Boulevard 44-46, 1553 Copenhagen V. 
> Denmark 
> Direct tel: +45 33 38 67 20 
> 
> 
> 
> _______________________________________________
> Platforms mailing list
> Platforms at mailman.nerc-liv.ac.uk
> http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

-- 
Donald W. Collins
Oceanographer
National Oceanographic Data Center
NOAA/NESDIS/NODC E/OC1
SSMC3 Fourth Floor
1315 East West Highway
Silver Spring MD 20910-3282
Donald.Collins at noaa.gov
http://www.nodc.noaa.gov
Telephone: 301.713.3272 xtn 154
Fax: 301.713.3302


From accessions at ices.dk  Wed Dec 17 11:09:10 2008
From: accessions at ices.dk (Accessions)
Date: Wed, 17 Dec 2008 12:09:10 +0100
Subject: [Platforms] USA Katahdin
In-Reply-To: <494812A1.5000808@noaa.gov>
References: <s940ca64.035@wpo.nerc.ac.uk> <494812A1.5000808@noaa.gov>
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BE07@coral.ices.local>

Hi Don and Platform group,

I am not convinced that we are talking about the same vessel so we need more information.

Don, could you check the owner of the Katahdin/Misty Dawn. In the supplied link, the Misty Dawn has a different call sign  (WDC8124) than the Katahdin (WUY7620).

33H0 (33H zero) was suggested for the Katahdin, not 33HO (letter O). 

Cheers,
Marilynn

-----Original Message-----
From: platforms-bounces at biwebs1.nerc-liv.ac.uk [mailto:platforms-bounces at biwebs1.nerc-liv.ac.uk] On Behalf Of Donald Collins
Sent: 16 December 2008 21:42
To: platforms at biwebs1.nerc-liv.ac.uk
Subject: Re: [Platforms] USA Katahdin


Roy Lowry wrote:
> Hi Marilynn/Don,
> 
> It would be extremely helpful to have an approximate date when she was renamed to Misty Dawn.

It appears that 'Katahdin' may have been renamed to 'Misty Dawn' ca. Dec
2005 (see
http://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=2770596)

> 
> Cheers, Roy.
> 
>>>> Marilynn S?rensen <marilynn at ices.dk> 12/10/2008 5:27 pm >>>
> Dear Platform Group,
> 
> A request has come in for a code for USA vessel Katahdin.
> 
> Suggested code: 33H0
NODC platform code 33HO is currently in use for 'HORIZON ENTERPRISE':

<name>HORIZON ENTERPRISE</name>
<callsign>KRGB</callsign>
<platformclass>ship</platformclass>
<IMO>7617905</IMO>
<previousname>SEA-LAND ENTERPRISE</previousname> <notes>WOD code 8880; SEAS participating vessel; hull number 4651; built 1980 by Bethlehem Steel Corp.; see http://www.st.nmfs.noaa.gov/pls/webpls/cgv_pkg.vessel_id_list?vessel_id_in=623168</notes>

------------

Now, back to 'Katahdin'...

New suggested code: 323I
<name>Katahdin</name>
<callsign>WUY7620</callsign>
<platformclass>fishing vessel</platformclass> <IMO> 8813881</IMO> <notes>WOD code 9661; built 1988 by Duckworth Steel Boats, Inc., Tarpon Springs FL; 199 tons; renamed to 'Misty Dawn' by December 2005; see http://e-ships.net/index/M13.shtml</notes>

> <name>Katahdin</name> <callsign>WUY7620</callsign> 
> <platformclass>fishing vessel</platformclass> <IMO> 8813881</IMO> 
> <notes>built 1988, renamed to Misty Dawn possibly in December 2005, 
> WOD code 9661</notes>
> 
> This suggestion will need confirmation by NOAA because of new code suggestion. Don, also note call sign change - found on http://e-ships.net/index/M13.shtml. 
> 
Sorry for the digression, but I hope this will help us reconcile our respective tables. Thanks, Don

> Cheers,
> Marilynn
> ----------------------------------------------------------
> Marilynn S?rensen
> Data Manager
> International Council for the Exploration of the Sea H.C. Andersens 
> Boulevard 44-46, 1553 Copenhagen V.
> Denmark
> Direct tel: +45 33 38 67 20
> 
> 
> 
> _______________________________________________
> Platforms mailing list
> Platforms at mailman.nerc-liv.ac.uk
> http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

--
Donald W. Collins
Oceanographer
National Oceanographic Data Center
NOAA/NESDIS/NODC E/OC1
SSMC3 Fourth Floor
1315 East West Highway
Silver Spring MD 20910-3282
Donald.Collins at noaa.gov
http://www.nodc.noaa.gov
Telephone: 301.713.3272 xtn 154
Fax: 301.713.3302

_______________________________________________
Platforms mailing list
Platforms at mailman.nerc-liv.ac.uk
http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

****************************************************************************
Denne mail er blevet scannet af http://www.virus112.com
****************************************************************************


From marilynn at ices.dk  Wed Dec 17 11:17:45 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Wed, 17 Dec 2008 12:17:45 +0100
Subject: [Platforms] US HORIZON ENTERPRISE
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BE08@coral.ices.local>

Hi Platform group,

For alignment with NODC, ICES suggests adding the US vessel HORIZON ENTERPRISE.

Suggested code: 33HO (letter O) 

<name>HORIZON ENTERPRISE</name>
<callsign>KRGB</callsign>
<platformclass>ship</platformclass>
<IMO>7617905</IMO>
<notes>WOD code 8880; SEAS participating vessel; hull number 4651; built 1980 by Bethlehem Steel Corp.;Previous names: Austral Puritan 3 Nov.1980-27July 1983, American Puritan 12 Dec.1983-3 April 1987, Sea-Land Enterprise 15 Dec. 1987-25 April 2000, CSX Enterprise 26 April 2000-13 April 2003, Horizon Enterprise 14 April 2003 to present Dec.2008 </notes>

Lloyds link:http://www.lloydsmiu.com/lmiu/vessels/overview.htm?vesselID=134563

http://www.st.nmfs.noaa.gov/pls/webpls/cgv_pkg.vessel_id_list?vessel_id_in=623168

Comment: Lloyds says name before "Horizon Enterprise" was "CSX Enterprise"

Cheers,
Marilynn

----------------------------------------------------------
Marilynn S?rensen
Data Manager
International Council for the Exploration of the Sea
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
Denmark

Direct tel: +45 33 38 67 20 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081217/a67b3812/attachment.html 

From rkl at bodc.ac.uk  Thu Dec 18 19:47:51 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Thu, 18 Dec 2008 19:47:51 +0000
Subject: [Platforms] Platform code requests (Ship codes) -	improving the
	process
Message-ID: <s94aa90f.049@wpo.nerc.ac.uk>

Hi Neil/Marilynn/Lee,

I've read through your proposal and am very favourably impressed - you seem to have all the bases covered and I am convinced that what you propose will work and work well.  

I had one thought - whether or not to formalise a metdata element specifying size (e.g. length, which is frequently in the 'notes' section) but in the course of typing this e-mail talked myself out of it because:

1) This is heading down a slippery slope towards developing the 'ship codes' into a ship database.
2) This would raise the issue of having another code for RRS Discovery pre and post her refit in 1991 when she grew by 16m, which I don't think is a good idea.

Had you had any internal discussions in ICES on this or any other changes to the metadata held on each code?

Cheers, Roy.

>>> "Neil Holdsworth" <NeilH at ices.dk> 12/8/2008 1:56 pm >>>
Dear platform group,

 

There are a number of shortcomings with the current platform code assignment process, some of these are technical in nature and some are related to workflow processes and traceability of actions. The ICES Data Centre has been investigating ways in which we can improve the situation, both for you as users of the platform code process and for us as administrators of the platform codes.

 

Attached is a new web application and database that we intend to build and implement at the beginning of 2009. The purpose of the new system is:

-          Place the whole workflow process (from request, to acceptance, to assigment) on the web

-          Allow management and administration to take place in one application

-          Allow all ship requests/amendments to be handled in a standard way, in one place

-          Give users an online report of status on requests as well as views of all the history behind a specific platform code or request

-          Give users more power to update requests with additional information

-          Capture all communication and amendments in an automated audit trail through the application

-          Expolit web services etc. to automate request updates

 

The ICES Data Centre would ask that you take a look at the attached document and return with comments to Lee Martin <mailto:lmartin at ices.dk>  by Friday 19th December. After this point we will be building and testing this application with a view to launching it in early 2009. It is important that you are aware of this development as it will mean in the future we only accept platform requests through this process and according to the minumum criteria as described in the document. 

 

We hope this initiative will lead to a better management of platform codes and a clear management process for all involved. Thank you and we look forward to hearing from you.

 

Neil.

 

Neil Holdsworth
Head of Data Centre
International Council for the Exploration of the Sea 

Email: neil at ices.dk <mailto:neil at ices.dk> 

Web: www.ices.dk <http://www.ices.dk/> 

Tel: +45 3338 6718 

Fax: +45 3393 4215

H.C. Andersens Boulevard 44-46
1553 Copenhagen V. Denmark

 




From Michele.Fichaut at ifremer.fr  Fri Dec 19 09:20:05 2008
From: Michele.Fichaut at ifremer.fr (Michele FICHAUT)
Date: Fri, 19 Dec 2008 10:20:05 +0100
Subject: [Platforms] Platform code requests (Ship codes) -
	improving	theprocess
In-Reply-To: <4BA05716CBB9C24C911E746FE1A3B12708BDEF@coral.ices.local>
References: <4BA05716CBB9C24C911E746FE1A3B12708BDEF@coral.ices.local>
Message-ID: <494B6745.1020600@ifremer.fr>

Dear Marilynn and others,

I've read your document on Platform requests database, and I think  it 
will be a very useful
tool for those managing ship codes.
I am currently working on the French ships and I find very important to 
keep the address of websites where
a ship description is available; there can be several web sites per ship.
 Do you think these web addressesshould be kept in the Notes field, or
should it be worth to add a specific field for website address (that can 
be multiple)?

Best regards and all the best for Christmas period,

Mich?le




Marilynn S?rensen a ?crit :
>
> Dear platform group,
>
> There are a number of shortcomings with the current platform code 
> assignment process, some of these are technical in nature and some are 
> related to workflow processes and traceability of actions. The ICES 
> Data Centre has been investigating ways in which we can improve the 
> situation, both for you as users of the platform code process and for 
> us as administrators of the platform codes.
>
>  
>
> We intend to build and implement a new web application and 
> database at the beginning of 2009. The purpose of the new system is:
>
> -          Place the whole workflow process (from request, to 
> acceptance, to assigment) on the web
>
> -          Allow management and administration to take place in one 
> application
>
> -          Allow all ship requests/amendments to be handled in a 
> standard way, in one place
>
> -          Give users an online report of status on requests as well 
> as views of all the history behind a specific platform code or request
>
> -          Give users more power to update requests with additional 
> information
>
> -          Capture all communication and amendments in an automated 
> audit trail through the application
>
> -          Expolit web services etc. to automate request updates
>
>  
>
> The ICES Data Centre would ask that you take a look at the document at 
> http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20(Phase%201%20only)%20Final.doc 
> <http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20%28Phase%201%20only%29%20Final.doc>  
> and return with comments to Lee Martin <mailto:lmartin at ices.dk> by 
> *Friday 19^th December*. After this point we will be building and 
> testing this application with a view to launching it in early 2009. It 
> is important that you are aware of this development as it will mean in 
> the future we only accept platform requests through this process and 
> according to the minumum criteria as described in the document.
>
>  
>
> We hope this initiative will lead to a better management of platform 
> codes and a clear management process for all involved. Thank you and 
> we look forward to hearing from you.
>
>  
>
> Neil.
>
>  
>
> *Neil Holdsworth*
> Head of Data Centre
> International Council for the Exploration of the Sea
>
> Email: neil at ices.dk <mailto:neil at ices.dk>
>
> 	
>
> Web: www.ices.dk <http://www.ices.dk/>
>
> Tel: +45 3338 6718
>
> 	
>
> Fax: +45 3393 4215
>
> H.C. Andersens Boulevard 44-46
> 1553 Copenhagen V. Denmark
>
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Platforms mailing list
> Platforms at mailman.nerc-liv.ac.uk
> http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms

-- 
                                _
                              _| |_
                              (o o)
___________________________oOO-( )-OOo__________________________________
Michele FICHAUT - IFREMER/BREST - SISMER - B.P. 70 - 29280 PLOUZANE
TEL:(33)02.98.22.46.43/(33)02.98.22.49.16 (secr.) FAX:(33)02.98.22.46.44
Email: Michele.Fichaut at ifremer.fr  WWW : http://www.ifremer.fr/sismer/
________________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081219/d1d84dcf/attachment.html 

From friedrich.nast at bsh.de  Fri Dec 19 09:30:42 2008
From: friedrich.nast at bsh.de (Friedrich Nast)
Date: Fri, 19 Dec 2008 10:30:42 +0100
Subject: [Platforms] Platform code requests (Ship codes) -	improving the
 process
In-Reply-To: <s94aa90f.049@wpo.nerc.ac.uk>
References: <s94aa90f.049@wpo.nerc.ac.uk>
Message-ID: <494B69C2.9060805@bsh.de>

Dear Neil, Marilynn and Lee,
yes, it looks good - Anne and me had a deep look in your document and 
think it can improve our CSR business in particular. Anne has already 
sent some technical details, I felt the same as Roy adding more details 
as eg length would be senseful, but
- already a lot of this information is  the SDN Platform List (C174), 
and this should be merged in the ICES-DB, in addition
- a lot of information is with EurOcean?s ship list and
it shouldnt be hold threefold, and eg length should be always the same 
for the same ship at this three different places. How do we guarantee 
that? Will C174 information be mirrored by ICES?
Another item, I wondered was a new chief scientist with a new vessel 
wants to do a CSR, CSRonline. He tries the ship name, is directed to the 
request database, as he has a new one, wants to enter ship there, 
unknown, has to mail to ICES to get entered into the address DB, then 
has to wait two weeks to get his new ship registered... I know, that 
this is more the exception than the rule, but any idea to speed that up?

But in total the request database is fine, go ahead.

I wish you all a merry christmas and a good start for 2009,
Best regards
Friedrich

---------------------------------------------------------
  Bundesamt fuer Seeschifffahrt und Hydrographie  (BSH)
  Friedrich Nast (M42)
  Bernhard-Nocht-Str. 78        Tel: +49 (0) 40 3190-3420
  20359 Hamburg            Fax: +49 (0) 40 3190-5000
  http://www.bsh.de/            email: friedrich.nast at bsh.de
---------------------------------------------------------

-- 

Mit freundlichen Gr??en
Friedrich Nast
---------------------------------------------------------
  Bundesamt fuer Seeschifffahrt und Hydrographie  (BSH)
  Friedrich Nast (M42)
  Bernhard-Nocht-Str. 78	    Tel: +49 (0) 40 3190-3420
  20359 Hamburg		    Fax: +49 (0) 40 3190-5000
  http://www.bsh.de/            email: friedrich.nast at bsh.de
---------------------------------------------------------


From marilynn at ices.dk  Fri Dec 19 12:30:28 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Fri, 19 Dec 2008 13:30:28 +0100
Subject: [Platforms] Request database email list
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BE19@coral.ices.local>

Hi Roy and Platform group,

There have been questions about the registering of users of the request database. 

We have discussed this at ICES and propose that all members of the platform group will be automatically registered with a user name and password. The platform group member can then give out their user/password to appropriate users from their country. This would help ensure that

*	ICES does not become a bottleneck
*	the registered user list is not cluttered with addresses of temporary staff and one time users
*	there is coordination/shared responsibility between partners
*	the platform list has at least one member from each country

There will be a field for "Interim correspondance email" which we will use if we have questions. If the field is left blank, questions will go to the platform group user. 

ICES should be notified automatically when new members are added to the platform group so the person can be given a user name/password. Do you have any objections to this procedure? We have experience with this type of procedure from QUASIMEME and it works well.

Best regards,
Marilynn

----------------------------------------------------------
Marilynn S?rensen
Data Manager
International Council for the Exploration of the Sea
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
Denmark

Direct tel: +45 33 38 67 20 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081219/21bdbb52/attachment.html 

From marilynn at ices.dk  Fri Dec 19 12:51:12 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Fri, 19 Dec 2008 13:51:12 +0100
Subject: [Platforms] Request database: Web site field
In-Reply-To: <494B6745.1020600@ifremer.fr>
References: <4BA05716CBB9C24C911E746FE1A3B12708BDEF@coral.ices.local>
	<494B6745.1020600@ifremer.fr>
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BE1A@coral.ices.local>

Dear Michele,
 
In the database frontend, there is a field for a website and also one for a Lloyds confirmation site. The note field should not be used for websites and should be reserved for other types of information to help identify the ship.
 
During the confirmation process, if there is conflicting information, there is a comment field which can be used for another website etc.
 
We aren't interested in maintaining links and other background documents so we will use the website only to confirm information. If it isn't good enough, we will reject the site address. Therefore, multiple websites shouldn't be necessary and, if more than one is given, we will keep the best one. 
 
Best wishes,
Marilynn
 
________________________________

From: platforms-bounces at biwebs1.nerc-liv.ac.uk [mailto:platforms-bounces at biwebs1.nerc-liv.ac.uk] On Behalf Of Michele FICHAUT
Sent: 19 December 2008 10:20
To: Marilynn S?rensen
Cc: platforms at biwebs1.nerc-liv.ac.uk
Subject: Re: [Platforms] Platform code requests (Ship codes) -improving theprocess


Dear Marilynn and others,

I've read your document on Platform requests database, and I think  it will be a very useful
tool for those managing ship codes.
I am currently working on the French ships and I find very important to keep the address of websites where 
a ship description is available; there can be several web sites per ship.
 Do you think these web addressesshould be kept in the Notes field, or 
should it be worth to add a specific field for website address (that can be multiple)?

Best regards and all the best for Christmas period,

Mich?le




Marilynn S?rensen a ?crit : 

	Dear platform group,

	There are a number of shortcomings with the current platform code assignment process, some of these are technical in nature and some are related to workflow processes and traceability of actions. The ICES Data Centre has been investigating ways in which we can improve the situation, both for you as users of the platform code process and for us as administrators of the platform codes.

	

	We intend to build and implement a new web application and database at the beginning of 2009. The purpose of the new system is:

	<!--[if !supportLists]-->-          <!--[endif]-->Place the whole workflow process (from request, to acceptance, to assigment) on the web

	<!--[if !supportLists]-->-          <!--[endif]-->Allow management and administration to take place in one application

	<!--[if !supportLists]-->-          <!--[endif]-->Allow all ship requests/amendments to be handled in a standard way, in one place

	<!--[if !supportLists]-->-          <!--[endif]-->Give users an online report of status on requests as well as views of all the history behind a specific platform code or request

	<!--[if !supportLists]-->-          <!--[endif]-->Give users more power to update requests with additional information

	<!--[if !supportLists]-->-          <!--[endif]-->Capture all communication and amendments in an automated audit trail through the application

	<!--[if !supportLists]-->-          <!--[endif]-->Expolit web services etc. to automate request updates

	

	The ICES Data Centre would ask that you take a look at the document at http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20(Phase%201%20only)%20Final.doc <http://www.ices.dk/Datacentre/temp/Requests%20Database%20Utility%20-%20Requirements%20Specification%20%28Phase%201%20only%29%20Final.doc>   and return with comments to Lee Martin <mailto:lmartin at ices.dk>  by Friday 19th December. After this point we will be building and testing this application with a view to launching it in early 2009. It is important that you are aware of this development as it will mean in the future we only accept platform requests through this process and according to the minumum criteria as described in the document. 

	

	We hope this initiative will lead to a better management of platform codes and a clear management process for all involved. Thank you and we look forward to hearing from you.

	

	Neil.

	

Neil Holdsworth
Head of Data Centre
International Council for the Exploration of the Sea 

Email: neil at ices.dk <mailto:neil at ices.dk> 

Web: www.ices.dk <http://www.ices.dk/> 

Tel: +45 3338 6718 

Fax: +45 3393 4215

H.C. Andersens Boulevard 44-46
1553 Copenhagen V. Denmark

	 

	
________________________________


	_______________________________________________
	Platforms mailing list
	Platforms at mailman.nerc-liv.ac.uk
	http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms


-- 
                                _
                              _| |_
                              (o o)
___________________________oOO-( )-OOo__________________________________
Michele FICHAUT - IFREMER/BREST - SISMER - B.P. 70 - 29280 PLOUZANE
TEL:(33)02.98.22.46.43/(33)02.98.22.49.16 (secr.) FAX:(33)02.98.22.46.44
Email: Michele.Fichaut at ifremer.fr  WWW : http://www.ifremer.fr/sismer/
________________________________________________________________________
________________________________

Denne mail er blevet scannet af http://www.virus112.com <http://www.virus112.com>  
________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081219/56cfd78e/attachment.html 

From marilynn at ices.dk  Fri Dec 19 15:48:39 2008
From: marilynn at ices.dk (=?iso-8859-1?Q?Marilynn_S=F8rensen?=)
Date: Fri, 19 Dec 2008 16:48:39 +0100
Subject: [Platforms] Attributes
Message-ID: <4BA05716CBB9C24C911E746FE1A3B12708BE1F@coral.ices.local>

> Dear Roy anad Platform group,
> 
> We have had a look at whether or not to add additional attributes. There are a few points to consider:
> 
> *	How often is the attribute used to identify a vessel? 
> *	Who is to look up the information?
> *	Are people supplying it often in the notes?
> 
> Most requests have name, country and call sign as the only initial information. It is first when ICES or Roy start hunting that more attributes are found and conflicts identified. 
> 
> Lloyds and other web sites have lots of attributes that the platform list does not have. For example: Port of registry, Year of build, Owners (past and present), Length, Breadth, Weight, MMSI etc.etc.
> 
> One point of view could be: if there is not an attribute field, we will not add the information to the notes unless it is necessary for identifying the vessel. But sometimes we don't know that there is a problem until we compare the note fields.
> 
> Personally, I would add "Year of Build" since that is often used as the identifyer when multiple hull codes are needed. If length is not often used to identify the vessel, then it shouldn't be an attribute field.
> 
We would like to hear the opinion of more people from the platform group.

Have a peaceful holiday season.
Marilynn

----------------------------------------------------------
Marilynn S?rensen
Data Manager
International Council for the Exploration of the Sea
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
Denmark

Direct tel: +45 33 38 67 20 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081219/1d6477d3/attachment-0001.html 

From rkl at bodc.ac.uk  Fri Dec 19 23:25:48 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Fri, 19 Dec 2008 23:25:48 +0000
Subject: [Platforms] Platform code requests (Ship codes)	-	improving the
	process
Message-ID: <s94c2d86.039@wpo.nerc.ac.uk>

Hi Friedrich,

At the moment C174 is served by us and we synchronise metadata information with ICES through communication.  Longer term my hope is that will serve C174 directly, which will eliminate one source of error.

I had thought about the link to EurOcean for things like length, but the problem is that they cover a very small proportion of ships.  So, our only guard against differences in duplicated fields is vigilant checking!!

Cheers, Roy.

>>> Friedrich Nast <friedrich.nast at bsh.de> 12/19/08 9:30 AM >>>
Dear Neil, Marilynn and Lee,
yes, it looks good - Anne and me had a deep look in your document and 
think it can improve our CSR business in particular. Anne has already 
sent some technical details, I felt the same as Roy adding more details 
as eg length would be senseful, but
- already a lot of this information is  the SDN Platform List (C174), 
and this should be merged in the ICES-DB, in addition
- a lot of information is with EurOcean?s ship list and
it shouldnt be hold threefold, and eg length should be always the same 
for the same ship at this three different places. How do we guarantee 
that? Will C174 information be mirrored by ICES?
Another item, I wondered was a new chief scientist with a new vessel 
wants to do a CSR, CSRonline. He tries the ship name, is directed to the 
request database, as he has a new one, wants to enter ship there, 
unknown, has to mail to ICES to get entered into the address DB, then 
has to wait two weeks to get his new ship registered... I know, that 
this is more the exception than the rule, but any idea to speed that up?

But in total the request database is fine, go ahead.

I wish you all a merry christmas and a good start for 2009,
Best regards
Friedrich

---------------------------------------------------------
  Bundesamt fuer Seeschifffahrt und Hydrographie  (BSH)
  Friedrich Nast (M42)
  Bernhard-Nocht-Str. 78        Tel: +49 (0) 40 3190-3420
  20359 Hamburg            Fax: +49 (0) 40 3190-5000
  http://www.bsh.de/            email: friedrich.nast at bsh.de
---------------------------------------------------------

-- 

Mit freundlichen Gr??en
Friedrich Nast
---------------------------------------------------------
  Bundesamt fuer Seeschifffahrt und Hydrographie  (BSH)
  Friedrich Nast (M42)
  Bernhard-Nocht-Str. 78	    Tel: +49 (0) 40 3190-3420
  20359 Hamburg		    Fax: +49 (0) 40 3190-5000
  http://www.bsh.de/            email: friedrich.nast at bsh.de
---------------------------------------------------------

_______________________________________________
Platforms mailing list
Platforms at mailman.nerc-liv.ac.uk
http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms



From rkl at bodc.ac.uk  Fri Dec 19 23:27:28 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Fri, 19 Dec 2008 23:27:28 +0000
Subject: [Platforms] Request database email list
Message-ID: <s94c2e01.040@wpo.nerc.ac.uk>

Has my approval.

Cheers, Roy.

>>> Marilynn S?rensen <marilynn at ices.dk> 12/19/08 12:30 PM >>>
Hi Roy and Platform group,

There have been questions about the registering of users of the request database. 

We have discussed this at ICES and propose that all members of the platform group will be automatically registered with a user name and password. The platform group member can then give out their user/password to appropriate users from their country. This would help ensure that

*	ICES does not become a bottleneck
*	the registered user list is not cluttered with addresses of temporary staff and one time users
*	there is coordination/shared responsibility between partners
*	the platform list has at least one member from each country

There will be a field for "Interim correspondance email" which we will use if we have questions. If the field is left blank, questions will go to the platform group user. 

ICES should be notified automatically when new members are added to the platform group so the person can be given a user name/password. Do you have any objections to this procedure? We have experience with this type of procedure from QUASIMEME and it works well.

Best regards,
Marilynn

----------------------------------------------------------
Marilynn S?rensen
Data Manager
International Council for the Exploration of the Sea
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
Denmark

Direct tel: +45 33 38 67 20 





From rkl at bodc.ac.uk  Fri Dec 19 23:57:10 2008
From: rkl at bodc.ac.uk (Roy Lowry)
Date: Fri, 19 Dec 2008 23:57:10 +0000
Subject: [Platforms] Attributes
Message-ID: <s94c34ea.046@wpo.nerc.ac.uk>

Hi Marilynn,

I think 'commissioned' and 'decomissioned' do the job because they provide the basis of automated checking the validity of data or metadata such as  ROSCOPs attributed to the ship code. Note that I regard 'commissioned' to be equal to 'date of build' in the absence of any information to the contrary.  So I wouldn't have 'date of build' as well.

I would certainly place no restrictions on the usage of the notes field.  You never know what information will become necessary in the future! 

Cheers, Roy.

>>> Marilynn S?rensen <marilynn at ices.dk> 12/19/08 3:48 PM >>>
> Dear Roy anad Platform group,
> 
> We have had a look at whether or not to add additional attributes. There are a few points to consider:
> 
> *	How often is the attribute used to identify a vessel? 
> *	Who is to look up the information?
> *	Are people supplying it often in the notes?
> 
> Most requests have name, country and call sign as the only initial information. It is first when ICES or Roy start hunting that more attributes are found and conflicts identified. 
> 
> Lloyds and other web sites have lots of attributes that the platform list does not have. For example: Port of registry, Year of build, Owners (past and present), Length, Breadth, Weight, MMSI etc.etc.
> 
> One point of view could be: if there is not an attribute field, we will not add the information to the notes unless it is necessary for identifying the vessel. But sometimes we don't know that there is a problem until we compare the note fields.
> 
> Personally, I would add "Year of Build" since that is often used as the identifyer when multiple hull codes are needed. If length is not often used to identify the vessel, then it shouldn't be an attribute field.
> 
We would like to hear the opinion of more people from the platform group.

Have a peaceful holiday season.
Marilynn

----------------------------------------------------------
Marilynn S?rensen
Data Manager
International Council for the Exploration of the Sea
H.C. Andersens Boulevard 44-46, 1553 Copenhagen V.
Denmark

Direct tel: +45 33 38 67 20 





From friedrich.nast at bsh.de  Fri Dec 19 09:26:34 2008
From: friedrich.nast at bsh.de (Friedrich Nast)
Date: Fri, 19 Dec 2008 10:26:34 +0100
Subject: [Platforms] Platform code requests (Ship codes) -	improving
	the	process
In-Reply-To: <s94aa90f.049@wpo.nerc.ac.uk>
References: <s94aa90f.049@wpo.nerc.ac.uk>
Message-ID: <494B68CA.8050601@bsh.de>

Dear Neil, Marilynn and Lee,
yes, it looks good - Anne and me had a deep look in your document and 
think it can improve our CSR business in particular. Anne has already 
sent some technical details, I felt the same as Roy adding more details 
as eg length would be senseful, but
- already a lot of this information is  the SDN Platform List (C174), 
and this should be merged in the ICES-DB, in addition
- a lot of information is with EurOcean?s ship list and
it shouldnt be hold threefold, and eg length should be always the same 
for the same ship at this three different places. How do we guarantee 
that? Will C174 information be mirrored by ICES?
Another item, I wondered was a new chief scientist with a new vessel 
wants to do a CSR, CSRonline. He tries the ship name, is directed to the 
request database, as he has a new one, wants to enter ship there, 
unknown, has to mail to ICES to get entered into the address DB, then 
has to wait two weeks to get his new ship registered... I know, that 
this is more the exception than the rule, but any idea to speed that up?

But in total the request database is fine, go ahead.

I wish you all a merry christmas and a good start for 2009,
attached greetings from Hamburg.
Best regards
Friedrich

---------------------------------------------------------
  Bundesamt fuer Seeschifffahrt und Hydrographie  (BSH)
  Friedrich Nast (M42)
  Bernhard-Nocht-Str. 78	    Tel: +49 (0) 40 3190-3420
  20359 Hamburg		    Fax: +49 (0) 40 3190-5000
  http://www.bsh.de/            email: friedrich.nast at bsh.de
---------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PC110507.JPG
Type: image/jpeg
Size: 688943 bytes
Desc: not available
Url : http://mailman.nerc-liv.ac.uk/pipermail/platforms/attachments/20081219/f1aec73c/attachment-0001.jpe