[Esip-discovery] ESIP geoportal presentation

[Christine White]

Thanks for these notes Steve. After the presentation, I discussed the datacasting and service casting registration - as you noted, being able to harvest like a WAF, or add to the federated search list - with our team. Agree that this would be a useful enhancement.

Some folks from the Discovery Cluster are meeting soon (doodle poll<http://www.doodle.com/9yx4m847pq6hucf38eb9qbq3/admin#table> available to determine best time) to discuss issues related to the Discovery Cluster Testbed Project - one of those issues being defining requirements for a Discovery Cluster geoportal implementation.  It'd be great to have your input.

Christine

From: Stephen M Richard [mailto:steve.richard at azgs.az.gov]
Sent: Wednesday, November 09, 2011 7:37 PM
To: Christine White; esip-discovery at lists.esipfed.org
Cc: Ryan Clark; Genhan Chen
Subject: ESIP geoportal presentation

Christine-
Sorry I missed your presentation today, but fortunately the notes on the Wiki seem pretty good.
We've been looking at the service casting and datacasting stuff and it seems to me it's functionally analogous to a web accessible directory for publishing metadata records (with the possibility that the server might implement some filtering capabilities-nice addition).  Essentially the Atom feed is a collection of simple metadata records; the only functional additions over a CSW csw:record response with core queryables is a *slightly* more structured treatment of the links. I think geoportal will already harvest rss, so it would be easy to set it up to harvest the service- or data-cast rss or atom. The discovery cluster needs to work on is better conventions/documentation about what the link encoding will look like (have to account for THREDDS, WSDL, WADL, other serviceTypes; need some other attributes), and what the atom entries are about. If each of the service casts is about a single dataset, then the resource people are probably interested in is the data, and the service is incidentally a way to get the data.  Is there really a separate use case for service cast and data cast, or is what we are really interested in is just a feed that has entries for datasets with links for the variety of ways to get at the data, including a (possible) variety of services.

Geoportal already does OpenSearch and generates RSS and Atom responses. One thing we'd like to figure out is how to control the content and encoding of those responses, and how they are constructed from metadata that is harvested in different formats. Then it looks to me like you could set up a data or service cast from geoportal.

steve

Stephen M. Richard
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701   USA
phone: 520 209-4127
AZGS Main: (520) 770-3500.  FAX: (520) 770-3505
email: steve.richard at azgs.az.gov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-discovery/attachments/20111110/ba98b0a3/attachment.html>