Last time, I talked about how and why I simplified my notebook organization in Evernote. Today, I’ll discuss how I’ve simplified my tag organization. Both are still works in progress, but the tags more so than the notebooks.
To start, let me say that I’ve never been much of a tagger. There are several reasons for this:
- Evernote has a powerful search engine that usually allows me to find whatever I’m looking for in just a few seconds.
- With such a good search engine, adding tags is usually counterproductive for me, since it takes time to add them to a note, but I can find the note just as easily without them.
- Tags have a tendency to grow like weeds. I’d end up with a huge number, and when I look at them, I find that more than half my tags have less than 10 notes associated with them.
- With lots of tags, there is a tendency to forget how I’ve tagged something. In some places, it gets tagged “project” in others “projects.” This actually make searching by tags worse. If I search for everything tagged “projects” I don’t get the notes tagged “project” for instance.
That said, I do find value in tagging notes under certain circumstances. Regular readers will recall this diagram:
I find tags very hand for describing the “who” part of a note. I assign family member names as tags to notes to denote who that note is related to. Tags can sometimes be helpful with the “what” as well, but in all cases, a solid taxonomy is important for preventing uncontrolled tag growth. I’ll talk about that in a moment. First, let me show you what my tags used to look like.
My old tagging system
My old tagging system had 147 tags. Notes with tags are a little tricky because some notes have multiple tags and that obscures the actual count. However, a better measure in my opinion is how many tags were associated with 10 notes or less. In the old system 83 tags had 10 notes or less. Put another way, 56% of my tags had 10 notes or less.
10 notes is somewhat arbitrary, but it works for me. Of course, tags have to start somewhere, but generally speaking, these tags never really got used beyond their initial creation.
The system was flawed in other ways. There were inconsistent uses of the tags, and no real taxonomy with which to guide their usage. In my new tag organization, I’ve tried to fix that.
My new tax taxonomy
When I decided to simplify my tasks, the first thing I did was sketch out a taxonomy for the tags that would ensure that they did not grow accidentally. I also wanted to taxonomy to be a useful guide for what I used tags for. This taxonomy can be broken into two parts, the tag grammar, and the tag usage.
My tag grammar
The grammar is pretty simple. There are 3 rules:
- Tags will be lowercase.
- Tags will use hyphens instead of spaces.
- Tags will always be singular.
Let me explain each of these.
Lowercase just is more for uniformity of the look-and-feel, and to avoid unnecessary decision-making. Whether the tag is some thing, like bill, or a proper noun, it will always be rendered in lowercase.
Using hyphens instead of spaces actually makes searching a little easier. If I have a tag called “kitchen remodel”, I need to use quotes around my tag when I am searching. In other words, my search would look like this:
However, if I use a hyphen instead of the space, I don’t need the the quotes around my search:
It might not sound like much, but it saves some frustration (plus 2 characters for every search). It also helps to ensure I don’t get weird search results by typing something like this:
which actually looks for notes tagged “kitchen” that have the word “remodel” somewhere in the note.
As far as the tag always being singular, this helps avoid confusion. Should I call it “project” or “projects”? I no longer need to worry about that decision. It is always singular. I like singular because in the context of a single note, it makes sense. A note tagged “project” is clearly part of a project. “Projects” just sounds awkward to me.
This, of course, is personal preference, but having these three rules of grammar at the outset made it much easier to consolidate and simplify my tags.
My tag usage
Having established a basic grammar, I wanted to define how and when I’d use tags so that it was clear for any given note that I created. Actually, I already had a basic framework which I defined in a post back in January 2013. I tend to see my notes falling into one of four general categories:
- Documents. Notes with attachments like PDFs, Word files, images, etc.
- Events. These are notes that represent some event on a timeline. They could be notes from a meeting, or, more often than not, something that gets into Evernote through some automation I’ve set up, like a Foursquare checkin via IFTTT.
- Milestones. This is a special class of events that represent some achievement that I want to identify specifically. The day the Little Man graduated from pre-school, or the day the Little Miss said her first word.
- Information. These tend to be just plain vanilla notes. Maybe a shopping list, maybe an address that I jotted down, maybe something I clipped from the web.
Each of these general categories has its own usage, and so I tried to come up with a clear usage definition for each one. For instance, here is my usage for Documents:
This is a [___________] ______________ for _________________ Category Document Type Entity
When I am tagging a document, say one that I’ve scanned in, I use the above template to tag it properly. I say to myself that the thing that I just scanned is a tax form for Jamie. Or, if you want to see it in the template:
This is a [_tax_______] _form_________ for _Jamie___________ Category Document Type Entity
Note how neatly this model fits with my grammar? Three tags will get added to the note. All 3 are singular. All will be lowercase when I add them to the note, and use hyphens instead of spaces.
The brackets around Category mean that it is optional. I use it where appropriate, and don’t use it where it doesn’t make sense.
The category is a fairly broad classification, with a set number of tags that I try to keep as narrow as possible. It includes things like tax, medical, dental, retirement, school, insurance.
The document type is more narrow in scope, focusing primarily on the type of document: form, paystub, receipt, statement, and contract are among the most common ones that I use.
An entity is the person, company, project or organization to which the form is related. And yes, there can be more than one entity tag for a given document. So a medical form for the Little Man’s school might look something like this:
This is a [_medical___] _form_________ for _little-man, school_ Category Document Type Entity
The note gets 4 tags: medical, form, little-man, and school. If I search for all documents tagged little-man, this will show up. If I search for all documents tagged “medical” and “form” this will show up. You get the idea.
For notes that represent events and milestones, if they get tagged at all, the generally get entity tags. In other words, who or what is this tag related to?
What does my new tag organization look like?
While my tags are still more of work-in-progress than my notebooks, I have really made an effort to clean them up and bring them inline with my grammar and usage. Here is what my tag structure looks like today:
I’ve gone from 147 tags to 76–I’ve nearly cut my total tags in half. 29 of my 76 tags have 10 notes or fewer associated with them. That’s still a fairly high percentage (38%) but in this case, I know that most of these will increase over time as more notes are brought into this framework.
And you’ve probably noticed there are still a few problems:
- There is a “benefits” tag, which should be renamed “benefit”
- And there is the awkward “Disney.2012” tag which is really there as a placeholder that will eventually go away. Part of the process of simplifying my tags has involved building a temporary scaffolding that eventually gets taken down when all of the work is done.
Some tips for simplifying your own tags
As I went through this process, I gained a few insights that might be useful to others who plan on doing the same. These are not taxonomy specific, more process-specific on how you go about simplifying your structure.
- Export all of your notes with tags before you get started, so that you have a backup if you really screw things ups.
- Grab a snapshot of your Tags page before you get started so you have a baseline to work from. I grabbed mine with Skitch and stored it right in Evernote.
- Write down your taxonomy before you get started. This may seem tedious, but I can’t emphasize enough how much it helped me to have a clear, unambiguous taxonomy to work from.
- Tackle the low-hanging fruit first: if you are just renaming a tag, all you need to do is right-click on the tag in your tag page and click Rename…
- Be sure to sync Evernote after your updates so your changes propagate to all of your devices.
When you’ve finished with your updates to your tag organization there are a few post-update tasks to keep in mind:
- Test out your new organization to make sure it works the way you expect.
- Don’t forget to update any saved searches you have. Change a tag name does not update your saved searches. They need to be updated manually.
- Don’t forget to update tags at external integration points. If you have the Web Clipper automatically tag your notes, you’ll need to be sure to update the tags there. If you use IFTTT and include tags in your workflow, you’ll want to update your tags there as well.
- If you have email messages set up to automatically send email to Evernote, and include tags in the subject line, you’ll want to make sure to update those tags (in the subject line) as well.
So far, I’m pretty happy with my new, simplified organization of notebooks and tags. It feels leaner, and more agile, and it is definitely easier to use than it was before I cleaned things up.
If you have a suggestion for a future Going Paperless post, let me know. Send it to me at feedback [at] jamietoddrubin.com. As always, this post and all of my Going Paperless posts is also available on Pinterest.
Last week’s post: How I Simplified My Notebook Organization in Evernote (Part 1).