Member-only story

Documenting EDA — Numeric Columns

John Jarvis
4 min readOct 14, 2024

--

Image generated using Copilot

When I am transforming data being used for dashboards or reporting, sometimes it is important to have documentation to accompany it. Included in that documentation should be descriptive information about the data set.

This can be done a number of ways, each with associated value. For people on the business side of the audience, department wikis and internal blogs may not seem as intuitive as they do to people on the tech side of the audience. Still, it is important for the business to understand the details of the data they are relying on.

One way to make important details about the data accessible to the business side of the audience, is to create context relevant documentation. Part of being context relevant means providing details in ways that are consumable by the audience.

An image or screenshot is useful if it has no important text or numbers. But associated numbers must be presented in a way that can be copied and pasted. This is for the integrity of the output, to ensure that anyone who consumes the output can do so without altering the result.

To ensure that the output can be copied and pasted, but isn’t easy to alter, it can be exported as PDF files. This adds the benefit of allowing for charts or images to be included, in a context that tells a story. As opposed to a bunch of images and files in a…

--

--

John Jarvis
John Jarvis

Written by John Jarvis

Data Analyst with an MBA. I write about adapting to new technology and perspectives.

No responses yet