December 1995 From list-relay@UCSD.EDU Tue Dec 5 10:14:20 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id KAA28365 for ; Tue, 5 Dec 1995 10:14:19 -0800 Received: from post-ofc02.srv.cis.pitt.edu (post-ofc02.srv.cis.pitt.edu [136.142.185.11]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id JAA25586 for ; Tue, 5 Dec 1995 09:53:29 -0800 Received: from mtac.pitt.edu (server.mtac.pitt.edu [136.142.119.47]) by post-ofc02.srv.cis.pitt.edu with ESMTP (8.7.2/cispo-2.0.1.1) ID for ; Tue, 5 Dec 1995 12:45:03 -0500 (EST) Date: Tue, 5 Dec 1995 12:45:03 -0500 (EST) Received: from MTAC/SpoolDir by mtac.pitt.edu (Mercury 1.21); 5 Dec 95 12:44:04 -500 Received: from SpoolDir by MTAC (Mercury 1.21); 5 Dec 95 12:43:58 -500 Received: from [136.142.119.71] by mtac.pitt.edu (Mercury 1.21); 5 Dec 95 12:43:53 -500 X-Sender: dkrone@server.mtac.pitt.edu Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: genweb@UCSD.EDU From: dkrone@mtac.pitt.edu (David McFeeters-Krone) Subject: I am looking for info on computer geneology programs Hi, I would like any info you may have on mac programs to help coordinate my family tree. I know about Reunion, but have no idea if it is any good. Please reply if you know about this program or any other. Thanks -dave David McFeeters-Krone Mid-Atlantic Technology Applications Center 823 William Pitt Union Pittsburgh, PA 15260 (412) 648-7000 (f) -7003 http://oracle.mtac.pitt.edu/WWW/MTAC.html From list-relay@UCSD.EDU Tue Dec 5 17:30:58 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id RAA29285 for ; Tue, 5 Dec 1995 17:30:57 -0800 Received: from borg.mindspring.com (borg.mindspring.com [204.180.128.14]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id RAA17423 for ; Tue, 5 Dec 1995 17:24:16 -0800 Received: from swampfox.mindspring.com [168.121.63.114] by borg.mindspring.com with SMTP id UAA01026; Tue, 5 Dec 1995 20:24:08 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 5 Dec 1995 20:25:28 -0500 To: dkrone@mtac.pitt.edu (David McFeeters-Krone), genweb@UCSD.EDU From: swampfox@MindSpring.COM (Wally Smith) Subject: Re: I am looking for info on computer geneology programs At 12:45 PM 12/5/95, David McFeeters-Krone wrote: >Hi, > >I would like any info you may have on mac programs to help coordinate my >family tree. I know about Reunion, but have no idea if it is any good. >Please reply if you know about this program or any other. Thanks > >-dave > >David McFeeters-Krone >Mid-Atlantic Technology Applications Center >823 William Pitt Union >Pittsburgh, PA 15260 >(412) 648-7000 (f) -7003 >http://oracle.mtac.pitt.edu/WWW/MTAC.html Hi Dave: I'm still sort of new to this subject myself. I haven't really settled on a particular program yet. I started using Family Roots, but I don't really like it. I also have GenTree which is still less than what I want. I have a Demo copy of MacRoots which I haven't checked out completely. The best thing that I have going so far is a Hyper Card stack which I built myself, but I'ts not finished yet. Whish I could be more help. Wally Smith From list-relay@UCSD.EDU Wed Dec 6 04:43:40 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id EAA02034 for ; Wed, 6 Dec 1995 04:43:40 -0800 Received: from PSUVM.PSU.EDU (psuvm.psu.edu [128.118.56.2]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id EAA18362 for ; Wed, 6 Dec 1995 04:35:26 -0800 Message-Id: <199512061235.EAA18362@UCSD.EDU> Received: from PSUVM.PSU.EDU by PSUVM.PSU.EDU (IBM VM SMTP V2R2) with BSMTP id 3482; Wed, 06 Dec 95 07:24:18 EST Received: from PSUVM.PSU.EDU (NJE origin RSH1@PSUVM) by PSUVM.PSU.EDU (LMail V1.2a/1.8a) with RFC822 id 6348; Wed, 6 Dec 1995 07:24:18 -0500 Date: Wed, 6 Dec 95 07:24 EST From: "Steve Houtz" Subject: Re: I am looking for info on computer geneology programs To: dkrone@mtac.pitt.edu Cc: genweb@UCSD.EDU In-Reply-To: dkrone AT mtac.pitt.edu -- Tue, 5 Dec 1995 12:45:03 -0500 (EST) While I have not used the MAC version of Reunion I have seen the Windows versio n and was quite impressed by it. Its ability to integrate photos and data into one database is simple and easy to use. From list-relay@UCSD.EDU Mon Dec 11 16:21:45 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id QAA21470 for ; Mon, 11 Dec 1995 16:21:44 -0800 Received: from spacelink.msfc.nasa.gov (SPACELINK.MSFC.NASA.GOV [192.149.89.61]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id QAA15192 for ; Mon, 11 Dec 1995 16:11:28 -0800 Received: by spacelink.msfc.nasa.gov (5.0/SMI-SVR4) id AA00260; Mon, 11 Dec 1995 18:11:06 +0600 Date: Mon, 11 Dec 1995 18:11:05 -0600 (CST) From: "Charles R. Devanney" X-Sender: deva4200@spacelink To: "M. A." Subject: Devanney Family Message-Id: Organization: NASA Spacelink Teacher Resource Center-a service to educators X-Disclaimer: Message author is solely responsible for message content. Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 275 Anyone have info on the name Devanney. Originally from Sligo, Ireland. Came over with famine Imm. Settled in Sullivan County ,Pennsylvania. Patrick and Mary (Boland) Devanney came to USA in 1849. ---------- Charles R. Devanney Email:deva4200@spacelink.msfc.nasa.gov From list-relay@UCSD.EDU Fri Dec 15 09:50:33 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id JAA05642 for ; Fri, 15 Dec 1995 09:50:32 -0800 Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id JAA01992 for ; Fri, 15 Dec 1995 09:45:35 -0800 Received: from vanna.ljo.dec.com by mail11.digital.com; (5.65v3.2/1.0/WV) id AA24422; Fri, 15 Dec 1995 12:36:17 -0500 Received: from csac by vanna.ljo.dec.com; (5.65/1.1.8.2/10Oct94-8.2MPM) id AA14916; Fri, 15 Dec 1995 12:32:54 -0500 Received: by csac.ljo.dec.com; id AA11826; Fri, 15 Dec 1995 12:36:15 -0500 Date: Fri, 15 Dec 1995 12:36:15 -0500 From: JimIsaak Message-Id: <9512151736.AA11826@csac.ljo.dec.com> To: genweb@UCSD.EDU Subject: Tool for locating web pages (not genealogically specific) Below is a note about a tool that Genweb folks may find useful, it allows you to locate web pages that contain specific words or combinations of words. (for example, there are about 25000 references to "1776" on web pages, 1.5 million to "Washington" and 4000 to documents that contain both. ... more focused searches are possible as well.) ... this could be useful in locating information about names, persons, locations and so forth. Note that names that are directly listed on web pages are included here, but ones that are accessed via CGI scripts are not visible since they do not exist on a web page until "requested". Since this form of web "spider" only indexes the "direct" pages as opposed to the "forms-response" pages. (A CGI script that is triggered on access to a page would be indexed here, as opposed to one that is only triggered on completion of a form, or ismap, etc.) Anyway, a useful tool for research. Jim Isaak ------------------------------------ A new web indexing tool is available on the web, "Altavista" from Digital Equipment. This tool builds a "complete" index of all public web pages so that you can search for all occurrences of words, phrases or combinations of these. For example, there are about 20000 references on the web to "Bill Clinton", 1.2 million to "president" and 10,000 to pages with both. This response, along with the first 20 or so on the list (in a prioritized order) are delivered in real time. In this case, additional qualifiers for the query would be used to focus down the number of responses. To give this service a try, goto URL: http://www.altavista.digital.com (you can separately select searching of 8 billion words in 16 million web pages; or amongst the 13,000 Internet news groups.) ================================================================ For hypertext newsgroup or "notes" type collaboration, see Digital's "Workgroup Web Forum(tm)" demo web-site -- at: http://webforum.research.digital.com/ you can now download a demo copy to put on supported servers. (info on purchasing it is also available) ================================================================ For a real world public application, look up the NH primary election interactions on http://www.fosters.com/ the on-line pages for Foster's Daily Democrat of Dover. ---------------------------------------------------------------- Happy Surfing, Jim Isaak From list-relay@UCSD.EDU Sun Dec 17 03:16:12 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id DAA12005 for ; Sun, 17 Dec 1995 03:16:11 -0800 Received: from soback.kornet.nm.kr (soback.kornet.nm.kr [168.126.63.3]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id DAA14138 for ; Sun, 17 Dec 1995 03:12:55 -0800 Received: (from cmanis@localhost) by soback.kornet.nm.kr (8.6.12+hangul/8.6.9) id UAA10405; Sun, 17 Dec 1995 20:10:41 +0900 From: Cliff Manis Message-Id: <199512171110.UAA10405@soback.kornet.nm.kr> Subject: GenServ GEDCOM Server: Over 2 Million surnames To: roots-l@mail.EWorld.Com (ROOTS-L Genealogy Mail List) Date: Sun, 17 Dec 1995 20:10:41 +0900 (KST) Cc: cmanis@soback.kornet.nm.kr (Cliff Manis) X-Mailer: ELM [version 2.4 PL21-h4] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-kr Content-Transfer-Encoding: 7bit Content-Length: 2955 GenServ [ Genealogical GEDCOM Server System ] 2,000,000 ++ Surnames ON-LINE ! ! Over 1,500 different GEDCOM databases ON-LINE ! Genserv contains genealogical data originally submitted as databases (in GEDCOM format) from an ever-growing number of genealogists in the USA and various other countries. These databases contain basic genealogical information such as names, dates of birth, marriage, etc., details of family relationships, and often the details of the sources of this information together with other descriptive text. Automated searches of this information can be requested by means of commands sent to Genserv by electronic mail. More than 2,000,000 names ON-LINE in GEDCOM data in the GenServ database Please visit our homepage below. Are you a USER of the GenServ system ? If so, tell others. If not, now is the time to request the the latest documentation. The GenServ homepage has over 21,000 hits since 1 Oct. It has lots of interesting point to other Genealogical sites. We loaded more than 200 new GEDCOM files on the GenServ system in Nov 95. More and more users are benefiting are benefiting from the GEDCOM database info and reports which have been available since 1991. The GenServ database Server is ON-LINE and accessible only to those who have sent a GEDCOM file to the GenServ system. We have lots of different data reports available. This service is available ONLY to persons who have submitted a GEDCOM database themselves - the Genserv Project is thus an exercise in cooperative use of modern database and networking technology. You will receive an access code for this system with 10 days after I receive a GEDCOM database via postal mail. GEDCOM files are NOT accepted if sent via Email, Please check the DOCS. Its success depends on both the quantity and the quality of the genealogical information provided by its users. This system may have valuable information now to aid with your research. As indicated above, an absolute prior requirement is for you to provide a database in GEDCOM format - such databases can be produced automatically by many different genealogical database management systems. If you wish to participate, please request the DOCS below, and read them. Many different programs are available as shareware and commerical which will make a good GEDCOM file after you enter your family data. If interested - please request and read the GenServ DOCUMENTATION. This system is supported by the USERS of GenServ. You should receive the DOCS within two hours of your request to address below. We want your GEDCOM data - Please consider Complete documentation with a description of report types is available by sending an email request to addresses below. For complete GenServ Docs to: genserv-doc@progcons.com WWW - The Genserv homepage http://soback.kornet.nm.kr/~cmanis/ - From list-relay@UCSD.EDU Sun Dec 24 23:03:41 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id XAA06914 for ; Sun, 24 Dec 1995 23:03:26 -0800 Received: from connect.net (ns.connect.net [199.1.91.2]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id XAA03112; Sun, 24 Dec 1995 23:02:21 -0800 Received: from beau.connect.net by connect.net (SMI-8.6/SMI-SVR4) id AAA13285; Mon, 25 Dec 1995 00:57:40 -0600 Date: Sun, 24 Dec 95 23:56:37 PST From: Beau Sharbrough Subject: FGS Home Page To: Everton Lee <71610.1737@compuserve.com>, Hankinson Dave , Hoffman Lee H <71147.1736@compuserve.com>, Kyner Steve <73340.3236@compuserve.com>, Holsclaw Birdie and Russ <70260.267@compuserve.com>, List-GEDCOM , List-GenWeb , List-Lines , List-Roots , List-TMG , Manis Cliff , Tesler Larry , Wetmore Tom , Anderson Robert <74214.421@compuserve.com>, Andrews Mike <74511.2251@compuserve.com>, Archer George , Bosze Karon M <75070.1477@compuserve.com>, Bruce Dorothy , Clay Betty <76702.337@compuserve.com>, Eastman Dick <76701.263@compuserve.com>, Hamner Judy <75300.2161@compuserve.com>, Hoffman Gary , Lane Mickey , Ledden Larry <71543.2760@compuserve.com>, Raney Don , Rice Dennis , Rubeck Art <71511.3065@compuserve.com>, Rump W Fred , Steed John <75745.1371@compuserve.com>, Velke Bob <74774.653@compuserve.com>, Gabriel Henmar Gabe <73553.71@compuserve.com>, Burris Gene <74224.1771@compuserve.com>, Claunch Larry , Dow Bill , Hall Roland , Mavrogeorge Brian , Mutzabaugh Pat , Phipps Alan , Sanford Al , Slade Jim , Troyer Carl , Wylie John , Kerns Larry , Steele Jeri , Gehring Jacob G , Pence Richard , Whitaker John , Witcher Curt B , Wylie Barbara , Allison Bob , Bobo Charles H <74357.1553@compuserve.com>, Bobo Larry , Collier Kelly <103304.2654@compuserve.com>, Crane Rod and Madilyn <76373.565@compuserve.com>, Doyle Timothy B , Genealogical Computing editor , Green Karen , Helm Matthew Lynn , Jenkins Trevor , Lexicon Working Group , Mann Alan , Mann Alan E , Morris Travis <75013.1532@compuserve.com>, Quarterman John S , Rubeck Art , Schmidt Jennifer , StClair Mike , Whitaker Beverly X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII NOTICE TO PERSONS INTERESTED IN GENEALOGY: The Federation of Genealogical Societies (FGS) has been working for some time on a home page. While there are plans for changes in the works, it seems that this is as good a time as any to make their existence public, and to encourage their use by interested parties. In particular, some members of the FGS Board have particular changes in mind for specific areas. You will notice that a couple of pages say what the WILL have when they are done. Don't be alarmed, the problem does not lie with your set. It would be very useful if any of you have any comments to make about these pages, or suggestions. It would also be useful if you would spread the word further. I have sent it to several persons on the internet, but if someone would forward the announcement to other online services such as CompuServe, AOL, and Prodigy, I would be grateful. Karon Bosze generally helps out with things like this - if you're out there, Karon, I'm probably not being subtle enough, right? The URL is: http://www.connect.net/beau/fgs Try it, you'll like it. And in case you're wondering why I'm typing this so late on Christmas eve, well, it's gotten quiet around here for a change.... Hey! What's that clatter?!!! Grapevine 12/24/95 23:56:37 ======================================================== Beau Sharbrough Baseball season is over, and the long dark winter http://www.connect.net/beau is upon us. ======================================================== From list-relay@UCSD.EDU Tue Dec 26 00:15:53 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id AAA10056 for ; Tue, 26 Dec 1995 00:15:53 -0800 Received: from gw1.att.com (gw1.att.com [192.20.239.133]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id AAA29148 for ; Tue, 26 Dec 1995 00:13:22 -0800 From: ttw@beltway.att.com (T.T.Wetmore) To: lines-l@vm1.nodak.edu, genweb@UCSD.EDU Received: from beltway (beltway.mv.att.com) by ig1.att.att.com id AA08888; Tue, 26 Dec 95 03:11:38 EST Received: from grebe.beltway by beltway (4.1/SMI-4.0) id AA00452; Tue, 26 Dec 95 03:13:19 EST Date: Tue, 26 Dec 95 03:13:19 EST Original-From: beltway!ttw (T.T.Wetmore) Message-Id: <9512260813.AA00452@beltway> Original-To: att!vm1.nodak.edu!lines-l, genweb@ucsd.edu Subject: An HTML generating LifeLines Program Gang, It's "use 'em or loose 'em" time for me, so I'm using up vacation days til the end of the year. So I finally have some time to really learn about the Internet and the WWW. Look for a LifeLines home page soon. I've converted the LifeLines quick reference over to HTML format, all properly pagified. I've also had a little time to take a look at how some folks are starting to present their genealogical data on the WWW. Interesting, but we've got a ways to go. In preparing my own home page I've started experimenting with ways of generating HTML from LifeLines databases. There is a great untapped potential just waiting for some LifeLines programmer to work into. Tonight I wrote a little program that summarizes a person's ancestry in a single HTML file. It's based on generating a separate family summary for every ancestral family. The families are linked together through your ancsestors. I've attached the program for your amusement. Try running it on yourself in your LifeLines database and then opening the resulting output file with Netscape. Tom Wetmore - - - - - - - /* htmlfam -- output family group summaries in HTML format */ /* first draft -- 12/26/95 -- Tom Wetmore -- ttw@shore.net */ list(famq) /* family queue */ global(linki) /* persons who link to families */ global(showf) /* families that have been shown */ proc main () { getindi(per0, "Who do you want to start with?") set(fam0, parents(per0)) list(famq) table(linki) table(showf) enqueue(famq, fam0) while (fam, dequeue(famq)) { set(husb, husband(fam)) set(wife, wife(fam)) call insertifnew(linki, husb, fam) call insertifnew(linki, wife, fam) if (fam, parents(husb)) { enqueue(famq, fam) } if (fam, parents(wife)) { enqueue(famq, fam) } } call showhead() enqueue(famq, fam0) while (fam, dequeue(famq)) { if (not(lookup(showf, key(fam)))) { call showfam(fam) insert(showf, save(key(fam)), 1) } set(husb, husband(fam)) set(wife, wife(fam)) if (fam, parents(husb)) { enqueue(famq, fam) } if (fam, parents(wife)) { enqueue(famq, fam) } } call showtail() } proc insertifnew (tab, per, fam) { if (not(per)) { return() } if (lookup(tab, key(per))) { return() } insert(tab, save(key(per)), save(key(fam))) } proc showfam (fam) { "\n" if (per, husband(fam)) { "

"name(per, 0)"\n" if (evt, birth(per)) { "
born: "long(evt)"\n" } if (evt, death(per)) { "
died: "long(evt)"\n" } if (par, father(per)) { "
father: " call showlink(par) "\n" } if (par, mother(per)) { "
mother: " call showlink(par) "\n" } } if (per, wife(fam)) { "

"name(per, 0)"\n" if (evt, birth(per)) { "
born: "long(evt)"\n" } if (evt, death(per)) { "
died: "long(evt)"\n" } if (par, father(per)) { "
father: " call showlink(par) "\n" } if (par, mother(per)) { "
mother: " call showlink(par) "\n" } } if (evt, marriage(fam)) { "
married: "long(evt)"\n" } "

Children\n" children (fam, per, num) { "
" d(num) ". " call showchild(per) "\n" } "

\n" } proc showlink (per) { "" name(per, 0) "" } proc showchild (per) { if (lookup(linki, key(per))) { call showlink(per) } else { name(per, 0) set(evt, birth(per)) if (and(evt, year(evt))) { ", b. " year(evt) } set(evt, death(per)) if (and(evt, year(evt))) { ", d. " year(evt) } "." } } proc showhead () { "Genealogy Page\n\n" } proc showtail () { "\n" } From list-relay@UCSD.EDU Tue Dec 26 07:28:49 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id HAA12200 for ; Tue, 26 Dec 1995 07:28:38 -0800 Received: from arl-img-5.compuserve.com (arl-img-5.compuserve.com [198.4.7.5]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id HAA02854 for ; Tue, 26 Dec 1995 07:26:01 -0800 Received: by arl-img-5.compuserve.com (8.6.10/5.950515) id KAA06918; Tue, 26 Dec 1995 10:26:00 -0500 Date: 26 Dec 95 10:24:39 EST From: Mickey Lane To: GENWEB-L Subject: ROOTSBOOK (long) Message-ID: Season's greetings, y'all, Well, I guess it's time for an update on ROOTSBOOK. As most of you probably know, it's been off the web for the last two months. For the majority of the past year, I had a job (and equipment) that made it possible to put it up with very little fuss. I've taken a new job within the company and the situation is now different and it's unlikely to change anytime soon. I've been thinking of running a dedicated phone line into the house and setting up a 24 hour connection to some ISP but have not yet determined what cost that would have. The performance of the site would not be good but at least it'd be online. Comments on this idea most welcome... Even though ROOTSBOOK has been in hibernation from the public perspective, it's activities have been fast and furious from my point of view. I learned a *lot* about genealogy databases in the past year. I've learned a lot about other stuff too and it's all having an impact on the project's course. With this note, I intend to spell out some of the things I've learned and what I plan to do about them. Keep in mind that I'm basing this in terms of a database containing a million and a half entries. What may be an aggrivating circumstance requiring a few hours repair in a personal situation becomes major headache in something this size. Problems, in no particular order: * Shotgun programming techniques no longer work. You can't sort a 80 Mbyte index file in one go unless you have a system with a very large memory - 64 Mbytes or so. * There's a general class of problems relating to how different commercial programs abuse GEDCOM. * People publish (CompuServe, etc.) identical databases under different file names. This causes lots of duplicates in a collection of databases such as ROOTSBOOK. * You need to pay close attention to the fundamental architecture of the computer and the file system. Virtual memory is fine but if some monster structure you're constantly banging on is forced out to the page file, your performance is hosed. * A directory with 100 files in it works fine. A directory with 100,000 files doesn't. (Oh, it works but when?) * With the spread of published electronic genealogies, people cut and paste fragments of these files into their own work. A lot (most?) of the commercial programs don't do this very well and you wind up with dangling and duplicate pointers. * Disk space is an issue - I've come to think of one and a half gig as the proper amount of free space. * When entering information, people often use whatever spare field is handy for storing what they consider vital information. "Date of christening: Came to America in 1822." * People embed shorthand notes in places where they don't belong. "Name: Fred (lived in NY) Jones." * When dealing with lots of data, keyboard or windows activity is *very* expensive. * Tools should be written with the idea that Murphy is alive and well and that when an error occurs, the current state of the job should be saved so that activity can continue from the point of error, not the beginning. * People are releasing updates to previously published files. These releases contain both more and different information. (Interesting effect: Party A publishes info. Party B incorporates part of info into their work and releases that. Party A corrects info and re- publishes. You replace your copy of A's stuff. You now have conflicting info (new A vs. B) with no clear path to the source or what the fix is.) Working on the principle that the squeaky wheel gets the grease, I tackled the batch processing problems first. I wrote some tools to go find missing information and to generate corrective action scripts. This allowed me to carefully set things up and then let the computer crank all night. >From a code development perspective, I'm taking on the duplicate entry problem first. The other issues are ones that I've been dealing with to some extent for quite a while. They're not solved but they're understood and the needed work involves improving the current techniques. (This may lead one to conclude that while ROOTSBOOK does all sorts of big things well, it drops the ball on the little things. There is a certain amount of truth to this but I'm only one person and I work on what's interesting...) My first step was to define an identification mechanism for the duplicates. Wandering aimlessly around in a couple million entries wondering if this one matches that one is not going to be very productive. ROOTSBOOK has a pretty good indexing function. It produces an alphabetized list of all entries that have a legitimate name. I used this as a starting point and wrote a program (SPIDER.EXE) that parses this list to find groups of lines that contain the same name. It extracts the book/entry information and uses this to construct a list of "candidates." The candidates have several properties. They could be: * Bit-for-bit identical entries (most likely) * Identical persons from different researchers having different amounts of data. * Identical persons from a common source but containing transcription errors. (more common than you might think) * All of the above. (Observed!) * Completey unrelated. * If the list contains 4 or more people, there may be 2 (or more) unrelated matches. (I've seen lists of twenty or more.) The first item is easy to deal with. The last is... well, let's just say it enables the program to earn it's name. Having identified a list of candidates, the problem becomes what to do with them. The two main areas are who matches who and once a match is found, what type is it and what do we do about it? To find out who matches who, I established a property list for each candidate and set each item to an unknown state. I then entered a loop to compare each against all the others based on property information. Each comparison is a series of tests. Each test works on one thing - date of birth, mother's surname, etc. - and produces Yes and/or No votes (or no votes at all). As information is developed, the properties for the individuals are filled in. When complete, the properties are tested and (worst case) multiple lists of identical entries are produced. Each list refers to a single person. Dealing with these lists caused some serious beer drinking... ummmm... peer thinking. The easiest from a concept point of view was the bit-for-bit duplicates. Keep one, delete the rest, right? Nope. That causes all sorts of dangling pointers in the individual databases. Adding the code to fix all the pointers was certainly a possibility but added a nasty level of complexity to the program. In addition, it wasn't a solution for the other types of duplication. What I came up with was a new type of database record. In ROOTSBOOK terms, an X: record. Each entry in a duplicate list would get an X: record. One entry would be considered the "keeper" and the rest "extras." The keeper would get a number of X:0:NN records added that pointed to each extra and the extras would get an X:1: pointing to the keeper. All other records in the extras would be deleted. No changes were made to links. The one area that did require change was ROOTSBOOK's database engine. When it gets a request for an entry with an X:1:<..>N, it redirects the fetch to the referenced entry. There are still some warts on this solution but I think they will work out OK. Speaking of keepers and extras, the choice of which entry became which caused some problems and is still being worked. There are two aspects considered "good" in a ROOTSBOOK book: the entries should relate to the name of the book as much as possible and the books should be as small as possible. Trying to satisfy these points, though not always possible, adds to the code's complexity. What's nice about the X: record is it's extensibility to the other classes of duplication. An X:3:NN record might indicate that the entries are certainly the same people but that one contains a slightly different datum. If two entries had dates of birth of "JAN 15 1865" and "15 June 1865," the date test would return 3 yes votes and 1 no vote (since the months are different). Not knowing which is correct should prevent arbitrary joining of the two. On the other hand, if identically named parents, siblings and children indicate that these people really are the same entries, you want to establish a close coupling between the two so that they're always treated as a pair (or, groan, a group. My test case had six! identicals from different researchers.) Really smart software could expand on this scheme to make suggestions needing research. In other developments, I've abandonded the rule that stated that the PAGE program could not modify the database. (PAGE is what reads the database and makes the pages you see on the web server. It also does the date predictions.) When PAGE runs now, it submits the predictions to the database update engine so that subsequent runs of the indexer have access to them. This should greatly improve the quality of the index. The fact that PAGE and SPIDER generate updates to the databases derived from GEDCOM files has an interesting side effect in that the information is unique to ROOTSBOOK. While this first step opens the doors to all sorts of subsequent improvement steps, it also introduces yet another layer of insulation between what you see and the source of the data. Another effect is the circular nature of ROOTSBOOK's software. (Go ahead, say it :-) As changes are made, the effects of the changes cause still more changes in subsequent runs of different programs. If a good prediction makes it into a book, it may cause what was a bad prediction in some related entry to become a good one. If a duplication is documented, the additional info may enable more predictions. One thing this points out is the need for good backups. The shear size of the thing makes this a bit of a problem. In still other developments, I'm in the last quarter of writing a ROOTSBOOK class library, complete with test program. The library is roughly: RBObject - handles exceptions for all objects RBLiteralDate - holds text dates RBBinaryDate - processed dates, predictions, etc. RBLiteralPlace RBBinaryPlace RBEntry - the key ingredient for multiple dbs RBBook - a database file (similar to .GED) RBBibliography - a group of books RBBinaryEntry - an entry after conversion from file fmt RBCache - entries currently in use - spans machines There's also a series of classes dealing with a child, a group of children, marriages, unidentified relationships, assorted events, etc. These are pretty much intermingled and don't graph well. (How *do* you graph multiple inheritance with both static and private data?) When I get all this sorted out, I'll convert some of the common routines (and programs) now in C to C++. If I do set up a private web site, this one will have ftp access to ROOTSBOOK source code. That option was not available previously. No matter how hard I work on it, ROOTSBOOK is never going to amount to much until many people have had a chance to try it, break it, cuss it, fix it and generally pass judgement on it. Sorry to be so long winded. Comments (and donations :-), as usual, welcome. (Also welcome are thoughts on using a MicroVAX II with VMS 6.0 and UCX V? as a web server. I have code from a guy at OSU but it won't compile (DECC) due to some DECthreads lib that's missing.) Mickey. PS I didn't spel chek so if you run across some of the words I always spell wrong, chalk it up to haste, waste or eating too much paste. From list-relay@UCSD.EDU Tue Dec 26 23:00:11 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id XAA13679 for ; Tue, 26 Dec 1995 23:00:11 -0800 Received: from gw1.att.com (gw1.att.com [192.20.239.133]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id XAA12257 for ; Tue, 26 Dec 1995 23:01:48 -0800 From: ttw@beltway.att.com (T.T.Wetmore) To: lines-l@vm1.nodak.edu, genweb@UCSD.EDU Received: from beltway (beltway.mv.att.com) by ig1.att.att.com id AA23384; Wed, 27 Dec 95 01:59:54 EST Received: from grebe.beltway by beltway (4.1/SMI-4.0) id AA27216; Wed, 27 Dec 95 02:01:37 EST Date: Wed, 27 Dec 95 02:01:37 EST Original-From: beltway!ttw (T.T.Wetmore) Message-Id: <9512270701.AA27216@beltway> Original-To: att!vm1.nodak.edu!lines-l, genweb@ucsd.edu Subject: htmlfam -- 3rd draft Liners and Webbers, Here's a third draft of the HTML generating program I sent out yesterday. It is now smarter about the first person you select, and I like it's format better. The program generates a complete, self-contained HTML file that you can open with Netscape. Try it; you'll love clicking around in your ancestry. I also hope this program will stimulate some would-be LifeLines programmers to try their hand at their own pet output for WWW consumption. This is just another object lesson that with LifeLines you don't have to accept what anyone else's canned, HTML generator does; you can easily program your own. Still, after seven years, LifeLines remains the only genealogical system in which you have complete control over your output; you can generate any kind of output in any kind of format. Tom Wetmore - - - - - - - - - - - - - - - - - - - - - /* htmlfam -- output family group summaries in HTML format */ /* third draft -- 12/27/95 -- Tom Wetmore -- ttw@shore.net */ global(pert) /* person table */ global(showf) /* families that have been shown */ proc main () { getindi(per0, "Who do you want to start with?") set(fam0, parents(per0)) list(perq) list(famq) table(pert) list(lst) insert(pert, save(key(per0)), lst) table(showf) enqueue(perq, per0) while (per, dequeue(perq)) { if (fam, parents(per)) { if (per, husband(fam)) { call makelink(per, fam) enqueue(perq, per) } if (per, wife(fam)) { call makelink(per, fam) enqueue(perq, per) } } } call showhead() call showper(per0) enqueue(famq, fam0) while (fam, dequeue(famq)) { if (not(lookup(showf, key(fam)))) { call showfam(fam) insert(showf, save(key(fam)), 1) } set(husb, husband(fam)) set(wife, wife(fam)) if (fam, parents(husb)) { enqueue(famq, fam) } if (fam, parents(wife)) { enqueue(famq, fam) } } call showtail() } proc makelink (per, fam) { if (lst, lookup(pert, key(per))) { call enqueueifnew(lst, key(fam)) } else { list(lst) enqueue(lst, save(key(fam))) insert(pert, save(key(per)), lst) } } proc enqueueifnew (lst, key) { forlist (lst, el, num) { if (eqstr(key, el)) { return() } } enqueue(lst, save(key)) } proc showper (per) { call showone(per) families(per, fam, sp, num) { call showone(sp) call showmarr(fam) call showchildren(fam) } "
\n" } proc showfam (fam) { "\n" call showone(husband(fam)) call showone(wife(fam)) call showmarr(fam) call showchildren(fam) "
\n" } proc showone (per) { if (not(per)) { return() } "

"name(per, 0)"\n" if (evt, birth(per)) { "
born "long(evt)"\n" } if (evt, death(per)) { "
died "long(evt)"\n" } set(fam, parents(per)) if (par, father(per)) { "
father " call showlink(par, key(fam)) "\n" } if (par, mother(per)) { "
mother " call showlink(par, key(fam)) "\n" } } proc showmarr (fam) { if (evt, marriage(fam)) { "
married "long(evt)"\n" } } proc showchildren (fam) { if (eq(0, nchildren(fam))) { return() } "

Children\n" children (fam, per, num) { "
" d(num) " " call showchild(per) "\n" } } proc showlink (per, key) { set(lst, lookup(pert, key(per))) if (lst) { "" } name(per, 0) if (lst) { "" } call showevents(per) } proc showchild (per) { if (lst, lookup(pert, key(per))) { call showlinks(per, lst) } else { name(per, 0) call showevents(per) } } proc showlinks (per, lst) /* LOOSEEND -- THIS ROUTINE NEEDS MORE */ { if (eq(0, length(lst))) { call showlink(per, "start") } else { call showlink(per, getel(lst, 1)) } } proc showevents (per) { set(evt, birth(per)) if (and(evt, year(evt))) { ", b " year(evt) } set(evt, death(per)) if (and(evt, year(evt))) { ", d " year(evt) } } proc showhead () { "Genealogy Page\n\n" "\n" } proc showtail () { "\n" } From list-relay@UCSD.EDU Wed Dec 27 05:21:57 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id FAA15795 for ; Wed, 27 Dec 1995 05:21:57 -0800 Received: from dub-img-5.compuserve.com (dub-img-5.compuserve.com [198.4.9.5]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id FAA15756 for ; Wed, 27 Dec 1995 05:13:19 -0800 Received: by dub-img-5.compuserve.com (8.6.10/5.950515) id IAA17710; Wed, 27 Dec 1995 08:13:18 -0500 Date: 27 Dec 95 08:11:51 EST From: Mickey Lane To: GENWEB-L Subject: ROOTSBOOK & ISDN Message-ID: Yesterday, in connection with getting ROOTSBOOK back on line, I wrote : >I've been thinking of running a dedicated phone line into >the house and setting up a 24 hour connection to some ISP >but have not yet determined what cost that would have. I spent a good part of the day calling around to find out what the cost of setting up 24 hour inbound ISDN service would be. It ain't cheap. There's two parties to deal with - the ISP (independant service provider) and the phone company. The local ISP will set up a 24 hour ISDN connection (64 Kbaud) for $150/month plus $200 setup (DNS registration, etc.). The phone company wants about $120 to install and about $40/month for use. I need to buy a box for my end of the line at about $450. Total for first 3 months operation: about $1500 after you throw in cables, unexpected fees, etc. That's for 24 X 7 access at 64 Kbaud. I'm going to investigate on-demand dialup and smaller bandwidth solutions today. If I can get the 3 month expense down to $500 or so, I'll try it and see if I can beg donations from users to keep it alive. The only problem is that when ROOTSBOOK was online, it was in use 24 hours a day. On Wednesday and Thursday afternoons, there was a queue of users waiting to get at it... Maybe I'll win the lottery. How much does a T1 cost? Mickey. From list-relay@UCSD.EDU Wed Dec 27 15:34:42 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id PAA16852 for ; Wed, 27 Dec 1995 15:34:41 -0800 Received: from A.crl.com (A.crl.com [165.113.1.65]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id PAA26622 for ; Wed, 27 Dec 1995 15:35:05 -0800 Received: from A108002.ccr1.as.crl.com by A.crl.com with SMTP id AA27044 (5.65c/IDA-1.5 for ); Wed, 27 Dec 1995 15:34:17 -0800 Message-Id: <199512272334.AA27044@A.crl.com> X-Sender: cleow@a.crl.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Dec 1995 15:29:07 -0600 To: GENWEB@UCSD.EDU From: cleow@A.crl.com (Cleo Wilcox) Subject: Remove name from mailing list I seem to have been added to a mailing list because I am getting all sorts of strange E-mail. Please remove my name and E-mail address: Cleo Wilcox E-mail: cleow@a.crl.com Thank you. From list-relay@UCSD.EDU Wed Dec 27 16:19:02 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id QAA16899 for ; Wed, 27 Dec 1995 16:19:02 -0800 Received: from mail06.mail.aol.com (mail06.mail.aol.com [152.163.172.108]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id QAA09401 for ; Wed, 27 Dec 1995 16:16:50 -0800 From: JohnR238@aol.com Received: by mail06.mail.aol.com (8.6.12/8.6.12) id TAA15255; Wed, 27 Dec 1995 19:16:49 -0500 Date: Wed, 27 Dec 1995 19:16:49 -0500 Message-ID: <951227191536_25066105@mail06.mail.aol.com> To: MLANE@csi.compuserve.com cc: genweb@UCSD.EDU (genweb-l) Subject: Re: ROOTSBOOK & ISDN I thoroughly appreciated your in depth discussion of the issues we're facing regarding putting Rootsbook on the web and the problems associated with managing such a large amount of data. I face similar issues every day, and your comments helped me to focus on some areas I'd been trying to ignore. (GRIN). Now to the matter at hand. I work for an ISP, Georgia Business Net. I can help you set up the system on the net at much less cost. We are already doing this with similar systems, and it is working out well for all of us. Our proposal to you and others is to eliminate the ISDN/DSU/CSU/MABELL part of the circle altogether. We do this by placing your system next to ours and hooking you up directly on our Ethernet backbone and T1 line. You can still access the system any time as a sysop via telnet, pc anywhere et. al if you're running Windows NT and by Telnet, FTP, World Group, et. al if you're running Unix. The only "drawback" is that you can't physically touch the hardware, but for that you save a thousand bucks or so in purchasing two high speed modems (my end and yours) Ma Bell's setup charges and your monthly ISDN or whatever charges. All you'll need is local access to the net via telnet and you can get to the system anytime. Incidentally, $40 per month is a darn good price for ISDN access. Many parts of our area are being quoted up to $125 per month. It depends on how close you are to the ma bell office. We have ECNE (Netware) and UNE (Unix) certified engineers on site, a secure location, support staff on site till 11:00 and 24 hour beeper service if something goes down, so it's a great deal all around. We maintain disaster insurance on your box while it is on our site. Should you decide to terminate, your equipment will be returned at the end of the contract term. The cost for us to host your system is $150.00 per month with a minimum 6 month committment (first and last month in advance). You'll still have the $200 domain name registration fee (unless you opt to piggyback on Georgia Net). Incidentally, we really don't care what you do on your box. You can run a website, telnet only, ftp, World Group or even a plain old BBS. The whole thing can be up and running in 30 days. Give me a call at 1-800-201-6349 if you're interested in discussing this or have questions. BTW I am not a principal in this business, and gain no renumeration for your type connections. I have found, however, that this offers a best of all choices setup for many companies and individuals who wish to publish on the net. John Rigdon Georgia Business Net EMAIL JRIGDON@GANET.COM JOHNR238@AOL.COM From list-relay@UCSD.EDU Wed Dec 27 17:09:25 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id RAA16962 for ; Wed, 27 Dec 1995 17:09:24 -0800 Received: from linux.hays.org (hays.org [192.231.186.5]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id RAA10279 for ; Wed, 27 Dec 1995 17:11:19 -0800 Received: from nafai.hays.org (nafai.hays.org [192.231.186.12]) by linux.hays.org (8.6.9/8.6.9) with SMTP id RAA02377; Wed, 27 Dec 1995 17:10:57 -0800 Message-ID: <30E1EE8E.4657@Hays.ORG> Date: Wed, 27 Dec 1995 17:10:38 -0800 From: "John D. Hays" Organization: Hays Family Organization X-Mailer: Mozilla 2.0b3 (Win95; I) MIME-Version: 1.0 To: JohnR238@aol.com CC: MLANE@csi.compuserve.com, genweb-l Subject: Re: ROOTSBOOK & ISDN References: <951227191536_25066105@mail06.mail.aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit JohnR238@aol.com wrote: > Incidentally, $40 per month is a darn > good price for ISDN access. Many parts of our area are being quoted up to > $125 per month. It depends on how close you are to the ma bell office. > Yeah, Georgia is notorius for overcharging for ISDN. Here in Washington State Basic ISDN starts at around $40.00/mo. with per/minute charges for data (none voice/fax/analog) ... The per/min charge works out to less that a dollar an hour as I recall, but that still pushes it up for 24x7.. A new tarriff is available on one of the companies for about $70-80/mo. you get 24x7 unlimited local call. In California, I understand ISDN is quite cheap (a side effect of their environmental laws). > The cost for us to host your system is $150.00 per month with a minimum 6 > month committment (first and last month in advance). You'll still have the > $200 domain name registration fee (unless you opt to piggyback on Georgia > Net). > There are other companies that do this as well. =================================== John D. Hays ARS: KD7UW US Mail: 98291-0659 Email: jhays@Hays.ORG Web: http://www.hays.org/~jhays From list-relay@UCSD.EDU Wed Dec 27 17:24:27 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id RAA16981 for ; Wed, 27 Dec 1995 17:24:26 -0800 Received: from BART.BBN.COM (BART.BBN.COM [128.89.1.226]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id RAA10526 for ; Wed, 27 Dec 1995 17:26:24 -0800 Received: from GAAK.BBN.COM by BART.BBN.COM id aa26312; 27 Dec 95 20:27 EST Date: Wed, 27 Dec 1995 20:26:04 EST Message-ID: To: MLANE@csi.compuserve.com CC: genweb@UCSD.EDU In-reply-to: (message from Mickey Lane on 27 Dec 95 08:11:51 EST) Subject: Re: ROOTSBOOK & ISDN From: "Michael A. Patton" Reply-To: "Michael A. Patton, genealogy on the web" Another option you should think about is off-site hosting. One good option for this that I've seen is Paranoia.com, which is $100/year. It is limited to non-commercial usage, see their page about signing up at for details. You need your own access to the Internet for maintenance, but they'll house your pages. There are a bunch of other similar services. I think there's a page on them in Yahoo somewhere... -MAP From list-relay@UCSD.EDU Wed Dec 27 23:14:21 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id XAA17417 for ; Wed, 27 Dec 1995 23:14:19 -0800 Received: from gate.microware.com (gate.microware.com [198.17.151.51]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id XAA14643 for ; Wed, 27 Dec 1995 23:16:08 -0800 Received: by gate.microware.com; id AA07037; Thu, 28 Dec 95 01:13:44 CST Received: from mcrware.microware.com(192.52.109.32) by gate.microware via smap (g3.0.1) id xma007033; Thu, 28 Dec 95 01:13:14 -0600 Received: by mcrware.microware.com id AA24927 (5.67a8/IDA-1.5); Thu, 28 Dec 1995 01:14:49 -0600 Date: Thu, 28 Dec 1995 01:14:49 -0600 From: Scott McGee Message-Id: <199512280714.AA24927@mcrware.microware.com> To: genweb@UCSD.EDU, lines-l@vm1.nodak.edu, susan.king@trace.cgsg.com Subject: Can't load REUNION GEDCOM files Content-Length: 2301 More info on the REUNION gedcom files LifeLines won't load for me. First, I found out that they are written with REUNION 4.0. Second, it can save for REUNION, Ancestral Family, and Other. I tried all three varieties and none seemed to work. The Ancestral Family version produced the least errors. I looked at one file, and there were two kinds of errors. The first was both the SUBM and the first SOUR records both using @S1@. I tried deleting the SUBM record, and the error count decreased a bit. The second error is a bunch of lines like: Error: Record R93 is referred to but not defined. I looked, and there are a bunch of source records, most of which look pretty normal other than all data is in 1 NAME or 2 CONT tags (Hey, maybe that is all REUNION offers, I don't know) until I come to a SOUR record that looks like: 0 @S941@ SOUR 1 NAME @R93@ but of course, there is no R93 record anywhere in the file. It looks like a bunch of these is what is screwing things up. The person who produced these files for me doesn't seem to have had problems before, but has never used LifeLines either. Does anyone recognize this behavior, and if so, is it due to the way the program is used, or is this an actual bug that should be reported to the REUNION people. Susan, do you know where these references came from? I just finished playing with one file, and found that if I just delete all the SOUR records with the bogus @Rnnn@ pointers, it will in fact load into LifeLines. It seems that the behavior of LifeLines is in fact due to invalid GEDCOM files. (Tom, you should be glad to hear that!) Now if I can just figure out how to fix em all without having to hand edit all the bad pointer out. Thanks to anyone who can shed light (and the many who responded so far!) Scott GENEALOGY | Do you know who your ancestors are? | Scott McGee -----------+---------------------------------------+--------------------- email: smcgee@microware.com | What? Me speak for web: http://genealogy.org/~smcgee/homepage.html | someone else? Nah! ---------------------------------------------------+--------------------- See my genealogy page at http://genealogy.org/~smcgee and my GenWeb page at http://genealogy.org/~smcgee/genweb From list-relay@UCSD.EDU Thu Dec 28 02:30:15 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id CAA19410 for ; Thu, 28 Dec 1995 02:30:14 -0800 Received: from gateway.informix.com (gateway.informix.com [192.216.240.3]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id CAA17571 for ; Thu, 28 Dec 1995 02:32:04 -0800 Received: from informix.com (infmx.informix.com) by gateway.informix.com (4.1/SMI-4.1) id AA11668; Thu, 28 Dec 95 02:24:00 PST Received: from obelix.informix.com by informix.com (4.1/SMI-4.1) id AA19522; Thu, 28 Dec 95 02:31:43 PST Received: from balti by obelix.informix.com (4.1/SMI-4.1) id AA02694; Thu, 28 Dec 95 10:34:38 GMT Sender: doom@informix.com Message-Id: <30E271E5.6A89@informix.com> Date: Thu, 28 Dec 1995 10:31:01 +0000 From: Mark Dooling Organization: Informix Software X-Mailer: Mozilla 2.0b3 (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: "Michael A. Patton, genealogy on the web" Cc: MLANE@csi.compuserve.com, genweb@UCSD.EDU Subject: Re: ROOTSBOOK & ISDN References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In my experience, the best page listing such resources is: http://thelist.com Regards Mark Dooling Michael A. Patton wrote: > > Another option you should think about is off-site hosting. One good > option for this that I've seen is Paranoia.com, which is $100/year. > It is limited to non-commercial usage, see their page about signing up > at for details. You need > your own access to the Internet for maintenance, but they'll house > your pages. There are a bunch of other similar services. I think > there's a page on them in Yahoo somewhere... > > -MAP -- MARK DOOLING : Technical Support UK : +44 181 818 1042 : mailto:doom@informix.com inside: http://koetsu/~doom outside: http://www.ftech.net/~doom and this is me with hair plus stupid grin: http://koetsu/~doom/testmail.html From list-relay@UCSD.EDU Thu Dec 28 05:02:16 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id FAA19505 for ; Thu, 28 Dec 1995 05:02:16 -0800 Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id FAA18376 for ; Thu, 28 Dec 1995 05:03:15 -0800 Received: from ip-bend1-24.teleport.com (ip-bend1-24.teleport.com [206.163.116.56]) by desiree.teleport.com (8.6.12/8.6.9) with SMTP id FAA07621 for ; Thu, 28 Dec 1995 05:03:12 -0800 Received: by ip-bend1-24.teleport.com with Microsoft Mail id <01BAD4E1.F8C1F1E0@ip-bend1-24.teleport.com>; Thu, 28 Dec 1995 05:04:31 -0800 Message-ID: <01BAD4E1.F8C1F1E0@ip-bend1-24.teleport.com> From: Jeff Murphy To: "'GenWeb mailing list'" Subject: Adding queries to genealogy pages Date: Thu, 28 Dec 1995 05:04:17 -0800 Encoding: 31 TEXT I would like to be able to provide queries for users of my page. The problem is that I don't know enough html to do it. What I had in mind was for someone to be able to enter their name, emal address, and a query, like: "Looking for RHOADS, VICK, and NOFFSINGER lines [blah, blah, blah]". Multiple lines for the query. Then I want to be able to keep them on the system for a period of time, and display all of them to anyone who wants to see them. I know part of the problem is learning the FORM statements. That looks fairly simple. It is the redisplay of the data that I don't know how to handle. Is this cgi-bin stuff? (I haven't looked into that at all.) But more than this, though, I think it would be nice to be able to allow everyone with a genealogy page access to the same code, so that anyone who wants to add queries to their page could do so. Not that these would be interlinked - although given the time and inclination, I don't see why not - but that there would be some uniformity in the approach. My page assumes an interest in Muhlenberg Co., KY, so there is really no need for someone to go into where they are searching. Others would have different approaches to their queries, if they wish to have them at all. Anyone want to write some code? I'm always happy to turn a project over to someone more competent. Jeff Murphy Redmond, OR jmurphy@teleport.com see my home page for genealogy in Muhlenberg Co., Kentucky http://www.teleport.com/~jmurphy/ From list-relay@UCSD.EDU Thu Dec 28 05:45:08 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id FAA19562 for ; Thu, 28 Dec 1995 05:45:07 -0800 Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id FAA07194 for ; Thu, 28 Dec 1995 05:42:01 -0800 Received: from ip-bend1-24.teleport.com (ip-bend1-24.teleport.com [206.163.116.56]) by desiree.teleport.com (8.6.12/8.6.9) with SMTP id FAA12794 for ; Thu, 28 Dec 1995 05:41:57 -0800 Received: by ip-bend1-24.teleport.com with Microsoft Mail id <01BAD4E7.61AEF5E0@ip-bend1-24.teleport.com>; Thu, 28 Dec 1995 05:43:14 -0800 Message-ID: <01BAD4E7.61AEF5E0@ip-bend1-24.teleport.com> From: Jeff Murphy To: "'GenWeb mailing list'" Subject: More on queries Date: Thu, 28 Dec 1995 05:41:45 -0800 Encoding: 187 TEXT Having written the previous message, I just found this one, which would meet all *my* needs, if I can get it installed on our system: The Nizkor Guest Book Written by Jamie McCarthy (jamie@nizkor.almanac.bc.ca) for the Nizkor Project (http://www.almanac.bc.ca/). Copyright 1995 Jamie McCarthy. The source code for the Nizkor Guest Book may be publicly distributed by any means, as long as the above authorship and copyright notice is kept intact. If a modified version is distributed, please explain what changes have been made. It may be used free of both charge and obligation. This guest book is a bit different from others I've seen, because it protects against hacker invasion. It doesn't automatically post every entry to the public guest book page. Rather, it archives them in a private directory until the webmaster(s) get(s) around to confirming them. (Or deleting them, or moving them to a "special" page for safekeeping.) Furthermore, hacker mischief is discouraged by limiting the number of entries archived to 100, and by limiting the size of each entry to 16K, so the absolute worst they can do is use up 1,600K on your hard drive. It 's also designed to be clean and dignified; no fancy formatting of incoming entries is allowed, and HTML codes are stripped, so that people can't put giant pictures of Barney into your guest book. See for why it's a good idea to Barney-proof your guest book. Only

and tags are allowed. If you haven't yet seen the guest book in action, you can see what it looks like to the public, at the Nizkor Project: You can't see the private "webmaster-only" half of it -- the part where users' entries are confirmed and actually placed on the guest book -- because, well, because that part is private. If you want to see what it looks like, you'll have to install your own copy! To install your own copy, you'll need these requirements: REQUIREMENTS 1. Access to a computer (unix strongly recommended) that is running perl5 (5.001m recommended). You may be able to convince the code to work on a non-unix system or on perl version 4, but don't come to me for help. 2. cgi-lib.pl and, if it's not already installed, sufficient security clearance to install it. If you don't know what cgi-lib.pl is, visit . If you don't know whether you have it, look in /usr/local/lib/perl5 and maybe /usr/local/lib. 3. A bit of patience, to change all the constants over from my system to yours. This is pretty straightforward. 4. Sufficient security clearance or permission from your sysadmin to do each of the following: a. To create a "private" directory that your HTTP daemon can access. This can be anywhere in the file system, and should not be readable by the outside world (unless you don't care if people read your incoming entries and your "special guest book," see below). Note that unix HTTP daemons (NCSA, for example) often run as user "root" but spawn subprocesses to do real work; the user/group IDs of those subprocesse s depend on how the HTTP daemon is configured. b. To install a public cgi-bin program. If you don't know what a cgi-bin is, see . If you don't know whether you have that clearance, ask around; if you still don't know, politely ask your system administrator. c. To install a private cgi-bin program. On NCSA httpd, creating any private directory means adding a line to the configuration file, killing the httpd process, and restarting it. I imagine it's similarly painful with other software. If you're not the sysadmin, don't be surprised if your sysadmin balks at doing this. It also requires a bit of knowledge of how user authentication works, which for NCSA httpd is pretty simple; see . Got all that? Good! Here are the installation instructions. INSTRUCTIONS 1. With your favorite editor, open up both ngb-confirm.pl and ngb-sign-in.pl and configure all the constants to be the way you like them. They're all well-marked at the top of each file, you can't miss them. If you don't know Perl, this may still be a bit intimidating. Here's all you need to know. Any line that starts with "#" is a comment. Any word that starts with "$" is a constant (or a variable). And, I put text into a comment in two ways. One way is with double quotation marks, as in: $myConstant = "the text"; Or, with line-oriented quoting: $myConstant = <. The URL to access it from a web bro wser would be . When you access that web page for the first time, you'll see a notice telling you that your guest book has been created. Or, you could type, from the unix command line, "/usr/fred/priv-cgi-bin/ngb-confirm.pl", which would give you a lot of HTML code, and somewhere in that code would be the same notice. 5. Call up your guest book file on your favorite web browser and see if you like it. If not, edit it. You can edit it however you please, as long as you don't change the line: 6. Test the sign-in script on your favorite browser. If you configured all the constants correctly in instruction 1, there should be a link to that script right on the guest-book.html page. If not, try accessing it manually. For example, pretend the sign-in script is in the directory /usr/fred/pub-cgi/bin/, which is set up to be . The URL to access it from a web browser would be . Run through the sign-in process, and be sure it gives you the message about your entry being added. Then go to the confirmation URL and be sure your entry shows up correctly. Then delete your entry (or add it, if you like). That's it! You now have a working guest book! Enjoy. If you have any questions, feel free to email me at jamie@nizkor.almanac.bc.ca. Jeff Murphy Redmond, OR jmurphy@teleport.com see my home page for genealogy in Muhlenberg Co., Kentucky http://www.teleport.com/~jmurphy/ From list-relay@UCSD.EDU Thu Dec 28 06:04:48 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id GAA19606 for ; Thu, 28 Dec 1995 06:04:47 -0800 Received: from arl-img-4.compuserve.com (arl-img-4.compuserve.com [198.4.7.4]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id GAA07375 for ; Thu, 28 Dec 1995 06:06:40 -0800 Received: by arl-img-4.compuserve.com (8.6.10/5.950515) id JAA27720; Thu, 28 Dec 1995 09:06:39 -0500 Date: 28 Dec 95 09:04:35 EST From: Mickey Lane To: GENWEB-L Subject: ROOTSBOOK & JAVA Message-ID: Too much idle time breeds weird ideas... To recap discussions re getting ROOTSBOOK back on the web, ISDN (64k) costs $1500 for setup and 3 months fees with $200/mo ongoing. Regular modem (28.8k) costs about $900 for the 3 months plus $120/mo ongoing. ROOTSBOOK had a lot of users when it was online and I would expect the same - or more - when it comes back. The 28.8 solution is not good enough for this anticipated load. Unless.... For those who haven't used ROOTSBOOK, it's output is lots and lots of very similar pages all using standard text. Perhaps 50% of the characters are the same from page to page. It occurs to me that a Java applet could be written that would vastly reduce the number of characters flowing across the 28.8 line and if smartly done, may yeild a performance better than the current format over 64k ISDN. Or, as occured to me when I was first looking into Java, a series of applets - each one adopting the appearance of the user's commercial genealogy package of choice. (I'll leave the possibilities here for others to explore...) If implemented, that would make 28.8 useable for some time to come. I'd still be faced with about $120/mo operating costs though and while I like y'all a lot, that's a bit steep. I've been thinking of some type of low-tech subscription mechanism to cover the costs. Perhaps a couple bucks a month mailed in, get access codes by return Email. Thoughts? Mickey. From list-relay@UCSD.EDU Thu Dec 28 06:04:49 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id GAA19612 for ; Thu, 28 Dec 1995 06:04:49 -0800 Received: from arl-img-4.compuserve.com (arl-img-4.compuserve.com [198.4.7.4]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id GAA18848 for ; Thu, 28 Dec 1995 06:06:42 -0800 Received: by arl-img-4.compuserve.com (8.6.10/5.950515) id JAA27735; Thu, 28 Dec 1995 09:06:40 -0500 Date: 28 Dec 95 09:04:37 EST From: Mickey Lane To: GENWEB-L Subject: Re: ROOTSBOOK & ISDN Message-ID: John Rigdon of Georgia Business Net said: >I work for an ISP, Georgia Business Net. I can help you set up the system on >the net at much less cost. ... >Our proposal to you and others is to eliminate the ISDN/DSU/CSU/MABELL part >of the circle altogether. We do this by placing your system next to ours and >hooking you up directly on our Ethernet backbone and T1 line. You can still >access the system any time as a sysop via telnet, pc anywhere et. al if >you're running Windows NT and by Telnet, FTP, World Group, et. al if you're >running Unix. I won't speak for Unix but NT doesn't have a native telenet service (daemon) and PC anywhere won't work with it at all. I've had experiences with the third party telenet packages and there are some security issues that need to be addressed before I'd allow their use. >The only "drawback" is that you can't physically touch the >hardware, but for that you save a thousand bucks or so in purchasing two high >speed modems (my end and yours) Ma Bell's setup charges and your monthly ISDN >or whatever charges. You do, on the other hand, need to purchase another computer. There's also the issue of backups and the periodic system management tasks that can't be done over the net. >All you'll need is local access to the net via telnet >and you can get to the system anytime. Incidentally, $40 per month is a darn >good price for ISDN access. Many parts of our area are being quoted up to >$125 per month. It depends on how close you are to the ma bell office. The local ISP provides intermittant ISDN access for $29.50/mo and 28.8 for less than that. 24 X 7 is what runs the price up. >The cost for us to host your system is $150.00 per month with a minimum 6 >month committment (first and last month in advance). You'll still have the >$200 domain name registration fee (unless you opt to piggyback on Georgia >Net). That's exactly what the local ISP quotes for 24 X 7 ISDN service at 64 Kbaud. I've made some more inquires. The $200 domain name setup seems to be a fixed thing unless you want to deal with InterNIC yourself. A 28.8 line open 24 X 7 will run $100/mo plus the standard phone company charges for a second line (perhaps $25/mo - I didn't call them yet) so the ongoing operating expenses are about $125/mo. Setup of the 28.8 line is $200 DNS + phone co. install ($50?) + a 28.8 modem at $200 for a one time total of $450. Keep in mind that this is all for 24 X 7 inbound service. Intermittant outbound service is *lots* cheaper. Mickey. From list-relay@UCSD.EDU Thu Dec 28 08:23:22 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id IAA19758 for ; Thu, 28 Dec 1995 08:23:22 -0800 Received: from california.et.byu.edu (california.et.byu.edu [128.187.133.10]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id IAA09381 for ; Thu, 28 Dec 1995 08:24:36 -0800 Received: by california.et.byu.edu; Thu, 28 Dec 1995 09:23:12 -0700 (MST) Message-ID: <199512281623.JAA27279@california.et.byu.edu> Subject: Re: ROOTSBOOK & ISDN To: genweb@UCSD.EDU Date: Thu, 28 Dec 1995 09:23:11 -0700 (MST) Cc: rex@surfutah.com From: rex@surfutah.com (Rex Myer) Reply-to: "rex@surfutah.com (Rex Myer)X-Mailer":rex@surfutah.com.X-Mailer:ELM[version.2.4.PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Mickey, I have not replied to a listserver before so if this goes to the wrong place, please e-mail me directly. Thanks. As long as everyone is putting their 2 cents in on how to get your services hosted in the most affordable manner, I will add mine for what it may be worth. A friend of mine has a service of providing what is called a virtual server. For around $20(US) (no more than $30) a month you can get ftp, telnet, http (Web) server, POP3 e-mail with control over aliasing. That is all I remember for the moment mainly because those are the only ones I use. His service does not cover the DNS registration through internic (or whoever) which is $50(US)? setup and $50(US)? per year. He wrote the virtual server himself by modifying the BSD kernal. To my knowledge he is the only one offering a virtual server. Some advantages to a virtual server: - It currently runs on a T1 connection. (They will be upgrading their connection soon.) You don't have to pay for the connection setup or monthly use (to phone company, et al). - They have their own hardware and backup system already in place. You don't have to invest in the hardware to get going there or for the connection. - To the outside world, it behaves the same as a regular server. - It uses UNIX OS (advantage from my point of view). - You are your own webmaster, so you don't have to worry about getting security clearance from the CGI monitors to add your own flavor of CGI (or even Java). Some disadvantages: - It uses UNIX OS (could be a disadvantage to some). - You still need to get an internet provider to connect to the server to do system maintenance on the virtual server. (Still the cost is way below the investment required for a real server). If you want to see a virtual server in action, you can check out surfutah.com at: http://www.surfutah.com/ Or my pages on surfutah at: http://www.surfutah.com/consultants/rex/ (just general http server example) http://www.surfutah.com/web/famtrak/ (some ftp example) http://www.surfutah.com/web/webgen/ (CGI web stuff) This is not meant to offend those that don't like advertisements. I just thought that I would offer a suggestion on it. Cheers, Rex -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rex Myer Consultant rex@surfutah.com http://www.surfutah.com From list-relay@UCSD.EDU Thu Dec 28 11:34:17 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id LAA20067 for ; Thu, 28 Dec 1995 11:34:17 -0800 Received: from A.crl.com (A.crl.com [165.113.1.65]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id LAA24145 for ; Thu, 28 Dec 1995 11:32:56 -0800 Received: from A108002.ccr1.as.crl.com by A.crl.com with SMTP id AA14072 (5.65c/IDA-1.5 for ); Thu, 28 Dec 1995 11:32:08 -0800 Message-Id: <199512281932.AA14072@A.crl.com> X-Sender: cleow@a.crl.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 28 Dec 1995 11:26:46 -0600 To: genweb@UCSD.EDU From: cleow@A.crl.com (Cleo Wilcox) Subject: MAILING LIST REMOVE NAME FROM MAILING LIST. Thank you Cleo Wilcox 420-C Washington St. Vallejo, CA From list-relay@UCSD.EDU Thu Dec 28 13:40:42 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id NAA20299 for ; Thu, 28 Dec 1995 13:40:42 -0800 Received: from ns1.ptd.net (ns1.ptd.net [198.80.46.1]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id NAA26599 for ; Thu, 28 Dec 1995 13:41:49 -0800 From: hughie@postoffice.ptd.net Received: from cs2-6.leh.ptd.net (cs2-6.leh.ptd.net [204.186.4.22]) by ns1.ptd.net (8.6.12/8.6.9) with SMTP id QAA22434 for ; Thu, 28 Dec 1995 16:41:24 -0500 Date: Thu, 28 Dec 1995 16:41:24 -0500 Message-Id: <199512282141.QAA22434@ns1.ptd.net> X-Sender: hughie@postoffice.ptd.net X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: GENWEB@UCSD.EDU UNSUBSCRIBE "EVERYBODY dies sometime - the difference is what you do 'till then." ...Pastor Richard A. Hughen, Sr. From list-relay@UCSD.EDU Thu Dec 28 18:28:34 1995 Received: from UCSD.EDU (mailbox1.ucsd.edu [132.239.1.53]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id SAA20705 for ; Thu, 28 Dec 1995 18:28:33 -0800 Received: from mail04.mail.aol.com (mail04.mail.aol.com [152.163.172.53]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id SAA00733 for ; Thu, 28 Dec 1995 18:27:53 -0800 From: JohnR238@aol.com Received: by mail04.mail.aol.com (8.6.12/8.6.12) id VAA25719; Thu, 28 Dec 1995 21:27:53 -0500 Date: Thu, 28 Dec 1995 21:27:53 -0500 Message-ID: <951228212751_26076051@mail04.mail.aol.com> To: MLANE@csi.compuserve.com cc: genweb@UCSD.EDU Subject: Re: ROOTSBOOK & EMAIL For about two years now I've been providing similar type info. via email only. The system has proved to be efficient relative to the costs, especially when I've worked through the numbers for providing a potentially higher level. The difference is essentially FREE email feeds against a couple hundred bucks and up just as you've discovered. I seriously doubt myself that you'll provide any adequate service without a full T1 connection. I now have 12 machines servicing the email queue and the system still continues to fall further and further behind. As I've added capacity, the queries have grown even faster. About 6 months ago I put the most requested files on an FTP server and they now average over 400 downloads per day. I said all that to say this. I think an email server can be made to work quite effectively, but we are still way ahead of the wave of the masses getting on the net. Anything you do now must be scalable without breaking the bank and for me, email is the only "no cost" solution. Just handling my current queries on a "telnet" basis would require a system capable of handling 600 sessions per day - that's 30 - 50 simultaneous users! - with no capacity for growth. I use Pegasus mail with a back end program I've written to parse each folder and send back the requested files. For items that require a search of the data bases, it goes in a queue and the system eventually spits out the message back. I think most all of yours will be query searches, so you can route everything to a batch process and send back emails. Incidentally, inspite of my best efforts at explaining proper syntax for the email requests, I still have to have someone spend an hour per day reading the correcting the batches before they go to the program. When I tried spitting out improperly formatted queries early on and just ignoring them, the number of further "personal" emails I had to answer was horrendous. - and people get very offensive when their emails go unanswered. John Rigdon From list-relay@UCSD.EDU Thu Dec 28 20:28:14 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id UAA20940 for ; Thu, 28 Dec 1995 20:28:13 -0800 Received: from Joyce-Perkins.tenet.edu (Joyce-Perkins.tenet.edu [198.213.2.6]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id UAA21251 for ; Thu, 28 Dec 1995 20:29:25 -0800 Received: (from sseibert@localhost) by Joyce-Perkins.tenet.edu (8.7.1/8.7.1) id WAA11536; Thu, 28 Dec 1995 22:29:24 -0600 (CST) Date: Thu, 28 Dec 1995 22:29:24 -0600 (CST) From: Johnette Sue Seibert cc: genweb@UCSD.EDU Subject: Re: ROOTSBOOK & EMAIL In-Reply-To: <951228212751_26076051@mail04.mail.aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII SET DIGEST From list-relay@UCSD.EDU Fri Dec 29 22:25:09 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id WAA24864 for ; Fri, 29 Dec 1995 22:25:09 -0800 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id WAA13743 for ; Fri, 29 Dec 1995 22:24:49 -0800 From: ttw@beltway.att.com (T.T.Wetmore) To: lines-l@vm1.nodak.edu, genweb@UCSD.EDU Received: from beltway (beltway.mv.att.com) by ig1.att.att.com id AA27352; Sat, 30 Dec 95 01:23:01 EST Received: by beltway (4.1/SMI-4.0) id AA01033; Sat, 30 Dec 95 01:24:47 EST Date: Sat, 30 Dec 95 01:24:47 EST Original-From: beltway!ttw (T.T.Wetmore) Message-Id: <9512300624.AA01033@beltway> Original-To: att!vm1.nodak.edu!lines-l, genweb@ucsd.edu Subject: Tom Wetmore's URLs on WWW FYI, Tom Wetmore is now on the WWW. Here are the main URLs: http://www.shore.net/~ttw -- Tom Wetmore's home page http://www.shore.net/~ttw/lines/lines.html -- LifeLines home page ttw@shore.net -- My private email address If you have references to me or to LifeLines in your WWW pages, please change them to these new links. For those of you keeping links to GenWeb databases, I have a database of my own ancestors at (of course, it's an HTML file generated by LifeLines!): http://www.shore.net/~ttw/anc.html Thanks, Tom Wetmore, ttw@shore.net, ttw@beltway.att.com From list-relay@UCSD.EDU Sat Dec 30 06:00:56 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id GAA27123 for ; Sat, 30 Dec 1995 06:00:55 -0800 Received: from mail02.mail.aol.com (mail02.mail.aol.com [152.163.172.66]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id FAA18737 for ; Sat, 30 Dec 1995 05:52:51 -0800 From: SEKnoblock@aol.com Received: by mail02.mail.aol.com (8.6.12/8.6.12) id IAA26001 for genweb@ucsd.edu; Sat, 30 Dec 1995 08:52:50 -0500 Date: Sat, 30 Dec 1995 08:52:50 -0500 Message-ID: <951230085250_81025043@mail02.mail.aol.com> To: genweb@UCSD.EDU Subject: New Web Genealogy Hello I have a small genealogy up using Gene Stark's ged2html for windows at (http://www.webcom.com/cityg/home/jgunnell/persons.html). Also my ancestry is available at (http://www.webcom.com/cityg/home/ancestry/persons.html) Steve +---------------------------------------------------------------------+ | C I T Y G A L L E R Y http://www.webcom.com/cityg | | The History of 19th Century Photography | | Biography and Geneaolgy cityg@webcom.com | | 19th Century Exchange Steve Knoblock Prop'r | +---------------------------------------------------------------------+ From list-relay@UCSD.EDU Sun Dec 31 06:20:11 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id GAA00589 for ; Sun, 31 Dec 1995 06:20:11 -0800 Received: from gw1.att.com (gw1.att.com [192.20.239.133]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id GAA05016 for ; Sun, 31 Dec 1995 06:17:50 -0800 From: ttw@beltway.att.com (T.T.Wetmore) To: lines-l@vm1.nodak.edu, genweb@UCSD.EDU Received: from beltway (beltway.mv.att.com) by ig1.att.att.com id AA22963; Sun, 31 Dec 95 09:14:43 EST Received: from grebe.beltway by beltway (4.1/SMI-4.0) id AA15477; Sun, 31 Dec 95 09:16:29 EST Date: Sun, 31 Dec 95 09:16:29 EST Original-From: beltway!ttw (T.T.Wetmore) Message-Id: <9512311416.AA15477@beltway> Original-To: att!vm1.nodak.edu!lines-l, genweb@ucsd.edu Subject: HTML Ahnentafel Generator Liners, Webbers, In a continuing effort to demonstrate the flexibility of LifeLines for generating HTML files, here's another LL program for you to try out. This program will generate an HTML page with a simple ahnentafel. Each person is hyperlinked to their child, father, mother, or "same as" reference. There is one modification needed to make this program cover all the bases. In cases of pedigree collapse, there will be a few persons what should have more than one child link (the same persons that are targets of the same as links that are included). This is a simple modification to the program that I will add. As is, this program follows all upward links correctly, regardless of pedigree collapse. In the downward direction only the first child link will be followed in the cases where a person has more than one child earlier in the table. Pretty minor issue really, but thought I should tell you anyhow. It is leaving out these little details that drives me crazy about the commercial programs. Let me again then advertise the benefits of LifeLines over all other genealogical programs and GEDCOM to HTML translators. With LifeLines you can generate HTML files in any format you want from GEDCOM files. You don't need to wait for anyone to write that specific GEDCOM to HTML translator that generates HTML files that look just right to you on the web. You can write or modify a LifeLines program to give you exactly what you want. Power to the people, my friends. Tom Wetmore - - - - - - - - - - htmlahnen - - - - - - - snip - - - - - - - - - - - - /* htmlahnen -- Generate an ahnentafel chart in HTML format */ /* Tom Wetmore */ /* Version 1, 12/31/95 */ proc main () { getindi(per, "Whose Ahnentafel do you want?") if (not(per)) { return() } set(title, concat("Ahnentafel of ", name(per, 0))) call htmlhead(title) call htmlheading(3, title) print("Ahnentafel of ", name(per), "\n") list(ilist) /* list of persons waiting to be output */ list(clist) /* list of children of those persons */ list(alist) /* ahnen numbers of those persons */ list(glist) /* generations of those persons */ table(ktab) /* table of all persons who have been output */ enqueue(ilist, per) /* initialize all structures */ enqueue(clist, 0) /* first child is empty */ enqueue(alist, 1) enqueue(glist, 1) set(cgen, 0) while(per, dequeue(ilist)) { set(chl, dequeue(clist)) set(ahnen, dequeue(alist)) set (tgen, dequeue(glist)) if (ne(cgen, tgen)) { "

" call htmlstrong("Generation ") call htmlstrong(d(tgen)) "\n

" set(cgen, tgen) } "

" set(old, lookup(ktab, key(per))) if (old) { d(ahnen) " Same as " d(old) "(" call htmllink(concat("#", key(per)), "link") ")" } else { call htmlname(key(per)) print(".") insert(ktab, save(key(per)), ahnen) d(ahnen) " " call htmlstrong(name(per, 0)) "\n" if (chl) { "(" call htmllink(concat("#", key(chl)), "child") ")" } if (par,father(per)) { enqueue(ilist, par) enqueue(clist, per) enqueue(alist, mul(2, ahnen)) enqueue(glist, add(cgen, 1)) "(" call htmllink(concat("#", key(par)), "father") ")" } if (par,mother(per)) { enqueue(ilist, par) enqueue(clist, per) enqueue(alist, add(1, mul(2, ahnen))) enqueue(glist, add(cgen, 1)) "(" call htmllink(concat("#", key(par)), "mother") ")" } if (e, birth(per)) { "
b. " long(e) "\n" } if (e, death(per)) { "
d. " long(e) "\n" } } "\n" } call htmltail() } proc htmlhead (title) { "" title "\n\n" } proc htmltail () { "\n\n" } proc htmlstrong (str) { "" str "" } proc htmllink (href, link) { "" link "" } proc htmlname (name) { "" } proc htmlheading (lev, head) { "" head "\n" } From list-relay@UCSD.EDU Sun Dec 31 07:50:23 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id HAA00691 for ; Sun, 31 Dec 1995 07:50:23 -0800 Received: from gp.magick.net (gp.magick.net [198.68.11.1]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id HAA06403 for ; Sun, 31 Dec 1995 07:51:39 -0800 Received: by gp.magick.net (Linux Smail3.1.29.1 #3) id m0tWQ2r-000xCPC; Sun, 31 Dec 95 07:51 PST Date: Sun, 31 Dec 1995 07:51:37 -48000 From: Denise Fields Subject: Searches To: genweb@UCSD.EDU cc: linesl@vm1.nodak.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This may not be the way to request info, but wwhen I signed up with genweb, I did not get info on how...certainly did from ROOTS-L. Anyway, pulled these addresses from mail I keep getting, and thought okay I'll try it, and then when you guys shoot me down, please explain what I am doing wrong?! Am seeking info on Garner, Fields, Wightman, Stelting, Karstetter, Willard, Koehler, Edson, Oden, Davies (Uncle Tom Cobbly and all!). Skip uncle tom, just a bit of early Sunday morning humor. Even an address for proper submission/search format would be helpful! Thanks and happy New year! Denise From list-relay@UCSD.EDU Sun Dec 31 09:02:45 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id JAA00791 for ; Sun, 31 Dec 1995 09:02:44 -0800 Received: from roxy.sfo.com (roxy.sfo.com [205.162.14.50]) by UCSD.EDU (8.6.12/8.6.9) with ESMTP id JAA07529 for ; Sun, 31 Dec 1995 09:03:33 -0800 From: mavrogeorge@genealogysf.com Received: from [205.162.14.119] (sf-119.sfo.com [205.162.14.119]) by roxy.sfo.com (8.7.3/8.7.3) with SMTP id JAA15682 for ; Sun, 31 Dec 1995 09:02:15 -0800 (PST) Date: Sun, 31 Dec 1995 09:02:15 -0800 (PST) Message-Id: <199512311702.JAA15682@roxy.sfo.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Subject: html generator To: genweb@UCSD.EDU X-Mailer: SPRY Mail Version: 04.00.06.21 Wow have I been playing around with a great tool. The new update to Roots4 has an option in the reports section to create an html page. You have the same options you have as if you were printing one as to the form - descendant, genration, family, and what type of information to include, etc. Also lets you tell it what to use as a background, for an email gif, for a gedcom gif, for a title graphic, for a table of contentsgraphic etc, etc. Even includes the ability to put in a WAV file if you want. There are also options for making a local html file, making one for a server, putting it all in one file, putting it in several files and how many people per file, -- this is great stuff! I scanned in some photos, cranked up the R4, followed the simple screens, and voila!! an html page. You can see it on my home page http://www.sfo.com/~genealogysf - it is the Paspalas/Varkas genealogy. When you look at it keep in mind that this was done from menu options in Roots4 and I didn't make -any- changes to the generated html source. I just uploaded it to my provider. From list-relay@UCSD.EDU Sun Dec 31 16:25:21 1995 Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54]) by fuji.ucsd.edu (8.6.9/8.6.9) with ESMTP id QAA01427 for ; Sun, 31 Dec 1995 16:25:20 -0800 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by UCSD.EDU (8.6.12/8.6.9) with SMTP id QAA16905 for ; Sun, 31 Dec 1995 16:27:16 -0800 From: ttw@beltway.att.com (T.T.Wetmore) To: lines-l@vm1.nodak.edu, genweb@UCSD.EDU Received: from beltway (beltway.mv.att.com) by ig1.att.att.com id AA17934; Sun, 31 Dec 95 19:24:13 EST Received: from grebe.beltway by beltway (4.1/SMI-4.0) id AA19488; Sun, 31 Dec 95 19:26:00 EST Date: Sun, 31 Dec 95 19:26:00 EST Original-From: beltway!ttw (T.T.Wetmore) Message-Id: <9601010026.AA19488@beltway> Original-To: att!vm1.nodak.edu!lines-l, genweb@ucsd.edu Subject: htmlahnen version 2 Liners & Webbers, Here's R2 of LifeLines program htmlahnen, a program that generates an HTML version of an ahnentafel from a LifeLines database. The output looks a lot cleaner, and this version fully handles all problems of pedigree collapse. Try it, you'll like it. Tom Wetmore - - - - - - - - - - - snip, snip - - - - - - /* htmlahnen -- Generate an ahnentafel chart in HTML format */ /* Tom Wetmore */ /* Version 2, 12/31/95 */ proc main () { getindi(per, "Whose Ahnentafel do you want?") if (not(per)) { return() } set(title, concat("Ahnentafel of ", name(per, 0))) call htmlhead(title) call htmlheading(3, title) print("Ahnentafel of ", name(per), "\n") list(ilist) /* list of persons waiting to be output */ list(alist) /* ahnen numbers of those persons */ list(glist) /* generations of those persons */ table(ktab) /* table of all persons who have been output */ table(ctab) /* table of child links */ enqueue(ilist, per) /* initialize all structures */ enqueue(alist, 1) enqueue(glist, 1) set(cgen, 0) call addchild(ctab, 0, per) while(per, dequeue(ilist)) { set(ahnen, dequeue(alist)) set (tgen, dequeue(glist)) if (ne(cgen, tgen)) { "

" call htmlstrong("Generation ") call htmlstrong(d(tgen)) "\n" set(cgen, tgen) } "

" set(old, lookup(ktab, key(per))) if (old) { call htmlstrong(d(ahnen)) " Same as " call htmlstrong(d(old)) call htmllink(concat("#", key(per)), " link") } else { call htmlname(key(per)) print(".") insert(ktab, save(key(per)), ahnen) call htmlstrong(d(ahnen)) " " call htmlstrong(name(per, 0)) "\n" set(lst, lookup(ctab, key(per))) set(comma, 0) forlist (lst, key, n) { if (comma) { ", " } else { set(comma, 1) } call htmllink(concat("#", key), "chld") } if (par,father(per)) { enqueue(ilist, par) call addchild(ctab, per, par) enqueue(alist, mul(2, ahnen)) enqueue(glist, add(cgen, 1)) if (comma) { ", " } else { set(comma, 1) } call htmllink(concat("#", key(par)), "fath") } if (par,mother(per)) { enqueue(ilist, par) call addchild(ctab, per, par) enqueue(alist, add(1, mul(2, ahnen))) enqueue(glist, add(cgen, 1)) if (comma) { ", " } else { set(comma, 1) } call htmllink(concat("#", key(par)), "moth") } if (e, birth(per)) { "
b. " long(e) "\n" } if (e, death(per)) { "
d. " long(e) "\n" } } "\n" } call htmltail() } proc addchild (ctab, per, par) { set(lst, lookup (ctab, key(par))) if (not(lst)) { list(lst) if (per) { setel(lst, 1, save(key(per))) } insert(ctab, save(key(par)), lst) } else { setel(lst, add(1, length(lst)), save(key(per))) } } proc htmlhead (title) { "" title "\n\n" } proc htmltail () { "\n\n" } proc htmlstrong (str) { "" str "" } proc htmllink (href, link) { "" link "" } proc htmlname (name) { "" } proc htmlheading (lev, head) { "" head "\n" }