search

ioos / system-test

IOOS DMAC System Integration Test project
github.com/ioos/system-test/wiki
The Unlicense
7 stars 14 forks source link

Improve CSW-driven workflows with geolinks #57

Open rsignell-usgs opened 10 years ago

rsignell-usgs commented 10 years ago

@tomkraldis has created a tiny python package to resolve different types of links returning from CSW query. We should use this in any of our system tests where we need to find certain link types (e.g. SOS, OPeNDAP, etc) https://github.com/geopython/geolinks

birdage commented 10 years ago

@rsignell-usgs thats pretty neat

kwilcox commented 10 years ago

Note: this should also handle service type URNs

dpsnowden commented 10 years ago

Also note the following repo...https://github.com/OSGeo/Cat-Interop. @tomkralidis initiated the Cat-Interop project in part to collect the various ways services are identified (esp. the URI syntax) in CSWs. I think some of the ideas from Cat-Interop became geolinks. Not sure of the status of either right now.

tomkralidis commented 10 years ago

cc @smrazgs @dpsnowden for https://github.com/OSGeo/Cat-Interop, https://github.com/OSGeo/Cat-Interop/blob/master/LinkPropertyLookupTable2.csv currently provides the latest consensus on link type defs and lookup values. https://github.com/geopython/geolinks initially provides a sniffer to try to detect a service/link type and provide the appropriate identifier (geolinks can certainly be expanded to provide more than the identifier). pycsw uses geolinks when parsing links during CSW-T Insert/Harvest operations.

I think the logical way forward is to harden the CSV lookup table some, mint/version it and then peg geolinks thereafter against it, thus providing a more concrete baseline. We have also run into discussions of authority/ownership (OSGeo? OGC? Other?), so this should be agreed upon also for the long run.