User talk:Norajames

Topics


Welcome

Welcome to WeRelate, your virtual genealogical community. We're glad you have joined us. At WeRelate you can easily create ancestor web pages, connect with cousins and other genealogists, and find new information. To get started:

If you need any help, I will be glad to answer your questions. Just click on my signature link below and then click on the “Leave a message” link under my name in the upper left corner of my profile page. Thanks for participating and see you around! Debbie Freeman --DFree 00:55, 11 February 2011 (EST)


Next step: Review your GEDCOM [11 February 2011]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded McClure file February 2011_2011-02-11_01.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.

--WeRelate agent 00:10, 12 February 2011 (EST)

Next step: Review your GEDCOM [11 February 2011]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded McClure file February 2011_2011-02-11_01_01.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.

--WeRelate agent 00:37, 12 February 2011 (EST)

McClure file February 2011_2011-02-11_01_01.ged Imported Successfully [12 February 2011]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.

--WeRelate agent 11:23, 12 February 2011 (EST)

Next step: Review your GEDCOM [12 February 2011]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded Sheehan file February 2011_2011-02-12.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.

--WeRelate agent 11:40, 12 February 2011 (EST)

Next step: Review your GEDCOM [12 February 2011]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded Sheehan file February 2011_2011-02-12_01.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.

--WeRelate agent 12:06, 12 February 2011 (EST)

Next step: Review your GEDCOM [12 February 2011]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded Sheehan file February 2011_2011-02-12_01.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.

--WeRelate agent 12:19, 12 February 2011 (EST)

Note re Family Matching [12 February 2011]

Hello and welcome to WeRelate. After I imported your gedcom file I noticed that you have added alt dates when matching existing pages using Ancestry Trees as a source. We do not consider this a reliable source. When editing existing pages which have acceptable sources we recommend that you do not make changes to the page without citing a reliable source. On early people we have had volunteers spend a lot of time repairing the damage done by merging unreliable information. It is distressing to them to see these things added back again and again.

When processing your gedcom, you definitely should match pages as you have done. But when you get to the second step with the check boxes for info to add, please stop and compare. You can leave unchecked any information that you have not personally researched or have a reliable secondary source. Thanks! --Judy (jlanoux) 15:56, 12 February 2011 (EST) (WeRelate Volunteer)


Hi, I'm new to this so I appreciate the specific comments. I was really pretty careful about those changes, for the most part making the changes if they were dates that I had found on a headstone, etc. But I definitely appreciate knowing what is considered acceptable, and, of course, courteous.

I'm not sure from your message if there's anything else I should do at this point about the changes that I made, in order to restore them, or if you are saying that you have already changed everything back and that there's nothing further that I should do about these.--Norajames 16:06, 12 February 2011 (EST)

No, thanks. You don't have to do anything else now. I only wanted to advise you for future gedcoms. Hope you enjoy WeRelate. --Judy (jlanoux) 16:16, 12 February 2011 (EST)

Oh, I think I understand what you are saying now. Are you saying that it seemed as though I was using Ancestry Trees as a source. No. That would not have been my intention; I don't consider that a reliable source either. That may have been in my software from an earlier stage of research, but I didn't notice those citations when I uploaded the GEDCOM. And I did notice as I was doing the merging and matching that some people had somehow found one of my trees on Ancestry.com as a public member although I'm confused about how that could have happened because I never intentionally uploaded my tree there, and I did click on that as a source because it seemed already to be there and I didn't want to be rude and not include someone else's earlier citation, even though I didn't like it that it was a citation of my work on Ancestry.com that I didn't know they had!

Ah, this is all a little confusing!--Norajames 16:19, 12 February 2011 (EST)


Okay, thanks. And yes, I am enjoying this! I think WeRelate is the most wonderful thing! You people are brilliant to have thought of this.--Norajames 16:20, 12 February 2011 (EST)


Judy,

You said that you'd imported my Sheehan GEDCOM, but I'm not finding a files for relatively recent ancestors -- people born in the 1800's. On the other hand, I think most of those ancestors from the same time period in my McClure GEDCOM are there. When I click on My Relate then Trees and look at my Sheehan file it says Admin review. Does this mean that it's not online yet?

Thanks.--Norajames 16:37, 12 February 2011 (EST)

It looks like you uploaded a new file after the one I imported this morning. I'll go check it now. --Judy (jlanoux) 17:33, 12 February 2011 (EST)

Oh okay, I didn't realize you were referring to the first file. Thanks and I'll wait to hear more.--Norajames 17:36, 12 February 2011 (EST)


Sheehan file February 2011_2011-02-12_01.ged Imported Successfully [12 February 2011]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.

--WeRelate agent 17:36, 12 February 2011 (EST)

Thanks, Judy!--Norajames 17:39, 12 February 2011 (EST)


Stanley [16 February 2011]

Hi Here is some information I gave found on Thomas Stanley.

Sir Thomas Stanley 4th Baronet of Bickerstaffe 86 was born on 27 Sep 1670 in Preston, England and died on 7 May 1714 in Hanover, Virginia, (United States) at age 43.

Research Notes: From Dr. Stanley Klein: "The 11th Earl of Derby, Edward Stanley (1689-1776) was Thomas's brother, whose descendent, Lord Edward Stanley served as the UK Prime Minister 3 times. It is Edward's line from which Frederick Arthur Stanley descended (1841-1908), and for whom the Stanley Cup was named."

Sir Thomas Stanley, 4th Bt.1 M, #13811, b. 27 September 1670, d. 7 May 1714 Sir Thomas Stanley, 4th Bt.|b. 27 Sep 1670\nd. 7 May 1714|p1382.htm#i13811|Sir Edward Stanley, 3rd Bt.|d. 16 Oct 1671|p1381.htm#i13809|Elizabeth Bosvile||p1381.htm#i13810|Sir Thomas Stanley, 2nd Bt.|b. 22 Oct 1616\nd. May 1653|p1381.htm#i13807|Mary Egerton||p1381.htm#i13808|Thomas Bosvile||p24769.htm#i247682||||

Last Edited=18 Oct 2007

    Sir Thomas Stanley, 4th Bt. was born on 27 September 1670.1 He was the son of Sir Edward Stanley, 3rd Bt. and Elizabeth Bosvile.1 He married, firstly, Elizabeth Patten, daughter of Thomas Patten, on 16 August 1688.1 He married, secondly, Margaret Holcroft, daughter of Thomas Holcroft, after 1694.1 He died on 7 May 1714 at age 43.1
    Sir Thomas Stanley, 4th Bt. succeeded to the title of 4th Baronet Stanley, of Bickerstaffe, co. Lancs [E., 1627] on 16 October 1671.1

Children of Sir Thomas Stanley, 4th Bt. and Elizabeth Patten

   * Reverend John Stanley1 d. 1781
   * Edward Stanley, 11th Earl of Derby+1 b. 17 Sep 1689, d. 22 Feb 1776

Citations

  1. [S37] Charles Mosley, editor, Burke's Peerage, Baronetage & Knightage, 107th edition, 3 volumes (Wilmington, Delaware, U.S.A.: Burke's Peerage (Genealogical Books) Ltd, 2003), volume 1, page 1102. Hereinafter cited as Burke's Peerage and Baronetage, 107th edition.

Elizabeth Patten1 F, #13812, d. 1694 Elizabeth Patten|d. 1694|p1382.htm#i13812|Thomas Patten||p24769.htm#i247683||||||||||||||||

Last Edited=29 May 2008

    Elizabeth Patten was the daughter of Thomas Patten.1 She married Sir Thomas Stanley, 4th Bt., son of Sir Edward Stanley, 3rd Bt. and Elizabeth Bosvile, on 16 August 1688.1 She died in 1694.1
    Her married name became Stanley.

Children of Elizabeth Patten and Sir Thomas Stanley, 4th Bt.

   * Reverend John Stanley1 d. 1781
   * Edward Stanley, 11th Earl of Derby+1 b. 17 Sep 1689, d. 22 Feb 1776

Citations

  1. [S37] Charles Mosley, editor, Burke's Peerage, Baronetage & Knightage, 107th edition, 3 volumes (Wilmington, Delaware, U.S.A.: Burke's Peerage (Genealogical Books) Ltd, 2003), volume 1, page 1102. Hereinafter cited as Burke's Peerage and Baronetage, 107th edition.

If you can get ahold of the Descendants of Adam deAldithley book or tree it has a lot of information and sources in it. If you need to contact me for more information you can at lairdofcadboll@yahoo.com or an alt w.moistner@btinternet.com Hope this is of some help.--Lairdofcadbolol 08:35, 16 February 2011 (EST)


Person/Family page titles [3 March 2011]

Hello Norajames, I am a volunteer administrator here at WeRelate. I noticed that you are renaming pages to include people's middle names. WeRelate's page titling convention suggests users title pages with first name and last name only. For more information see this help page. Thanks, --Jennifer (JBS66) 14:19, 2 March 2011 (EST)


I would like to know on what basis this user has added a completely new name for Elizabeth Romney, wife of Joseph Ball, as "Julia." It was a very rare case in this time frame to have a middle name, and if one had one, it was almost always a full name of a grandparent. This user has offered no documentation for any of the sundry changes she has made to this tree. --Craig Kilby, Mary Ball Washington Museum & Library volunteer, professional genealogist.

(As a matter of record, we are not completely certain that the first wife of Joseph Ball was Elizabeth Romney. However, it is beyond doubt her name was Elizabeth. This is the first time I've ever seen her styled "Julia Elizabeth." There is no record that I know of that calls her that. The name "Julia"is NEVER used in this family in Virginia.--Persisto 19:19, 2 March 2011 (EST)


Person:Elizabeth Seaman (14) [2 March 2011]

You added an Elizabeth Seaman to Family:John Seaman and Martha Moore (1). This is a problem.

The biggest problem is that you put no sources. The second problem is that John already had a daughter named Elizabeth in his first marriage. His second wife's name was Martha, so why would he have a second daughter named Elizabeth? The third problem is that you have Elizabeth born in Roxbury, Massachusetts when all the other children in the family are born on Long Island. The fourth problem is that I am having troubles find a source that gives the maiden name of Caleb Carman's wife Elizabeth. For example, Source:Thomas C. Carman and Phebe Carman does not give her maiden name.

It looks like a mistake. Please either correct it or add some quality sources to justify it. --Jrich 21:10, 2 March 2011 (EST)

Some hints that might head you in the right direction: Family:Unknown Carman and Hannah Seaman (1) and John Carman of Hempstead by Henry Alanson Tredwell. --Jrich 22:10, 2 March 2011 (EST)

Adding Families without any birth or death dates or documentation [3 March 2011]

Hi Nora, I noticed that you added Matilda West as a daughter of John West and Matilda Scarborough, without any dates, sources and/or documentation. Also you've added several successive generations of the Hack family, also without any dates, soures and/or documentation. Since WeRelate relies upon dates, places and other information as part of the matching process, we'd appreciate it if you could please add whatever dates, information and sources to these persons. Names added without any dates, documentation or sources have very little genealogical value to others that are researching these families, since there is no information to determine 1) when/where they were born, 2) where they lived, 3) when/where they died, or 4) other records or other types of documentation to assist others.

Documenting the sources of the information in your family tree is important for the following reasons (among others):

  • For your own work: You can go back to the source when you find data that conflicts with what you already have.
  • When publishing or sharing your work: You can demonstrate the level or quality of research you've conducted. You can also help other researchers find the source of the information for their own work.
  • When collaborating with others: Source documentation can be compared when conflicting data surfaces.

This last is particularly relevant when using WeRelate, which is a collaborative environment that creates a single page for each person and family. When we merge our collective work in this way, discrepancies are bound to arise. Source documentation helps resolve those discrepancies.

Thanks for your compliance and understanding of these policies.

Best regards,

Jim - Co-Administrator on WeRelate--Delijim 12:14, 3 March 2011 (EST)



Hi Jim,

It appears that my connecting my Matilda West as a child of John West and Matilda Scarborough is a mistake, since I see that their daughter, Matilda, married a Wise. I'm going to remove this link and I'm also going to remove the Hacks where they link to my later Hecks because I now see where there was an additional error. Also thank you for the gentle reminder about dates and sources. I got tired yesterday during a very long day of data entry and toward the end of the day created a number of files with names only because it was, frankly, easier, planning to go back and enter whatever else I have today and tomorrow.

Thanks again, Nora



JRich:

Many thanks for the suggestion of the book. It was generous and is appreciated!

Nora


Person:Abigail Carman (7)

I looking at this page and am trying to figure out what it is saying.

Right now it looks like it is saying that Abigail m. (1) Jonathan Pyne who died in 1694 and she married in 1685 to Timothy Halstead who died in 1735. This is self-contradictory.

The source cited only describes Jonathan Pyne and says nothing about Timothy Halstead. He does, however, give a death date for Abigail of 19 May 1732.

Source:Halstead, William Leon. Story of the Halsteads of the United States, p. 62, gives the tombstone from St. John's Episcopal Church in Elizabeth, NJ: Here lyeth ye body of Abigail, wife of Timothy Halstead Who Died May ye 19th A. D. 1732 and in Her 68th yr of Age. He says that Timothy and Abigail had 11 children starting in 1686 and continuing through 1709. If this is true, she could not be the same person who was wife of Jonathan Pyne.

Secondarily, it make you wonder where Mr. Putman (your PDF author) got his death date.

Another point. John Carman Jr.'s will of 14 Sep 1684 indicates his daughter Abigail is under age (18 for women), so she was born 1666 at the earliest. Both the Abigail's shown marrying Timothy Halstead are older than this. --Jrich 17:05, 5 March 2011 (EST)


Will of Richard Haines [8 March 2011]

Thank you for sharing the will for Person:Richard Haines (1). Can you please provide a citation for where it was found? Thanks. --Judy (jlanoux) 11:06, 8 March 2011 (EST)


Penelope [31 October 2012]

Please don't undo the merges; just delete the incorrect Information. The merges were done because there was evidence of multiple parents that needed fixing. Actually as long as whatever you do results in no more than one set of parents for each child, I don't mind what you do. Jillaine 09:40, 30 October 2012 (EDT)

I would also suggest that this merge not be undone. I've taken a look at both pages prior to the merge, and it is my belief these are intended to be the same family. In bringing the two duplicate families together, it highlights the need for additional cleanup and sources, preferably by users who are familiar with the research of this family. The wildly incorrect data needs to be removed (as do the "GEDCOM file imported on" citations) and the more accurate data needs to be sourced. Norajames, I can begin by renaming the page back to Penelope Prince, and I will delete the inaccurate parents of Baron Van Princess and Penelope Kent. I will also merge the 3 duplicate Sarahs. Your assistance in helping to improve the quality of these pages would be greatly appreciated. --Jennifer (JBS66) 13:50, 30 October 2012 (EDT)

Thank you so much. I'll work on cleaning this up and will get to this as I can over the next several days.--Norajames 17:23, 30 October 2012 (EDT)

thank you everyone! Jillaine 01:05, 31 October 2012 (EDT)

GEDCOM Export Ready [15 March 2013]

The GEDCOM for tree McClure family tree is ready to download. Click here.


GEDCOM Export Ready [15 March 2013]

The GEDCOM for tree McClure family tree is ready to download. Click here.