-
Notifications
You must be signed in to change notification settings - Fork 11
Document Management System
cccs-ip edited this page Oct 28, 2014
·
7 revisions
PLEASE NOTE : A working file of these tables in available on Google Drive
URL | maps to BibTex `url`; the WWW address |
URL-alt | |
CCCS folder - orig | |
sub-folder - orig | |
original file name | |
original file name -alt | |
revised file name | |
Country / Countries | |
Region(s) | |
BIBTEX entry type | |
CCCS entry type | |
Year | maps to BibTex `year`; the year of publication (or, if unpublished, the year of creation) |
Author(s) | maps to BibTex `author`; the name(s) of the author(s) (in the case of more than one author, separated by and) QUESTION: How does BibTex handle multiple authors? How to distinguish between multiple authors |
Editor(s) | maps to BibTex `editor`; the name(s) of the editor(s) |
Book Title | maps to BibTex `booktitle` the title of the book, if only part of it is being cited; (NOTE: would need to be either 'book' or 'journal') |
Book Chapter | maps to BibTex `chapter` the chapter number |
Article Title | maps to BibTex `title`; the title of the work |
Journal / Publication | maps to BibTex `journal`; the journal or magazine the work was published in |
Vol | maps to BibTex `volume` the volume of a journal or multi-volume book |
Issue | maps to BibTex `number`; the "(issue) number" of a journal, magazine, or tech-report, if applicable. (Most publications have a "volume", but no "number" field.) |
Pages | maps to BibTex `pages`; page numbers, separated either by commas or double-hyphens. |
Series | maps to BibTex `series`; the series of books the book was published in (e.g. "The Hardy Boys" or "Lecture Notes in Computer Science") |
maps to BibTex `crossref`; the key of the cross-referenced entry | |
Language | |
Publishing Agency | maps to BibTex `institution`; the institution that was involved in the publishing, but not necessarily the publisher |
Publishing House | maps to BibTex `publisher`; the publisher's name |
Publisher's City | maps to BibTex `; publisher's address (usually just the city, but can be the full address for lesser-known publishers) |
Publisher's Address | maps to BibTex ` (**NOTE**: relationship may need to be re-evaluated); |
Doc ID# | |
ISSN / ISBN | |
Abstract | |
Bibliographic Annotation | maps to BibTex `annote`; an annotation for annotated bibliography styles (not typical) |
attribute tag | |
Reviewer Notes | maps to BibTex `note`; miscellaneous extra information |
CCCS isn't currently referencing articles with these values, but we would like to enable the field by default
edition | the edition of a book, long form (such as "First" or "Second") |
eprint | a specification of an electronic publication, often a preprint or a technical report |
howpublished`; how it was published, if the publishing method is nonstandard | |
key | a hidden field used for specifying or overriding the alphabetical order of entries (when the "author" and "editor" fields are missing). Note that this is very different from the key (mentioned just after this list) that is used to cite or cross-reference the entry. |
month | the month of publication (or, if unpublished, the month of creation) |
organization | the conference sponsor |
school | the school where the thesis was written |
series | the series of books the book was published in (e.g. "The Hardy Boys" or "Lecture Notes in Computer Science") |
type | the field overriding the default type of publication (e.g. "Research Note" for techreport, "{PhD} dissertation" for phdthesis, "Section" for inbook/incollection) |
VALUE | DESCRIPTION | REQUIRED | OPTIONAL | Notes |
---|---|---|---|---|
article | An article from a journal or magazine. | Required fields: author, title, journal, year | Optional fields: volume, number, pages, month, note, key | |
book | A book with an explicit publisher. | Required fields: author/editor, title, publisher, year | Optional fields: volume/number, series, address, edition, month, note, key | |
booklet | A work that is printed and bound, but without a named publisher or sponsoring institution. | Required fields: title | Optional fields: author, howpublished, address, month, year, note, key | |
conference | The same as inproceedings, included for Scribe compatibility. | |||
inbook | A part of a book, usually untitled. May be a chapter (or section, etc.) and/or a range of pages. | Required fields: author/editor, title, chapter/pages, publisher, year | Optional fields: volume/number, series, type, address, edition, month, note, key | |
incollection | A part of a book having its own title. | Required fields: author, title, booktitle, publisher, year | Optional fields: editor, volume/number, series, type, chapter, pages, address, edition, month, note, key | |
inproceedings | An article in a conference proceedings. | Required fields: author, title, booktitle, year | Optional fields: editor, volume/number, series, pages, address, month, organization, publisher, note, key | |
manual | Technical documentation. | Required fields: title | Optional fields: author, organization, address, edition, month, year, note, key | using 'manual' as indicator for policy documents, including both actual policy and 'good practice' notes |
mastersthesis | A Master's thesis. | Required fields: author, title, school, year | Optional fields: type, address, month, note, key | |
misc | For use when nothing else fits. | Required fields: none | Optional fields: author, title, howpublished, month, year, note, key | |
phdthesis | A Ph.D. thesis. | Required fields: author, title, school, year | Optional fields: type, address, month, note, key | |
proceedings | The proceedings of a conference. | Required fields: title, year | Optional fields: editor, volume/number, series, address, month, publisher, organization, note, key | |
techreport | A report published by a school or other institution, usually numbered within a series. | Required fields: author, title, institution, year | Optional fields: type, number, address, month, note, key | includes ADB 'special evaluation studies' |
unpublished | A document having an author and title, but not formally published. | Required fields: author, title, note | Optional fields: month, year, key |
type | the field overriding the default type of publication (e.g. "Research Note" for techreport, "{PhD} dissertation" for phdthesis, "Section" for inbook/incollection) |
VALUE | DESCRIPTION |
---|---|
policy | associated primarily with 'manual' |
operational guide | associated primarily with 'manual'; sometimes with 'book' |
evaluation study | associated primarily with 'tech report' |
case study | |
loan agreement | associated primarily with 'manual' |
project agreement | associated primarily with 'manual' |
operational update | associated primarily with 'tech report' |
impact assessment | associated primarily with 'tech report' |
technical assistance report | associated primarily with 'tech report' |
brochure | associated primarily with 'misc' |
proposal | associated primarily with 'misc' |
terms of reference | associated primarily with 'misc' |