...
Informal Opening Discussion
Arrivals and Departures
Bras Richter is the CRU’s newest member, an IS Business Automation Senior, filling the vacancy created when Soujanya departed.
.
Jacob Clausen has resigned to take a private sector job in Colorado.
Crash DB Systems Review
TraCS Systems and Crash Form development
...
Steven Parker / Andi Bill
Maintenance Updates and System Stability
CRASHDB-1658: Server Maintenance, September 22
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1658 Configuration typo for a security path led to a temporary transmission issue in UAT.
CRUBIZ-1655: Purchases of Crash Reports through http://Wisconsin.Gov
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRUBIZ-1655
Prioritized JIRA Issues and Enhancements
JIRA Completed
CRASHDB-1659: Resolve System Contact Information
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1659
JIRA In Progress
CRASHDB-1541: Duplicate Failure Message: Retransmission vs. Reuse
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1541 Pending CRASHDB-1570.
CRASHDB-1570: Pipeline work on SOAP and REST
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1570 Deployed TST and UAT to new DevOps environment.
CRASHDB-1637 – Resolve – 503 Error
Jira Legacy server System Jira serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1637 No issues since moving PRD Resolve into the new DevOps environment last month.
JIRA Planning
2023 RP Refinalization
Purge and Archiving Processes
Purge and Archive processes continuing to run smoothly.
1,152,959 total archived crashes of which 542,592 represent purged crashes (the archive adds approximately 13K crashes per month). This includes 2,159,983 total image files.
HWYCLASS Working Group
Working group meeting Tuesday, September 24
Phase 2 Prototype Testing Rollup
Phase 3 Implementation Planning
WisTransPortal / Community Maps
Community Maps citations and warnings data layer in progress.
Working with BTO (AASHTOWare)
City of Madison (Citian)
Crash Records Unit
Brad Richter / Polly Ebbinger / Mike Satteson
...
Issue Type | New since 8/23 | Resolved since 8/23 | Remaining |
---|---|---|---|
Document # Reuse* | 41 | 44 | 11 |
Retransmissions | 55 | 55 | 0 |
Potential Duplicate | 1 | 0 | 1 |
LE Questions | 6 | 5 | 1 |
Informatica Data Catalog Project
The CRU has just started work with BITS and Informatica to catalog the crash database:
A critical goal of this project is to get our database into compliance with DOA Standards for data security classification. As part of this work, each field in the database will need to be assigned a security classification ranging from public to confidential.
But we intend to get much more out of this project.
Authoritative Field Documentation, which serves as the source for the TraCS F2 help and for the documentation provided to analysts and the public.
A data linage that maps the path and transformations of data fields as they move from TraCS to the Crash Database and Data extracts. Provide the whos, whens and hows of data changes and modifications
Metadata change management, allowing us to to provide the data stability needed for 5-year analyses but also to gracefully adapt the data to new and changing standards.
Fatality Case Management and Reporting
Out sole FARS analyst was on leave for the first half of September. This has put me too much is the weeds to provide a formal analysis and metrics. But I can provide some anecdotal highlights.
The Daily Fatality Report
The old access database is now fully relegated to legacy reporting. It is quite demanding to maintain. But we are keeping it alive to maintain reporting continuity as we develop new reports. We be changing delivery mechanisms. Starting on Monday, 30 September, reports will be distributed using Lyris rather than being manually setup and mailed through Outlook.
Cause of Death Revio
DMV Systems and SR
Ken Matthews
...