<html 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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.m
{mso-style-name:m;}
span.EmailStyle21
{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>
<!--[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]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Houston, we may have a problem……..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> steve.donegan@stfc.ac.uk
[mailto:steve.donegan@stfc.ac.uk] <br>
<b>Sent:</b> 08 November 2010 16:36<br>
<b>To:</b> Lowry, Roy K.<br>
<b>Cc:</b> jds@geodata.soton.ac.uk<br>
<b>Subject:</b> RE: P021 keyword storage in NERC/MEDIN metadata<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi Roy,</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I think the problem stems from the fact that MEDIN provides the
keyword value i.e. "Zoobenthos taxonomy-related counts" and with this
in the iso gmd:thesaurusName element section gives a title of "SeaDataNet
P021 parameter discovery vocabulary" - there is no specification of the
actual term id & url i.e. </span><strong><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:black'>http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB</span></strong><span
class=m><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>" elsewhere in the gmd:thesaurusName section. The ingest
system doesnt touch this element at all -its the portal that takes the keyword
value and recursively looks it up in available lists to get a definition - I
think this is how it works from what I've seen - until the actual term url and
version number is specified in the metadata I dont think there's a lot that can
be done?</span></span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span class=m><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:blue'>cheers,</span></span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span class=m><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:blue'>Steve</span></span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lowry,
Roy K. [mailto:rkl@bodc.ac.uk] <br>
<b>Sent:</b> 08 November 2010 15:55<br>
<b>To:</b> Donegan, Steve (STFC,RAL,SSTD)<br>
<b>Cc:</b> Jason Sadler<br>
<b>Subject:</b> P021 keyword storage in NERC/MEDIN metadata</span><span
lang=EN-US><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Hi
Steve,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>I’m
currently trying to understand/overcome the consequences of the dynamic nature
of the P021 vocabulary, which has a governance that allows term broadening and
term deprecation for the MEDIN/NERC portals. Basically, what can happen
as a result is that the text associated with a given URI can change and,
if they specify P021 and just P02, they can disappear. Anything
that disappears (moves into P022) has a replacement P021 term indicated by a
1-to-1 mapping.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>In
SeaDataNet we manage this by refreshing the vocabulary in the metadata
generation tools that produce the XML. This leaves the issue of stale
P021 text and deprecated codes in XML files ‘in transit’ and metadatabases
generated from the ingestion of these files. We only ingest and
store the URIs: translation to text is handled by a dynamic call to the
vocabulary server. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>If
the URI has a version number embedded in it then this call returns the text as
it was at the time of metadata creation. Alternatively, replacing the
version number by ‘current’ in a URL or ‘::’ in a URN causes the most
up-to-date text to be displayed. We have adopted the latter approach in
SeaDataNet, but it isn’t the only approach.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Deprecation
in SeaDataNet is dealt with by a daily cron that sweeps the metadatabases and
automatically translates any deprecated URIs into their replacement.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>I’m
not sure how this issue is being dealt with in the MEDIN/NERC case, but some
code I’ve seen lately (which I think is the portal) seems to do a
verifyTerm against the current vocabulary list, which if you aren’t refreshing
content seems like an accident waiting to happen.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Any
clarification you can give me on what happens to MEDIN XML after they have been
harvested would be helpful.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Cheers,
Roy.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></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>
<p>-- <br>
Scanned by iCritical. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>