From 8dd0b11cedd59f140e354bbf3d7238b84d14cebc Mon Sep 17 00:00:00 2001 From: Kyle Meyer Date: Thu, 5 Jun 2014 01:06:57 -0400 Subject: README rephrasing --- README | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'README') diff --git a/README b/README index 6ee1c9e..cf71e0a 100644 --- a/README +++ b/README @@ -27,10 +27,12 @@ The Bog workflow is focused around the citekey, which is the only study information that must be included in the notes. This unique identifier is used as a link to the BibTeX file and other associated files. -In the example below, the citekey "name2000word" is a study heading. Bog -expects the citekey to be the title or property of a heading. The -citekey "another1999study" is a reference to another study (which may or -may not have a subtree in this or another Org file). +In the example below, the citekey "name2000word" is a study heading. A +study heading is defined as a heading the has a citekey as a title or as +the value of =bog-citekey-property=. When a citekey occurs anywhere else +(like "another1999study" below), they are taken as a reference to +another study (which may or may not have a subtree in this or another +Org file). #+begin_example @@ -60,8 +62,8 @@ settings can be modified. Many Bog functions take the citekey from the notes. If the point is on a citekey (like "another1999study" above), then that citekey will be used. -Otherwise, the citekey will be taken from the first parent heading that -is a study (if that makes sense for the given function). +If this fails, many functions will try to take the citekey from the +first parent heading that is a study heading. - =bog-find-citekey-file= -- cgit v1.2.3