COORS Court Conviction CSV importer not properly transcribing location values

[RFK250]

Describe the Bug The COORS Court Convictions importer is not correctly importing the Location field on import.

• FYI, it looks to me like the importer is trying to import from the CSV correctly (csvRow['location'] - the CSV column is indeed labeled 'location') but I suspect the variable is not properly labeled (conviction['location_of_violation'] - but I think that should just be conviction['location']).
• That's just my best guess, but I absolutely could be completely wrong. :)
• Side note: Row 80 is where certain violation tickets get transformed into court convictions. It's working fine, just in case you have to tinker with it too. :)

Expected Behaviour On import, the value in the CSV Location column should populate the Location field in the Court Conviction record.

Actual Behaviour The Location field is not being populated (or at least is showing a "-" on NRCED)

Implications Until this bug is addressed, users will not be able to understand where a given court conviction was made. This is confusing to the user, although the risk is minimal.

Steps To Reproduce Steps to reproduce the behaviour:

1. Go to the NRPTI Import UI
2. Select COORS as the system
3. Select Court Convictions as the Record Type
4. Drag and drop a court conviction file (ask Kyle for one) and click Start Job.
5. Look at the court conviction records on NRCED. Records that come from this file will show a "-" as the location.
   • Note that it will look like only some of the Court Convictions are missing locations because some will show locations. The ones that show locations actually come from Violation Ticket files (see the second bullet under Describe the Bug).

[RFK250]

@pinkyandthekane Did this ever get pushed into production, btw? Or is it in the build that's being held up by the BCMI work?