In order to slim down the harvesting logic repo, datagov wants to remove/replace some of the harvester codebase
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
[ ] GIVEN harvesting logic repo \
WHEN code has been refactored \
THEN it will no longer be present in the repo.
Background
we're moving forward with using the HarvestRecord table as our source for comparison instead of ckan.
we don't need any S3 logic
if we pursue using ckan-solr for our comparison in the future having s3 functionality would prove useful. we can re-add it when we need it.
we don't need functionality to read records from ckan
the HarvestSource class no longer needs many of its required init args because it will derive those attributes from the harvest source info it requests
this ticket won't remove functionality for creating, updating, or deleting packages from ckan
User Story
In order to slim down the harvesting logic repo, datagov wants to remove/replace some of the harvester codebase
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
Background
HarvestRecord
table as our source for comparison instead of ckan.HarvestSource
class no longer needs many of its required init args because it will derive those attributes from the harvest source info it requestsSecurity Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch