Import all harvest sources from CKAN to H2.0

[jbrown-xentity]

User Story

In order to cutover harvesting to 2.0, data.gov admins want harvest sources created in harvesting2.0 for all harvesting.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN a tool/script is created for importing harvest sources into H2.0
  WHEN the harvest import happens
  THEN all the harvest sources with data from catalog are imported into H2.0

Background

Security Considerations (required)

None

Sketch

We should define and plan mapping from CKAN harvest source types into new harvest types, focused on job "type" and config object into the new H2.0 extract type and schema type.

We should only import harvest sources that have data; if it doesn't that should be documented in some type of auditable list. Most of these items will remain removed (consider reaching out to data providers), but a few may just have CKAN errors that we should resolve instead of ignoring.