Improve CSW-based harvesting #184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 13 commits
May 30, 2022 18:39
Due to our custom logic that deals with package publication there was a bug preventing ckanext-harvest from creating harvesting jobs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements customization of the harvesting extension in order to be able to generate new EMC datasets from remote CSW-based sources.
Implementation uses a new CKAN plugin named
HarvestingPlugin- this is due to bug ckan/ckanext-spatial#277 in ckanext-spatial which prevents having both custom validators and customizing harvesting in the same plugin.The new
HarvestingPluginplugin implements theISpatialHarvestinterface that is provided by ckanext-spatial and then provides a customget_package_dict()method which transforms thedata_dictas created by the CSW harvester into the structure expected by the EMC datasets.Note that the datasets that are harvested are explicitly not made public by default - they must go through the same manual inspection stage that normal EMC datasets go through. This means that an organization member with the 'org admin' role needs to manually mark each harvested dataset as public.
fixes #177