From: David Masterson <dsmasterson@outlook.com>
To: Anders Johansson <mejlaandersj@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Tracking Tags ??
Date: Thu, 24 Jan 2019 01:07:23 +0000 [thread overview]
Message-ID: <DM6PR07MB5532945EC4B65DBAA217F59DA59A0@DM6PR07MB5532.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87womvz9mx.fsf@gmail.com> (Anders Johansson's message of "Wed, 23 Jan 2019 16:17:10 +0100")
I wrote:
>> Anyone have a good method of tracking the Tags that you've used across
>> all of your Org files? Some sort of Tag Index to help you keep track
>> of the tags you've used and where you've used them so that you don't
>> start creating new tags that differ from old ones by (say)
>> capitalization? Or to help you find everything tagged a certain way
>> when you're moving to a new tagging style? Perhaps an index where
>> you could keep a note on why and when you created the tag?
>>
>> Is there any tools for this?
Geez, my grammar is terrible because I dropped words! (fixed)
Anders Johansson <mejlaandersj@gmail.com> writes:
> I have struggled with similar issues in the context of using tags for
> coding in qualitative data analysis. The stuff that I’ve hacked
> together for solving this (pretty particular) use case are 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
> material in text form) and I haven’t thought much about adapting it to
> be used for all my org files.
Interesting. It seems you're building an Emacs internal database of
tags stored in Emacs variables. I'm thinking it might be better to
store the information as Org meta file where a header is a tag and under
that might be a note and a table of references to where the tag is used.
> For a project, you can easily extract a list of all used tags, rename
> and merge them. You can define a file for each project as a codebook,
> where the use of each tag is documented. There is also a more fancy
> tag-completion via helm that optionally fetches info from the codebook
> file.
Still learning helm and how it applies.
> Another approach for keeping a sort of index is John Kitchin’s org-db
>
> http://kitchingroup.cheme.cmu.edu/blog/2017/01/03/Find-stuff-in-org-mode-anywhere/
> Current code:
> https://github.com/jkitchin/scimax/blob/master/org-db.el
Hmm. Beyond my Emacs hacking...
Thanks.
--
David
next prev parent reply other threads:[~2019-01-24 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:17 Tracking Tags ?? Anders Johansson
2019-01-24 1:07 ` David Masterson [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 0:53 David Masterson
2019-01-23 18:24 ` Colin Baxter
2019-01-23 18:46 ` John Kitchin
2019-01-23 19:48 ` Colin Baxter
2019-01-23 20:22 ` John Kitchin
2019-01-23 21:57 ` Ken Mankoff
2019-01-24 1:12 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR07MB5532945EC4B65DBAA217F59DA59A0@DM6PR07MB5532.namprd07.prod.outlook.com \
--to=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=mejlaandersj@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).