Creating a new profile to merge with old to correct LNAB unknown - correct way to go?

Question

I just sourced a profile and found the wife's last name at birth was unknown. I now know it. Should I create the profile and suggest a merge? The profile is not mine, but I have the sources and have included all data in the profile I edited. The profile manager had no information on the marriage at all. I have since added that. I have not yet touched the spouse's information, except the marriage data would have been added automatically based on relationship.

Comments

Hi Raewyn,

There is some good advice already offered below, I just have to add a clear and direct answer to your question...

No, please do not purposely create a new duplicate profile... I do not believe is the correct way to go :)

Have a super positive day!

- Keith

---

Thanks for your input. I don't like duplicating stuff!

Answer 1

I can't say its the correct way to go, but it is one possible way to go.

I believe the preferred way to go is to edit the LNAB on the original profile. But technically, under the hood, it is not much different than creating a new profile and merging.

Comments

For the database yes, it makes a difference.  

The only correct way is to keep working on the same profile and NOT add a duplicate.  

Even if a duplicate is merged it is alway in the database and creates more work for the server.

---

Guy, maybe you have more insight into the code than I do, but an edit of the LNAB produces an identical merge log and redirect as does a merge of two existing profiles. As far as I can tell, there is no difference at all.

---

I don't agree but I might be wrong.

I think we should ask the question to the tech guys.

Answer 2

That would work, but it's probably nicer to ask the profile manager to make the change.

Answer 3

Is there even a profile manager for the wife?

If she is an orphan you can adopt her temporarily and give her the LNAB you found.

On the question: as Dennis says, technically it's the same thing. Changing the LNAB on a profile is also a sort of merge.

I use the merge method for changing LNABs only in cases where there is a manager, that manager is long-gone and I don't have enough LNAB changes to do on their profiles to warrant going through the Unresponsive Manager procedures.

Comments

Thanks for asking the most obvious question. I hadn't even looked (not very good researching is it?). It's orphaned and blank except for the marriage data I edited on the linked husband' profile. I will 'foster it for a moment. Not a full adoption. Maybe I can improve on that profile too. Get's another unknown off the unknown list. But it's a Smith, so that might be akin to having another unknown as there are so many! I found one in my family and just about had heart failure - it can be a tricky name to research due to it being quite common.

---

Ah, you forgot to mention that it was orphaned :)

In that case the answer is easy... adopt it, make the changes, then abandon it later (if you wish).