I have very tentatively started to incorporate Evernote into my system. Evernote's proper place in definitely seems to be for elegantly managing general reference. (I already use Toodledo to manage tasks and projects, and am happy with it).
It took me a while to get to grips with the limitations of Evernote with regards to control over organisation. Really I think I was just forced to confront some existing uncertainties about managing general reference. Coming up with something 'complete' took a lot of thought, as none of the approaches I found from a quick Google search resonated with me. Below is the description I developed for myself but, as I said, I'm being very tentative about this so I'm looking to unearth any potential problems or - if I actually haven't missed anything – show off my own take on effective general reference management! What are your thoughts?
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
The approach
-Stacks behave as filing cabinets (so just having one GR stack should be enough)
-Tags and notebooks both behave as file folders
--Tags are used to file by topic, author or company
--Notebooks are used to group things by type of material (e.g., recipes, manuals, inspiring pictures) where helpful, with a 'general' notebook for anything without a clear 'type' category
-Hyphenated tags can be used where an item belongs to multiple 'topic, author or company' categories to subcategorise within each and an item would otherwise have to be mislabelled under one parent category or another.
This system is as simple as it can be, and as sophisticated as it needs to be, but it is delicate and could be undermined, become confused and collapse if not used mindfully.
Filing can still be done quickly, easily and intuitively without sacrificing control or flexibility. Filing this way can be done without being torn between different, seemingly incompatible ways of organising reference material ('style - inspirational pictures' Vs. 'inspirational pictures - style') or having to duplicate files. It is not necessary to organise past 'topic, author or company' where it would be unhelpful to do so but it is possible.
The hyphenated tagging seems cumbersome but you may never need it, and you'll be thankful for it if you do. I looked into hierarchical tagging as a more elegant alternative but Evernote requires tag names to be unique anyway, so it would not work as an alternative.
Considerations
-'Type of thing' categories (notebooks) should be preceded by a specifying word where the broader category would be uselessly wide-spanning. i.e., inspiring pictures, rather than pictures or pictures - inspiring. (Having the specifier before the 'type of thing' works as a failsafe against using second titles inappropriately.)
-Tagging issues: Plural v. singular, capitals v. lower case. Be consistent, though you probably would be anyway.
-Hyphenated tags should ONLY be used if there is a need to avoid contradictions in subcategories. Remember, the system is delicate and must be used properly.
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
So, what do you think? Anything worth adding to the list of considerations? Have I missed anything? Have I created a complex system and missed the simple alternative?
It took me a while to get to grips with the limitations of Evernote with regards to control over organisation. Really I think I was just forced to confront some existing uncertainties about managing general reference. Coming up with something 'complete' took a lot of thought, as none of the approaches I found from a quick Google search resonated with me. Below is the description I developed for myself but, as I said, I'm being very tentative about this so I'm looking to unearth any potential problems or - if I actually haven't missed anything – show off my own take on effective general reference management! What are your thoughts?
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
The approach
-Stacks behave as filing cabinets (so just having one GR stack should be enough)
-Tags and notebooks both behave as file folders
--Tags are used to file by topic, author or company
--Notebooks are used to group things by type of material (e.g., recipes, manuals, inspiring pictures) where helpful, with a 'general' notebook for anything without a clear 'type' category
-Hyphenated tags can be used where an item belongs to multiple 'topic, author or company' categories to subcategorise within each and an item would otherwise have to be mislabelled under one parent category or another.
This system is as simple as it can be, and as sophisticated as it needs to be, but it is delicate and could be undermined, become confused and collapse if not used mindfully.
Filing can still be done quickly, easily and intuitively without sacrificing control or flexibility. Filing this way can be done without being torn between different, seemingly incompatible ways of organising reference material ('style - inspirational pictures' Vs. 'inspirational pictures - style') or having to duplicate files. It is not necessary to organise past 'topic, author or company' where it would be unhelpful to do so but it is possible.
The hyphenated tagging seems cumbersome but you may never need it, and you'll be thankful for it if you do. I looked into hierarchical tagging as a more elegant alternative but Evernote requires tag names to be unique anyway, so it would not work as an alternative.
Considerations
-'Type of thing' categories (notebooks) should be preceded by a specifying word where the broader category would be uselessly wide-spanning. i.e., inspiring pictures, rather than pictures or pictures - inspiring. (Having the specifier before the 'type of thing' works as a failsafe against using second titles inappropriately.)
-Tagging issues: Plural v. singular, capitals v. lower case. Be consistent, though you probably would be anyway.
-Hyphenated tags should ONLY be used if there is a need to avoid contradictions in subcategories. Remember, the system is delicate and must be used properly.
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
So, what do you think? Anything worth adding to the list of considerations? Have I missed anything? Have I created a complex system and missed the simple alternative?