Hi Markus,
sure - the portals don't care where the record details are retrieved from, as long as they're available through ideally a typical protocol request or, less ideal, a custom link. Both protocol and access point should be stored in the Index, but I guess that's not the big issue.
Cheers, Jörg
-----Ursprüngliche Nachricht----- Von: "Markus Döring (GBIF)" [mailto:mdoering@gbif.org] Gesendet: Mittwoch, 15. September 2010 11:08 An: Guentsch, Anton Cc: Holetschek, Jörg; Tim Robertson (trobertson@gbif.org); ipt@lists.gbif.org; Berendsohn, Walter G. Betreff: Re: [IPT] GBIF Integrated Publishing Toolkit
[forwarding to list again as the message was rejected]
retrieving a full record from the network is a basic often needed feature. But there might be scenarios where people do not want to have a running server at all and prefer to simply publish their dataset to somewhere else. In that case "somewhere else" could be responsible for exposing the records. An IPT used for (national) hosting might be such a solution (given the record resolution is implemented). But one could also think to serve the full, original record by GBIF centrally for those cases. That would require GBIF to cache a full record as it came in of course, e.g. the full ABCD or a DWC with extensions potentially unknown to us. We have that on our wishlist for quite some time already.
Is it correct that both solutions, IPT record resolution or central GBIF resolution, would work for the BioCASe portals?
Markus
On Sep 15, 2010, at 10:48, Guentsch, Anton wrote:
Hi Markus,
I am not so familiar with the IPT but may be this as a clarification: Some of the "special interest networks" using GBIF/BioCASE technology heavily rely on the ability of provider software to return a full data record (e.g. ABCD and its extensions) for a given ID. This is in particular essential for the DNA-Bank-Network, which uses ABCD plus the DNA-extension. A second example is the emerging GBIF-D soil zoology network. Personally, I think that these networks have a great potential for demonstrating the capabilities of the GBIF infrastructures being based on high-quality data subsets and interfaces which directly serve a certain user community.
For the IPT I think that at the very least we would need some kind of interface which makes every record addressable. Preferably, the record should be a full record in the sense that DNA-extensions etc. are somehow represented.
Best regards, Anton
-----Ursprüngliche Nachricht----- Von: "Markus Döring (GBIF)" [mailto:mdoering@gbif.org] Gesendet: Mittwoch, 15. September 2010 10:24 An: =?iso-8859-1?Q?=22Holetschek@ns.gbif.org; Holetschek, Jörg Cc: Tim Robertson (trobertson@gbif.org); ipt@lists.gbif.org; Guentsch, Anton; Berendsohn, Walter G. Betreff: Re: [IPT] GBIF Integrated Publishing Toolkit
Jörg, currently it is not planned to provide single record access of any kind as we removed any record storage, e.g. the previous H2 database, to increase performance and reduce resource requirements. But if that is indeed needed we could add it back in of course. A simple link to a record in xml or rdf based on its ID would be sufficient?
Markus
On Sep 15, 2010, at 10:11, Holetschek, Jörg wrote:
Hi Tim,
the removal of the TAPIR interface will cause problems for all of our
BioCASe portals - for showing the complete record details, they do a DiGIR/BioCASe/TAPIR request, which would then fail.
Will there be an alternative option to get the DwC XML document, for
example via a deep link?
Cheers from Berlin, Jörg