We are excited to release version 0.3.0 of Miso Dataset today that is full of new features. For the gory details, you can take a look at the closed issues, but this post will cover the major enhancements to the Dataset library.
Miso Dataset has been on quite a world tour! It has helped visualize the Australian Census, Bosnian Media, and explored Electoral College votes for the US election. Thanks to all your valuable feedback, we are making improvements all the time. We wanted to share a few major ones in this release.
Miso Dataset now supports:
Until now, if you wanted to add columns to your dataset that were somehow based on your existing set of columns, you had to manually create a column, compute the data and update the rows. This was both computationally expensive and somewhat cumbersome. In this release, we’ve added the ability to add a computed column - a column that is based off of the existing rows that also updates its values as data is added or updated.
Here is an example of creating a computed column:
Prior to this release, when creating a Dataset, a custom column was created called
as a unique identifier for your rows. Most of the time however, our data already
contains unique identifiers that we would much rather use. Dataset has been updated to support this
functionality which you can enable by setting the
idAttribute property on dataset
creation. This also makes it much simpler to access a specific row by
its custom identifier. For example, if your dataset is using its ISO3 column as
IDs, you can now simply write
Here is an example:
update method was one of our trickier APIs to remember. Not only did it allow for updating
a single row, sets of rows or function-based updating, but each one of those updates required a slightly different
signature. In this release we are changing how the update function looks but keeping the functionality intact.
Here is an example of all the ways to update your dataset:
This makes it much easier to update a set of arbitary rows with individual changes in one go and only generate a single event.
Last but not least, we have rewritten our sort routine to increase its performance substantially.
You should now see an improvement of about 8x in your routines that utilize the
Thank you all for the invaluable feedback and keep telling us what you want to see Miso Dataset do!
– Irene and Alex