Newsletter Collection

By tmphelps on Sun, 05/31/2020 - 12:36

Forums

I have an almost complete collection of family newsletters written between 1932 and 1953. EE 14.21 provides clear instructions on citing newsletter articles.

EE 14.21 also acknowledges that periodicals may undergo name changes over time: that is the case with my collection. For ease of asking my questions:
  Name: "Whatisit"  Vol I     Editor: Person A
  Name: "Brunswick Stew" Vol II - X  Editor: Person A
  Name: "Rev. G.W. Phelps Clan News" (5 issues, no Vol, but individually dated) Editor: Person B
  Name: "The Blue Wolf" Vol I - VII   Editor: Person A
  Name: "The Blue Wolf" (no vol but rather consecutive issue no. 1 - 13, dated)  Editor: Person A
  Name: "The Blue Wolf" Vol 1  Editor: Person C
(Each of the Volumes has edition numbers with dates)

Question 1: I believe is it appropriate to group all of my various references to individual newsletter articles into a single Source List Entry. Using the model suggested in EE 14.21 I would propose:
  Rev. G. W. Phelps Family Newsletter (variously GWP Family News), 1932-53.
Does this seem appropriate?

Question 2: The example reference notes given in EE 14.21 include volume, date, and page. EE 14.8 says "Evidence Style identifies issues by their dates rather than issue number." In my case, specifically as it pertains to "The Blue Wolf" newsletters, it is the volume number (or lack thereof) that potentially leads to confusion. Picking up and interpreting EE 14.9 in light of EE 14.8, and thinking about my specific case, does this "template" work?
  "Article Name," GWP Family News: {Specific Newsletter Name} (Date): {page number w/o brackets}.

Question 3: Stepping back I realize that this collection of newsletters is, in reality, privately held material. While the newsletter article format described above still "feels" correct, would it be appropriate or necessary to add a second layer to both the Source List: "Privately held by Thomas M. Phelps, [ADDRESS FOR PRIVATE USE,] Bostic, North Carolina." and the reference notes: "; Rev. G. W. Phelps Family Papers, 1857—, privately held by Thomas M. Phelps, [ADDRESS FOR PRIVATE USE,] Bostic, North Carolina."?

Tom

Submitted byEEon Sun, 05/31/2020 - 16:10

Tom, you've well demonstrated why there is no simple, rigid formula for citing anything—and why we need to thoughtfully consider the circumstances surrounding whatever source we use. In answer to your questions:

Q1: Yes that works. But, if I understand you correctly, are you also saying that the newsletter went under the title The Blue Wolf, Whatisit, and The Brunswick Stew? If so, that needs to be included in your full identification,

Q2: That would work, but your first reference note citation should identify the source in full as you did in the Source List Entry.

Q3: That addition would be helpful, although it is not usually deemed essential.

 

EE - Thanks for the feedback. Just to be sure that I understand a couple of points. In the Source List, following "variously" I should include each of the various names by which the newsletter went over it's lifetime? (I admit that I was not clear from the example in EE 14.21 that only showed one name in the example). And also, is the "master name" (the name before the "variously") meant to be a generic name for the collection or one of the names that actually appeared on at least one newsletter.

Tom

Submitted byEEon Wed, 06/03/2020 - 09:53

Q1:  "In the Source List, following "variously" I should include each of the various names by which the newsletter went over it's lifetime?

Yes.

Q2: Is the "master name" (the name before the "variously") meant to be a generic name for the collection or one of the names that actually appeared on at least one newsletter.

In the Source List, typically, the dominant (e.g., longest running or current) name would be used, followed by an identification of the other names by which that newsletter was known. If you wish to create a series name that is easily identifiable, you might do so. The essential thing is to make it clear what you are using.