<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="5.0" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
<info>
    
    
    
    
    
    
    
<title>Evernote</title><biblioid class="uri">http://norman.walsh.name/2009/11/01/evernote</biblioid>
<volumenum>12</volumenum>
<issuenum>38</issuenum>
<pubdate>2009-11-01T16:51:13-05:00</pubdate>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2009</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>With a scanner and some Python, I'm an enthusiastic convert to Evernote.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#Evernote"/>
</info>

<para xml:id="p1">I first tried
<link xlink:href="http://www.evernote.com/">Evernote</link> more than a
year ago. It seemed interesting, especially the ability to extract text
from uploaded notes, even handwriting. It's not performing traditional
OCR, but it does build a list of likely words in each note. That's
enough to make search quite useful.</para>

<para xml:id="p2">Here we see a match for “America” in my barely legible scrawl captured
by <link xlink:href="http://www.jotnot.com/">JotNot</link>:</para>

<mediaobject role="flickr">
    <!--Evernote search-->
  <imageobject xlink:href="http://www.flickr.com/photos/ndw/4067864012/">
    <imagedata fileref="http://farm3.static.flickr.com/2631/4067864012_e9601362f9_d.jpg"/>
  </imageobject>
</mediaobject>

<para xml:id="p3">Even though this all seems pretty cool, I never really used it very much.
Part of the problem was that I didn't seem to be putting very much into it.
If you've only got six notes, you don't need folders or tagging or clever
search to find them.</para>

<para xml:id="p4">A few weeks ago, <personname>
      <firstname>Michael</firstname>
<surname>Mealling</surname>
    </personname>
<link xlink:href="http://twitter.com/mmealling/status/4844492645">pointed out</link>
that one way to fix
the data problem was to scan documents directly into Evernote.
<emphasis>That</emphasis> turned out to be an <emphasis>excellent</emphasis>
suggestion.</para>

<para xml:id="p5">For example, I've had a manilla folder of articles torn from magazines
in a drawer in my desk for ages. The threshold for getting torn out and
shoved in that folder was pretty high because, let's be honest, if I
put too many things in that folder, I'll neither remember what's there
nor be able to find it if I do remember.</para>

<para xml:id="p6">Twenty minutes with a scanner and suddenly I've got something that
I can tag, categorize, and search painlessly. What's more it's something
I <emphasis>have with me</emphasis> on my laptop or my phone or anywhere
I can get to a web browser: it's not in a folder in a drawer thousands
of miles away (as my desk is this week, for example).</para>

<para xml:id="p7">Of course, then I had a <emphasis>much bigger</emphasis> problem.
I am very, very reluctant to put my data in your application if I can't
get it back again. Repeat after me: no roach motels. I wish Evernote every
success in the world (I'm even doing my part, to the tune of $45/year, to
keep them around), but it's not hard to imagine a future in which I've
come to rely on them as a repository of important information only
to discover some Thursday afternoon that they've gone away or
<link xlink:href="http://www.wired.com/epicenter/2009/01/magnolia-suffer/">lost all
my data</link> or otherwise left me high and dry.</para>

<para xml:id="p8">To their credit and my relief, they have an API. It's not the sort
of RESTful Web API I've come to expect from these sorts of services, but
that's ok. It's published and documented and claims to support Java,
Perl, PHP, Python and Ruby out of the box.</para>

<para xml:id="p9">A few short hours of hacking and a few hundred lines of Python
and I had a backup tool that gets back everything I put into Evernote
<emphasis>and</emphasis> an XML representation of the search data.
What more could I ask for?</para>

<para xml:id="p10">(If you're interested in trying <link xlink:href="examples/backup-evernote.py">my backup script</link>,
you'll need to go through Evernote support to get your own API key and
configure a few lines to indicate where you want the files stored, but
after that it should work for you too. YMMV, of course.)</para>

<para xml:id="p11">My script creates an XML representation (natch!) of the details returned
by the Evernote APIs. Eventually, I'll probably decide to fix things so it doesn't
create a single potentially enormous file, but it doesn't much matter to
me at the moment because I turn around and drop this into the
<link xlink:href="http://www.marklogic.com/product/marklogic-server.html">MarkLogic
Server</link> instance that I use for my local PIM data.
</para>

<para xml:id="p12">Now, instead of collecting only the
<emphasis>very most</emphasis> interesting
articles I see and losing them in a folder, I collect anything that
interests me even slightly, confident in the knowledge that I'll
always be able to find it, and everything else, with ease. Alongside
those articles, you'll find scanned business cards, recipes, specifications,
notes, photographs of whiteboards and napkins, receipts, and a host of
other interesting words and ideas that I've captured as the universe pushed
them past me.</para>

<para xml:id="p13">Pretty sweet.</para>

</essay>

