I thought that profiles were numbered from old to new.

Question

I have an example of newer profile by date, having a lower number than an older profile.

Comments

If Corkins-88 and Corkins-103 represent the same person, they will need to be merged.

---

I now see you have suggested the merge, so it'll be up to the other Profile Manager to respond - and to merge the higher number to the lower.

---

There are the same person, but Corkins-108 was created in 2016, and corkins-88 in 2017.  Merge is always into the lower number

---

I can't explain why the lower number was created after the higher number (a glitch of some kind with the numbering? Because I didn't think numbers were recycled, due to redirects), but 103 needs to merge into 88.

---

Most likely explanation is that Corkins-88 is the result of a previous merge and ended up with a creation date of when the merge took place, although I didn't realize that's the way it's done.

---

@ Gaile - we can't see that, though - privacy lock.

---

As Gaile notes, the creation date for Corkins-103 comes from a merged profile, McNeil - Corkins-1, which was created on 16 Apr 2016.

Corkins-103 was created on 19 Jul 2019, probably to correct the birth surname/LNAB for McNeil - Corkins-1.

---

Change logs:

Corkins-103

McNeil_-_Corkins-1

---

Melanie, it's good for me that privacy prevents us from seeing it - that way I can't be embarrassed by being found to have made a bad guess <grin>

---

Ahh, but, Gaile - you weren't wrong!

Answer 1

They are numbered as they are created. I wouldn't worry about the order in terms of chronology.

Comments

That is wha I thought, but in this case that is not true...
Corkins-103 wa created in 2016, and Corkins-88 in 2017

Answer 2

Maybe in the past two profiles were merged and the number was free again then.

And now as you created the profile it was the lowest free number.

Comments

Dieter, although it doesn't seem especially logical, WikiTree never re-uses a number.  This is driven by the WikiTree ID being the unique record index.  After a merge takes place, the ID number that disappears is still used in the database as a re-direct to the new ID number to ensure not breaking any links that may already exist to the old ID from other profiles.  Every time we create a profile, the highest current sequential number for the same LNAB is incremented by one.

---

OK, I got that.