From: Andreas Burtzlaff <andy13@gmx.net>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Workflow for attaching, linking, and saving bibtex links together with notes?
Date: Wed, 12 Aug 2009 09:31:56 +0200 [thread overview]
Message-ID: <20090812093156.75cd1703.andy13@gmx.net> (raw)
In-Reply-To: <7bef1f890908111944t3cfef53cyf1fd1e2819e7c387@mail.gmail.com>
The use case is very similar to the one I'm starting to get comfortable
with, so here is my vision:
Fireforg could download the pdf , use Zotero's translators to extract
bibliography information and other metadata from a site, and send that
and the file's path to org. There, this information becomes a heading
with properties, like this:
* [[<link to pdf>][<Title>]] <General note>
:PROPERTIES:
:ID: <unique id>
:CUSTOM_ID: <human readable id, possibly generated from authors and year>
:BIB_TYPE: <article, ...>
:BIB_AUTHORS: ...
:BIB_TITLE: ...
...
:URL: ...
:END:
All further notes go into that subtree.
A lisp function generates bibtex entries from these properties for headings,
optionally filtered by tag, property, occurrence of links to it in a certain file, etc.
That way, all information is inside the org file and the entry has a
unique id throughout.
In search results fireforg will mark those entries already imported to
your org files and let's you visit all notes about them.
There are some hurdles to take, though, but it's not overly complicated.
Anyone willing to join in, to make this reality?
Andreas
P.S. Didn't check whether such an idea came up before on the list.
PP.S There was a similar question in this thread:
http://thread.gmane.org/gmane.emacs.orgmode/14756/
next prev parent reply other threads:[~2009-08-12 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 2:44 Workflow for attaching, linking, and saving bibtex links together with notes? Alan E. Davis
2009-08-12 4:25 ` Alan E. Davis
2009-08-12 7:31 ` Andreas Burtzlaff [this message]
2009-08-12 9:34 ` Eric S Fraga
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=20090812093156.75cd1703.andy13@gmx.net \
--to=andy13@gmx.net \
--cc=emacs-orgmode@gnu.org \
--cc=lngndvs@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).