Opened 12 years ago
Closed 12 years ago
#700 closed enhancement (fixed)
Implementation of CSW Harvest
| Reported by: | heikki | Owned by: | heikki |
|---|---|---|---|
| Priority: | major | Milestone: | v2.7.0 |
| Component: | General | Version: | v2.6.3 |
| Keywords: | csw harvest transaction | Cc: |
Description
The current implementation of CSW Harvester is not only disabled in the code, but it also doesn't work, it's incomplete.
New implementation addresses concerns stated in current source code as follows:
- make it protected (define a specific service for Harvest and Transaction operations)
Do exactly that, split GeoNetwork CSW endpoint in a Discovery endpoint and a Publication endpoint. The Publication endpoint will deal with Harvest and Transaction, thus finally protecting Transaction at the service level.
- Harvest operation does not allow to restrict harvested records by criterias (CQL or Filter)
That's true, but it's the CSW spec, so nothing to do about it. If you want to use the Harvest operation you should know its specification and its limitations.
- Harvest operation does not allow to define privileges for harvested records
Proposal is to use the same setting that's used for Transaction, to decide whether to make the harvested metadata public.
- Harvest operation does not allow to define logos
That's true, but it's the CSW spec, so nothing to do about it. If you want to use the Harvest operation you should know its specification and its limitations.
Committed in trunk rev 8667