Add additional properties to CKAN metadata to define Flask DB Relationship

[btylerburton]

User Story

In order to allow for the correlation between a record in CKAN and a record in the flask db interface, datagovteam wants to add new properties to the CKAN metadata:

• record_id
  • the id of the record in the flask db
  • needed to display a link to the original metadata in the CKAN UI interface
• harvest_source_id
  • the id of the flask db harvest_source that this record corresponds to
  • needed to clear entries out of CKAN DB and Solr without clearing an organization's other datasets
• harvset_source_name
  • the human readable name of the flask db harvest_source
  • needed to display name of harvest source in CKAN UI

Acceptance Criteria

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

• GIVEN I am harvesting a new harvest source
  WHEN I am pushing a new dataset to CKAN via the REST API
  THEN I want that to include the origin_record_id, origin_harvest_source_id, and origin_harvest_source_name as additional metadata properties

• GIVEN I have harvested a new dataset
  WHEN I look at the metadata in CKAN I will see additional properties of origin_record_id, origin_harvest_source_id, origin_harvest_source_name that are not part of the original dataset's metadata.

Background

[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

• Add origin_record_id, origin_harvest_source_id and origin_harvest_source_name as extra metadata properties prior to positing the dataset to CKAN
• Confirm these properties show up on the dataset after harvest
• Confirm these properties persist on package_update

[btylerburton]

updated to include harvset_source_name

[FuhuXia]

This is closely related to #4847.

[btylerburton]

Closing in favor of #4847