# Entering datapoints using Tinderbox

**URL:** <https://forum.beeminder.com/t/entering-datapoints-using-tinderbox/449>\
**Category:** Tech\
**Created:** [January 23, 2015, 5:07pm UTC](https://forum.beeminder.com/t/entering-datapoints-using-tinderbox/449 "2015-01-23T17:07:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\
**Post date:** [July 29, 2015, 9:03am UTC](https://forum.beeminder.com/t/entering-datapoints-using-tinderbox/449/2 "2015-07-29T09:03:10Z")

</div>

I haven’t updated the above linked code for ages, because the one that gets tweaked is the one embedded in my task list. It’s now more efficient, but it’ll take some effort to extract. Doubtless there will be more changes now that they’ve fixed the ‘edict’ feature, in Tinderbox 6.3.1.

My task list is based on @dreev’s [priority scheme](http://stackoverflow.com/a/5689300). I calculate the urgency-adjusted age of each item, and sum the squares of them, as suggested in [backlog minding](http://expost.padm.us/backlogminding). And of course, I [beemind the resulting total](https://beeminder.com/pjh/backlog).

---

_[View the full topic](https://forum.beeminder.com/t/entering-datapoints-using-tinderbox/449)._