<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you both. Some answers:<br>
<ol>
<li>We are here talking about the new portal, not the existing portal
- we are aiming to try to cut over in a couple of months.</li>
<li>TAPIR is the common goal, but I'd rather always be explicit.</li>
<li>If the connection protocol or endpoint is the only change, we
should make it possible to do this without forcing a re-index, but we
will be indexing everything afresh for the new portal.</li>
<li>We are going to have a more self-service interface for users to
handle this setting and many others.</li>
</ol>
Thanks,<br>
<br>
Donald<br>
<pre class="moz-signature" cols="72">------------------------------------------------------------
Donald Hobern (<a class="moz-txt-link-abbreviated" href="mailto:dhobern@gbif.org">dhobern@gbif.org</a>)
Deputy Director for Informatics
Global Biodiversity Information Facility Secretariat
Universitetsparken 15, DK-2100 Copenhagen, Denmark
Tel: +45-35321483 Mobile: +45-28751483 Fax: +45-35321480
------------------------------------------------------------
</pre>
<br>
<br>
John R. WIECZOREK wrote:
<blockquote
cite="mid8e794ee60702280914y6a045c8dxd8e5d2979d8861@mail.gmail.com"
type="cite">Or you could flag all of the DiGIR ones and leave TAPIR
ones unflagged, the idea being that TAPIR is the common goal toward
which to strive.<br>
<br>
<div><span class="gmail_quote">2007/2/28, Renato De Giovanni <<a
href="mailto:renato@cria.org.br">
renato@cria.org.br</a>>:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi
Donald,<br>
<br>
This is excellent news!<br>
<br>
Two quick questions:
<br>
<br>
* For providers that want to migrate to TAPIR and already have data<br>
indexed by GBIF from previous DiGIR/BioCASe instances, what will be the<br>
recommended procedure? (will it be necessary to re-index everything or
is
<br>
there an easy re-configuration process on the GBIF side?). Do they need
to<br>
contact GBIF to specify both the new TAPIR accesspoint and the old one<br>
that will be replaced or is there a way to do this just by interacting
<br>
with the UDDI registry?<br>
<br>
* On the web pages where GBIF lists providers, BioCASe/ABCD ones are<br>
marked with a special flag. Can you do the same for TAPIR providers when<br>
they start to pop up?<br>
<br>
Best Regards,
<br>
--<br>
Renato<br>
<br>
> The new GBIF data portal can index data provided using TAPIR with<br>
Dwc/Geo/Cur or ABCD 1.20/2.05/2.06.<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
tdwg-tapir mailing list
<br>
<a href="mailto:tdwg-tapir@lists.tdwg.org">tdwg-tapir@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir">http://lists.tdwg.org/mailman/listinfo/tdwg-tapir</a><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
tdwg-tapir mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tdwg-tapir@lists.tdwg.org">tdwg-tapir@lists.tdwg.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir">http://lists.tdwg.org/mailman/listinfo/tdwg-tapir</a>
</pre>
</blockquote>
</body>
</html>