ROOTSWEB REVIEW: Genealogical Data Cooperative Weekly News Vol. 1, No. 15, 23 September 1998; Circulation: 212,500+ Copyright (c) 1998 RootsWeb Genealogical Data Cooperative Editors: Julia M. Case and Myra Vanderpool Gormley, CG * * * * * CONTENTS: News and Notes from RootsWeb; On the Internet? Must be Fair Game!; Census Project Uploads and This Week's Top Ten New Databases in the USGenWeb Archives;Connecting through RootsWeb; Mailing Lists; Web Sites; Humor; Reprint Policy; Author Guidelines; Unsubscribe Instructions * * * * * NEWS AND NOTES FROM ROOTSWEB LIST DOWNTIME (by Ellen Seebacher). Last week, as RootsWeb Review readers know, lists.rootsweb.com was down for a couple of days. Tim Pierce, RootsWeb's mailing-list administrator, sent out a notice (from a different RootsWeb server) to nearly all subscribers to RootsWeb mailing lists, explaining that the lists were not functioning and we were working on the problem. Some folks tried to be helpful, however, and forwarded Tim's "mailing lists are down" notice ... to their (surname, locality, or special-interest) mailing lists. Unfortunately, because those lists were not working, this accomplished three things: * The forwarded notice didn't reach anyone while lists.rootsweb.com was down; no one could send or receive messages on any of the lists hosted on that machine. * After lists.rootsweb.com was fixed and the lists there began to function again, some subscribers received multiple forwarded messages (which had been stored on an incoming server) saying that the lists were not working. * Many people became, understandably, confused -- thinking that lists.rootsweb.com had gone down _again_. If we have a future crisis which causes downtime for mailing lists, please help us to prevent mass confusion by allowing RootsWeb staff to handle the updates. Thanks to all our readers for understanding! Special thanks to RootsWeb listowner Jeff Owens for pointing out the problem for RootsWeb Review. * * * ROOTSWEB HELPDESK. For answers to your questions about RootsWeb, visit the HelpDesk at: * * * WANT TO JOIN THE COOPERATIVE? For membership details, please visit: * * * * * This article first appeared in "UFT Notes & News" at on Thursday, 17 September 1998. ON THE INTERNET? MUST BE FAIR GAME! by Rhonda R. McClure On the Internet? Must be fair game? In a word -- WRONG. Just because you find something on the Internet, that does not mean that you can take it and use it on your Web page. There are usually copyright issues that will affect how and what you can incorporate into your own Web page. Creating a Web page that shares your family history or your favorite Web links is just like writing an article for a periodical or publishing your family history in a book. You spend large amounts of time and sometimes money gathering the information. You crank microfilms and work through dusty tomes. You've spent hours putting the information into your genealogy program. And then you design and create your Web page. You work out the bugs and make sure that the page looks good no matter what browser a person is using. And you finally share your masterpiece with the world. It's almost harder than giving birth. A month or two later you are out surfing the Internet. And suddenly there in front of you is a large portion of your own hard work. Only, it is now being claimed by someone else. Unfortunately this is becoming a regular scenario on the Internet. People think that just because something is available on the Internet, that makes it in the public domain. However, this is not the case. The public domain is where material on which copyright or patent rights have expired goes. Electronic publishing is publishing. You cannot take someone else's work and call it your own. You may be asking yourself then about such items as births, marriages and deaths. What about the dates and places? Those can't be copyrighted. And you are thinking neither can a link to a Web site. This is true. However, the way in which a person displays this information -- that is what is copyrighted. So, the next time you are surfing the Internet and find a site that you particularly like, please don't copy the source and make it your own. Compliment the developer of that site and ask them if you can add a link to their page on yours. Don't take others' hard work; that is their property. Don't be a thief on the Internet. Remember the Golden Rule. It applies in cyberspace too. * * * * * USGENWEB CENSUS PROJECT -- NEW UPLOADS Allamakee County, Iowa, 1850 transcribed from an S-K publication by Jane Schoh, Nancy Rathbun, Sue Kenyon, and Mike Peterson Clark County, Arkansas, 1840 transcribed by Betsy Mills * * * TOP TEN NEW DATABASES ADDED TO THE USGENWEB ARCHIVES 1. WATSON'S ANNALS of PHILADELPHIA and PENNSYLVANIA located in Philadelphia county archives. Vol. I (complete) and Vol. II (in progress). Published 1857. 2. GUIDEBOOK TO HISTORIC GERMANTOWN, 1902 3. HISTORY OF SCHUYLKILL COUNTY, PENNSYLVANIA, with Illustrations and Biographical Sketches of Some of Its Prominent Men and Pioneers. New York: W. W. Munsell & Co., 36 Vesey Street, 1881 (complete with all line drawings) 4. GENEALOGICAL AND BIOGRAPHICAL ANNALS OF NORTHUMBERLAND COUNTY, Floyd, 1911 5. "75 Years of Sully County History 1883-1958" (South Dakota) 6. Index for the Civil War Pension Records for Louisiana submitted by the Louisiana State Archives. 7.-10. World War I Registrations -- South Dakota; Iowa; Alaska; Madison Parish, Louisiana. * * * * * CONNECTING THROUGH ROOTSWEB: Thanks for sending your stories. Last week I subscribed to the SIMPSON mailing list through RootsWeb. After receiving my confirmation notice and instructions, I made up a query and got it right out. My husband's father, a SIMPSON, died when he was about two years old and he was adopted by his step-father. (I had some information that I had received from his sister and this is what I based my query on.) The very first e-mail that I received from the SIMPSON list was from a person who said that they did not match up with our SIMPSONs but if I wanted to I could check out a site that had SIMPSONs from Iowa. I clicked on the site address and started scrolling down the page...bingo! There were my husband's uncle and aunt. The site was owned by the son-in-law of my husband's first cousin. Thanks RootsWeb! Barb * * * I had been so busy lately, I had not looked at my mailing list digests for weeks. It was a fluke that I opened a ROOTS-L file and spotted a query for ROUNDS from Don Ford. This is one of my husband's surnames that we have not found much about, so I decided to contact him. After a few e-mails, we discovered we had a common history -- The B. F. Rounds Artificial Limb Company of Kansas City, Missouri, ca 1898. Don's grandmother's brother, Benjamin F. Rounds owned this factory. His grandmother was Mayme Rounds of Kansas City. I knew I had heard someone, somewhere mention a company like this, so I contacted my father-in-law, who I discovered still owns a copy of this manufacturer's brochure. This was his grandmother, Gladys Rounds' father's company, but he had no other information for me, except that "a lady with the first name Elizabeth" had contacted him years before, and told him she was a distant relative doing ROUNDS research. I told Don Ford, who had grown up in Tulsa, where my father-in- law's father was raised, and gave him the phone number of my father-in-law's cousin in Oklahoma. Don called her and reported back that she had done ROUNDS research and knew all about Elizabeth, and gave him her phone number. It turns out that Elizabeth Rounds Turner of Kansas City has completed a book on the ROUNDS family of Kansas City, and we should be receiving copies of her information shortly. Don also was amazed that my husband's ROUNDS family and his own family all grew up in the same place, even attended the same church, but never knew each other. Then he looked over some funeral flower records for his grandmother -- and found listed on the "gifts from" page was the name of my husband's grandparents. Valerie * * * * * MAILING LISTS: To subscribe or unsubscribe from any RootsWeb mailing list, send an e-mail message with only the word SUBSCRIBE (or UNSUBSCRIBE) in the subject and the body of the message to [name of list]-L-request@rootsweb.com (for mail mode) or to [name of list]-D-request@rootsweb.com (for digest mode). For example, if you wish to discuss royal families, send your SUBSCRIBE message to: GEN-ROYAL-L-request@rootsweb.com For an index to most user mailing lists hosted by RootsWeb, visit . (PLEASE NOTE: Although all of the new mailing lists mentioned in RootsWeb Review are "live," it might be a few days before they appear on the ~maillist site.) NEW MAILING LIST REQUESTS. USGenWeb and WorldGenWeb hosts may have FREE locality mailing lists for the areas they host and for that purpose may ignore the "Sponsors-only" warning on the list request page. Please request new mailing lists at: NEW SURNAME MAILING LISTS ALVERSON (includes Alvison, Alberson and Olverson) BANKSTON (particularly in Pennsylvania, North and South Carolina and Georgia prior to 1850) BARGER BECKHAM BRADY CALLAM (especially Augustus Callam) CALLAWAY (includes Calaway, Caloway and Calloway) CHICKERING CLIMAS (includes Clemas and Clymas) COURTNEY (and other spellings) CUTHRELL (includes Cuthriell) DOXSIE (includes Doxey, Doxsee, Doxy, Dox, Docksey and Doxee) EHLERS FARTHING FUTRILL GERALD HIGBIE (includes Higbee and Higby) HOEY (includes Hoy and Haughey) ISAACS (in pre-1830 America with a focus in Virginia, Maryland, and the Carolinas) LATOURETTE MATTIX PASS (includes Pas, Passe, and Pace) PATZKOWSKI PIRZ RANEY (includes Raney) RHONE SHELDON SPONBERG STANTON (descendants of Thomas Stanton of Stonington, Connecticut) TARWATER (includes Theurwachter, Torwarter, etc.) WAY NEW REGIONAL MAILING LISTS GERMANY: PFALZ -- The Palatinate, an area between what is now Hessen, Saarland and Rheinland MEXICO: MEXICO SCOTLAND: BUTESHIREGENWEB -- Bute and Arran Islands SCT-KIRKCUDBRIGHTSHIRE -- Kirkcudbrightshire UNITED STATES: GAPIKE -- Pike County, Georgia GASCREVE -- Screven County, Georgia IAADAMS -- Adams County, Iowa ILROOTS - Illinois Roots INVIGO -- Vigo County, Indiana KSBOURBO -- Bourbon County, Kansas KSOTTAWA -- Ottawa County, Kansas MOBUTLER -- Butler County, Missouri MOCHRIST -- Christian County, Missouri NCGATES -- Gates County, North Carolina NJOCEAN -- Ocean County, New Jersey OHCARROL -- Carroll County, Ohio OKCLEVEL -- Cleveland County, Oklahoma OKKAY -- Kay County, Oklahoma OKMCCLAI -- McClain County, Oklahoma OKOTTAWA -- Ottawa County, Oklahoma ORKLAMAT -- Klamath County, Oregon TNOBION -- Obion County, Tennessee TXELLIS -- Ellis County, Texas TXPOTTER -- Potter County, Texas TXRANDAL -- Randall County, Texas WICALUME -- Calumet County, Wisconsin WICLARK -- Clark County, Wisconsin WISHEBOY -- Sheboygan County, Wisconsin NEW MAILING LISTS (ETHNIC, SPECIAL INTEREST, MISCELLANEOUS) ARCHIVES-CC -- USGenWeb county coordinators handling their USGW Archives directories CENSUS-CHAT -- Discussing the Census Project and tips in locating information CENSUS-ORG -- Executive Committee of the Census Project EnglandGenWeb-CC -- County Coordinators for EnglandGenWeb FreeBMD-Admins -- People administrating the Free (UK) Birth, Marriage, Death Records Project GERMAN-CANADIAN -- German-Canadian genealogical issues USGW_WEB -- USGenWeb National Webmasters * * * * * NEW WEB ACCOUNT REQUESTS. To request a Web account please e-mail the information to: NEW WEB SITES: Some of these might not yet be accessible. If one that interests you isn't up yet, please check again in a few days or a week. (the ~[tilde] before the name is required) will work for most of the following. If not, you will find most of them at the USGenWeb Project or the WorldGenWeb Project . For example, to visit the Hamburg, Germany Web site, go to: DEUTSCHLAND (GERMANY) deuham -- Hamburg deuscn -- Schleswig-Holstein ICELAND islwgw -- Iceland WorldGenWeb SCOTLAND sctsti -- Stirlingshire U.S.A. alcwroot -- Alabama Civil War Roots flgulf -- Gulf County, Florida gaclay -- Clay County, Georgia gadecatu -- Decatur County, Georgia gagrady -- Grady County, Georgia gathomas -- Thomas County, Georgia kyfloyd -- Floyd County, Kentucky kyfrankl -- Franklin County, Kentucky kyohio -- Ohio County, Kentucky kytodd -- Todd County, Kentucky mestonin -- Stonington, Maine medeeris -- Deer Isle, Maine mocamden -- Camden County, Missouri mocooper -- Cooper County, Missouri msnoxube -- Noxubee County, Mississippi ncmil -- North Carolina Military Project neotoe -- Otoe County, Nebraska ohsummit -- Summit County, Ohio orpionpr -- Oregon Pioneer Project sdbrule -- Brule County, South Dakota sdhaakon -- Haakon County, South Dakota tnoverto -- Overton County, Tennessee txfrio2 -- Frio County, Texas HOMEPAGES ANSPACH and KENDERDINE Families * * * * * CENSUS RECORDS by Brian Mavrogeorge The Constitution of the United States specifies that a census be taken every 10 years. At first, federal marshals were tasked with overseeing census activities (the Bureau of the Census was not formed and funded until 1902). You can find microfilm copies of the census schedules for 1790, 1800, 1810, 1820, 1830, 1840, 1850, 1860, 1870, 1880, fragments of the 1890, 1900, 1910, and 1920 at the National Archives in Washington, D.C., regional branches of the National Archives, the Family History Library (FHL) in Salt Lake City, and at other public, private, and institutional libraries throughout the country. Sometimes the parts of the federal census that deal with enumerating people (population, mortality, slave, and veteran schedules) don't have what you need. Consider checking the state census records. Some states took their own periodic censuses to qualify for statehood, additional representatives in Congress, special federal funding projects, and for other reasons. These state records complement the federal returns in that the enumerators asked different questions than those doing the federal enumeration, and the state censuses were conducted in years in between the federal census. As an example, the 1875 census in Kansas lists: the individual's location, name, description (including age, sex, color, occupation, place of birth), the last residence before moving to Kansas, whether an apprentice or learning profession in what field, and the previous military unit if a veteran. Other states with some form of surviving 20th-century enumerations, including special military, school or veteran lists, were Alabama, Alaska, Arizona, Arkansas, California, Connecticut, Florida, Indiana, Iowa, Maine, Minnesota, Nebraska, New Jersey, New Mexico, New York, North Dakota, Oklahoma, Oregon, Rhode Island, South Dakota, and Wisconsin. This additional "in between" information will help you track where an ancestor lived and what the previous residences might have been, and reveal the names of children who were born and died between the federal censuses. Some of the state census records have been abstracted and some indexed. Check the FHL Catalog at a local Family History Center for published abstracts and indexes. The FHL also has microfilm of some state censuses. For a good overview of census records with detailed examples of the questions asked in each federal census, I consult the "Family Tutor: Basic Genealogy Records." This multimedia tutorial is available as part of the continuing series of genealogy tutorials in Ultimate Family Tree . And, I'm anxiously awaiting the release of the 1910 New York City census on CD-ROM . Those pesky immigrant ancestors won't be hidden for long! * * * * * HUMOR: From: "Dale 'Doc' Schneider" CAREER ADVICE "I am at a career crossroads; should I become an astronaut, a fireman, or a system administrator?" This is the kind of question that these "handy comparison charts" were just made to answer: PURPOSE OF YOUR CAREER Astronaut: Advance scientific knowledge for the good of humanity. Fireman: Save lives and property. Sysadmin: Assure uninterrupted access to alt.binaries.erotica.sheep. ADVICE YOU'LL GIVE KIDS WHO WANT TO FOLLOW IN YOUR FOOTSTEPS Astronaut: "Study science and math and eat your vegetables." Fireman: "Study science and math and eat your vegetables." Sysadmin: "DON'T DO IT! RUN AWAY!" QUESTION YOU'LL BE MOST TIRED OF ANSWERING Astronaut: "Where do you go to the bathroom?" Fireman: "Do you really slide down a pole when the alarm sounds?" Sysadmin: "Can't you do anything about all this spam I get?" WILL YOU EVER BE ON TV? Astronaut: Yes! Fireman: Occasionally. Sysadmin: Only MSNBC's "The Site," which doesn't technically count as TV. WILL YOUR JOB EVER GET ANY EASIER? Astronaut: As computers get more and more advanced and able to control more of the functions of the space vehicle, yes. Fireman: As more and more people install smoke detectors in their homes, yes. Sysadmin: As more and more clueless newbies discover the Internet, absolutely not. INSPIRING MOVIE ABOUT YOUR PROFESSION Astronaut: "The Right Stuff" Fireman: "Backdraft" Sysadmin: Uh, gee, I'm really drawing a blank here. "Wargames"? YOUR WORK HOURS Astronaut: Fairly long days during the mission, but lots and lots of time between missions to relax. Fireman: 24-hour shifts, but 48 hours between shifts to relax. Sysadmin: Not really "work hours" or even "work days"... more like "work millennia." FRINGE BENEFITS OF YOUR JOB Astronaut: Good stories to impress members of the opposite sex. Fireman: Good stories to impress members of the opposite sex. Sysadmin: You get ALL of the jokes in "Dilbert." NUMBER OF COMPLAINTS ABOUT YOUR PROFESSION Astronaut: A few, from people who think the government should be spending its money in different ways. Fireman: A few, from people who think you take too long to arrive following a 911 call. Sysadmin: You'll have to learn what comes after "trillion" to be able to count them all. YOUR VEHICLE Astronaut: Multimillion-dollar space vehicle atop multimillion- dollar rocket. Fireman: Big red truck with flashing lights and siren. Sysadmin: 1945 Willys Jeep In conclusion, if the sysadmin option has seemed the most appealing in even one of these categories, you should become a sysadmin. * * * * * ROOTSWEB REVIEW is e-mailed on Wednesdays to all RootsWeb Members, subscribers to RootsWeb-hosted mailing lists, submitters to the RootsWeb Surname List (RSL), and other RootsWeb users. DOWNLOAD BACK ISSUES FROM . PERMISSION TO REPRINT articles from ROOTSWEB REVIEW is granted unless specifically stated otherwise, PROVIDED: (1) the reprint is used for non-commercial, educational purposes; (2) full credit is given to RootsWeb Genealogical Data Cooperative and the author involved, in a notice crediting RootsWeb Review (volume, number, publication date, and the address of RootsWeb's main Web page at ) and the author (name, e-mail address, and URL, if applicable). AUTHORS MUST ADVISE THE EDITORS AT THE TIME OF SUBMISSION OF AN ARTICLE for consideration for publication in ROOTSWEB REVIEW if their special permission to reprint is required. UNSUBSCRIBE INSTRUCTIONS: If you would prefer not to receive future issues of RootsWeb Review, please e-mail: RootsWeb-Review-L-request@rootsweb.com and put ONLY the word "unsubscribe" (omit the quotation marks) in the subject line and in the body of the message. THE EDITORS OF ROOTSWEB REVIEW, THE STAFF OF ROOTSWEB GENEALOGICAL DATA COOPERATIVE, AND THE WONDERFUL VOLUNTEERS AT THE ROOTSWEB HELPDESK ARE UNABLE TO RESPOND TO REQUESTS FOR GENEALOGICAL RESEARCH ASSISTANCE. THANK YOU FOR NOT ASKING! ____ Julia M. Case, Co-editor of "Missing Links" and "RootsWeb Review" To subscribe, put ONLY the word "subscribe" (omit quotation marks) in subject and body of message and e-mail to the address(es) above. RootsWeb Genealogical Data Cooperative P.O. Box 6798, Frazier Park, CA 93222-6798