I mentioned way back in December that I fell down a research rabbit hole at the end of 2017 but I never said what that rabbit hole was: it’s about data management and library learning analytics. I’m not quite ready to reveal the full results of that research project (the paper is currently working its way through the publication process), but I will be discussing my results at the ALA Annual Conference in New Orleans next week!
My talk is actually a follow up of my ALA 2017 talk but with actual research results to share. I’ll be specifically discussing anonymization, consent, and security, because hooboy do I have some things to say in these areas.
If you can’t make it to ALA, I’ll be posting the slides afterwards and hopefully you’ll see the paper in the near future too!
Today on the blog, I’m going to talk about the difference between a bar chart (right-left bars) and a column chart (up-down bars). For many, the difference seems negligible — simply the direction of the bars — but the choice between the two can often make a difference in terms of readability of your chart.
I’ll demonstrate my point using a recent published example of a column chart that might be better as a bar chart. The paper the chart comes from is really great and my critique of its Figure 6 in no way means that I don’t find the rest of the article to be of excellent quality. The chart is one of several examples I’ve seen but I’m allowed to reproduce it here under a CC BY license.
Here is the column chart in question. It displays where data curation actions are happening and overlays people’s satisfaction with that activity. Can you spot the major issue?
I’m really interested in the findings in the chart but I can’t get much actionable information out of it because so few of the columns are labelled (or even fully labelled). Additionally, it’s difficult to match the existing labels to columns due to the diagonal orientation of the text. All this is an artifact of the charting software compressing labels to fit in the allotted space.
The key point I want to make is that label dropping is less likely to happen in a bar chart (right-left bars). It’s usually easier to make a chart taller than to make it wider in order to provide the necessary label space. Plus, the text automatically orients itself in the proper direction so you don’t need to turn your head to read the chart. Overall, this makes for a more readable, more usable chart.
To show the difference, I reproduced a subset of the column chart as a bar chart. I think that it’s much easier to read and take away concrete findings because you can interact with every category in the chart.
So next time you’re making a column chart that needs a lot of labels, I hope you consider using a bar chart instead. It really does make a difference and your readers will appreciate a more readable chart.
 There’s an artifact in Excel not letting me use an overlay line as in the original chart but I think the overlapped bars sufficiently demonstrate the original point.
Every once and a while, I run across a topic and think, “surely I’ve covered this one my blog?” The most recent of these topics, which came up when I wrote December’s Exit Strategy post, concerns file formats.
File formats and exit strategies go hand-in-hand, as you don’t want to be stuck with inaccessible data in an unreadable file format. Proprietary, out-of-date, little used formats lower the chance that you’ll be able to access your data when you need it. Ask anyone with 20-year old files if they can use those files and you’ll likely see why file formats matter.
When it comes to choosing file formats that last, file types actually exist a spectrum. The best formats are open, well-documented, and in wide use. Clear examples are .TXT instead of .DOCX, or .CSV instead of .XLSX or .SAS. In the middle of the spectrum we find something like .PDF, which is an Adobe file format but in such wide use that it will be usable for many years. Also note that the spectrum of preferred file formats shifts over time (hello Lotus Notes and WordPerfect!).
Since there is no one right answer for any data type, the key thing for picking a good file format is to ask yourself if your content is currently in a file format that is uncommon or can only be opened by a specific software program. If the answer is yes, now is the time to make a backup copy of that data in a more open format. Even if you lose some formatting in the process, it’s better to have some data in an open format than having no data because it’s locked in an unreadable format. By making a copy, you also don’t have to lose the performance of the original file format while gaining the sustainability of the new; you can, of course, wholly switch to a better format if that is feasible. It’s also worth reviewing old data for formats that are no longer popular or supported.
Good data management is the sum of a number of small practices and picking good files formats is a piece of this puzzle. The more you are aware of how closed your current file formats are, the better you can plan for making that data usable into the future.
One phrase that’s bound to come up at every data management conference is “carrot versus stick” vis-a-vis incentivizing researchers to manage their data better. Carrots are rewards for good practices and sticks are requirements and their consequences relating to data management. There is inevitably discussion over which method is more effective for implementing data management.
Another phrase that I often hear in similar settings is “eating our own dog food” or “drinking our own champagne”. This is another way of saying “practice what you preach”, in that data experts should apply their advice to their own files.
These phrases are used so often that I’ve decided that they need to be combined as “eating our own carrot sticks”. It’s at least more appetizing than some of the other “eating our own…” options and a bit of snarkiness provides relief from predictability.
But to say something serious in this blog post, all of these phrases emphasize the importance of *doing* data management. It’s not enough to have the knowledge or to be given the incentive. It is only in the act of actually managing the data that we get value.
So I challenge you, whether you are a data management novice or an expert, to find one new data management practice to implement this month. Because a carrot stick a day keeps the data disaster away*.
* Okay, now I’m taking it too far, I know. I can’t help myself.
There was a long discussion on twitter yesterday (okay, I went on a rant) about the vast number of data management books that have been published for librarians in the past few years. While not exclusively data management books for librarians, here is the long list of data management books that I’m aware of:
We do not need any more “here’s how to build data services at a large research institution in a western country” books, thank you. I would happily buy books about data services at smaller institutions, in non-western countries, for data service support beyond PhDs and faculty, for building on data information literacy principles, and how to manage data when you’re a researcher (I’m happy to have competition for my own book!).
Please feel free to point people to this post when someone suggests writing/publishing another “building data services for librarians” book.
A lot has changed between then and now – I finished my MLIS, started my current job, published a book, and pursued some pretty interesting data-related research projects – but this blog has continued to be a wonderful project for me.
Details: Leave a comment on this post by 2018-02-28 describing your worst data disaster; the worse the data disaster the more likely I’ll feel you need my book. A winner will be chosen on 2018-03-01. United States only.