Adding a Reference: Difference between revisions

From Cybersecurity Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 39: Line 39:
a) A link to the ''BibTeX'' entry for the reference (this should show only a single BibTeX entry in detail format - e.g. [http://cyber.law.harvard.edu/cybersecurity/Special:Bibliography?f=wikibiblio.bib&title=Special:Bibliography&view=detailed&action=&keyword=DoD:2007 ''BibTeX'']
a) A link to the ''BibTeX'' entry for the reference (this should show only a single BibTeX entry in detail format - e.g. [http://cyber.law.harvard.edu/cybersecurity/Special:Bibliography?f=wikibiblio.bib&title=Special:Bibliography&view=detailed&action=&keyword=DoD:2007 ''BibTeX'']


b) A link to the Google Books entry for the reference, e.g., [http://books.google.com/books?id=ILaY4jBWXfcC&dq=Security+Engineering&ei=1NFRTNz5KJeMygTr6dDqBQ&cd=1 ''Google Books'']  (This can often be found in the BibTeX entry.)
b) A link to the ''Google Book''s entry for the reference, e.g., [http://books.google.com/books?id=ILaY4jBWXfcC&dq=Security+Engineering&ei=1NFRTNz5KJeMygTr6dDqBQ&cd=1 ''Google Books'']  (This can often be found in the BibTeX entry.)


c) A link to the WorldCat entry for the reference, e.g., [http://www.worldcat.org/title/security-engineering-a-guide-to-building-dependable-distributed-systems-second-edition/oclc/639194438&referer=brief_results ''World Cat''].
c) A link to the ''WorldCat'' entry for the reference, e.g., [http://www.worldcat.org/title/security-engineering-a-guide-to-building-dependable-distributed-systems-second-edition/oclc/639194438&referer=brief_results ''World Cat''].


d) A link to Amazon.com's page for the reference (since this often contains useful reviews and other information about the work), e.g, [http://www.amazon.com/Security-Engineering-Building-Dependable-Distributed/dp/0470068523/ref=sr_1_1?ie=UTF8&s=books&qid=1280430777&sr=8-1 ''Amazon''].
d) A link to ''Amazon''.com's page for the reference (since this often contains useful reviews and other information about the work), e.g, [http://www.amazon.com/Security-Engineering-Building-Dependable-Distributed/dp/0470068523/ref=sr_1_1?ie=UTF8&s=books&qid=1280430777&sr=8-1 ''Amazon''].


(See [[Security Engineering]] for an example that contains all of these links.)
(See [[Security Engineering]] for an example that contains all of these links.)

Revision as of 09:29, 6 August 2010

To add a new bibliographic reference entry:

1) Search for information on the reference including links to accessible copies online, reviews, discussions and/or the web site of the author or sponsor.

2) Next create the BibTeX entry for the reference. (See Guidelines for adding Bibliography entries.)

3) Create a blank page for the reference. To do this within the wiki format, you need to choose an existing page to create the link. Normally, this will be a category page, however, if you are unsure of what categories will be appropriate, you could enter it into the listing of all references on the Cybersecurity Annotated Bibliography.

The title of the new reference page will normally be the short version of the reference title. For example, if the title of the reference is "Pricing Security: Vulnerabilities as Externalities," the page will be named Pricing Security. The exception will be where that page already exists (Cyberwar for example), in which case you will need to include the subtitle to create a unique page name.

4) Clicking on your newly created link will open a blank editing page (if it does not then you need to come up with a new unique page name). Copy and paste the contents of the sample template or some other reference page similar to the new reference into the newly created page. You should copy the source of the template (by selecting the "edit" tab) rather than the displayed page text.

5) Begin editing the template. The "Full Title of Reference" should contain both the main title and any subtitle separated by a colon.

6) The full citation should consists of the bluebook formatted citation for the reference followed by a link to the full text of the reference if available labeled as Web or SSRN depending if the link goes directly to the text or to an intermediate SSRN page. This link should appear on the same line as the citation. If there is a second source for the full text of the reference, it should follow labled as AltWeb.

(An example of the use of AltWeb is available at Why Information Security is Hard.)

(An example of the use of SSRN is available at Overcoming Impediments to Information Sharing.

Note that Web, AltWeb, SSRN, BibTex all are italicized.

7) On a separate line (place one blank line after the citation to force the Wiki to line space), put the following as applicable:

a) A link to the BibTeX entry for the reference (this should show only a single BibTeX entry in detail format - e.g. BibTeX

b) A link to the Google Books entry for the reference, e.g., Google Books (This can often be found in the BibTeX entry.)

c) A link to the WorldCat entry for the reference, e.g., World Cat.

d) A link to Amazon.com's page for the reference (since this often contains useful reviews and other information about the work), e.g, Amazon.

(See Security Engineering for an example that contains all of these links.)

8) Create links to the appropriate categories for the reference. When you add a category to the reference page, you must also place a link to the reference page into the Table of Contents page for that category and every Table of Contents page higher in the hierarchy. So, for example, if you categorize the reference under TOC-> Issues-> Economics of Cybersecurity->Insurance, then links to it must appear under Insurance, Economics of Cybersecurity and Issues. Links from TOC Category pages back to the reference page should follow the table format shown in the TOC. If more than two authors, abbreviate to "<first author> et. al"

a) Categories should be separated by top level Table of Contents topics and in the following order (not only those top level topics in which the current reference has an applciable category need appear), i.e.:

  • Overview:
  • Resource by Type:
  • Treats and Actors:
  • Issues:
  • Approaches:

b) Categories within a single top level Table of Contents topic should be separated by semicolons and arranged in alphabetical order, i.e.

c) Categories refer to the major themes of the reference. If the reference only mentions a category in passing but does not focus on it, then it need not be included.

9) Add Glossary, Keyword entries in alphabetical order separated by commas. You can copy links from the Keyword Links page directly into the reference page. Make sure to create kinks from the Keyword Index and Glossary of Core Ideas page back to the reference. If another reference by the same author is linked under a given keyword, use [2], [3], etc. for succeeding entries.

a) Links to Keywords are appropriate even when the item is only mentioned in passing in the reference. The purpose of keywords are to help someone unfamiliar with the term or to provide a way to find other references with the same keyword but appearing in a separate category.

b) If you need to add a new keyword to the Keyword Index and Glossary of Core Ideas, make sure to update the Keyword Links page. It is also a good idea to email either David Abrams or Caroline Nolan of the addition.