Citing a historical article on a website

I'm trying to write my first ever biographical sketch of an ancestor, and now that I've got all of his genealogical story written out with neattly footnoted citations to records and databases, which I'm most familiar with, I'm going to embellish his sketch with some interesting historical facts.  I've been reading through EE edition 2, Sections 2.33 - 2.54.  This may seem elementary, but I've never done this before and I'm a bit lost.

I'd like to cite the following article on this webpage, but I'm lost as to what elements should be involved in the citation, and how they all should be ordered.

http://www.baruch.cuny.edu/nycdata/disasters/cholera-1866.html

Here's my first, albeit poor, attempt at a citation to this article.

Baruch College, "Trade & Transportation, Disasters, New York City Distasters, III. Major Epidemics, E. Cholera (1866)," baruch.cuny.edu (http://www.baruch.cuny.edu/nycdata/disasters/cholera-1866.html : copyright 2014).

I cited Barch College first because they appear to be the "creator" of the website.  They I cited the path I took from the main page to get to the article, followed by the main website, the full web address of the article and the copyright infomation on the bottom of the webpage.  I'm certain this isn't right... probably not even close.  I just would like a little guidance.

David P. Slager Jr.

Submitted byEEon Fri, 06/17/2016 - 08:39

David, it's good to hear that you are finding 2.33–2.54 useful, although I suspect you meant to type 2.32.  As 2.32 points out (or the QuickStart Guide tucked in at the flyleaf of the third edition), citing an article at a website is like citing a chapter in a book where each chapter has a different author. The basic pattern is this:

Author of Article [if shown], "Name of Article," Creator of Website/Book, Name of Website (Publication place=URL : Date), specific data.

Following this pattern, when I use the link you give above, my takeaway is this:

"Disasters: New York City (NYC) Cholera Outbreak of 1866," Baruch College Weisman Center for International Business, NYCdata: It's All Here! (http://www.baruch.cuny.edu/nycdata/disasters/cholera-1866.html : accessed 17 June 2016), para. 3.

At the link, I don't see the same article and website titles that you give and that—of course—points to the trickiness of citing online material.

Submitted bydpslageron Fri, 06/17/2016 - 10:17

Thank you for your clarity on the citation.  I believe my mistake in the title of the article that I placed in quotation marks was actually my attempt to provide to the reader the path to the article from the website's "Home" page.  From the citation you provided above I see that it's not a priority to provide that path, and you're just dealing with the article itself, which makes sense.

I do need a little further clarity on the last part of the citation.  You stated, "para. 3."  I don't understand what that is related to.  Is is referencing the third paragraph in the article or is it a reference to the previous page (disasters index) which states, "III. Major Epidemics" under which heading this particular article is linked?

~ David

Submitted byEEon Fri, 06/17/2016 - 16:18

David, when we cite a chapter in a book, we cite the specific page number within the chapter, right?  B extension, when we cite an article at a website, most citations will call for indicating exactly where in the article one would find the information being cited. In this particular case, the website article is so short that a paragraph number is likely unnecessary; but, since EE is providing a model here, we added "para. 3" to indicate that data of that sort needs to be provided.

As for the "disasters index" on the previous page, the specific link you gave didn't lead to an index, so that wasn't included in the citation.

As for path, certainly citing a path (or "waypoints") is a legitimate approach. Whether to cite a path or a direct URL generally hinges upon the complexity of the site. When, let's say, we are citing digitized court files posted online in a highly structured collection that has no index and has to be accessed by drilling down through several layers of sub-collections, then a path might be the best way to identify what we have used. EE has various examples of this, using the > sign to indicate the progression from largest element to smallest.