Allow metadata publishing and searching to operate against any OGC:CSW endpoint.
This will allow GeoNode to be configured against any OGC:CSW regardless of underlying implementation/deployment.
This will also allow for plug and play interoperability in the context of publication and discovery, as well as seperation of concerns for supporting components of GeoNode.
Jeffrey Johnson (on behalf of Tom Kralidis)
TBD (1.2 ??)
For Review and Comment
GeoNode allows for users to publish maps and data in a central node/location. Data are published to underlying data services (OGC:WMS/OGC:WFS/OGC:WCS). Metadata are published to an underlying catalogue service (OGC:CSW).
Data are discoverable by GeoNode via querying the OGC:CSW, processing search results, and binding to relevant data services accordingly.
Abstracting GeoNode's catalogue and metadata functionality to be OGC:CSW agnostic would add value to the project for integration with any OGC:CSW server implementation. Example OGC:CSW server implementations may include (but are not limited to) pycsw, deegree, etc.
Use owslib exclusively as the OGC:CSW client library. Enhance and fix owslib as required.
Use as much of the OGC:CSW implementation as possible. Keep implementation specific functionality as required:
Provide test mechanisms to demonstrate interoperability with various OGC:CSW implementations. TODO: need to further clarify
See discussion on the geonode-dev list here.
Ariel +1 - I would like to take care of the review and merging of this work.