Phil,
I guess you wanted something like a graphic representation showing the number of providers/records using TAPIR versus the same with DiGIR over the time. I also wanted to see this. The closest thing we can probably do now is to query GBIF's UDDI registry. Today the figures are:
* 64 TAPIR providers. * 190 DiGIR providers. * 157 BioCASe providers.
But I have no idea about how this is changing over the time and I don't know what happens when a registered DiGIR provider switches to TAPIR (if the old record gets deleted in the registry or not). I also don't know if all providers there are active, and we should certainly consider that not all existing providers (DiGIR or TAPIR) are registered there.
I cannot tell about the other networks, but I know that the speciesLink network is planning to migrate all local providers to TAPIR. Not sure when exactly this is going to happen.
There are many ways you can harvest data from a TAPIR service. Markus mentioned how GBIF is doing this. The easiest way is probably using filterless search requests with TAPIR paging.
Best Regards, -- Renato
So we have DiGIR running at Mobot for Tropicos data, and clients hit it to harvest data. I was just wondering if people are still deploying DiGIR at all, or are they just using Tapir by default? It seems to have taken over for DiGIR, and I want to know if that's a 'standard' that we should follow.
For testing, yes, we're talking more of performance; make sure our network and server will handle X load. So I guess I want to know more of, how do clients attach to a Tapir server, how do they pull the data from us?
Sorry if this is such a newbie question, but I can't understand this aspect from the docs I've read.
Thanks for the reply!
Phil