From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Tue, 23 Sep 2014 09:52:26 -0400 [thread overview]
Message-ID: <87bnq6wijp.fsf@yale.edu> (raw)
In-Reply-To: 87ppem8oo7.fsf@grothesque.org
Christoph Groth writes:
> But not all is good:
>
> - Scaling: Some simple tests seem to indicate that org mode
> becomes too sluggish with files of about 50k lines. This is a
> dimension that could be easily reached over 10 years if the
> file grows by 20 lines per day on average. This is not a
> problem in the beginning, but if the scheme does not scale to
> a few thousand entries, this renders the whole idea way less
> interesting.
> - More advanced searching is lacking: AFAIK org mode currently
> does not support searching for articles of a given author that
> also contain a given keyword in the notes.
> Any insights about these two problems? Perhaps the scaling could
> be managed by splitting index.org into several files (by year
> for example). But how to search then? It's probably not a good
> idea to add all the bibliography org-files into the agenda. (Is
> there a way to have a secondary list of agenda files?) Perhaps
> the solution for both problems would be to write a fast
> commandline query tool for such org-databases? The tool could
> even use a fast cache if necessary.
BibTeX provides bibtex-search-entries (in a bib file it is bound
to C-c C-a), which searches for entries with a certain field
matching a regexp. Perhaps you want to take advantage of that
function to direct your org searches to bib files and back. Check
also bibtex-files and bibtex-search-entry-globally, since you
would then be able to split the org files and export into several
bib files if a single bib file proves too much. My current
articles.bib is about 14k lines, and it is not sluggish at all,
but I will have to wait a couple of years until I tell you if a
50k one would be.
Best,
--
Jorge.
prev parent reply other threads:[~2014-09-23 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 20:50 Managing articles in orgmode and collaboration Christoph Groth
2014-09-09 9:13 ` Christoph Groth
2014-09-09 10:48 ` Thorsten Jolitz
2014-09-09 11:40 ` Christoph Groth
2014-09-09 12:18 ` Vikas Rawal
2014-09-09 12:24 ` Fabrice Popineau
2014-09-09 12:48 ` Thorsten Jolitz
2014-09-09 14:22 ` Samuel Loury
2014-09-09 20:25 ` John Kitchin
2014-09-09 16:34 ` Thomas S. Dye
2014-09-09 16:56 ` Jorge A. Alfaro-Murillo
2014-09-09 17:30 ` Rasmus
2014-09-10 10:31 ` Christoph Groth
2014-09-10 14:33 ` Jorge A. Alfaro-Murillo
2014-09-23 13:14 ` Christoph Groth
2014-09-23 13:52 ` Jorge A. Alfaro-Murillo [this message]
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=87bnq6wijp.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).