<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:st="" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns0="http://schemas.microsoft.com/office/2004/12/omml">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
{mso-style-priority:99;}
span.MSOHYPERLINK
{mso-style-priority:99;}
a:visited
{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
{mso-style-priority:99;}
p
{mso-style-priority:99;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0pt;
mso-margin-bottom-alt:auto;
margin-left:0pt;
font-size:12.0pt;
font-family:"Times New Roman";}
pre
{margin:0pt;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.emailquote, li.emailquote, div.emailquote
{mso-margin-top-alt:auto;
margin-right:0pt;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@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-US link=blue vlink=purple>
<div class=Section1><pre><span class=apple-style-span><font size=2 color=black
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:black'>Don’t depreciated terms in P021 get stored the same as depreciated Organisation names do in EDMO? <o:p></o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></span></pre><pre><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>I’ve looked at the gmd quickly and I don’t think there is an obvious solution but you could specify a </span></font><span
class=apple-style-span><font color=black face=Arial><span style='font-family:
Arial;color:black'>gmx:Anchor xlink:</span> for each keyword sp you could also link to the “</span></font></span><strong><b><font
color=black face=Arial><span lang=EN-GB style='font-family:Arial;color:black'><a
href="http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB"><span style='font-weight:
normal'>http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB</span></a></span></font></b></strong><strong><b><font
color=navy face=Arial><span lang=EN-GB style='font-family:Arial;color:navy'>” id</span></font></b></strong><span
class=apple-style-span><font color=black face=Arial><span lang=EN-GB
style='font-family:Arial;color:black'> </span></font></span><span
class=apple-style-span><font color=black face=Arial><span style='font-family:
Arial;color:black'>Which might solve this issue. We have used this elsewhere. <o:p></o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>James – you understand this way better than me? ….<o:p></o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>Cheers<o:p></o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></span></pre><pre><span
class=apple-style-span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>Bex</span></font></span><font
color=black face=Arial><span style='font-family:Arial;color:black'><o:p></o:p></span></font></pre>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> medin_standards-bounces@biwebs1.nerc-liv.ac.uk
[mailto:medin_standards-bounces@biwebs1.nerc-liv.ac.uk] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Lowry, Roy K.<br>
<b><span style='font-weight:bold'>Sent:</span></b> 08 November 2010 16:45<br>
<b><span style='font-weight:bold'>To:</span></b>
medin_standards@mailman.nerc-liv.ac.uk<br>
<b><span style='font-weight:bold'>Cc:</span></b> Clements, David O.; Jason
Sadler; Thorne, Kay<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Medin_standards] FW:
P021 keyword storage in NERC/MEDIN metadata</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><st1:City w:st="on"><st1:place w:st="on"><font size=2
color="#1f497d" face=Calibri><span lang=EN-GB style='font-size:11.0pt;
font-family:Calibri;color:#1F497D'>Houston</span></font></st1:place></st1:City><font
size=2 color="#1f497d" face=Calibri><span lang=EN-GB style='font-size:11.0pt;
font-family:Calibri;color:#1F497D'>, we may have a problem……..<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span lang=EN-GB
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0pt 0pt 0pt'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
steve.donegan@stfc.ac.uk [mailto:steve.donegan@stfc.ac.uk] <br>
<b><span style='font-weight:bold'>Sent:</span></b> 08 November 2010 16:36<br>
<b><span style='font-weight:bold'>To:</span></b> Lowry, Roy K.<br>
<b><span style='font-weight:bold'>Cc:</span></b> jds@geodata.soton.ac.uk<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: P021 keyword storage
in NERC/MEDIN metadata<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:blue'>Hi Roy,</span></font><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;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></font><strong><b><font size=2 color=black face=Arial><span
lang=EN-GB style='font-size:10.0pt;font-family:Arial;color:black'>http://vocab.ndg.nerc.ac.uk/term/P021/59/ZOOB</span></font></b></strong><span
class=m><font size=2 color=blue face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial;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></font></span><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><span class=m><font size=2 color=blue face=Arial><span
lang=EN-GB style='font-size:10.0pt;font-family:Arial;color:blue'>cheers,</span></font></span><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><span class=m><font size=2 color=blue face=Arial><span
lang=EN-GB style='font-size:10.0pt;font-family:Arial;color:blue'>Steve</span></font></span><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Lowry,
Roy K. [mailto:rkl@bodc.ac.uk] <br>
<b><span style='font-weight:bold'>Sent:</span></b> 08 November 2010 15:55<br>
<b><span style='font-weight:bold'>To:</span></b> Donegan, Steve (STFC,RAL,SSTD)<br>
<b><span style='font-weight:bold'>Cc:</span></b> Jason Sadler<br>
<b><span style='font-weight:bold'>Subject:</span></b> P021 keyword storage in
NERC/MEDIN metadata</span></font><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>Hi Steve,<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>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></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'>Cheers, <st1:City w:st="on"><st1:place w:st="on">Roy</st1:place></st1:City>.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Calibri><span lang=EN-GB style='font-size:
10.0pt;font-family:Calibri'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'><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></span></font></p>
<p><font size=3 face="Times New Roman"><span lang=EN-GB style='font-size:12.0pt'>--
<br>
Scanned by iCritical. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>