GENEALOGY-DNA-L Archives

Archiver > GENEALOGY-DNA > 2011-11 > 1321026847


From: William Hurst <>
Subject: Re: [DNA] Problems with some surname project admins
Date: Fri, 11 Nov 2011 10:54:07 -0500
References: <DEDCC72F374144CBA14F391D0350122D@RayHardyPC>,<0f3e01cca018$7b5f3c80$721db580$@org>,<201111110245.pAB2juDU014396@mail.rootsweb.com>,<REME20111110231520@alum.mit.edu>,<1321007892.32868.YahooMailNeo@web28207.mail.ukl.yahoo.com>,<BEAB5992-8898-4455-922C-29BEE351677F@earthlink.net>,<83F4A691-B642-43F1-A8F9-638DFBFE6E07@verizon.net>
In-Reply-To: <83F4A691-B642-43F1-A8F9-638DFBFE6E07@verizon.net>


Hi Jim and all,

Please be careful and not get FTDNA or ISOGG to issue some generic list of requirements for project administrators. Those would probably apply mainly to surname projects without saying so. And don't try to tell me otherwise; I have to sift through info every day from FTDNA about 12-marker matches, etc., in my mtDNA haplogroup projects. Haplogroup and geographic projects are very different from surname projects. Some of those are good, some not. But don't expect me to collect names of Patriarchs! Or Matriarchs either, for that matter.

Bill Hurst

> I wonder if there shouldn't be a published list of expectations: ones that new customers would expect of their project and the Admins; and ones the Admins agree to in order to become an Admin - these expectations should be the same. We can't go overboard here, but there should be some basics.
>
> Customer should expect results to be grouped; Admin should group results.
>
> Customer should be able to contact others in the group; Admin should forward email to matches.
>
> Admin should have/show Patriarchs; customer should provide Ancestry to Admin (at least several generations)
>
> Customer may remain private; Admin must not link customers to results without permission.
>
> Jim - Sent from my iPhone - FaceTime!



This thread: