James Brown
James Brown
## User Story In order to be able to cancel a pending job or stop a running job, data.gov harvester admins want a cancel option. ## Acceptance Criteria - [...
## User Story In order to run jobs as often as possible, data.gov harvesters want job completion to notify the flask app/controller so that it can start new jobs waiting...
## User Story In order to know if catalog-next has enough data to go live, data.gov owners want a spreadsheet detailing the state of the catalog, and the stats compared...
## User Story In order to have an integrated CKAN for the new harvester2.0, data.gov admins want a fixed version of datagovtheme. ## Acceptance Criteria [ACs should be clearly demoable/verifiable...
## User Story In order to have space in cloud.gov for new development, data.gov admins want more memory added to the contract. ## Acceptance Criteria [ACs should be clearly demoable/verifiable...
## User Story In order to have a stable catalog-next to test against, data.gov admins wants a protected branch and infrastructure for another catalog to be deployed. ## Acceptance Criteria...
## User Story In order to have a well documented API, data.gov admins want an OpenAPI spec document describing the Flask API for harvesting. ## Acceptance Criteria [ACs should be...
## User Story In order to get value from Harvester2.0, data managers want Harvester2.0 released to production. ## Acceptance Criteria - [ ] GIVEN Harvester2.0 is built \ AND the...
## User Story In order to be able to reset/restart a harvest source, data.gov admins want a clear function/API route. ## Acceptance Criteria [ACs should be clearly demoable/verifiable whenever possible....
Currently when harvesting under a new harvest source, if the name conflicts with CKAN then CKAN rejects the dataset. This is bad practice; we don't want CKAN to block datasets...