all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Clemente <n142857@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode for knowledge management
Date: Mon, 13 Oct 2014 10:15:33 +0700	[thread overview]
Message-ID: <87lhokd5ii.wl-n142857@gmail.com> (raw)
In-Reply-To: <871tqc3d2j.fsf@ericabrahamsen.net>

El Mon, 13 Oct 2014 10:42:28 +0800 Eric Abrahamsen va escriure:
> >
> > This is the bit I'm not sure about...
> >
> > * project_a
> > ** experiment about blah     :proj_name:theme:
> > [2014-10-11]
> >
> > Did x, y, and z today. Will analyze results tomorrow.
> >
> > [2014-10-12]
> >
> > Wow. Interesting finding. This will help a lot and may be relevant to
> > future projects!
> >
> …
> 
> Perhaps both links and tags are what you're after then: you could leave
> a link to the general finding inside "experiment about blah" (to remind
> yourself you took that note), but also use the tags to open Agendas on
> both project and theme, so you can see all the relevant information in
> one place.
> 


> > * project_a
> > ** experiment about blah     :proj_name:theme:

  I think it's crazy to use topics as tags. How many topics/themes are there? Wikipedia counts many million. Names of topic are very subjective. Topics are often mixed, split apart, refined, renamed, grouped in supertopics, …
  In org it's easy to remodel hierarchical headers but it's not easy to remodel tags (much less, hierarchical tags).

  So rather than:

** some construction          :plastics_engineering:


  I would have:

Engineering.org:
* Plastics
* Houses
* …


  I understand you use tags and „tag search“ to be able to look for bits of a particular topic in a file which is not related to the topic.
  It would be better to have a tag that in addition links to a particular tree. With that you'd have the freedom of tagging anything and the flexibility of headers.

  Some brainstorming about how to link tags with headers: Two options:

1) There is a main tag in a header, and the other tags link to it (with C-c C-o you navigate to the main tag).

proj1.org:
** some construction          :plastics_engineering:

Engineering.org:          :<<<plastics_engineering>>>:
* Plastics
* Houses
* …


2) You use links and you ask for backlinks

proj1.org:
** some construction [link to P]

Engineering.org:
* Plastics
  :ID: 1231212311122
* Houses
* …

And then… a key to *search for links to a header* („backlinks“). Can org do this now?.
E.g. you go to „Plastics“ and you search „all the backlinks found in proj1.org“. Then you have the generic knowledge and in addition all the bits of specific knowledge about that topic.


Maybe this is already possible… Whether it's useful, I don't know.

  reply	other threads:[~2014-10-13  3:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 22:17 org-mode for knowledge management Louis
2014-10-09 23:54 ` Marcin Borkowski
2014-10-10 15:46   ` Daniel Clemente
2014-10-10 21:40     ` mbork
2014-10-10 21:48     ` John Hendy
2014-10-11  2:53       ` Eric Abrahamsen
2014-10-12  4:54         ` John Hendy
2014-10-13  2:42           ` Eric Abrahamsen
2014-10-13  3:15             ` Daniel Clemente [this message]
2014-10-13  5:17               ` Samuel Wales
2014-10-14  3:47                 ` Daniel Clemente
2014-10-14  1:14               ` Eric Abrahamsen
2014-10-11 11:36       ` Daniel Clemente
2014-10-11 19:45         ` Brady Trainor
2014-10-12  4:29           ` Daniel Clemente
2014-10-12  5:03         ` John Hendy
2014-10-12  7:48           ` Daniel Clemente
2014-10-14  2:14             ` John Hendy
2014-10-10  0:18 ` Thomas S. Dye
2014-10-10  2:32   ` Louis
2014-10-10  2:34   ` Louis
2014-10-13 19:29   ` Louis
2014-10-13 19:36     ` Thomas S. Dye
2014-10-13 23:10       ` Louis
2014-10-13 13:11 ` Brett Viren

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhokd5ii.wl-n142857@gmail.com \
    --to=n142857@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.