<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 name=Generator content="Microsoft Word 14 (filtered medium)"><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;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for the explanation, Markus!<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jörg<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Markus Döring [mailto:mdoering@gbif.org] <br><b>Gesendet:</b> Donnerstag, 10. Juli 2014 14:19<br><b>An:</b> Holetschek, Jörg<br><b>Cc:</b> api-users@lists.gbif.org; GBIF Developers Developers<br><b>Betreff:</b> Re: [API-users] Dataset contacts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Jörg,<o:p></o:p></p><div><p class=MsoNormal>this is intended behavior. These contacts are rendered as associate parties in the portal project block:<o:p></o:p></p></div><div><p class=MsoNormal><a href="http://www.gbif.org/dataset/570489ac-e114-4a17-9340-2e01ee7d9ee3">http://www.gbif.org/dataset/570489ac-e114-4a17-9340-2e01ee7d9ee3</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The contact type is not required. And even though we try to have a primary administrative contact that is also not a requirement.<o:p></o:p></p></div><div><p class=MsoNormal>But in this specific case our tapir "metadata synchronisation" could be a bit more clever and detect the type.<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>Markus<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><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 10 Jul 2014, at 11:18, Holetschek, Jörg <<a href="mailto:j.holetschek@bgbm.org">j.holetschek@bgbm.org</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi guys,<br><br>I'm using the API to get dataset metadata from the registry (<a href="http://api.gbif.org/v0.9/dataset">http://api.gbif.org/v0.9/dataset</a>).<br><br>Each dataset entry has a 'contact' element, which is a list of contacts. Usually, each contact has a certain type. In the given example in the documentation, there are two contacts, each of type ADMINISTRATIVE_POINT_OF_CONTACT:<br><a href="http://api.gbif.org/v0.9/dataset/4fa7b334-ce0d-4e88-aaae-2e0c138d049e/contact">http://api.gbif.org/v0.9/dataset/4fa7b334-ce0d-4e88-aaae-2e0c138d049e/contact</a><br><br>However, paging through the datasets, I hit contacts that somehow look different. For example, they don't have a type, which breaks a script if you want to find the primary administrative contact, for example:<br><a href="http://api.gbif.org/v0.9/dataset/570489ac-e114-4a17-9340-2e01ee7d9ee3/contact">http://api.gbif.org/v0.9/dataset/570489ac-e114-4a17-9340-2e01ee7d9ee3/contact</a><br><br>Is that intended? Or is it leftovers from the old registry?<br><br>Cheers,<br>Jörg<br><br>---//------------------------------------------------------------<br>Jörg Holetschek<br>Coordinator Biodiversity Data Networks<br>Botanic Garden & Botanical Museum Berlin-Dahlem<br>Dept. Biodiversity Informatics<br><br>Königin-Luise-Str. 6-8, D-14195 Berlin<br>+49 (0)30 838-50150, <a href="mailto:j.holetschek@bgbm.org">j.holetschek@bgbm.org</a><br>------------------------------------------------------------//---<br><br><br>_______________________________________________<br>API-users mailing list<br><a href="mailto:API-users@lists.gbif.org">API-users@lists.gbif.org</a><br><a href="http://lists.gbif.org/mailman/listinfo/api-users">http://lists.gbif.org/mailman/listinfo/api-users</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>