TMG-L Archives

Archiver > TMG > 2001-08 > 0996797123


From: "Gail Roorda" <>
Subject: Re: [TMG] SDI
Date: Thu, 2 Aug 2001 19:05:23 -0500
References: <LPBBLNDDAJKOKCPDIILLIEBKCPAA.neagley@epix.net> <3B695981.D0C12467@reigelridge.com>



I was not sure whether Neagley wanted to know what the source should say OR
how to write it which is a different thing. Over time I have done different
things. At one time I used a citation much like Terry's. I may have just
modified the online URL template. (I COULD look that up since the source I
modified would still be printed on the citation window, but I won't <grin>)
I DID use the person and file number but I just typed them in the title box
with commas in the correct places, etc. I finally wrote a wrote a custom
source and since this seemed more correct for a database, I designated a
field for person, a field for the file number,etc. I put Social Security
Death Index in the title field..

However, WHATEVER form I used my citations to the online SSDI database have
always SAID ie printed out something like this.

John H. Smith, no. 493-16-7527, Social Securtity Death Index, online at
<http://www.ancestry.com>(or rootsweb, etc), printout dated 02 August 2002.
<COMMENTS> My "comments" are something similar to the sentence in Mills
identifying that the online database is compiled from the Social Securty
Death Benefits index... etc.This probably could be improved ie require less
typing, but I don't have thousands of cites to the SSDI.

Short Citation
Subject, File Number, Social Security Death Index, online at [URL]

Bibliography

Social Security Death Index. Online at <http://www.ancestry.com>;. Printout
dated 02 August 2001.

Frankly I am thinking of eliminating the last sentence. This is how Mills
does an electronic website citation.
However, at least, in my own understanding of what Mills says a bibiograpy
should be general. I do cite individual census households. I am NOT trying
to start another discussion on the value of doing that as opposed to using
more generic sources. HOWEVER I would think that there would be no valid
reason to cite individual printouts etc. in a bibligraphy. Frankly I have
never printed out a bibligraphy <teehee> and I have used this program for
several years.

I have a pretty good idea of how my endnotes look. I check them carefully
as I am creating them. When I print out a group sheet or descendency report
I always print out the notes. Although I always "do" a bibliographic
template when I rewrite a source or create a custome source, I suspect that
if I ever need a bibliograpy this document will require a great deal of
"clean up"!

Anyway Neagley there is more than one way to "skin a cat" at least when
using TMG. I just figure out how my endnotes should read when printed out
and then I either create a custom source or modify an existing template to
get what I want.

Gail


> Neagley wrote:
> >
> > TMG:
> >
> > I am getting a bunch of information using the Social Security Death
Index.
> > I am wondering how to source it. I just have a temporary source
citation
> > right now, but I would like to fill it in real soon!
>
> Remember that there is not one SSDI, but several different ones
> created by different data collectors. So I source it like any other
> database on the same location. Recently, I've been using the one on
> RootsWeb. For online data bases, I have a custom source:
>
> FF: [TITLE], online [URL]<, [CD]>
>
> SF: [SHORT TITLE], online [URL]<, [CD]>
>
> Bib: [TITLE]. Online [URL]
>
> So then I create a "source" for RootsWeb, as follows:
>
> Title & Short Title: Rootsweb.com
>
> URL: <<http://userdb.rootsweb.com/>>;
>
> When I make a citation to that source, I enter in the CD the name of
> the database, date accessed, and any notes that apply to the
> particular cite -- like:
>
> Social Security Death Index, accessed 28 May 2000, shows date, and
> last residence as Washington, Tazewell, Il 61571
>
> I've thought about adding the person's name or SS# also in the CD, but
> haven't yet.
>
> Terry Reigel
>
>
> ==== TMG Mailing List ====
> Send messages and replies to <>.
>


This thread: