When I wrote the comment I wasn’t aware that a distinction between dataset name and display title existed. Of course, immediately after posting the comment I went digging and found that what I wanted was readily available. That would account for your finding a dataset called “beer” when you looked at my profile (previously it was “NOVEMBEER etc etc” then “DECEMBEER etc etc”).

This left me in the awkward position of returning to this page to see a comment AWAITING APPROVAL that didn’t make a damn bit of sense. I considered writing yet another comment indicating that you should ignore the first, but I decided not to dig the hole any deeper.

Nevertheless, I appreciate the quick response. Maybe at some point someone else will see this and not make the same ridiculous mistake that I did.

d daytum beer : newcastle : 2

Your eloquent titles are only for the display. Since you can make multiple displays from a single data set, additions are directed at the data set, rather than the display.

I hope this makes sense. Nicholas.

I try to keep my data set names to 1 word that is memorable and short, like “running” or “concerts”… which makes the process much much easier, and less prone to failing should you make a typo.

Cheers, Nicholas.

But can we get some aliases for the datasets? I gravitate towards the unnecessarily long as titles go (mostly to amuse myself, but still).

Had I been paying attention to the blog, I would have noticed that this functionality existed this time last month, and I may have been more likely to follow through on “NOVEMBEER: BEER CONSUMED, NOVEMBER 2008,” for example.

That being said, maybe I wouldn’t have. The title isn’t exactly convenient for texting purposes. Especially when I’ve been drinking. AND it takes up over 1/3 of a Twitter direct message.

But I like that title. And I want to use it for December, too. I’m going to add a “d daytum DECEMBEER blah blah blah _ _” template to my phone, but I have to imagine there’s a possible solution that’s a bit less janky.