From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining a knowledge-base ?
Date: Sat, 9 Jan 2010 22:58:23 +0000 (UTC) [thread overview]
Message-ID: <87wrzqyjg8.fsf@mean.albasani.net> (raw)
In-Reply-To: 000e0ce0d5d8ec0c7a047cbbd544@google.com
Hi,
d.sturb@gmail.com writes:
> I was wondering if anyone uses org-mode for this kind of use, and
> would really be interested in reading how you maintain such a system.
> I'm especially interested in methods that relate to structuring and
> 'querying' the knowledge base, since it's of no use if information
> can't be found easily.
I have a similar file; it started as a place to collect interesting
bookmarks in and is naturally named bookmarks.org.
Step by step, it evolved to be my location for all kinds of information
- not only from the interwebs - that I want to keep.
For me, the outline is enough to maintain the structure.
I have some level 1 headings loosely related to my interests, like
* University
* Latin
* Emacs
** Org
** Gnus
...
* Quotes
...
* Unsorted (yet)
etc. The last heading is my default inbox for everything new.
I let stuff linger there for a while to make my mind up if it is really
worth keeping. Whenever I have some time left (or too much accumulated
there), I sort them in my Level 1's or delete them if they are not that
important on a second glance.
Up to now, I had no trouble finding anything, either looking into the
appropiate heading or just using C-s. Its all just text ;).
So no tags or properties needed so far, but most items are not related
to each other, so I have no use for heavily linking, yet.
Nice thread, I am interested what others will say.
next prev parent reply other threads:[~2010-01-09 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 14:08 Tips on maintaining a knowledge-base ? d.sturb
2010-01-09 14:56 ` Ian Barton
2010-01-09 22:58 ` Memnon Anon [this message]
2010-01-10 11:20 ` andrea
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=87wrzqyjg8.fsf@mean.albasani.net \
--to=gegendosenfleisch@googlemail.com \
--cc=emacs-orgmode@gnu.org \
/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).