As a Conservation Officer Service administrative user, I want COORS violation ticket records to be automatically imported and published so I don't have have to query and manually upload them.
Additional Context
Currently, no manual data transforms or reviewed are needed by COS staff. The COORS administrative user simply runs the SQL query, exports the output to a CSV file, and then uploads the CSV file the NRPTI.
COORS sits behind a firewall in Zone B, so it will not be possible to simply pull the data from OpenShift. No API exists.
A comparable situation existed for the FLNR-NRIS-CSV importer. The solution was to user FME Server to query the data, transform it, push a CSV file out to the S3 bucket, then trigger the NRPTI integration to import that CSV file as FLNR-NRIS-CSV Inspections. This was acceptable to IT security.
A copy of the SQL query is available. It is very long and complex.
Acceptance Criteria
GIVEN COORS Violation Ticket data is transformed and available to NRPTI
WHEN The nightly cron job runs
THEN COORS Violation Tickets are automatically imported and published to NRCED
jakemorr
commented
4 months ago
As a Conservation Officer Service administrative user, I want COORS violation ticket records to be automatically imported and published so I don't have have to query and manually upload them.
Additional Context
Acceptance Criteria GIVEN COORS Violation Ticket data is transformed and available to NRPTI WHEN The nightly cron job runs THEN COORS Violation Tickets are automatically imported and published to NRCED