As a Ministry of Forests (FOR) administrative user, I want COORS administrative sanction records to be automatically imported and published so I don't have have to query and manually upload them.
Additional Context
The actual act of issuing hunting/angling/guiding licence suspensions and then publishing them is a manual process that involves two systems operated by two users from two different agencies.
Current user workflow:
FOR staff requests a CSV file from COORS staff
COORS staff runs an Administrative Sanctions SQL query, exports to CSV, and sends file to FOR Staff.
FOR staff reviews records and manually cross-references records with the WILD system.
FOR staff logs into COORS, finds records that require updating, and updates them - including manually adding a marker into an open text "notes" field that the SQL query will identify.
FOR staff then requests an updated CSV file from COORS staff, and uploads it to NRPTI to publish to NRCED.
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, and push a CSV file out to the S3 bucket, then trigger the NRPTI integration to import that CSV file as COORS-CSV Administrative Sanctions.
A copy of the SQL query is available. It is very long and complex.
Acceptance Criteria
GIVEN COORS admin sanction data is transformed and available to NRPTI
WHEN The nightly cron job runs
THEN COORS admin sanctions are automatically imported and published to NRCED
jakemorr
commented
3 days ago
As a Ministry of Forests (FOR) administrative user, I want COORS administrative sanction records to be automatically imported and published so I don't have have to query and manually upload them.
Additional Context
The actual act of issuing hunting/angling/guiding licence suspensions and then publishing them is a manual process that involves two systems operated by two users from two different agencies.
Current user workflow:
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, and push a CSV file out to the S3 bucket, then trigger the NRPTI integration to import that CSV file as COORS-CSV Administrative Sanctions.
A copy of the SQL query is available. It is very long and complex.
Acceptance Criteria GIVEN COORS admin sanction data is transformed and available to NRPTI WHEN The nightly cron job runs THEN COORS admin sanctions are automatically imported and published to NRCED