From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: CHARPENTIER Emmanuel <emmanuel.charpentier@aphp.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"jkitchin@andrew.cmu.edu" <jkitchin@andrew.cmu.edu>
Subject: Re: should a BIBLIOGRAPHY keyword supercede org-cite-global-bibliography?
Date: Mon, 19 Jul 2021 13:40:48 -0400 [thread overview]
Message-ID: <CAF-FPGNeiZ52KFCuW1HgOtZ+CC7y1zRuhHxn+cnayEWSOMDx2g@mail.gmail.com> (raw)
In-Reply-To: <d2c44155b876d0357cac47926256c9703ce8eb14.camel@aphp.fr>
Yes, you're right Emmanuel.
I guess this goes back to my file type/extension issue then.
I do expect this to be a non-issue in time though, as related packages
update to fully support all three common input formats.
On Mon, Jul 19, 2021 at 1:29 PM CHARPENTIER Emmanuel
<emmanuel.charpentier@aphp.fr> wrote:
>
> > It seems like that should not be the case, i.e. if you define
> > BIBLIOGRAPHY keywords it means you do not want to use the ones in
> > org-cite-global-bibliography. Is there a scenario where the union of
> > those makes sense?
>
> Yes indeed: you may have
> - A library for background issues (e. g. methodology)
> - A (or several) subject matter-specific library (e. g. a
> subdiscipline, a method, etc...)
> - A library specific to the question you are discussing (e. g.
> results of a bibliographic search specific to your question).
>
> The first one is a perfect target for org-cite-global-bibliography. The
> last one is of course a target for #+BIBLIOGRAPHY ; I'd tend to let the
> subject matter library as a file-specific #+BIBLIOGRAPHY (my subject
> matters tend to vary...), but this depends on your field.
>
> You may also think of this typology as books, reviews and research
> papers respectively...
>
> HTH,
>
> --
> Emmanuel Charpentier
>
next prev parent reply other threads:[~2021-07-19 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 17:29 should a BIBLIOGRAPHY keyword supercede org-cite-global-bibliography? CHARPENTIER Emmanuel via General discussions about Org-mode.
2021-07-19 17:40 ` Bruce D'Arcus [this message]
2021-07-19 17:54 ` John Kitchin
2021-07-19 18:06 ` Bruce D'Arcus
2021-07-19 18:07 ` CHARPENTIER Emmanuel via General discussions about Org-mode.
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 16:07 John Kitchin
2021-07-19 16:18 ` Bruce D'Arcus
2021-07-20 0:01 ` Vikas Rawal
2021-07-20 0:52 ` Thomas S. Dye
2021-07-20 1:42 ` Bruce D'Arcus
2021-07-20 8:03 ` 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=CAF-FPGNeiZ52KFCuW1HgOtZ+CC7y1zRuhHxn+cnayEWSOMDx2g@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=emmanuel.charpentier@aphp.fr \
--cc=jkitchin@andrew.cmu.edu \
/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).