<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks for raising this Rui<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">This is just a note to say that we are beginning to discuss starting the design of a more expressive model for data exchange, and indexing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I am afraid that is not a short term task though, but it will of course cover interactions (species related and evidence of interactions). As things progress, your input would be very welcome, both
on this topic and the broader model.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">IPT <ipt-bounces@lists.gbif.org> on behalf of Rui Figueira <ruifigueira@isa.ulisboa.pt><br>
<b>Date: </b>Thursday, 28 June 2018 at 15.45<br>
<b>To: </b>Markus Döring <mdoering@gbif.org><br>
<b>Cc: </b>"ipt@lists.gbif.org" <ipt@lists.gbif.org>, helpdesk <helpdesk@gbif.org><br>
<b>Subject: </b>Re: [IPT] update of Darwin Core Resource Relationship extension<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Hi Markus,<o:p></o:p></p>
<p>Thank you for your quick reply.<o:p></o:p></p>
<p>I understand the need to make the updated extension "correct", accordingly to the "class".<o:p></o:p></p>
<p>However, the lack of implementation on GBIF in ingesting related resources is a point of concern.<o:p></o:p></p>
<p>It brings to my memory the XVII Congress of the European Mycological Association (EMA), in 2015, in Madeira. In that congress, Dmitry Schigel and myself, we were invited to organise a symposium on Biodiversity Informatics and Fungal Data, in the end of the
first day. But, in the opening plenary session of the the conference, the President of EMA, David Minter, stated with emphasis that GBIF deliberately lacked support to all mycological researcher community. His main argument was that GBIF does not support interactions
between species, which is critical data for many fungi species. Unfortunately, I think we have to agree with him!<o:p></o:p></p>
<p>Using associatedTaxa is a limited solution if we want to document the occurrence of the interaction. And using the extension will create problems when documenting interactions between different biological groups, namely in the metadata description.<o:p></o:p></p>
<p>I came across this problem precisely because I am preparing and update of a dataset of fungi
<a href="https://www.gbif.org/dataset/651c0bec-bd78-4300-bbb0-5ed172fc82af">https://www.gbif.org/dataset/651c0bec-bd78-4300-bbb0-5ed172fc82af</a>, where all fungi are associated with a plant host. The use of the extension would allow us to define, for example,
the establishment means of the host. But, if GBIF is not ingesting the resource relationship, we are only left with the option of using associatedTaxa and occurrenceRemarks to document interactions, which is not my preferred option.<o:p></o:p></p>
<p>Best regards,<o:p></o:p></p>
<p>Rui<o:p></o:p></p>
<pre>------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Rui Figueira<o:p></o:p></pre>
<pre>Coordenador do Nó Português do GBIF<o:p></o:p></pre>
<pre><a href="mailto:ruifigueira@isa.ulisboa.pt">ruifigueira@isa.ulisboa.pt</a><o:p></o:p></pre>
<pre>Instituto Superior de Agronomia<o:p></o:p></pre>
<pre>Herbário<o:p></o:p></pre>
<pre>Tapada da Ajuda, 1349-017 Lisboa, Portugal<o:p></o:p></pre>
<pre>Tel. +351 213653165 | Fax. +351 213653195<o:p></o:p></pre>
<pre><a href="http://www.gbif.pt">http://www.gbif.pt</a><o:p></o:p></pre>
<pre><a href="http://www.isa.ulisboa.pt">http://www.isa.ulisboa.pt</a><o:p></o:p></pre>
<div>
<p class="MsoNormal">On 06/28/2018 11:38 AM, Markus Döring wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Rui, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">the scientificName term was dropped because it is not part of the regular DwC relation "class":<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://rs.tdwg.org/dwc/terms/index.htm#relindex">http://rs.tdwg.org/dwc/terms/index.htm#relindex</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The resource relation can relate any kind of things and GBIF needs to lookup the ids to find the scientificName of the related resource in your case. Unfortunately this is not implemented right now, so by upgrading to the latest "correct"
version of the extension you will lose the related scientific name on the GBIF occurrence page. <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">When I look at your example the data is a little unexpected though.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">The relatedResourceID is given as 701c94f1-16eb-4c1e-8449-f3b046100187:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><a href="https://api.gbif.org/v1/occurrence/1585354292/verbatim">https://api.gbif.org/v1/occurrence/1585354292/verbatim</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This should be the occurrenceID of the occurrence record for the plant it feeds on (<span style="font-size:10.5pt;font-family:"Helvetica Neue",sans-serif;background:white">Pistacia terebinthus)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">If I lookup this record in your dataset it is missing:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.gbif.org/occurrence/search?dataset_key=85a3c886-3312-45c9-b040-4d7634653246&occurrence_id=701c94f1-16eb-4c1e-8449-f3b046100187&advanced=1">https://www.gbif.org/occurrence/search?dataset_key=85a3c886-3312-45c9-b040-4d7634653246&occurrence_id=701c94f1-16eb-4c1e-8449-f3b046100187&advanced=1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If I look at the taxonomic overview of your dataset it is all Arthropoda, so the related food plants all seem to be excluded?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.gbif.org/occurrence/taxonomy?dataset_key=85a3c886-3312-45c9-b040-4d7634653246&advanced=1">https://www.gbif.org/occurrence/taxonomy?dataset_key=85a3c886-3312-45c9-b040-4d7634653246&advanced=1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you only want to annotate an occurrence record with the plant it feeds on you should not be using the relations extension but instead look into dwc:associatedTaxa: <a href="http://rs.tdwg.org/dwc/terms/index.htm#associatedTaxa">http://rs.tdwg.org/dwc/terms/index.htm#associatedTaxa</a><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">With regards,<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>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 28. Jun 2018, at 12:14, Rui Figueira <<a href="mailto:ruifigueira@isa.ulisboa.pt">ruifigueira@isa.ulisboa.pt</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi IPT list members,<br>
<br>
Could anyone help me to understand what are the implications of doing an update of the Darwin Core Resource Relationship extension, that our IPT installation is asking to update?<br>
<br>
I am particularly concerned with the dataset <a href="http://ipt.gbif.pt/ipt/resource?r=edp_tua_arthropoda_eia">
http://ipt.gbif.pt/ipt/resource?r=edp_tua_arthropoda_eia</a>, that is using this extension. The table resourcerelationship.txt in the dataset uses the term scientificName to identify the name of the tree where larva of butterflies feed on. This is reflected
in the occurrence data at <a href="http://gbif.org">gbif.org</a>, for example, in this record:
<a href="https://www.gbif.org/occurrence/1585354292">https://www.gbif.org/occurrence/1585354292</a>.<br>
<br>
I noticed that the update of the extension dropped the term scientificName. So, could anyone guide me on the changes that I need to do in the dataset, in order to be able to update the extension and have the same or equivalent information about the relationship
in the record at <a href="https://www.gbif.org/occurrence/1585354292?">https://www.gbif.org/occurrence/1585354292?</a><br>
<br>
Best regards,<br>
<br>
Rui<br>
<br>
-- <br>
------------------<br>
<br>
Rui Figueira<br>
Coordenador do Nó Português do GBIF<br>
<a href="mailto:ruifigueira@isa.ulisboa.pt">ruifigueira@isa.ulisboa.pt</a><br>
Instituto Superior de Agronomia<br>
Herbário<br>
Tapada da Ajuda, 1349-017 Lisboa, Portugal<br>
Tel. +351 213653165 | Fax. +351 213653195<br>
<a href="http://www.gbif.pt">http://www.gbif.pt</a><br>
<a href="http://www.isa.ulisboa.pt">http://www.isa.ulisboa.pt</a><br>
<br>
_______________________________________________<br>
IPT mailing list<br>
<a href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a><br>
<a href="https://lists.gbif.org/mailman/listinfo/ipt">https://lists.gbif.org/mailman/listinfo/ipt</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>