Munnin
From Zanecorpwiki
John and I conceived of a note taking system. My first application was a fact aggregator, but John convinced me that the first/base system should be both simpler and less specific.
The idea became, in general, the ability to take notes in order to:
- externalize memory
- store memories securely (fight the tide of forgetfulness)
- share thoughts
Contents |
The Name
The name was developed on the first day. I'm a huge fan of Norse mythology, and my file server is called Munin. While I was mucking around setting up John's permissions, realized that the story of Munin was a strong metaphor for the system we were working on.
Version 0.1
Day 1; Sketching in Version 0.01
The goal was to get notes into the system with the right amount of thought as to where to go next. John and I had some good discussion on the best data layout model. It wasn't clear how to handle publication references or the location within the publication. In the end, we settled on a single publication table that would hold the 'primary reference key' with the expectation that specific publication types would get secondary tables that would flesh things out.
There would be multiple types, which would be tied to publications in terms of what's appropriate. For instance, for books you could specify pages or percent, but not time codes. For AV you could specify time codes or percent, but not pages.
Dy the end of day one, I'd integrated the Kibbles user account module (TODO: link) (such as it was at the time) and created service and interface for creating notes on books. John and I developed the basic data model as well as the book and web article specific stuff. John worked on pulling and caching ISBN data from the web.
Day 2; Fleshing out Version 0.01
We started out with a spirited discussion of tagging and ideas about a modular service system. A lot to do today.
