In order to keep an accurate count of the state of our datasets, datagovteam wants to update the Harvesting database with the results of the CKAN delete operation.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
[ ] GIVEN a record is marked to be deleted from CKAN Solr
AND that operation is successful
THEN we should log that success
AND we should add mark that dataset as "state: success" in the harvest_records db.
[ ] GIVEN a record is marked to be deleted from CKAN Solr
AND that operation is unsuccessful
THEN we should log that failure
AND we should create a new error in the harvest_error table
AND we should mark that dataset "state: error" in the harvest_records db
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
User Story
In order to keep an accurate count of the state of our datasets, datagovteam wants to update the Harvesting database with the results of the CKAN delete operation.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
[ ] GIVEN a record is marked to be deleted from CKAN Solr AND that operation is successful THEN we should log that success AND we should add mark that dataset as
"state: success"
in theharvest_records
db.[ ] GIVEN a record is marked to be deleted from CKAN Solr AND that operation is unsuccessful THEN we should log that failure AND we should create a new error in the
harvest_error
table AND we should mark that dataset"state: error"
in theharvest_records
dbBackground
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch