Media & Source Naming Process
I am revisiting these two topics in order to pass along my many thanks to everyone who posted hints and advice regarding how to handle sources and media obtained from Ancestry.com through TreeShare.
I have concluded that I will no longer use TreeShare to post sources or media to my Roots Magic tree. (At least until TreeShare does a better job of handling the following issues).
There are several reasons for this:
- Sources and Fact Types posted by TreeShare usually will not match my templates in use in RM. Sources that are essentially the same will be duplicated if Tree Share posts them.
- TreeShare does not post master source citation details and leaves these tabs blank.
- TreeShare will post media to my Media Directory with an Ancestry file ID name consisting of number and letter strings, which is unidentifiable to the reader. This makes finding and identifying the file in my media directory, by person or event, very difficult.
My alternative is to use the following process (It works for both RM WebHints and TreeShare, as well as with other Genealogy software). I use TreeShare as an “extended” webhint tool. This process avoids the problems previously mentioned.
- Review the Webhint or TreeShare record on Ancestry and determine if it should be loaded to my tree in RM.
- If yes, add a new fact, and master source, to the tree member’s profile in RM. (This allows use of my “standard” fact types and master sources. If necessary, a new fact type, or master source, can be created in RM). If no, close the hint.
- Copy master source citation details, from Ancestry.com hint record, and paste into the master source detail tab for the tree member’s fact source.
- I copy and rename every image and PDF during the download process, and save the new file into my media directory appropriate subfolder. I name the media using my set of media naming templates. (This avoids both duplication and the use of the Ancestry.com media ID.) I then add the media to the appropriate fact or source in my TM tree member’s profile.
In addition, I use my own master source naming templates. This avoids having essentially duplicate sources in my RM source list. I also add a prefix to the master source name (examples – [CEN] =census, [BR] =birth record, etc.), followed by my standard master source naming templates. This forces the RM master source list to sort by the prefix and makes identifying duplicates for merging or editing much easier. (So far as I can tell, the master source prefix does not affect reports, GEDCOM’s, or TreeShare updates to Ancestry.com, and changes in master sources are passed through to all citations using that source.)
This process may seem slow and “clunky” (and it is) but I prefer to call it “one and done”. I do not have to go back and edit or correct records brought in by TreeShare. I am using this process going forward for all newly added records. Over time I plan to edit all of my existing records to bring them into compliance.
Thanks again to all for your help and ideas