<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18854">
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<STYLE>
<!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:1.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:"Arial","sans-serif";
color:navy;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma" lang=EN-US link=blue vLink=blue>
<DIV>Hi Mark & Becky,</DIV>
<DIV> </DIV>
<DIV>I think this approach looks very sensible, however I'm not sure that the way the document is set out is the way to go: there are 5 separate downloads referenced in the offshore litter guidelines for the other common tables - that's a lot of messing about for a user ! Could we be clever about this and populate the print or web documents, on demand, with the common tables (e.g. Project, Survey) : e.g. as they are downloaded from the site ? Either that or find a simple way to rebuild each guideline (without copying and pasting 50 times....), should ever anything change in any of the common tables ? This might be possible to do with PDFs using ghostscript and\or distiller: if the common tables were stored as separate PDFs and each guideline as a PDF with the dataset specific information, it could be easy scripted (for each guideline) to just merge the relevent pdfs to generate the full guideline should anything change. Hope that make sense !</DIV>
<DIV> </DIV>
<DIV>Regarding the web mockup, one thing that might not be immediately clear is the allowable relationships between the sample techniques\events and the datasets. The loose structure of the webpage indicates it might be possible to combine two disparate tables (e.g. Trawl & Dredge & Photos). Of course that is assuming nobody actually goes and reads the actual Data guideline, which I'm sure a lot will, but I feel something more graphical\interactive might help. </DIV>
<DIV> </DIV>
<DIV>Steve</DIV>
<DIV><BR>>>> "Charlesworth, Mark E" <mecha@bodc.ac.uk> 14 April 2010 17:46 >>><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">All,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">At the last meeting there was a clear steer to provide more a modular approach to the Data Guidelines to stop the repetition of content between different ones. Myself and Becky have discussed this approach and come up with a proposed solution. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Basically the approach is to provide common tables as stand alone web documents and then give the web address in the guidelines at the appropriate point. If tables need updating this means a lot less work. I have done an example using the existing offshore litter guideline which is attached and the tables it refers to in that document are also attached.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Further details are below and a very rough mock up of how we can describe this in a webpage also attached. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">For those who had strong feelings about this can you please provide some comments back to myself and Becky by mid next week? We can then make the necessary amendments and put the new structure and some more guidelines that we have waiting to publish on the website in the next 2 weeks.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Best Wishes<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Mark<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></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">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Charlesworth, Mark E <BR><B>Sent:</B> 17 March 2010 13:10<BR><B>To:</B> Becky Seeley<BR><B>Subject:</B> RE: Web uploads<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Hi Becky,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Basically as we discussed I have seperated out the project, survey and fixed station tables which will be generic to all (where applicable in the case of project and fixed station) into their own documents - attached. </SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">The trawl and tow information is also seperated out and this would in my mind fall in the category of 'Sample Event' which would also include grab and core, water sample, oceanographic profile etc - it is slightly different to the data guideline you wrote but we can amend it.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> </SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">One thing I have struggled with is whether to seperate out the Data Production Tools (sample and processing methods,) from the sample data or leave together. I have edited the litter guideline to give an example of what I expect a MEDIN Guideline could look like under this new framework and have pulled it out the Data Production Tools bit seperate but it may need more thought. </SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Yesterday I started doing a mock up of what the web page introducing it could look like but I like your matrix more!</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Are you around tomorrow so we can go through all this on phone and plan?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Cheers</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Mark</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV id=divRpF139222>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center>
<HR align=center SIZE=2 width="100%">
</DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Becky Seeley [bese@MBA.ac.uk]<BR><B>Sent:</B> 17 March 2010 10:36<BR><B>To:</B> Charlesworth, Mark E<BR><B>Subject:</B> RE: Web uploads</SPAN><o:p></o:p></P></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt">Hi Mark, </SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt">I’ve been trying to consolidate the standards stuff as per our phone conversation last week. I attach a matrix I made showing the sections seen in each standard which I hope helps show the commonalities between them. The first two levels are standard, level three is standard but has specific requirements on what is included in the methodology. I’m gonna have a quick look at levels 4-6 to see how much is common. </SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center>
<HR align=center SIZE=2 width="100%">
</DIV>
<P class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Charlesworth, Mark E [mailto:mecha@bodc.ac.uk] <BR><B>Sent:</B> 16 March 2010 11:44<BR><B>To:</B> Allen, Terence J<BR><B>Cc:</B> Becky Seeley<BR><B>Subject:</B> Web uploads</SPAN><o:p></o:p></P></DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 10pt">Hi Terry</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 10pt">Can you upload these Data Guidelines to this page: <A href="http://www.oceannet.org/marine_data_standards/medin_data_guide.html" target=_blank>http://www.oceannet.org/marine_data_standards/medin_data_guide.html</A></SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 10pt">Use the titles:</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 13.5pt">Recording offshore litter data</SPAN></B><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 13.5pt">Oceanographic vertical profile data</SPAN></B><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">Also, In the last paragraph change the sentence ‘</SPAN><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #666666; FONT-SIZE: 10pt">MEDIN are in the process of deriving guidelines for physical oceanographic measurements, litter and seabed mapping and geophysics.’ To ‘MEDIN are in the process of deriving guidelines for other physical oceanographic measurements, biology and seabed mapping and geophysics.’</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #666666; FONT-SIZE: 10pt">Cheers</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #666666; FONT-SIZE: 10pt">Mark</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<P class=MsoNormal><BR>-- <BR>This message (and any attachments) is for the recipient only. NERC <BR>is subject to the Freedom of Information Act 2000 and the contents <BR>of this email and any reply you make may be disclosed by NERC unless <BR>it is exempt from release under the Act. Any material supplied to <BR>NERC may be stored in an electronic records management system. <o:p></o:p></P></DIV></DIV></DIV></BODY></HTML>