IncrediMetaBeta 22 Posted December 20, 2016 Share Posted December 20, 2016 Is there a workaround to getting a tag list? Is using SQL on a copy of the .exb file possible? I've noticed a number of posts on the forum about obtaining a tag list. They seem to dwell on 1) you cannot export or print a tag list in EN and/or 2) it would be a nice feature to have and will you please make it immediately or yesterday. It appears that none of these posts has yielded a definitive answer about a workaround. I have about 3,000 tags. That number is rapidly growing. I access EN two ways: EN for Windows and online in Chrome. I curate the tags in a hierarchy. I am aware that the prevailing consensus seems to be that tags are a superior way to organize one's EN content than notebooks, at least beyond some threshold volume of notes. But it has become tough to organize tags. My tags and their hierarchy are in continual flux as I add notes. I have about 35,000 notes. I continue to add tags and to delete and rearrange them. I am experimenting with the use of "special characters," ie., punctuation characters, to establish various categories. By "curation" I mean inspecting how the tags are organized (naming conventions and hierarchical arrangement) to be sure there is internal consistency. Part of the difficulty in doing so is that: a) there are so many; I can only see a small subset of them at a time; c) lacking an overview, I tend to have several curation and re-organization efforts going on concurrently and/or only partially implemented. d) these curation and re-organization efforts can be in conflict. The whole effort has become analogous to examining an entire landscape sequentially by examining parts of it through the narrow aperture of a drinking straw. But examining things sequentially can never replace simultaneous examination. I want to see all the tags. I need an overview, and to see their hierarchical organization at a glance. I am aware that there is no feature in EN to either print or export tags. Can I extract the tags using SQL? Doing so would not change the actual working file. I could use a copy of my .exb file (Windows platform), perhaps renaming it to a .db, and obtain from that renamed file a list of all of my tags. I recognize it is not good to go into the original backend database file with SQL tools. I would never touch that. It would be helpful to get even just a tag list, regardless of the hierarchical level of each tag. Getting the tags in their hierarchy would be good, though it's not strictly necessary. If you believe that it is infeasible to access the tags in a read-only manner via SQL, please let me know if you are aware of some other option. For example, alternately, is there some third-party software, perhaps analogous to VB for Office, or some macro-like utility of some kind, that would enable me to copy the tags successively, whether from within EN for Windows or EN in my browser, and paste them into MS Word? I am confident that it will be infinitely easier to manage them, once I have them in a word-processing document. I will be able to see the tags and their hierarchical position all at once rapidly, to grok relationships among them, disparities; similar, duplicative labels, etc. Changes to them in a Word doc can then be easily made in the original EN file. I would welcome any suggestions. That said, I do not imagine it would be helpful to question, why do you have so many tags? If you are thinking in those terms, please realize that you may be using EN for entirely different purposes and/or not have as much content. I have about 35,000 notes. Consider that the interrelationships among notes increase enormously as you add new topical areas. I want to track these with the tagging system. Nor do I imagine it would be helpful to ask, how can you use so many notes? Consider that, for the value that I wish to create, I do not need to use them all. Nor is it possible at the moment that I clip them to determine either exactly how I might use them or the likelihood that I will do so. Please realize that the process of capture with EN is often done intuitively, rather than with extensive planning aforethought. In that respect, EN is (or should be) not only a way of managing information. It is also (or should be) a way of managing how to allocate one's limited attention. Likewise, scrolling through a very lengthy tag list in EN for Windows does not support human cognitive strengths and inherent limitations. Link to comment
This topic is now archived and is closed to further replies.