Convert QA script to work with catalog-beta

[tdlowden]

Feature/what we're after

[A brief, one-sentence description of the outcome we're trying to achieve]

Anticipated/hypothesized benefits

• [benefit A]
• [benefit B]

Measurements/metrics

• [description of a thing that can be monitored or tested to measure and validate when the outcome has been achieved]

References/background

• [notes about desirable attributes or context for the epic]
• [links to previous research, possible routes to take, things that multiple stories will likely need to refer to]

[rshewitt]

we don't need to do this. we have enough of the data. this is harvest_record on prod. if there's enough missing data in dataset then we'll need to fix it (there's 360k which seems sufficient). this is a search issue.

   c   |                                              name                                               
-------+-------------------------------------------------------------------------------------------------
 73655 | archived-ngda-standalones
 53583 | current-ngda-standalones
 34066 | DOI USGS DCAT-US
 27041 | nasa-data-json
 20861 | ioos
 18941 | healthdata-gov
 13549 | ngdc-paleo
 12555 | noaa-nesdis-ncei-accessions
  6360 | 2016-addrfn
  4218 | epa-sciencehub
  4091 | state-of-california
  3885 | DOI NPS DCAT-US
  3806 | ngdc-mgg-multibeam
  3800 | nos-ngs
  3275 | doj-json
  3273 | pacific-fisheries-environmental-laboratory
  3233 | 2017-edges
  3233 | 2017-areawater
  3232 | 2018-faces
  3232 | 2020-roads
  3232 | 2018-edges
  3230 | 2017-facesah
  3230 | 2018-linearwater
  3229 | 2018-roads
  3229 | all-roads-county-based-shapefile
  3223 | 2017-roads
  3220 | 2017-addr
  3220 | 2017-addrfeat
  3220 | 2017-addrfn
  3220 | current-address-range-feature-name-relationship-file

[tdlowden]

Question: do we still need this?