From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anders Johansson Subject: Re: Tracking Tags ?? Date: Wed, 23 Jan 2019 16:17:10 +0100 Message-ID: <87womvz9mx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmKHU-0006C2-9T for emacs-orgmode@gnu.org; Wed, 23 Jan 2019 10:17:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gmKHP-0005dz-Ez for emacs-orgmode@gnu.org; Wed, 23 Jan 2019 10:17:29 -0500 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]:38547) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gmKHL-0005Ys-BK for emacs-orgmode@gnu.org; Wed, 23 Jan 2019 10:17:23 -0500 Received: by mail-lf1-x130.google.com with SMTP id a8so1851219lfk.5 for ; Wed, 23 Jan 2019 07:17:21 -0800 (PST) In-Reply-To: DM6PR07MB553290F09BC9EDCC84D4812AA5990%40DM6PR07MB5532.namprd07.prod.outlook.com&Subject=%5BO%5D%20Tracking%20Tags%20%3F%3F List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: dsmasterson@outlook.com, emacs-orgmode@gnu.org > Anyone have a good method of tracking the Tags that you've use=20 > across > all of your Org files? Some sort of Tag Index to help you keep=20 > track of > the tags you've used and where you've used them so that you=20 > don't start > creating new tags that differ from old ones by (say)=20 > capitalization? Or > to help you find everything tagged a certain when you're moving=20 > to a new > tagging style? Perhaps an index where you could keep a note on=20 > why and > when you created the tag? > Is there any tools for this? I have struggled with similar issues in the context of using tags=20 for coding in qualitative data analysis. The stuff that I=E2=80=99ve=20 hacked together for solving this (pretty particular) use case are=20 available here: https://gitlab.com/andersjohansson/orgqda Maybe some of the ideas there can help? This is centred around projects (a bunch of files with research=20 material in text form) and I haven=E2=80=99t thought much about adapting=20 it to be used for all my org files. For a project, you can easily extract a list of all used tags,=20 rename and merge them. You can define a file for each project as a=20 codebook, where the use of each tag is documented. There is also a=20 more fancy tag-completion via helm that optionally fetches info=20 from the codebook file. Another approach for keeping a sort of index is John Kitchin=E2=80=99s=20 org-db http://kitchingroup.cheme.cmu.edu/blog/2017/01/03/Find-stuff-in-org-mode-an= ywhere/ Current code: https://github.com/jkitchin/scimax/blob/master/org-db.el --=20 Anders Johansson