CSW Debug Blog
Post to this group blog about your metadata Catalog Service for the Web (CSW) client and server implementation efforts and debugging sagas. I encourage occasional rants of the cathartic nature.
ISO 19139 service metadata record srv:DCPList codelist confusion
It appears that the GeoNetwork WMS harvest selects an incorrect codeListValue for a service metadata record's srv:DCPList (Distributed Computing Platform). Currently, it enters HTTP-GET and HTTP-POST. However, there is a bit of confusion within GeoNetwork and among standards and profiles. Specifically, one could interpret a conflict between DCP in a service's GetCapabilities (OGC) and a service's metadata record (ISO):
OGC Schema Issues in Relation to CSW
In order to create metadata for both static datasets and dynamic, online services and for use with CSW, the OGC created an xml schema that merges the schema for ISO19115 (dataset metadata) and ISO19119 (service metadata) (see secion D.1.5, page 105 in OGC 07-045). The way that was accomplished was by creating a schema located at http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd. The contents of that schema are quite simple -- it looks like this:
Connecting to GeoNetwork's MckoiDB through the Druid Database Manager
Here is a tutorial on how to connect to GeoNetwork's MckoiDB through the Druid Database Manager: http://geonetwork-opensource.org/documentation/how-to/druid_dbms
Note that the GeoNetwork 2.4.2 installer will not prompt you to provide a MckoiDB user name and password. Those are generated automatically and stored in
\geonetwork\web\geonetwork\WEB-INF\db\account.prop
- Login to post comments
Useful site for CSW testing and resources
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
- Login to post comments
GeoNetwork 4.2.1 exploration notes v3
BUG: what I consider a bug
FEATURE: what I consider a missing feature
TODO: possibilities that need to be explored or decide on
GeoNetwork 4.2.1 exploration notes v2
BUG: what I consider a bug
FEATURE: what I consider a missing feature
TODO: possibilities that need to be explored or decide on
GeoNetwork 4.2.1 exploration notes v1
BUG: what I consider a bug
FEATURE: what I consider a missing feature
TODO: possibilities that need to be explored or decide on
CSW metadata editors we are exploring
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:
Ruminations on XML and large datasets
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.
Metadata about Metadata for a Service That Provides Metadata
... kind of sounds like overkill, but there's reason behind the confusion!
Imagine that you're trying to find some data. In the USGIN scheme, in order to find data you search through CSW services, which are catalogues full of ISO1939 metadata documents. Each of these documents points you to a dataset or service that is somewhere, hopefully online, for you to take a look at. These CSW services are like the card catalogues of the digital era.
List of interesting metadata implementation recommendations and profiles
Following is a list of some metadata implementation recommendations and profiles I am looking at.
Configuring deegree-csw
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").
Geospatial data and metadata protocols, services, standards, and profiles
The beginnings of a list of geospatially enabled data and metadata protocols, services, standards, and profiles we are getting exposed to. Please, comment with corrections and additions.
What is the difference between CSW, CS-W, and CS/W?
Well .. I couldn't find any difference between CSW, CS-W, and CS/W.
CSW Clients and Servers we are testing
Following is a list of Web Service client, server, and hybrid applications we are aware of that are supposed to handle the CSW 2.0.2 protocol. Check out OGC's registry of products for more CSW implementations.
Public CSW services to test against
Here are some CSW services I use to test CSW clients against
CatalogConnector CSW Client
USGIN CatalogConnector test client http://catalog.usgin.org/catalogConnector/ (version 0.5)
This promising, stand-alone, Java-based, CSW web client is currently being developed by SDI Catalonia (IDEC) and USGIN at http://sourceforge.net/projects/catalogconnecto/
