Fix incident report excel export bug
The incident report exports narratives in HTML. Change to plain text format. Example:
<p>At 1:10 pm 1.5 miles from the trail head on the Spray Park Trail (heading back to Mowich Lake), participant tripped on a root and ended up bumping her brow bone on another root. Student did not present with any signs of head trauma, the bump site swelled to approximately 2.5 cm in diameter and no bleeding was noted. Patient reported minor discomfort, no current medications. Applied a cold compress with bandana soaked with cold creek water and continued to hike out. Patient still retained normal mentation and reported no significant discomfort associated with the bump. Advised that she will likely get a black eye over the next couple days, the swelling may not go down right away, and to consult her normal physician if she has concerns. Student was able to drive herself home with no further medical attention.</p>
Becca Polglase
shared this idea
AdminJeff Bowman
(Associate Director of Information Technology, The Mountaineers)
responded
The way the report renders currently is not a bug. It is how rich text data is stored in the file of completed forms. Rich text allows those filing a report to be able to use simple formatting to add things like paragraph breaks in the narratives. Changing the Incident Narrative and Lessons Learned fields from Rich Text to Plain Text would be a huge step backwards, making it much harder to collect good data.
This rich text only affects the data file download. There are two other sources of submitted incident reports, (1) the emailed report submission, and (2) the stored report submissions. Both of these are nicely formatted and easy to read.
Because it’s raw data, it should be relatively easy to turn the downloaded file into one nicely-formatted document with any number of tools. One simple approach is to use the “mail merge” capability in the Word and Excel applications.
We have the “Create More Robust Safety Committee Data Analysis” idea, http://feedback.mountaineers.org/forums/273688-general-feedback/suggestions/7002958-create-more-robust-safety-committee-data-analysis. It will provide an improved incident reporting and analysis system.
-
Cindy Hoover
commented
I would find the report much easier to read, if it were in plain text. I can decifer it in HTML, but might choose to not bother if rushed. It should be fixed.
-
Krissy Fagan
commented
I agree. This needs to be fixed as it is very difficult to read.
-
Michael Hansen
commented
We need to get this bug fixed as soon as is feasible. The usefulness of the data is time sensitive (perishable), so the longer it is unavailable to practical users, the more likely Clubwide safety will be impaired.
-
Jerry Logan
commented
This should be one of our highest priorities to fix if we are going to be able to learn and disseminate lessons from abnormal events.
-
Tony Tsuboi
commented
As a Safety Officer, it is painful having to parse through this unreadable format. It makes our job harder to do. It makes recruiting others to help a hard sell. Let's fix this.
-
Tony Tsuboi
commented
It's not that we need this in text vs HTML. It's that we need to restore things to they way they were earlier, i.e. without the markup tags and weird characters. This is a bug that was introduced in the last build.