Ticket #496 (closed requirement: fixed)
Provide a mechanism for exporting GEMINII metadata via a CSW interface
Reported by: | johnbywater | Owned by: | wwaites |
---|---|---|---|
Priority: | critical | Milestone: | ckan-v1.4-sprint-2 |
Component: | uklii | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description
Change History
comment:5 Changed 3 years ago by thejimmyg
- Owner changed from johnbywater to thejimmyg
- Priority set to awaiting triage
- Component set to uklii
- Summary changed from Respond to CSW "GetCapabilities" request to Provide a mechanism for exporting GEMINII metadata via a CSW interface
This would only apply to packages that had a HarvestedDcoument? record (ie had been harvested).
There are two approaches for this:
- Build the capability to respond to CSW "GetCapabilities?" and "Get Records" requests
- Export to an existing CSW server to provide the mechanism for us
comment:6 Changed 3 years ago by thejimmyg
- Owner changed from thejimmyg to wwaites
- Milestone set to ckan-v1.4-sprint-2
The latest plan after update with PP is as follows:
- CKAN will have a CSW interface
- OS GenoNetwork? will use this interface to determine:
- New documents
- Modified documents
- Removed documents
- OS will then handle the serving back to the EU since GeoNetwork? already implements the custom filters the EU may require (their docs are ambiguous).
This means the creation of the CSW server extension is now a high priority but it only needs to know about documents in the harvested_documents table. I've already implemented a REST API to get the those documents (but depending on the implementation it may need changing).
comment:7 Changed 3 years ago by thejimmyg
- Priority changed from awaiting triage to critical
- Status changed from new to closed
- Resolution set to fixed
- Type changed from story to requirement
Will has implemented this now and OS have confirmed their export to GeoNetwork? works.
Note: See
TracTickets for help on using
tickets.