Forums
Dear Editor;
Items on the Library and Archives Canada website are always a challenge to cite, because of the torturous path to the target records and the way in which they are identified. In the course of verifying my research data, I decided that I needed to re-do the citation for a particularly complicated situation involving a passenger manifest, which only contained the correct sailing info on the initial page and had the two persons of interest on another page.
I should note that the only way to simplify the path to the location of the browsable images was to use a more involved URL. Otherwise one would have to cite a "trail-of-breadcrumbs" to access the database, do a search and then browse the images.
I believe I've a reasonably workable solution in the following example, but I am a bit concerned that my punctuation is not yet quite correct. Your comments would be appreciated.
Footnote
"Item: Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," browsable images, Library and Archives Canada (https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : accessed 13 June 2021), manifest; image 1, n.p., S.S. Minnedosa, Liverpool to Saint John, N.B., departing 15 February 1921, arriving 23 February 1921; image 9, p. 8, lines 10 & 11, “Murison, Thomas B” and “Murison, Ruby [cursive note 'Louise']”; citing “microfilm Reel Number T-14842, Reference: RG 76, Item Number: 19707.” Arrival-date error reported.
Short Footnote
"Item: Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," Library and Archives Canada, manifest, S.S. Minnedosa, Liverpool to Saint John, N.B., departing 15 February 1921, arriving 23 February 1921, lines for “Murison, Thomas B” and “Murison, Ruby [cursive note 'Louise'].”
Bibliography
"Item: Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24." Browsable images. Library and Archives Canada. https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : 2021.
History-Hunter, you do have…
History-Hunter, you do have a knack for finding doozies! Your punctuation is intelligible, which is the purpose of punctuation, though EE would handle a couple of points a bit differently in an effort to make things as clear as possible.
First Reference Note:
"Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," browsable images, Library and Archives Canada (https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : accessed 13 June 2021), image 1: Manifest cover page, S.S. Minnedosa, London to Saint John, N.B., departing 15 February 1921, arriving 23 February 1921; image 9: p. 8, lines 10 & 11, “Murison, Thomas B” and “Murison, Ruby [cursive note: 'Louise']”; citing “microfilm Reel Number T-14842,
Reference:Record Group 76, ItemNumber:19707.” Arrival-date error reported.Subsequent Note:
"Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," p. 8, lines 10–11, “Murison, Thomas B” and “Murison, Ruby [cursive note 'Louise'].”
Source List Entry:
"Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24." Browsable images. Library and Archives Canada. https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : 2021.
To explain several of the suggestions I've made:in citations: it's not usually necessary to copy the database labels for items. Specifically,
The main problem with what's being cited here is that we must mix image numbers and page numbers. That is almost always inadvisable; but it seems unavoidable in this case. EE would clarify the distinction with a colon after the image number.
The basic punctuation rule is this: When a string of commas separate items in a series, the implication is that all items are on an equal level or otherwise comparable—but they aren't in this case.
To distinguish the two major things that are being cited (image number in the database vs. information that's on the page of the original), the most effective solution would be to cite the image number, followed by a colon to introduce the information taken from the image—i.e., the data from the page.
Once the colon makes the introduction, then each relevant detail from the imaged page can be separated by commas because they are all of equal value.
Two last nits:
Dear Editor; I suspect that…
Dear Editor;
I suspect that this is one case in which separating the layers and citing the image layer first would allow one to simplify the citation. It would result in separating the issue of dealing with the image numbers and page numbers. It would also make it more clear that the manifest was correct and the reflection in the database name was in error.
Bingo! That's why EE…
Bingo! That's why EE emphasizes the concept of citation layers. Well, to be precise, EE would cite the original document first—using as much data as can be gleaned from the images themselves.
Dear Editor; Your help with…
Dear Editor;
Your help with this citation is truly appreciated, especially your clear explanation of your reasons for the suggested changes. I seem to be starting to generate clean enough citations that the import of such comments are more easily understood. Thank you.
I admit it. I do have a talent for running head-on into the "doozies." If my research takes me in a certain direction, I'm not shy about dealing with the difficulties involved. On occasion, this has allowed me to find some real gems that could have been otherwise missed.
Could you explain why you have substituted "London" for "Liverpool." I believe the initial page of the manifest states that "Liverpool" was the port of embarkation.
Your "Two last nits" actually highlight two points that have been on my list of things to research. You've answered my concerns about whether the "S.S." should be italicized. The observation regarding the length of the subsequent note reminds me that the subject of constructing them and "what level of detail is enough?" is often lightly covered. I hope that you will have the time to deal with that more full in some future "QuickNote."
[My apologies for the typo…
[My apologies for the typo in the last sentence. Laptop keyboards sometimes don't respond as fast as I seem to type. "more full" should be "more fully."]
Re London vs. Liverpool, the…
Re London vs. Liverpool, the cited database tells us this ...
This, of course, circles back to the more-basic issue of mixing data from the database with data from the document.
Yes. I see they've made more…
Yes. I see they've made more than one error in their cataloguing.
I will attempt doing the citation using the concept of multiple citations to a single source and post my attempt for your comments. Since my initial post, I have come across something similar in the manifests on Ancestry. So; understanding how to do this form of citation is essential.
It may serve as a good example for others tackling manifests in which the essential data is scattered across several sheets/images.
Dear editor; I've cobbled…
Dear editor;
I've cobbled together a first attempt at using the concept of multiple citations to a single source. It doesn't seem much shorter, but is certainly easier to read.
If I've understood the EE book correctly, one essentially lists individual citations to the source terminated by colons. That way all the information between the colons are "on the same level." In the case of the source being a database with images, one would then terminate the whole list by appending an "imaged as ..." clause.
I've repeated the user-generated "title" in each clause to indicate that the clauses all belong to the same source. I'm unsure if this is necessary. I believe the structure implies the clauses are associated with the training source.
Footnote
Short Footnote
Bibliography
I noted a typo in my…
I noted a typo in my explanation. Drop the word "training" from " I believe the structure implies the clauses are associated with the training source." I try to check things before pressing save, but something inevitably slips by.
H-H, did you mean to render…
H-H, did you mean to render all words in italics?
No. I don't know why it did…
No. I don't know why it did that. It was fine in my word processor. I'll post it again and see if I can get it to look as it does in the word processor. Thank you for bringing it to my attention.
Footnote Manifest of the S…
Dear Editor;
I believe I've resolved the issue. The webpage was picking up my unitalicized block-quote tag and interpreting it as defined by the webpage block-quote tag, which appears to be italicized. I have basically cut and pasted raw text into the webpage and formatted it within the webpage text editor. It "seems" to look as I intended. Please let me know if there are still issues.
Footnote
Manifest of the S.S. Minnedosa, cover page, Liverpool to Saint John, N.B., departing 15 February 1921, arriving 23 February 1921; Manifest of the S.S. Minnedosa, p. 8, lines 10 & 11, “Murison, Thomas B” and “Murison, Ruby [cursive note: 'Louise']”; imaged in "Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," browsable images, Library and Archives Canada (https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : accessed 13 June 2021), images 1 and 9. Arrival-date error reported.
Short Footnote
Manifest of the S.S. Minnedosa, Liverpool to Saint John, N.B., departing 15 February 1921, arriving 23 February 1921, p. 8, lines 10–11, “Murison, Thomas B” and “Murison, Ruby [cursive note 'Louise'].”
Bibliography
"Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24." Browsable images. Library and Archives Canada. https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : 2021.
H-H, we could whittle that…
H-H, we could whittle that down a bit more by altering the punctuation a bit:
First Reference Note:
Manifest of the S.S. Minnedosa, cover page (Liverpool to Saint John, N.B., departing 15 February, arriving 23 February 1921) and p. 8, lines 10 & 11 (Murison, Thomas B, and Murison, Ruby [cursive note: Louise]); imaged in "Passenger lists of the MINNEDOSA arriving in Saint John, N.B. on 1921-02-24," browsable images, Library and Archives Canada (https://www.bac-lac.gc.ca/eng/discover/immigration/immigration-records/passenger-lists/passenger-lists-1865-1922/Pages/item.aspx?IdNumber=19707 : accessed 13 June 2021), images 1 and 9. Arrival-date error reported.
One other point I meant to mention earlier. Your last comment "Arrival-date error reported" is inexplicable without more explanation. What is the error? To whom and by whom is it reported? Are you saying that the database reports an error (if so, where) or that you have spotted an error and reported it to the creator of the database?
Thank you for the taking the…
Thank you for the taking the time from your other activities to provide this feedback. It's appreciated.
I understand how you collapsed the two references into one clause. I was puzzled by the use of the parentheses, but I believe I understand why you used them. It seems that they help compartmentalize the data into a hierarchy (overall manifest, manifest page, page contents).
I'll be using this second citation style much more often. I have a number of online sources, such as manifests, which tend to require citing multiple references within the same source. Leading with the item-info results in a "cleaner" looking citation. I was a little hesitant to try it, because I had not previously had the chance to see both options side-by-side and analyze how the same information was being represented in the two ways.
The removal of the quotes around the passenger names leaves me with two small questions...
I've always wondered about the way one should represent names shown in reversed order in a record. Potential options include citing them as a quoted pair (as in my attempt), a comma delimited list (as you have done) or reversing them (first name and then last name). Is one more correct? By the way; did you intend to put a comma in "Thomas B, and" or should this have been a period?
I'll revise the "Arrival-date error" note to "Discrepancy between manifest arrival date and that in collection name has been reported to Library and Archives Canada." I should likely let the the LAC know that the departure port of London in their database should be Liverpool. It occurs to me that those two errors are just two more reasons that one needs to look at the raw information. Imagine if I had just depended upon the database...
Yes, parentheses are another…
Yes, parentheses are another valuable punctuation tool to "compartmentalize" pieces of information. In this example, the parentheses serve the same function as parentheses do when we cite publication details after the title of a book or journal. It compartmentalizes the not-always-essential data that is not on an "equal" level with all other data items in the sequence that is being separated by commas.
Yes, too, the use of the comma in the extracted names was intentional—i.e.:
Murison, Thomas B, and Murison, Ruby
Again, it follows the standard punctuation format we use when we cite, say, joint authors in a bibliography where names must be inverted (12.10):
Surname, Given Name, and ....
When the surname is followed by the given name (which modifies the surname), punctuation rules calls for a pair of appositive commas before the given name and after it.
Typically, in a bibliography, we would not invert the name of the second author that is being added to the name of the first author. In your situation, in which we are stringing together passenger names exactly as they appear in the ship roll, the second passenger name is inverted but the same punctuation rule applies: Surname <comma> Given Name <comma> and ....Surname <comma> Given Name.
As for putting quotes around the personal names that are taken from a ship roll (or a census or any other record), EE does that only if there is a problem with the record's rendition of the name—say, it differs from what the reader would expect if they went to the record to find the person who is being discussed. (For example see EE 6.20, p. 271 "Correcting Database Errors," sentence 4.)
As for the risks of depending upon what's fed to us in a database: EE could not agree with you more.