CSW requirements

appears to mostly be compiled by Armin Retterath, Kompetenz- und Geschäftsstelle GDI-RP

Has listing of active CSW servers, some requirements listings

http://www.mapbender.org/CSW_Requirements

We presented the following posters at the 2009 GSA Annual Meeting in Portland, Oregon. Note, the PDF files are large.

• USGIN: Interoperable Geoscience Data Services on the Web - How do we get there? (45MB PDF) by Stephen Richard, Lee Allison, Ryan Clark and Wolfgang Grunberg, Arizona Geological Survey
• Catalog Service for the Web, Implementing Interoperable Services for Discovering Geoscience Resources (46MB PDF) by Wolfgang Grunberg, Stephen Richard and Ryan Clark, Arizona Geological Survey.

The official documentation for the app-schema extension has been revamped! There is a lot more to look through here - absolutely a must-read for anyone interested in using GeoServer to serve GeoSciML features.

http://docs.geoserver.org/trunk/en/user/data/app-schema/index.html

BUG: what I consider a bug
FEATURE: what I consider a missing feature
TODO: possibilities that need to be explored or decide on

Now that we know what kind of CSW services we can pull off, we need to pay more attention to creating and maintaining metadata. Right now, I just do a bunch of ETLs from our in-house data repositories (ArcSDE, Access, Excel, etc.) to CSW Insert Transaction XML files. That method is not user friendly and editing individual metadata records are a pain.

So, here are some CSW metadata editors I am looking at:

At present, there is no user-interface component that helps you configure a complex-feature WFS in GeoServer. I'm sure that it is being worked on, but in the meantime, the configuration is done manually, by building the appropriate directory structure and putting XML configuration files in the right places.

This is an example of the directory structure that has to be in place.

When you configure a complex feature service, you have to manually map your data connection parameters into an XML document called a mapping file. I found that the easiest way to make this connection is as follows:

While working on thoroughly understanding CSW & metadata related OGC and ISO standards, I can not but start questioning XML and its use to carry and format data. After all, USGIN's goal is not just to implement interoperable USGIN metadata and data profiles but also to encourage their widespread adoption. The following blog entry "How XML Threatens Big Data" by Michael Driscoll discusses some of the limitations XML poses to dealing with large datasets and ease of use.

This is a list of our configuration changes too deegree-csw - specifically version 2.3-pre (missing link) with an PostgreSQL backend.

Follow instructions in deegree's documentation

See deegree_csw_2.0.2_documentation_en.pdf. Make sure the document is in a version corresponding to your version of deegree-csw (in this case "deegree Web Catalogue Service v.2.2").