Tips and Tricks / Hopefully this can help you as a quick reference
One Name Study Links
Conform & Improve Bios
Make a "simple Bio Template" that can be cut/pasted to profiles and fill in/reorganize the information (this will give a feeling of uniformity to your profiles) (add Wiki Links if you can); i.e.,
- Add Sources - Timeline Narrative is Helpful
(i.e., not having 10 year-old fathers or 7 year-old brides: Colonial Virginia men married between 16/18 and 30 years old and women between 15 and 25; and many had lost their 1st spouse by 30 and then remarried, often to a widow/widower).
Name and/or aka's son/dau of/ or presumed parents
B-M-D Estimate or Actual w/inline source (use ref name= if source is multiple use; this will consolidate the source line)
All known spouses and their parents (if known)
Wills are really helpful and often contain names of children or other relations
All Identified children and who they married if possible -- this will help others to attach profiles/make connections
- Sometimes this can be done by grouping; i.e., sourced children - unsourced children
Duplicates and Merging
MERGING Logic == Hope this helps to further clarify your merging confidence and how the process works.
- Summary of "my process" == one on one help using the following Duncan Profile -- John of Aberdeen Family. (Duncan-6033 is the most ACCURATE bio Info)
(Duncan-166 is the LOWEST LNAB found with the minimal info (Duncan-166 to be retained on/at final merge/final bio). 1. Save the entire Merged Info on first step. 2. Access Edit mode again; add comment merge cleanup Reorganize Info; delete dup sources/comments/etc; format, add sources, etc.
If you get stuck or have any questions, let me know - I am happy to help out.
- Some of this can be a bit tricky and complex. but the main objective always remains the same - One Profile per person w/ merges to delete erroneous dups/info; Always merge to Lowest Correct LNAB
Final = 1 Profile w/Most Current/Correct info (conformed to correct parent/child/Bio/Source, etc.) and hopefully/ultimately achieves the (1500-1700- 5-Star Bio protocols as established. (please Include a profile link on (Pvt/email) questions to assist others to see what you are looking at/doing vs what I am trying to explain/accomplish) = send via email or private message if possible - profile posts are good; can be a copy/paste (but there are character limits) These can get missed as they are part of the "feeds" - if you don't have a correct feed tag, you don't see it unless you circle back to a specific profile).
You can use the same "logic for all profiles / all timeframes (on merges I propose. -- It is harder/longer to explain than the actual process itself) (ALWAYS Merge Highest Number to the Lowest Correct LNAB (Last name at Birth) Number -- as often as possible; (thus other dups are merged direct into the lowest possible number vs (over and over) tier/step level merges)
Do research BEFORE proposing a merge - this ensures more accurate merge info and in the end is less time consuming'. than trying to figure out which is right - which is wrong. (Findings are incorporated to most accurate bio whenever possible but profile research info should contain some type of match before proceeding with merge (unless, of course, you already know the answers and the merge corrects the problem). Also, always good to check info on Ancestor/Descendant profiles - you may find something you did not know. (or included)
- Merges benefit everyone - more accurate attachments; less conflicts, etc. (single profile contains consolidated info and sources); (no info duplicates are weeded out of the system, etc.)
In a merge "Nothing is Lost". The Bio Information is combined - Children "follow the parents" - Managers follow the individual and are combined on final profile (one at the top, the other at the bottom; Thus, the statement "profile clean up" comes into play). What that entails is "delete duplicate or erroneous information; combine sources and acknowledgements into one section and add other section notes as needed (i.e. discrepancies, wills, timelines etc.) - All of these items are "traced via the contributions pages. and can be recovered if serious mistake made.
- Primary Goal *** 1 Profile Per Person = ONLY One Profile Representing the Same Person. Info As accurate as possible with Sources clearly shown (Final Profile LNAB; with dup source info combined) (Re: Tree info (i.e., ancestry files, etc s/b used as reference point only. these are often incorrect - unreliable without sources).
Lots of wrong info on web - (Info (links) should be from 'FREE' sites if possible (FHC) - Not Paid sites. -- if info from paid sites, the actual source/origin info needs to be typed out on the profile bio so it can be readily seen by anyone without having to "pay for it" -- WikiTree is Free - the information is free to everyone with an interest).
The older the history - the harder to find any sort of proof they existed. It is a lot easier to maintain, (link to and/or add to) just ONE existing profile - rather than trying to research 20 different profiles to determine the dups, merging the info, correcting the old, finding the mistakes, etc. on a dozen different files. Each profile is treated as an "Individual" and should be about that "individual". (utilize Pre-Merge notes - traceable under the changes)... (beware of the "fiction" accounts on royalty -- even Peerage and Burkes can be wrong -- More commoners than royalty; although if you can go back far enough there is probably a common connection -- 1000-1200 but likely no records)
The question to ask on merges is DO THEY "REPRESENT" THE SAME PEOPLE - WHY - IF YES, = MERGE (think as if it is the individual; even if dates locations are not exact/same - final cleanup of merges should resolve any remaining discrepancy) -- IF NO, WHY NOT - BIO SCHOULD CONTAIN SPECIFIC DISCREPANCY NOTE SOURCE SPECIFICS (the person who rejects should be able to provide the why's; SOURCES AND RESEARCH and exactly Why they are different people from a proven source) - Sometimes it is a true REJECT. (i.e., proven contemporary; or alternate merge or action is needed - bios should be updated to contain this info to prevent further merge requests)
- (Update Profile Bio to "Prove why they are 2 different people" (same place/same time w/soft links). This can prevent others from trying to merge the same profiles over and over - and/or making a wrong attachment. (example GA vs VA)
(do not waste time marking as an unmerged matches - they either are or are not -- because in theory the (pre-merge) research is already done before the proposed merge and discrepancies resolved/noted. (enter discrepancy info as applicable on the bios and/or contemporary links as applicable) There is always a but ----- and mistakes happen - this is one reason why 2 people are approving the merge - they sometimes have "different" info.
The most common reason for duplicates are "Parallel files"; i.e., (usually an Ancestor) where one or more GEDCOMS (Profile Created) are imported for the same person vs "attaching" to an existing family. Sometimes these files have a difference in the upper information which the MatchBot does not catch as a duplicate ; or sometimes the information is just incorrect and needs to get properly attached/incorporated to someone else. (at least from a manual aspect that is what seems to be one of the main problem - other issues are - unsourced tree to tree copies - inadequate sourcing) That is one main reason why the "sources or evidence information is so important". Always use a "reliable source" with viewable links if possible.
Ancestry.Com as a Source
Just to clarify on my "negative" remarks about Ancestry -- I don't mean the Actual designated "Source" stuff like: Source: S224 Title: Marriages of Some Virginia Residents 1607-1800 by Dorothy Ford Wulfeck, pub. 1986 Abbreviation: Marriages of Some Virginia Residents 1607-1800 by Dorothy Ford Wulfeck, pub. 1986 Italicized: Y Source: S231 Title: Virginia County Records SPOTSYLVANIA COUNTY 1721-1800 - Deed Book Abbreviation: Virginia County Records SPOTSYLVANIA COUNTY 1721-1800 - Deed Book Italicized: Y
I do mean the designated stuff like (-- might just as well be under "acknowledgement" section if you want to keep on the Profile) Edmund West, comp.. Family Data Collection - Individual Records [database on-line]. Provo, UT, USA: Ancestry.com Operations Inc, 2000.
Source: S98 Abbreviation: Ancestry Family Trees Title: Ancestry Family Trees Publication: Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members. Note: This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created. Repository: #R2 Paranthetical: Y Page: Ancestry Family Trees Quality or Certainty of Data: 3 Data: Text: http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=12744898&pid=419313255 Repository: R2 Name: Ancestry.com Address: Ancestry.com CONT http://www.Ancestry.comName:Ancestry.comAddress1:http://www.Ancestry.com
Too often this is the only "Source" given for information. These links mean nothing and you can't use them to find anything under Ancestry -- Not even the Ancestry Tree Files (at best you need to wade through 100's and even then, if you don't have An Account you can't see anything anyway. (not even the 'source info") Too often the only thing you can determine from this is that at best it was a Tree-To-Tree Copy which may or may not be anywhere correct. At least when you have a source, you can check the index info if it was included as part of the import , and in many cases this was a free source originating from Family Search anyway. So I do agree Ancestry has a lot in the way of actual sources but many are "free" anyway.-- more to the point - Are They Reliable
if the record on Ancestry has an image you can provide a FREE link to the image in your citation Steps to create a free ancestry image link:
- 1. Open image.
- 2. Click the tools icon on the right side of the image.
- 3. Click the Share drop-down and choose Facebook.
- 4. Close the window that pops up to share the image on Facebook.
- 5. Copy the link in the next popup window.
- 6. Use the link as is or truncate by removing everything after the second number. Example: (Remove the bolded portion) https://www.ancestry.com/sharing/14887273?h=f44681&utm_campaign=bandido-webparts&utm_source=post-share-modal&utm_medium=copy-url
7. Create a free image link with the remaining URL. Example:
- These links/images are not as maneuverable or zoomable as ordinary images on Ancestry and aren't ideal for mobile devices but usually are easily viewable on a computer
8. Test Link before exiting to make sure page is still viewable
Add Links for Clean Up Purposes
'Common Links used on VA people (under the Source Section Some "viewable links" under the Category Section (so do not have to keep looking them up) https://www.wikitree.com/wiki/Category:Collins_Family_Clean_Up_Effort_2021%2C_Collins_Name_Study - for things like: Library of Virginia - Patents & Land Grants https://lva-virginia.libguides.com/land-grants Virginia Memory Collections A-Z https://www.virginiamemory.com/collections/collections_a_to_z Revolutionary War Bounty Land Claims Virginia Land Office Patents and Grants
FHC Catalog Links Isle of Wright Chapman - Wills and administrations of Isle of Wight County, Virginia, 1647-1800 Authors: Chapman, Blanche Adams, 1895-1958 (Main Author) reprinted in an improved format Boddie - Seventeenth Century Isle of Wight County, Virginia: A History of the County of Isle of Wright, Virginia, During the Seventeenth Century, Including Abstracts of the County Records John Bennett Boddie; Genealogical Publishing Com, 1973 - Travel - 756 pages
Things that are common on the VA people (under the Source Section (with ref name tags) are: "Links are provided for reference and convenience only (and are considered unreliable/unproven unless sources are contained within). (Generic Disclaimer + ref name tags) <ref name=RAP>Prewitt, Richard A. "The Collins Book (Most complete/sourced and consolidated info located for early Collins Families)</ref> <ref name=TCB> (vs Isle of Wright) [http://www.lauderdalecountymsarchives.org/uploads/2/6/2/1/2621480/the_collins_book_-_joseph__collins__lucy_marchbanks_-_their_descendants.pdf Prewitt, Richard A. "The Collins Book - Thomas (b1707) pg 4 #A62 son of #A6]</ref> <ref name=TBD>:  Needs Verif</ref> <ref name=REV> by Will Graves</ref> <ref name=CHA>Chapman Index V2; Collier, John, 465. Collier, William, 76. Collins, Cornelius, 367. Collins, George, 143. Collins, James, 480. Collins (Colans), John, 266, 287, 302, 320, 351, 361, 397, 421, 422, 425, 431. Collins, Luke, 287, 327, 362, 426. Collins, Minton, 287. Collins, Richard, 417, 424. Collins, Sasana (Susana), 308, 350. </ref> <ref name=SCR>Crozier </ref>
Final Review Clean Up Process
Consider following items during Final Review Clean Up Process
Conform Top to Bottom Discrepancy explanations, etc.; in line sources, etc. deletion of or archive of completed profile notes; category assignments, etc. https://www.wikitree.com/wiki/Category:Collins_Family_Clean_Up_Effort_2021%2C_Collins_Name_Study
Narrative Summary i.e., under the ==Bio section== John Doe - son of AKA Names / Styled As : Birth Estimate : Marriage Estimate *Spouse(s) with Parent if known : Death Estimate Separate section for identified children with link & spouse info
Template Review Profile managers: s/b limit of 6 (last activity date) Graphics - Dups Suggestions (cleared if possible to level 1 - 2 - discrepancies fixed) Generation 0: Generation 1: Categories: Sources; timeline and pictures Profile posts -