 |
Rootsweb lists |
|
| |
|
|
| |
|
|
| |
Rootsweb
hosts a huge number of lists and boards which have a wide
readership. Some may be specific enough to warrant posting
an announcement in order to recruit participants for your
own DNA/Surname project.
The following pointers on how to announce your project to
Rootsweb are from Lauren Boyd, volunteer list administrator
of several Surname/DNA lists at Rootsweb, who posted the following
notes with the title "How to Win Friends and Influence
List Admins". We've adapted them a little bit and are
used with permission.
They are not from Rootsweb staff themselves, however, they
are very sound comments, do's and don'ts which should apply
to the majority of the 26,000 lists that Rootsweb hosts.
|
|
| |
|
|
| |
|
|
|
Be sure that your message has content beyond just announcing
the DNA |
|
| |
Project -- it should be drafted specifically for the list
you are posting to and contain something that pertains to *that*
list. |
|
| |
|
|
| |
|
|
|
Engender a good relationship with the List Administrator whenever
|
|
| |
possible. It is much easier to work with someone you "know."
And remember -- they make the list rules!
After reading the guidelines in the Welcome message, it may
stand you well you to ask the List Admin if it is "ok"
to post your DNA message. |
|
| |
|
|
| |
|
|
|
The magic formula to reach any list admin is: |
|
| |
listname-admin@rootsweb.com
where the actual list name is substituted for "listname".
For example:
genealogy-dna-admin@rootsweb.com or Jones-admin@rootsweb.com |
|
| |
|
|
| |
|
|
|
Take your time to ensure you are creating a quality message
--- you want |
|
| |
to put best foot forward for your project. |
|
| |
|
|
| |
|
|
|
READ the Welcome Message and understand the guidelines for
*each* list |
|
| |
-- they generally are different. |
|
| |
|
|
| |
|
|
|
Don't join a list and immediately send a post re the DNA Project
that is |
|
| |
your interest. For many list admins, joining and posting *immediately*
sends up red flags and your message may be considered as spam! |
|
| |
|
|
| |
|
|
|
Don't cc (or bcc) a bunch of lists with your message. |
|
| |
|
|
| |
|
|
|
Don't join, post and unsubscribe. This really sends red flags!
|
|
| |
Don't "hit and run"! |
|
| |
|
|
| |
|
|
|
Be especially careful when posting to LOCALITY lists for SURNAME
projects.
|
|
| |
Make mention of the particular family or branches in the area
that you would like to be in contact with "or any others
of that surname". If the locality has a high concentration
of those of your surname in the area, make mention of it --
don't leave that important detail out! |
|
| |
|
|
| |
|
|
|
Don't send messages to every LOCALITY that you can think of.
Blanket |
|
| |
posts are looked at as spam. They could also get you globally
rejected from Rootsweb's resources.
If you know your surname folks were in a LOCALITY in general
-- like California or France, but not a specific area, like
San Francisco or Paris or the county they are in, then look
for a generic list for the entire state or country to post to.
Do not send blanket posts to each county or shire or city listed
for the LOCALITY. |
|
| |
|
|
| |
|
|
|
In all instances, if you can work your announcement into a
query message |
|
| |
rather than a strict and straightforward announcement, it
will be better received. |
|
| |
|
|
| |
|
|
|
It would (probably) also help to mention in your announcement
that the |
|
| |
Project is an all-volunteer effort and not a commercial venture.
Many List Admins are confused about this and perceive the projects
to be commercial ventures instituted by the various labs, rather
than supported and "catered" to by the DNA services
and labs. |
|
| |
|
|
| |
|
|
|
One of the main guidelines for Rootswebs' admins is no marketing
|
|
| |
messages or costs. This also includes soliciting contributions
or donations to the project (remember, not everyone in a family
will need to provide a sample, although many will want to know
the results and help with the funding).
You can of course provide the cost of testing and other information
by private email or provide the link to your Project web site
that explains this in detail. |
|
| |
|
|
| |
|
|
|
Do *not* put the "lab" address, such as www.dnaheritage.com,
|
|
| |
www.ftdna.com, www.relativegenetics.com etc. under your signature,
which implies you are part of their staff! This leads others
to perceive your message as a commercial post. |
|
| |
|
|
| |
|
|
|
Do, when referring to the "lab" (service) include
the link to join the FAQ's |
|
| |
page. For DNA Heritage, the FAQ's page is at www.dnaheritage.com/faqs.asp
|
|
| |
|
|
| |
|
|
|
If there is a (surname)-DNA-L to compliment your project,
make mention |
|
| |
that those interested in a deeper discussion of genetic genealogy
for this surname are welcome and encouraged to join and continue
the conversation. |
|
| |
|
|
| |
|
|
|
Keep a cool head when responding to the List Admin when admonished
re |
|
| |
"commercial posts". Don't take them personally.
Most admins are nice folks like yourself, but may not be as
interested or informed as you are about DNA and genealogy. Some
"don't believe in it".
And for those, you may never "win the argument" --
so don't linger in one. Remember you catch more flies with honey... |
|
| |
|
|
| |
|
|
|
For working in UPDATES re your project and trying to drum
up more |
|
| |
participants – which all projects need to do, be just
as careful in your message composition and where you target
to send them. |
|
| |
|
|
| |
|
|
|
Don't post weekly updates re your project. It is too frequent
for Surname |
|
| |
or Locality lists. If there are no juicy details to share,
try to keep your posts to monthly or quarterly so the List Admin
does not have to deal with complaints from listers who don't
share your DNA interest.
Maybe even ask the Admin to help you figure out how frequently
the list could stand reminders about the project. They may be
willing to add a tagline directing folks to your project or
to contact you for information re the DNA project. This would
work for Surname lists, but not really for Locality lists. |
|
| |
|
|
| |
|
|
|
Post when there is something juicy to report and make it enticing!
|
|
| |
Focus on the genealogy aspect -- and gently insert that it
is thanks to the DNA Project that this connection was made.
Share the excitement! |
|
| |
|
|
| |
|
|
|
Don't breach confidentiality -- this scares some folks. If
the DNA |
|
| |
participants openly state they are part of the project then
go ahead and say Tom and Dick and Harry matched and this provides
a link between different lines which had a brick wall. The section
of DNA being tested cannot identify anyone’s as an individual
(it's very different to a full forensic profile), but it is
important to manage project information properly.
If the participants prefer to remain nameless, you can share
in a more general sense and still credit the project for making
a cousin connection. |
|
| |
|
|
| |
|
|
|
Post messages that have nothing to do with DNA -- participate
in the list. |
|
| |
Let listers get familiar with you. |
|
| |
|
|
| |
|
|
|
Once a related DNA list has been established for the surname,
encourage |
|
| |
listers and project participants to join you there for an
active discussion. Work *with* the surname list admin on this
issue. Many admins would possibly add a tagline encouraging
those interested in discussion of genetic genealogy for that
surname to join the DNA related list.
Some might even be open to a quarterly FAQ to be posted re the
project. |
|
| |
|
|
| |
|
|
|
Do not send full reports on the project to the surname list
-- send a teaser |
|
| |
and an invitation to join the discussion and read more on
the related DNA list. This will help grow the project's discussion
list and keep the main surname list subscribers from complaining
or tuning out your messages --- deleting on sight, or unsubscribing
from the Surname list. It will also encourage those interested
to not hold back their comments and contributions, but to take
them to the related DNA list where they know the majority *is*
interested in the topic. |
|
| |
|
|
| |
|
|
|
Contribute actively to the Surname-DNA lists and help build
traffic and |
|
| |
interest -- it will serve your project in the long run. |
|
| |
|
|
| |
|
|
| |
Signature lines: some comments |
|
|
Keep your signature line to 4 lines or less, per Netiquette.
|
|
|
Don't include your signature line if it is longer than your
message! |
|
|
Perhaps turn off your signature file when it does not apply
to the venue or |
|
| |
message you are sending. Listers may be aware you are the
DNA project manager for a given surname. It may be more appropriate
to use the signature reflecting this on a more selective basis.
Those receiving Digest mode messages get bombarded with repetitive
and long signature lines. |
|
| |
|
|
| |
|
|
|
Inform your project participants that may share your enthusiasm
of |
|
| |
spreading the word about the project that there is a right
way and a wrong way to do so --- share pointers with them that
will put best foot forward for the project rather than engender
complaints.
You don't want all your efforts to build good relations hindered
by someone's blunder --- even though well intended. |
|
| |
|
|
| |
|
|
|
When asking others to "spread the word" remind them
of guidelines that |
|
| |
will engender a good reception of the news. |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
