Hi Rod,
Good to have you on board.
Yes I think this is a good possibility for future enhancement. I see
two main issues - neither technical.
1) There is some odd non 1:1 relationship between what is considered a
collection and a DiGIR/TAPIR end point. Looking through lists of DiGIR
providers they seem to overlap collections or represent parts of
collections. If we create collections in BCI that just exist to
represent the coverage of a DiGIR provider then we are kind of
becoming a service registry rather than a list of real world things -
which worries me slightly.
2) The GBIF data portal probably already knows bout all the DiGIR/
TAPIR/BioCASe providers out there and is probably scraping them
already and knows when they are down so that might be the natural
place to put a list of providers and their current status rather than
building anything new.
If we get the web service fields filled in for a reasonable number of
collections I would, at a minimum, write a web service to retrieve a
list of them so that any third party could write their own polling
mechanism. In fact if BCI were to take on such a role that is probably
how I would implement it anyway. I'll bear this in mind if I ever find
time to expand the JSON service - soon I hope.
Does that make sense?
Roger
On Sep 18, 11:32 am, Rod Page <
r.p...@bio.gla.ac.uk> wrote:
> I guess this is a feature request. Given that the Biodiversity
> Collections Index will potentially list all DiGIR/TAPIR providers, how
> about showing the current status of those providers?
>
> Dave Vieglais' BigDighttp://
bigdig.ecoforge.net/did this for a
> while, but doesn't seem to have been updated since February this year.
> I wonder if having a symbol beside the web service would prompt the
> people responsible for these services to ensure they are online (base
> don the assumption that BioCol is a visible resource). I'm constantly
> amazed by how many are offline (or change web server, or schema
> version, or resource code). One could even use a sparkline to show
> status history over time. The status checking itself doesn't need to
> be too fancy. Whether the service returns a 404 would be a start,
> followed by more sophisticated error checking if need be. Dave may
> have some code, or I could write something.
>
> What prompted me to suggest this is I just edited the Smithsonian fish
> collection record, and the DiGIR provider ishttp://
nhb-acsmith2.si.edu/emuwebvzfishesweb/webservices/digir.php.
> Having a web server called
nhb-acsmith2.si.edu is asking for it to
> break (OK, maybe I'm being unfair, there's a redirect to there fromhttp://
acsmith.si.edu/emuwebvzfishesweb/webservices/digir.php, but you
> get my point).