Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
publications
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Verified Software
publications
Compare revisions
17f68a5306aa9a7042d1f40ebef497642fa273cc to cbaae7971663c2141e1e6123d77c8e2a9fd54f36
Compare revisions
Changes are shown as if the
source
revision was being merged into the
target
revision.
Learn more about comparing revisions.
Source
verified-software/publications
Select target project
No results found
cbaae7971663c2141e1e6123d77c8e2a9fd54f36
Select Git revision
Branches
master
Swap
Target
verified-software/publications
Select target project
verified-software/publications
1 result
17f68a5306aa9a7042d1f40ebef497642fa273cc
Select Git revision
Branches
master
Show changes
Only incoming changes from source
Include changes to target since source was created
Compare
Commits on Source (1)
Update README
· cbaae797
Thomas Wood
authored
7 years ago
cbaae797
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+70
-25
70 additions, 25 deletions
README.md
with
70 additions
and
25 deletions
README.md
View file @
cbaae797
...
...
@@ -5,11 +5,13 @@ This repository contains the group's (and its members') publications, BibTeX
references, and associated materials.
## How to Deposit a Publication.
1.
To fulfill funding and REF requirements and for long-term archival, all papers and
tech reports should be deposited into
[
Imperial Spiral
](
http://spiral.imperial.ac.uk/
)
within THREE MONTHS OF ACCEPTANCE. Do this now, so you don't
forget. Once this is done, email Teresa with a copy of the accepted submission so that she can publish the details of
the acceptance in the news section of the website.
1.
To fulfill funding and REF requirements and for long-term archival, all
papers and tech reports should be deposited into
[
Imperial Spiral
](
http://spiral.imperial.ac.uk/
)
within THREE MONTHS OF
ACCEPTANCE. Do this now, so you don't forget.
2.
Email Teresa with a copy of the accepted submission so that she can publish
the details of the acceptance in the news section of the website.
2.
Create a BibTeX record for the publication in
the
[
publications.bib
](
publications.bib
)
file. Post-publication, records can
...
...
@@ -19,33 +21,76 @@ the acceptance in the news section of the website.
appropriate version of each field, as they all usually vary in quality.
See below for BibTeX style notes.
3.
Commit files associated with the publication
in
this directory. Files
should
be named with the bibtex key as the
base
of the file name, and the
appropriate extension from the
table
below according to document purpose.
3.
Commit files associated with the publication
to
this directory.
*
Files
should
be named with the bibtex key as the
root
of the file name
*
, and the
appropriate extension from the
section
below according to document purpose.
## Copyright Notes
You should check with the publisher's T&Cs (in particular the Copyright waiver
form) to determine which version of the paper you are allowed to publish here.
Often it is only the pre-print edition that is passed to the publisher
**before**
they make any changes. The final proof copy and the publisher's own
copy is often not permitted to be published.
## BibTeX Record Structure
Record keys have the preferred format of
`<first author surname><year><first
word of title>`
Fields:
*
**doi**
: Please remove the
`http://dx.doi.org/`
prefix, so the doi is of the
form
`nn.nnnn/....`
]
*
**url**
: This field should
**not**
contain a duplicate of the doi. It
**
Please take careful note of this section!
**
You
**must**
check with the publisher's T&Cs (in particular the Copyright
waiver form) to determine which version of the paper you are allowed to publish
here. Often it is only the
*pre-print*
edition that is passed to the publisher
*before*
they make any changes. The final proof copy and the publisher's own
copy is usually not permitted to be published on the author's own website.
## BibTeX
A BibTeX record looks like this:
```
bibtex
@Type
{
Key
,
field
=
{value}
,
field
=
{value}
,
}
```
For details of the possible types of entries, and their minimal set of required
fields, see [the Wikipedia BibTeX article](https://en.wikipedia.org/wiki/BibTeX#Entry_types).
For the group websites, we've chosen a BibTeX key format of:
`<first author surname><year><first word of title>`, this is used as the
record's key in the `publications.bib` file, and as the root of the filename
for each associated file (article, slides, etc) in this repository.
In values, Surround special characters and characters requiring exact
capitalisation in `{}` curly braces. For example:
`Naud{\v{z}}i{\={u}}nien{\.{e}}` and `{ECMAS}cript`.
### Fields Style Guide
* **author**: Author names should be separated by `and`, names can be in either
the `Last, First` *(preferred)* or `First Last` style.
Multiple-word last names should use the `Last, First` style to minimise
confusion. For example: `da Rocha Pinto, Pedro and Fragoso Santos, Jos{\'e}
and D'Osualdo, Emanuele`. For further details of how BibTeX treats names, see
[this summary](http://artis.imag.fr/~Xavier.Decoret/resources/xdkbibtex/bibtex_summary.html#names).
* **doi**: Please remove the `http://dx.doi.org/` prefix, so the DOI, so it is
of the form `nn.nnnn/xyzabc`. For display on the website, this value will be
prefixed with `http://dx.doi.org/` to produce a link to the publisher's
article website.
* **url**: This field should **not** contain a duplicate of the doi. It is
generally only used to link to the publisher's version if the publisher does
not also issue a DOI.
*
**month**
: Add the exact date of the conference as publication date.
This will keep the file hidden until the actual publication date.
not also issue a DOI. If the publisher's link is the same location as the DOI
after redirections, then it should not be filled in the url field.
* **month**: **Required** The first three letters of the month of publication (possibly in
the future). This field does not require quoting or placing into braces.
The standard months are: jan, feb, mar, apr, may, jun, jul, aug, sep, oct,
nov, dec. For example: `month = mar,`.
Publications will not appear on the websites until their month of
publication (as per Philippa's policy decision).
* **year**: **Required** Year of publication.
* **file**: This field is added automatically by the JabRef reference manager,
it is ignored by the website. It is mostly useful as a quick check in the
JabRef user interface that all publications have an associated file. See next
section for file matching on the website.
* **booktitle**: For the `@inproceedings` type, this is the title of the
conference proceedings. Different publishers prefer different (long) styles,
Philippa usually prefers something short like POPL'12. We may need to find a
way to standardise on this.
### Further Reading/References
* [Wikipedia BibTeX article](https://en.wikipedia.org/wiki/BibTeX)
* The [BibTeX FAQ](http://mirrors.ctan.org/biblio/bibtex/contrib/doc/btxFAQ.pdf)
* [Xavier Decoret's guide](http://artis.imag.fr/~Xavier.Decoret/resources/xdkbibtex/bibtex_summary.html)
* [Tame the BeaST](http://www.lsv.fr/~markey/BibTeX/doc/ttb_en.pdf), by Nicolas
Markey
## Publication File Extension Types
Publication file types are listed in the configuration file
...
...
This diff is collapsed.
Click to expand it.