wp-content/papercite-data
or
wp-content/blogs.dir/XXX/files/papercite-data
(in case of multiple sites hosted on WordPress), with
the following subfolders (none is mandatory):
bib
contains your bibtex filespdf
contains your pdf filestpl
contains your custom templatesformat
contains your custom entry formatsbib
folder, and your pdf files
into the pdf
folder. To match a bibtex entry with a PDF file, the
PDF file should have be named KEY.pdf
where KEY is the
bibtex key in lowercase, where :
and /
have been replaced by -
.You end with the following to print the list of references:
bibshow
and bibtex
optionsHere are the list of options that can be given to papercite.
Some of
these options can be set at a global level (through ) and page/post
level (using custom fields with a prefix
papercite_
). These options are shown .
First, some options are necessary to tell which bibtex file should be used:
file
: The default bibtex file (can be a URL)timeout
: The default time-out before reloading an
external resourceYou can modify how publications are displayed using several options:
key_format
: How to format the citing key of the publicationtemplate
: How to format the publication. At a
global level, bibshow_template
and bibcite_template
are used to distinguish
between the template used respectively for bibshow
and bibcite
format
: Template used to
format one BibTeX entryGrouping and order options
group
: How to group publicationsgroup-order
: Group sort ordersort
: How to order publications within groupsorder
: Sort order within groupsEach of these options are described next. Finally, the template language used to format entries is described on the bib2tpl site, with the following modifications:
@?field=abc@
is true if the field is
equal to abc (numeric comparisons are possible with > and <)format
For example,
The key_format
controls how a key is associated to a
BibTeX entry. From within a entry template, the value of the key is
given by @key@
.
The following values are accepted:
numeric
(default) gives a unique increasing number
to each entry (1, 2, ...)cite
uses the bibtex keyThe format described how an entry is displayed. The following format are currently available:
ieee
(default) is the default format loosely
based on IEEE
Eventually, the template
option controls which template
is used to format the entries. It is based on the tpl
code. For the moment, the following templates are defined:
default-bibtex
is the default template used for the
bibtex
commanddefault-bibshow
is he default template used for the
bibshow
commandFrom a pratical point of view, the final format follows bib2tpl. In order
to create a bib2tpl template, templates and formats are merged:
in the template, @#entry@
is replaced by the content
of the format file. This allows to decouple the formatting of
entries with the formatting of the full bibliography.
With the bib2tpl code, some extra variables are defined:
@WP_PLUGIN_URL@
will be replaced by the plugin URL.@papercite_id@
is a unique id within the page/post@key@
is a the key as formatted with key_format
.@pdf@
is the URL to the auto-detected PDF (or
to the URL specified in the PDF field).The grouping is defined by the group
value (year
, firstauthor
,
entrytype
or none
). Group are sorted
depending on the group_order
value:
none
: No orderasc
: Ascendant orderdesc
: Descendant ordersort
option together
by a description of the sorting key. Note that the sort
Entries (within groups) are sorted
depending on the sort
key (year
, firstauthor
,
entrytype
or none
). The ordering is also influenced by the order
value.
none
: No orderasc
: Ascendant orderdesc
: Descendant order