Feature/what we're after
After definining the Dataset model in #5487, the harvester should start populating that table when it does a harvest.
Anticipated/hypothesized benefits
- Providing data that we can put on the page in the catalog
- Proves out the technology choice that we make
Measurements/metrics
- Number of rows in the Dataset table
References/background
- Two possibilities exist: (1) we can make
Dataset be a SQL "view" onto the HarvestRecord table (this makes everything else easy because we don't have to make a "sync" method for our harvest) OR (2) change the harvester to "sync" the harvested records into our Dataset format when we do the harvest (this probably also needs a script to initially populate the Dataset table).
- Don't initially worry about getting all of the information from Harvester into this table. Just some things flowing from the harvest process into
Dataset is sufficient.
Feature/what we're after
After definining the Dataset model in #5487, the harvester should start populating that table when it does a harvest.
Anticipated/hypothesized benefits
Measurements/metrics
References/background
Datasetbe a SQL "view" onto theHarvestRecordtable (this makes everything else easy because we don't have to make a "sync" method for our harvest) OR (2) change the harvester to "sync" the harvested records into ourDatasetformat when we do the harvest (this probably also needs a script to initially populate theDatasettable).Datasetis sufficient.