Vancouver style references (and others)

If you point me at a specifications document for Vancouver, I'll see what I can do.

We are planning on using Vancouver style to output our publications list via biblio. Vancouver is very close to CSE. I am still researching what all the differences are, but here are some of the key differences between CSE and Vancouver with respect to journal articles are the following:

1. Date Location
CSE inserts the year immediately after the author
Vancouver inserts it after the title(s), and before the volume/issue numbers.

2. Journal Titles
CSE usually uses full journal title (?)
Vancouver usually uses journal titles in abbreviated format following Medline style

3. Punctuation after Journal Titles
CSE uses a period followed by a space
Vancouver sometimes uses nothing but a space (?)

4. Punctuation after Date
CSE uses ?
Vancouver uses a semi-colon with no space following

I have already made some edits to the biblio_style_cse.inc file in order to produce something close to what we want. All the changes I made are to the "default" output style that starts around line 36 within the biblio_style_cse function:

      $output .= '<span class="biblio-title">';
      $output .= $inline ? l("$node->title", "$base/viewinline/$node->nid") : l("$node->title", "node/$node->nid");
      $output .= ". </span> \n";
			$output .= (!empty ($node->biblio_secondary_title)) ? check_plain($node->biblio_secondary_title) . '. ' : '';
			$output .= (!empty ($node->biblio_alternate_title)) ? check_plain($node->biblio_alternate_title) . ' ' : '';
  		$output .= (!empty ($node->biblio_year)) ? check_plain($node->biblio_year) . ';' : '';
      $output .= (!empty ($node->biblio_volume)) ? check_plain($node->biblio_volume) : '';
      $output .= (!empty ($node->biblio_issue)) ? '(' . check_plain($node->biblio_issue) . ')' : '';
      $output .= (!empty ($node->biblio_pages)) ? ':' . str_replace(" ", "", check_plain($node->biblio_pages)) . '.' : '';

This assumes that the abbreviated journal title is stored in the biblio_alternate_title field. It will no doubt make sense to make this presentation dependent on which biblio type is being displayed, but this is a quick and dirty solution for someone whose biblo database consists entirely of journal articles.

Also, I found that I ran into errors, or pages not loading properly, if I made edits to the header of the biblio_styles_cse.inc file, and I also couldn't get the admin panels to all work correctly even when I simply inserted a file named biblio_styles_vancouver.inc into the module folder. I'm not sure if this was because of other edits I was doing or not, but I have the impression that it was caused by my edits to this style file. It would be nice if it were possible for someone just to drop another style file into the folder and have it appear as a new style in the Preferences panel. Perhaps that is the intended functionality, and I just edited the file incorrectly?

The Vancouver style does not have a single authoritative document to determine how to use it. The general style is more or less settled upon, but different journals apparently have their own sets of quirks about small items related to the style. I don't know the best source of information about the Vancouver style format.

Here are a couple guides I consulted:
http://www.library.uq.edu.au/training/citation/vancouv.pdf (PDF, 80 KB)
http://www.nlm.nih.gov/bsd/uniform_requirements.html
http://www.ub.ntnu.no/viko/en/mod7/mod7_side16.php
http://www.lib.monash.edu.au/tutorials/citing/vancouver.html

Phil.

Thanks Phil,

You should be able to just drop it in the directory and have it show up in the GUI, it is important however to make the appropriate changes to the biblio_sytle_xxx_info() function since that's what attaches it to the GUI, and (obviously) change all references to "cse" to vancouver.

If you post the working vancouver sytle file here, I'll include it with the distribution.

Ron.

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.