kilavos 11 Posted March 10, 2016 Share Posted March 10, 2016 There are some discussions during the last years e.g. https://discussion.evernote.com/topic/57740-the-benefit-of-using-tags/ https://discussion.evernote.com/topic/35420-nested-notebook-stacks https://discussion.evernote.com/topic/93389-do-you-find-lots-of-notebooks-or-notebook-stacks-useful with a lot of convincing arguments, some good sample szenarios and statements - but also some misunderstanding and conventionalism to different szenarios - anyway, that's how I understand Evernote and its features. What do I mean? Basic considerations: in our private/office surroundings we are used to store a piece of paper in a tray, many papers in a folder, folders in racks etc. Physically (!) organized according to the categorie (shipping note, letter...), date (year...) etc. Similar to groceries in the kitchen. These objects are real and in relatively small quantity. And we have a certain place in mind (folder, rack) where to store - and to find (!). But when the quantity increases to thousands (like in a stock) and furthermore gets virtual like in a database like Evernote. Organization is done not by physics, but by information management. Not a certain place is relevant for organization, but other items. As a result the objects (goods in stock, files in computer, data in database) are stored chaotically (files - even cut in pieces, the FAT knows ...). How to organize this chaos? Well, each object gets one or more flags with description(s) of the essential features (producer, type of device, identifier, ...). What does this mean for Evernote? (The following items are valid - in my view - for those who use Evernote as a big database with occasional access as for those with daily intensive use in conjunction with shortcuts/favorites...) notebooks: there is no need for more than one=1 notebook (or only a few). As they do (should!) not have any relevance to organizational methods. Exception: (1) synced notebooks and local notebooks=no cloud=no syncing (2) notebook sharing in business version, (3) archive (not necessarily), (4) temperary purpose (as shown below). tags: they are the above mentioned flags. And - with an intelligent (!) nomenclatura - in a very effective manner. Name and structure of tags has to consider their handling: (1) tagging=assign one ore more tags (2) search via task symbol or left column (Windows) or saved search (3) shortcut/favorite. that means: criteria are (a) as few tags as possible (b) self-explanatory names (c) easy tagging via task bar icon (d) easy search via task bar icon task hierarchy: this is a logical (!) synopsis where the user can build a structure of tags. It only is of logical interest with user-relevant topics. And this must be understood - for the behaviour of Evernote this structure is completely non-relevant. There is no effect if a tag is located in the 1. or 2. or...level n. And that means: there is no relationship between the logical tag structure/hierarchy and the mode of operation of the tags. Expressions like "nested tags", "child-tags", "parent-tags" put the focus to an apperent properties which do not exist. (one implication following: the names of tags must be unique, even if they are located in different levels). You may swirl the above shown structure e.g. put all categories and tags in level 1: the logical structure is gone, but the tags work in the same way as before. Example (extract) in consideration with my own tag synopsis: transferring this blog via task bar icon to my Evernote I tag as follows: .WHEN .WHAT = category 1. level .IT = category 2. level .IT_Evernote = category 3. level IT_en_forum = tag 4. level IT_en_literature IT_en_syntax IT_en_tag = tag 4. level .IT_software IT_soft_windows10 .IT_hardware IT_hard_SSD .projects .projects_active proj_2016_SchermElectronic_PreAmplifier .projects_finished xproj_2015_Beyerdynamics_DT880 .WHO .company comp_Microsoft .media media_NYT media_xyz .person pers_TMichael = tag 3. level .WHERE .city city_washington city_london Given tasks are bold faced. Three tags on 3. and 4. level - number of level doesn't make any difference tags with a prefix (. oder @ or # ) are not used as tags - they are catagories, classes in order to organize in a logical/topical manner. tags are only those without any prefix. And these "real" tags are always in the highest level of the appropiate tree. Never the 1st oder 2nd in my synopsis. The naming of the tags follows the class. "pers_TMichael" indicates, that the tag belongs to the class "person" (shortform "pers") and the name of the person is "TMaichael", separated by a "_" (do not use space, because of more difficult use in searches). This has advantages for tagging and searching procedure: input of "pers_" lists all task with this leading expression. Even for a list of all notes which have the "pers"-prefix: make a search like "tag:per_*" and you will get all notes with tagged as persons. (same with "tag:IT_en_*" shows all notes with Evernote-tags). Advantage: the Evernote user only has to remember resp. keep in mind a small quantity of categories like "IT_en" or "pers", the rest will be listed by Evernote. Not hundreds or thousands of tags to remember. The part ".projects" (every project contains a bunch of notes) will show two items: name of tag might contain catagory and more than one identifier to differ and inform as well. When the project ist finished, the tags gets the prefix "x" and is moved to the project_finished section. The according notes themselves are not involved which is logical: this does belong organization and not the contant of the notes. Thus one has access to all active projects with "proj_" and to finished projects with "xproj_". And how to manage a project with a bunch of notes? This is another question...remember the barkeeper in "Irma la Douce"? With this tag naming I don't see any need for tagging the whole bunch of tags from the 1st up to the highest level proposed by JMichaelITX. There is no advantage but much more work. (even in case of listing all WHAT-notes one can do this with a temporary tag; but I don't think this is a realistic or often used szenario). Thus said the pseudo NB tags which are proposed by JMichaelITX do not make any sense in my opinion. The names in the first level in JMichaelITX's synopsis start with NB. What happens if you drop this NB and make it Business, Personal, IT etc. - nothing. Simulate the existance of notebooks which do not exist is self-deception. It is more confusing than illustrative, the "NB" is an empty statement. I think it is better to change way of thinking and stop using notebooks for organization, even as pseudo or wannabe. Last but not least: JMichaelITX mentioned the use or reminders with these pseudo NB-tags. But - what about using a search like "remindertime:*" or "remindertime:day -remindertime:day+2" or "remindertime:year -remindertime:year+1" and so on ? And if you use check boxes too: "-remindertime:day+2 remindertime:day-7 todo:false" will list tasks with reminders from last week till tomorrow. Transfer these and other saved searches to shortcuts and position them on top of the shortcut list. Done. I agree, this approach (tag naming etc.) is not new, often proposed and discussed in similar modes in this forum. Nevertheless my impression is that many users don't see the difference between tags themselves (function, importance, usage) and the nature, properties of the tag synopsis. As well as being proud to use no or only a few tags. Or flag their notes with keywords in the title. And so on.. Waiting for constructive criticism, counter-arguments, improvements, questions... Link to comment
This topic is now archived and is closed to further replies.