Nicola L. C. Talbot
24nd November 2005
The raeisf.cls class file is designed to produce the UEA review for RAE 2008 Individual Survey Form, for those who would rather use LATEX, instead of Word. It makes it a lot easier to fill in the form if you already have all your publications in a BibTeX database. This class file is based on the article class, and requires the following packages: geometry, longtable, bibunits, ifthen and rotating. Please make sure you have all these packages installed on your system before you use this class file.
When you LATEX your document, you will also need to run BibTeX on all the bu*.aux files created by bibunits. The bibunits package comes with a shell script called bibtexall which runs BibTeX on all .aux files found in the current directory. This unfortunately includes the main auxiliary file, however the script can be modified slightly so that it only runs BibTeX on the bu*.aux files:
#!/bin/bash for file in bu*.aux ; do bibtex `basename $file .aux` done
The form itself is generated using the command \makeform
. To produce a blank version of the form, simply do:
\documentclass{raeisf}
\begin{document}
\makeform
"ënd{document}
To enter information into the form, you must specified the required
information (using the commands described later) before the command \makeform
.
Any text placed after \makeform
will be appended to the form.
Your name is entered using the command \name
{your name}.
Your school is entered using the command \school
{your school}
All your publications (published, in press, submitted) need to be stored in one or more BibTeX databases (.bib files).
If they are all contained in a single .bib file, this file can be specified using the command:
\defaultbibliography
{bib name}. This command is defined in bibunits.sty, please read the
bibunits documentation for further details.
The raeisf class file comes with the BibTeX style file raeisf.bst. This style file defines the three extra fields: rank (RAE rank), jif (journal impact factor) and reviewed (peer-reviewed? Should have the value n or y). These fields can be used with all entry types. (Note that these fields will be ignored if you use any other style file.) This BibTeX style file will be used automatically by the raeisf class file.
The form stipulates that senior
author must be indicated using an asterisk. If you have a large centrally located bib file containing all your publications,
it's a nuisance having to edit it every time you want to use it in a different document. It may be easier to define a command,
called, say, \senior
, and redefine it depending on your document. Here is an example:
@preamble{"\def\senior{$^\ast$} % senior author"} @string{ESANN="Proceedings of the European Symposium on Artificial Neural Networks"} @inproceedings{cawley2004a, author = "Gavin C. Cawley{\senior} and Nicola L. C. Talbot", title = "Sparse {B}ayesian kernel logistic regression", booktitle = ESANN # " (ESANN-2004)", address = "Bruges, Belgium", pages = "133--138", month = apr # " 28--30", year = 2004, rank = "1", jif = "2.19", reviewed = "y" } @article{cawley2004b, author = "Gavin C. Cawley{\senior} and Nicola L. C. Talbot", title = "Hetroscedastic kernel ridge regression", journal = "Neurocomputing", volume = 57, pages = "105--124", year = 2004, rank = "5", jif = "3.0", reviewed = "y" } @inproceedings{saadi2002, author = "K Saadi and Gavin C Cawley and Nicola L C Talbot", title = "Fast exact leave-one-out cross-validation of least-squares support vector machines", booktitle = ESANN # " (ESANN-2002)", address = "Bruges, Belgium", pages = "149--154", month = apr, year = 2002 } @article{theobald2004, author = "Barry Theobald and J. Andrew Bangham{\senior} and I. Matthews and Gavin C. Cawley", title = "Near-videorealistic synthetic talking faces: Implementation and evaluation", journal = "Speech Communication", note = "submitted on invitation", year = 2004 }You now only need to change the first line to:
@preamble{"\def\senior{} % senior author"}and the asterisks will be removed.
(Note that the \senior
command is placed immediately after the surname with no
spaces, that way BibTeX will be fooled into thinking it is part of the author's surname, otherwise
the name won't be formatted correctly.)
All your publications after 31 December 2000 should be specified using the command:
\publications
[bib name]{cite list}
where bib name is the name of your BibTeX database. This can be omitted if you have
used the command \defaultbibliography
.
The argument cite list should be a comma-separated list of the bibliography entries you want included in this
section. For example:
\publications{cawley2004a,cawley2004b}
These are publications which have been accepted by the journal/publisher. This information is specified
using the command:
\accepted
[bib name]{cite list}.
This has the same format as \publications
described above.
These are publications which have been submitted to a journal. This information is specified
using the command:
\submitted
[bib name]{cite list}.
This has the same format as \publications
described above.
These are publications you are planning. This information can be specified using the command:
\planned
[bib name]{cite list}.
This has the same format as \publications
described above.
This is research you believe, if published before 31 July 2007, will be a high scorer in RAE terms. This information
is specified using the command:
\wouldlike
[bib name]{cite list}.
This has the same format as \publications
described above.
General note: the commands described in this section add items to a longtable environment, so be careful about
starting new lines -- use \newline
instead of
\\
.
The information for each research grant should be entered using the command:
\grantawarded
{PI}{Co-I}{Title}{Start Date}{End Date}{Date
Applied}{Amount}{Lead School}{Funder}
The information will be inserted into a table at the end of the
form. Example:
\grantawarded {Dr Gavin Cawley} {Dr Nicola Talbot} {An interesting project} {1 Jan 01} {31 Dec 02} {1 Jun 00} {1,000} {CMP} {EPSRC}
You should have a \grantawarded
command for each entry.
If you have the relevant data stored
in an Excel file, you can saved it as a CSV file, and use the csvtools package. For example, suppose you have
a CSV file called grants.csv that contains the following information (lines wrapped to fit on page):
PI,Co-I,Title,Start Date,End Date,Date Applied,Amount,Lead School,Funder Dr Gavin Cawley,Dr Nicola Talbot,An interesting project,1 Jan 01,31 Dec 02, 1 Jun 00,{1,000},CMP,EPSRC Dr Gavin Cawley,Dr Nicola Talbot,Another interesting project,1 Jan 02,31 Dec 03, 1 Jun 01,{2,000},CMP,EPSRCThen you can do:
\applyCSVfile{grants.csv} {\edef\cmdargs{ {\insertPI} {\insertbyname{Co-I}} {\insertTitle} {\insertbyname{Start Date}} {\insertbyname{End Date}} {\insertbyname{Date Applied}} {\insertAmount} {\insertbyname{Lead School}} {\insertFunder}} \expandafter\grantawarded\cmdargs}
Pending research grants can be entered using the command:
\grantpending
{PI}{Co-I}{Title}{Start Date}{End Date}{Date
Applied}{Amount}{Lead School}{Funder}
This has the same format as \grantawarded
.
Planned research grants can be entered using the command:
\grantplanned
{PI}{possible Co-I}{planned title}{est. start
date}{est. end date}{planned date of application}{est. amount to be applied for}{likely
funder(s)}
You should have the command \grantplanned
for each planned research grant.
Each research grant application you would like to make should be entered using the command:
\desiredRGapp
{PIs and Co-Is}{Title/Description}{Funding Body and
Amount}{Dates}
Each presentation should be entered using the command:
\presentation
{conference}{date and venue}{presentation}{type}
Each presentation should be entered using the command:
\futuremeeting
{conference}{date and venue}{presentation}{type}
Each meeting should be entered using the command:
\importantmeeting
{conference}{date and venue}
Each award should be entered using the command:
\majoraward
{title of award}{date}{awarding body}{reason}
Each possible future award is entered using the command:
\futureaward
{title}{date}{awarding body}{reason}
Each entry should be specified using the command:
\committeemembership
{body}{position/role}{period of membership}
Each entry should be specified using the command:
\membershipaspiration
{body}{position/role}{period of membership}
Each entry should be specified using the command:
\editorship
{journal/series}{position}{period}
Each entry should be specified using the command:
\editorshipaspiration
{journal/series}{position}{start date}
Each entry should be specified using the command:
\consultancy
{body}{position}{period}
Each entry should be specified using the command:
\consultancyaspiration
{body}{position}{period}
Each entry should be specified using the command:
\researchgrouping
{name}{affiliation}
You research plan or strategy should be entered using the command:
\researchplan
{text}
The details should be entered using the command:
\researchopportunities
{text}
This information should be entered using the command:
\generalviews
{text}
Dr Nicola Talbot
School of Computing Sciences
University of East Anglia
Norwich. NR4 7TJ
http://theoval.cmp.uea.ac.uk/~nlct