[4d] Investigate Harvest Source CMS Options

Purpose

We want to administer harvest source configs, but we're not sure if using a CMS is better than just writing our own SQLALchemy interface on top of the Harvest DB

Given the above, conducting research/investigation/prototyping is needed to provide factual knowledge on future steps.

4d of effort has been allocated and once compete, findings will be demonstrated and specific future actions will be decided.

Acceptance Criteria

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

GIVEN I have a created a model for harvest source configs AND it is represented in a CMS WHEN I add a new source THEN I should be able to query an API using that source's uniqueId and extract the relevant harvest source information

GIVEN I have the above API, WHEN I update the harvest source THEN I want a callback event to fire, which triggers a programmatic extraction of the relevant info AND insertion of that data into the Harvest DB

Background

NOTE that the CMS DB and Harvest DB should remain independent of each other as the schema a CMS uses will contain metadata that is not relevant to the Harvest DB table

Sketch

[ ] Stand up a CMS such as Strapi
[ ] Create a harvest source config model
[ ] Investigate callback triggers that will fire a script when a harvest source is created, updated or deleted
[ ] Investigate the ability to integrate Login.gov as an Authentication provider to the CMS
[ ] Determine that utilization of the above CMS will make the administering of harvest sources easier than hand coding a template and tying that to a SQLAlchemy process
[ ] Confirm it will integrate well with Flask. (ex. Strapi)

GSA / data.gov