Table of contents
- File data structure
- BibTex entries: how to store BibTeX entries, how special bibtex fields are used
- Attached files: how files associated to one bibtex entry can be detected
- Usage: describes the two ways to use papercite
Using the Media Library
It is possible to use the WordPress media library. In this case, the name of the file is controlled by the permalink. By default, the permalink is a processed version of the file name: the name is lowercased, extension is removed, etc. Due to WordPress limitations, it is necessary to attach the media file to a post before being able to edit the permalink.
The matching process is determined by the papercite option page. See the help on attached files.
Note that bibtex files are matched using the same process, with application/x-bibtex as the mime-type and no suffix.
Location BibTeX entries
BibTex files can be stored:
- Anywhere on the Internet – papercite will download any file if the
- As a custom field prefixed by
papercite_. For example, the URL
custom://datawill use the data in the
For each bibliographic entry, files can be automatically matched to retrieve e.g. the paper PDF, or the slides.
First, the key of the bibtex entry is transformed – lowercased, and the characters
/ are replaced by
-. The field determines the bibtex field that will be populated when matching. Then,
WordPress media matching A file will match if its mime-type corresponds (or is empty) and its permalink name matches [key][suffix]
The URL of the matched file will be stored in the field
FIELD of the bibtex entry, and will be available by templates. For example, this can be inserted to display a link to a presentation:
@?ppt@ <a href="@ppt@" title='Download PPT' class='papercite_pdf'<img src='@PAPERCITE_DATA_URL@/img/ppt.png' alt="[ppt]"/></a> @;@
EXTand mime-type can all be set in the preferences. Papercite will process the list of such triplets, and will set the bibtex field to the last matched file (if any).
This is my whole list of publications:
This is my latest conference paper:
[bibtex file=mypub.bib key=CGW2006]
You can also have a list of keys to display more than one paper:
[bibtex file=mypub.bib key=CGW2006,CGW2007]
This is my bibliography maintained at citeulike.org
This is my bibliography maintained at bibsonomy.org
This is a bibliography stored in the
papercite_data custom field:
bibfilter command adds small html form where user can choose from authors and publication types. It does:
- displays simple form
- reads data from the form (what is selected)
- alters parameters (author & type) according to data from the form in the original command
- passes this modified command as “bibtex” for further processing
Example of use:
[bibfilter group=year group_order=desc author=Nahodil|Vítků allow=incollection,mastersthesis sortauthors=0]
bibfilter uses the same parameters as bibtex command, with these modifications:
sortauthors=0/1: sort authors alphabetically in the form if equal to 1
note: if no selection is made in form, bibtex parameters are not rewritten, this means that you can combine both commands as follows: -if no filter for type is made, bibtex command is called with e.g. type=INPROCEEDINGS|INCOLLECTIONS -the same for authors, the parameter “author” defines: -all authors for bibfilter menu -all authors for bibtex command
Known limitations: sorting names in the form does not work with Czech diacritics very well, (e.g. Šafář, Řasa..)
The second way of using this plug-in (new to papercite), is to use bibcite and bibshow commands
[bibshow file=mybib.bib] Here is one reference [bibcite key=key1] and some others [bibcite key=key2,key3]
You can use
[/bibshow] to end the bibshow section and print the list of references:
- If the
[/bibshow]shortcode is not present, then the bibliography is automatically displayed at the end of the page/post.
- If the option is set, the
[bibshow]tag can be automatically added when a
[bibcite]is encountered. In this case, a default bibtex file should be given in the options.
Here are the list of options that can be given to papercite.
- Bibtex parser (papercite >= 0.3.16): you can choose the pear parser (deprecated) or the OSBiB-based parser (default).
- Database backend (papercite >= 0.4.0): The database backend is used to store the result of bibtex parsing in a database, allowing to speed up the processing of shortcodes when the BibTeX file is big.
Some of these options can be set at a global level (through preferences) and page/post level. These options are shown
papercite_options field with one line per option in the format:
field_name = field_value
First, some options are necessary to tell which bibtex file should be used:
file: The default bibtex URL(s) separated by commas (see what are the valid bibtex URLs).
timeout: The default time-out before reloading an external resource
You can modify how publications are displayed using several options:
key_format: How to format the citing key of the publication
template: How to format the publication. At a global level,
bibcite_templateare used to distinguish between the templates used respectively for
format: Template used to format one BibTeX entry
show_links: Enable (1, default) or disable (0) use of hyperlinks from
bibciteentries to the resulting list of publications
highlight: Highlight name(s) of specific author(s)
- The publication type can be fitered using
- Publications can be filtered by author using the following syntax:
author=name1&name2&name3. Filtering can match also authors whose name is substring of some other name (e.g. name “Su”). and is case sensitive in names which start with diacritics (e.g. Řehoř, Šimon..)
- The number of items to be displayed can be limited with the
limitargument. Its value, if greater than 0, gives the maximum number of items to be displayed
Grouping and order options
group: How to group publications
group-order: Group sort order
sort: How to order publications within groups
order: Sort order within groups
Each 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@ gives the number of entries in a field (author or editor)
- Conditions can be more expressive, e.g.
@?field=abc@is true if the field is equal to abc (numeric comparisons are possible with > and <)
Some options modify the bibtex processing:
process_titlescan be set to 1 (normal BibTeX behaviour – lowercase everything which is not between braces) and 0 (no processing)
You can modify the style of the citations by using the
format For example,
[bibtex file=mypub.bib format=ieee template=default-bibtex key_format=number]
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, …)
citeuses the bibtex key
The format described how an entry is displayed. The following formats are currently available:
Feel free to contribute new formats, but note that in the future the citation style might be written using the Citation Style Language (CSL).
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-bibtexis the default template used for the
av-bibtexis another template for the
bibtexcommand. It adds support for
abstractfield (toggled like the bibtex entry), explicit
doi:link and a Download PDF link for
default-bibshowis the default template used for the
From a practical 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 This to decouple the formatting of entries with the formatting of the full bibliography.
With respect to 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
@pdf@is the URL to the auto-detected PDF (or to the URL specified in the PDF field).
Here are some more general modifications:
- More generally,
@#fieldnameprints the number of entries in the field name (works with authors, editor and pages)
- A general if-then-else structure can be encoded by
@?condition@ ... @:@ ... @;@, where the “else” and “end if” can be used in a short version (no need to specify the condition), and where the condition can be more elaborate than in bib2tpl: you can use the operators
||with the same semantics as in main programming languages.
CSS can be used to customize the display of entries. Again, do not customize directly papercite files, this would be overwritten with plugin updates. The best solution is to use a plugin such as Simple custom CSS that allows custom CSS to be written and stored within the WordPress database.
In the default templates, the following classes are used:
papercitefor headers like the
h3header for grouping key display
papercite_entryfor a single bibtex
papercite_bibtexfor the bibtex code
papercite_pdffor the PDF link
papercite_doifor the DOI link
highlight option can be used to highlight specific parts of an author or editor list (see here for an example). You can specify arbitrary regular expressions. Each match of the regular expression will then be highlighted. For example,
[bibtex highlight="M. Mouse"]
will highlight all occurences of M. Mouse. Similarly,
[bibtex highlight="M. Mouse|D. Duck"]
will highlight all occurences of M. Mouse or D. Duck.
You can group the citations using the
group option with values
none (by default),
entrytype or any other valid bibtex field. You can order the groups using the
group_order option which can take values among
none (none by default).
[bibtex file=mypub.bib group=year group_order=desc]
The grouping is defined by the
group value (
none). Group are sorted depending on the
none: No order
asc: Ascendant order
desc: Descendant order
You can sort the citations using the
sort option together by a description of the sorting key. Note that the sort
[bibtex file=mypub.bib sort=year order=asc]
Entries (within groups) are sorted depending on the
sort key (see grouping for the list of possible keys). The ordering is also influenced by the
none: No order
asc: Ascendant order
desc: Descendant order