Ask Aleš: What Would You Like To Know About WikiTree Plus? w/host Greg Clark (Sep 2026)
Watch on YouTubeVideo summary
In this episode of "Ask Aleš," host Greg Clark and Aleš delve into several critical technical aspects and upcoming enhancements for WikiTree Plus, beginning with the complexities of descendant calculations. Aleš explains that computing total descendants for every profile in real-time is currently too computationally intensive, so such reports are not prioritized for live use; instead, he suggests calculating these statistics offline for specific high-profile historical figures like Brian Boru or Genghis Khan on special occasions. The conversation also addresses data accuracy regarding pre-1500 figures, where massive generational gaps often stem from uncorrected errors in birth dates rather than actual lineage jumps, while the team investigates how profile merges differ from "AutoBio" runs, noting that users must still manually clean up duplicate biography sections to avoid clutter and false suggestions.
The discussion further explores significant synchronization issues with Find a Grave, which has stopped updating its site map since July, preventing WikiTree's automated system from detecting new memorial data for four months. As a temporary workaround until the external service resumes updates, Aleš recommends that users manually mark incorrect suggestions as "correct" to prioritize them for review, while he considers reactivating older, less efficient update methods. On the software front, new features are being rolled out to improve profile quality metrics, including a revised ranking system that factors in BioCheck errors and source status, alongside a fix for keyword searches regarding research statuses like "Research Gold." Additionally, the platform now more accurately tracks unsourced profiles by excluding private biographies from the count, which currently stands at approximately 10% of the total database.
A major highlight of the session is the upcoming launch of a surname collaboration score feature designed to streamline "One Name Studies" by consolidating multiple surname variations into single reports. This new tool will ignore spacing and special characters to group related names, such as Peasley and Paisley, and will display key metrics like average content rank, error-free percentages, and the number of unsourced or unconnected profiles. To support this, a new surname index handles redirects regardless of apostrophe placement, while a similar rank index allows users to filter profiles by quality, with Rank 10 representing the highest standard. The feature is expected to go live within a month, with links already being synchronized to relevant WikiTree pages, marking a significant step forward in managing complex genealogical data.
The episode concludes with logistical updates and announcements for future community events, including the next "Ask Aleš" session scheduled for Friday, October 9th, and an overview of the weekly data processing workflow that takes about 24 hours to complete suggestion calculations. Aleš also expresses gratitude to Azure for their technical support and introduces his brother, Jiannis, who is a co-author of their software and is set to eventually lead WikiTree Plus upon Aleš's retirement. The hosts wrap up by reminding viewers of upcoming challenges, such as the monthly WikiTree Challenge featuring Justin York and the Source Thunk challenge, alongside regular community gatherings like the Genealogy Collaboration Hour on Saturdays and weekly chats on Thursdays, encouraging active participation in these initiatives to further improve the database.
Read the full video transcript
Welcome to our September As session.
>> Yay, there's Allesh. And we're here on
Zoom. Um, which is exciting because we
can see more people's faces. Um, and we
can see them move about. We know they're
live people who are with us.
Um, yeah. Now, if you're shy and you
don't want to share your camera or your
microphone, that's totally fine, of
course. Um, we don't want to make anyone
uncomfortable. Um, and the recording
will have basically the screen sharing
mostly. Um, but if you're shy about
having your face on camera, then just
turn off your video. Uh, and you can
always turn on your audio and ask
questions that way or just type in the
chat, whatever you prefer. So if you are
here um and you do have a question
please do use the chat um to let us know
put a Q in front and then the question
um and then we will switch to you and
then you um and you could re repeat the
question or elaborate after I uh mention
it but um
uh yeah so it's uh the whole thing is to
be able to ask a le uh anything you want
to know about wiki tree plus and uh so
um Now uh is anyone no one's sharing
their screen at the moment? Right.
>> Right.
>> Nope.
>> No. Okay. Um well I I will start sharing
my screen
now. Can do you see the zoom panels on
my screen or not?
>> No just the
>> just the
>> GTG post.
>> Okay. Oopsie. That's not what I wanted
to do.
Let me zoom in a bit there. Is that
legible?
One more I think.
>> One more. Okay.
>> Yeah. Okay then. Um so there uh from Ask
Allesh.
Uh okay. So the first question Patty we
did answer already in
>> last
>> on during the month I believe right?
>> Yeah. The one here that you had said is
uh the when we talked about uh high king
Brian Buu from Ireland uh and how many
descendants he has uh he thought that
kind of information about the wiki
treers with the most descendants would
be an interesting thing to put in the
treetops page. That's obviously not
something that would be calculated on
the fly. It would be something that
you'd have to pull from the data, right?
Um, but is that so your question I think
is is that something that's relatively
easy to calculate and then add to
treetops.
Am I summarizing that right, Patty?
>> Yeah, I presume it would be done once a
week or once a month or something
because
>> we've already decided it's too computer
intensive to do it on the fly. Mhm.
>> Well, um I mean that's a generic
question because finding the person with
most uh descendencies,
you would actually need to calculate uh
descendants from all profiles to see
which one has the most. So
>> I don't think that's something uh worth
that is worth doing. I of course that
could be optimized a lot such an
algorithm but uh
still um it would be quite complex. So
>> you would only need to do it for every
profile without ancestors.
>> Uh no for every profile with ancestors.
Oh yeah without dependence. Okay, but we
have millions of we can I think we have
a uh
keyword for that. So,
uh
let's search for missing
parents.
No, but it is something like that.
>> It's close.
>> No parents. Is it just no parents?
>> Maybe. I don't know. I'm searching for
it now.
>> No father
>> relation. No, that's different.
Something else.
It is something parent because that's
what we have on the w on the wiki tree
challenge space page for
>> no parent, right?
>> No parents. Yeah.
>> Okay.
Well, you see it each month on the
kickoff. We talked about
>> very a little something has sunk in.
>> It only takes me how many years.
>> So, we have uh 13 million such profiles.
So, it's
>> okay. It's just one quarter of profiles,
but still a lot.
>> That's still a lot. Yeah.
Yeah. M
>> and you know well I don't know how how
you would program it allesh but what I
would do is I I would probably start I
would I was thinking the same as you
like every profile would have a field
that says number of descendants and then
you go and then when you're at the top
you just have to add some the number of
descendants for each of your offspring
your immediate offspring and then you'd
have the final total. So you know after
all those calculations then calculating
the number of descendants of Brian Boru
is just a matter of summing the number
of his you know all his children up. So
that's a simple you know
>> yes but we have
>> but that but that calculation like that
just that's
>> we have we have profiles with millions
of descendants and
>> those would need to be summarized and
it's uh
>> kind of hard to do on the fly. I mean it
could be algorithm for it could be
written and it could be optimized quite
a lot but the question is do we really
need that
>> because probably there is one person
which most likely we already identified
>> um that has the most ancestors. M
well what about like so there are so
Brian Boru is obviously identified as
one who has lots already right and you
know people talk about Charlemagne and
Genghaskhan and you know there's some
key people in history where you know the
mythology out there is that you know
lots of the world half the world is
descended from them. Um, what about, you
know, picking some of those sort of
high-profile
people and just and figuring out th
those stats? Is that something that
could be done offline, you know,
>> because it wouldn't change much after,
>> right?
>> Yeah. After you would get the number, it
would stay uh constant.
>> The numbers will change, but the
individuals will stay the same.
>> Yeah. Most likely. And
>> they'll all be very early individuals.
So you probably could say it, let's only
look at people before 1500 or before
that.
>> This is from uh Brian M Kenetic.
And uh we have here what
in 18 generations
not that 12,000? No, this is not this is
the example you showed.
>> Yeah.
And it has only 1,200 uh 12,000
descendants. That's not really a lot.
>> But don't you have to click that show
all?
>> Uh no after 10.
>> Uh yeah, but I think that's just for the
table. Well, I can try if it will see
more.
>> I know from when we discussed this
before, it's in the millions, I think,
if you let it run.
>> Mhm.
I think it took something like four
minutes to run, I think.
>> Mhm.
>> Right.
>> So,
yeah.
>> So, in 26 generations, we came to uh
15
140 on that one. And so, 400,000.
>> And what year range are we talking
there? We're still only in 1500.
>> Still at uh Yeah. 1500
30 something generations to get to the
present.
>> Yes. But the real amount of profiles is
in 178 1900
thousand 19.
>> So that's where it'll really explode.
Right.
>> Yeah.
>> That's also the reason I stop because
otherwise
it just hangs there.
>> Right.
I can try it again because now some data
is cached and it might might do more but
uh not much
>> no the same
>> interestant
>> I can run offline the full descendant
list but uh
>> it will still uh
be um too slow.
>> Mhm.
>> And there are no
uh
son. But we have ancestors here. We I
mean even starting with his ancestors.
>> Yeah. He has another 30 generations of
ancestors.
>> So Oh, a lot of them.
back to the year zero is all there
almost
>> and even more
>> over here. Wow. So if we start with this
one uh
copy v3 ID and
so we are at 11,000 in 40 generations
and we are in 11 to500.
So,
>> wow.
>> Here
>> that's wild. Look at that. 400 years
different span between like the fourth
generation from the
>> but that's due to errors I'm certain.
>> Oh, it's Oh, it's not the difference
between a pure male line and a the
>> um could be a diff I mean there is a
distance some distance between
generations but not that much. M
>> um
uh because uh I mean it could be correct
but from what I was uh looking uh I I I
did uh research a few of such trees and
uh there are gaps in the trees or jumps
300 years forward or backward and so on.
So um those are all noted in suggestions
that this person can't be a father of
this person but uh
>> when they're born 300 years later yeah
they are not corrected. So
>> um that's the reason for a huge
difference.
>> Oh okay.
>> There's not enough pre500 qualified
people to correct them all.
>> Yeah. We can try descendants
for this person. But I have to enter
this in a general search.
Uh this will find um descendants from
this person as a search result. So we
will get uh them in a table. So we what
it was 130,000 descendants
>> was found and we can now uh check the
suggestions for them. Ah,
interesting.
For
>> Oh, look at that. Queen Elizabeth was
the first Elizabeth the first was the
first suggestion
>> even it wasn't even uh so only 100,000
were analyzed
>> and 50,000 suggestions were found and we
are interested
>> father's too old. So yeah, so these four
are definitely
>> uh
screwing up the table.
>> Yeah.
>> Uh
uhhuh. Okay. Uh oh. Okay. This is just
No, this is not really the problem the
problematic suggestions. It should be uh
>> there's one down there. 205.
>> Father too old or father too young.
Usually too old is the
>> really problematic one.
>> Mother was dead before birth. 250
profiles.
>> So these are the So this one was uh we
have 150 years gap here
between father and child.
>> Oh look at that. Ah
>> so these are the reasons for such a wide
spread of uh ears. Yeah.
>> Oh, look at that. 1604 to 1900.
>> We have even a private profile here.
>> Okay.
>> Jumped out.
So, this is the problem for such a
widespread. So if you're doing that for
your own uh family for 10 20 10 15
generations back uh you should first
clear the date errors if you want that
uh column to be correct
>> that makes sense too. Yeah.
>> So I don't think I will create a report
for all of them.
Um
I I mean if there is really an interest
I could uh do it for a few selected
profiles to calculate and monitor the
all descendants but
>> I don't really uh
>> want to I mean I don't see real point in
having that number. It will be big and
>> it will grow a bit each month each week
but uh
>> I think of importance here I think
>> I mean
>> it was a good idea though Patty for for
marketing I mean for
>> okay
>> but I can just I mean that's that's
something we could do you know just like
>> yeah it might be kind of fun to
>> like for St. Patty's Day. Um yeah,
>> you know, do if we calculated it the for
you know, King Brian Boru or on St.
Patty's Day, that would be an
interesting stat and topical.
>> Um
>> I don't think we have a Genghaskhan Day
or a William the Conqueror Day or
whatever.
>> I don't think Jesus Khan has a lot of
descendants on Wiki Tree.
>> Is it?
>> No.
>> But isn't he one of the ones that they
talk? But maybe a right wiki tree
doesn't have necessarily his branches.
Um,
>> it's mythology, Greg. But it's it's
mathematics.
>> Anybody who was alive a thousand years
ago and has any descendants alive today
has millions, if not billions of
descendants alive.
>> That's right. Yeah. Yeah.
>> Either they die out or they keep
increasing.
>> That's right. Yeah.
>> Yeah.
Uh,
>> so what is Genghaskhan's profile? Is
that Oh, yeah. There's only 17 profiles
connected within seven degrees.
>> It's unc Huh?
>> So, am I am I wrong? Is he not one of
the
>> Yeah, he's he's unconnected.
>> He's unconnected. Okay.
>> Okay. So,
>> yeah.
>> Charlemagne, I think, is there with a
huge number of descendants,
>> right? Charlemagne. That's Well, am I
wrong in in in thinking that Genghask
Kong is rumored to have lots of
descendants?
>> Yeah, there. No, that's right.
>> It is. Okay. I didn't misremember it.
It's just that it's not the part of the
world where Wiki Tree is big and strong
and has a huge presence,
>> which would be nice to change if
anyone's listening.
>> Um,
>> yeah, there's actually a post out for
can you help improve uh or get him
connected to the tree,
>> you know, back from 2022. stuff.
>> So, we could actually with no parents we
got uh 13 million but we could remove
the uh unconnected
because unconnected profiles surely want
to make it make an impressive number,
right?
>> Yeah.
>> But uh so it's 10 million to check.
Oh,
>> 1500 that will get it down a lot more.
>> Mhm.
>> Oh, I don't think it will. Uhhuh.
Pre-15. You mean just
>> Yeah. Pre 1500. Yeah.
>> But I have to put it in front of not
>> like this.
So we are at uh 40,000 profiles
h
well that's
>> and even pre 15 is too I think the
winner will most certainly be from first
century so
>> yeah um
>> the winner for sure Yes.
Did I click it? I think you did. I don't
see anything though.
>> It's happening.
Observers are busy.
Okay, it's 10,000 then.
As sure, you you gave me the wiki tree
ID, I guess, for this one.
>> Yeah, that's 12 descendants. So, not
really in the top list.
>> That's Genghaskhan.
>> Yeah, I I was just sharing Genghaskhan
and Charlemagne's IDs if anybody was
curious about them.
Whoa.
>> Yeah, but it's unconnected as you can
see here on the
>> console.
>> This is
>> so get to work people.
>> And the other one.
>> 17. Oh,
>> where where are even records back that
far?
>> Wow.
>> Okay, this one has a few more. Yeah,
>> this is Charles Carolingian
Carolian.
>> Carolingian
>> and it has ancestors.
>> Oh, surely they
>> are there the
>> He does have ancestors apparently. Yeah,
>> actually we can check ancestors here. So
>> we have 14.
>> How come they all have AD as their
initials?
>> Yeah. Ancestors and descendants.
>> Yes, of course. I know. I just had to
think about it.
I thought, you know, lots of families
have a very strict naming pattern that
they always follow.
>> But that's this is Wikry Plus naming
pattern.
>> It's not the same. Yeah.
And this icon are for maps and so on,
>> right? Yeah.
>> Yeah. Further on it.
>> Yeah,
it is very cool how you how with the
consistent icons you can pack so much in
such little space. I do love that.
>> Okay, just one descendant. Oh yeah,
sure. That's the last one. End of the
line,
>> right? Yes.
>> Yes.
>> Actually, we should check ancestors.
That's bit more. 31.
There we go. Oh.
So these are the ancestors of that
Italian princess Bertha, right?
>> Obviously.
>> Specifically. Yeah.
>> Mhm.
>> It's mostly France and German, but
>> yeah.
>> Okay. The location matching in that in
those at those dates is not really
correct.
>> Oh,
okay. Next question.
>> Okay. Okay. Uh, so Patty did have a
question if
um, and maybe you've already answered
this. His qu his his last question in
August was more about suggestions than
we Well, I guess that's part of Wikry
Plus. So that's
>> it was a suggestion about suggestions.
>> Suggestion about suggestions. It was
very very meta. Yes, it was about uh, he
had an unclean profile after merge
suggestion which really should have been
unclean profile after auto bio. and he
was wondering if the suggestion should
have been expanded to unclean profile
after emerge or autobio. And he
suggested that it was it'd be easy to
tell if it if the what was happened was
after an autobio because you'd have two
copies of biography and two copies of
sources.
>> No, but the other the second copy is
within the comment.
>> Okay. So you don't get a new suggestion.
No, it it's it's all on the same. It's
all in the bio.
>> Yes, but it's uh commented out by wiki
comment.
>> Yes, but it should still
>> So, you'll see it only in edit mode, I
think.
>> Oh, the second copy of the bio sources.
>> Mhm.
Actually, the original bio I think is in
commented out. It's not instantly
deleted.
Right.
>> It is suggested that you delete it after
validating, but
>> um as far as I know. Okay. K is missing.
But um
>> Mhm.
>> I think um that's the intent of it.
>> You want to do one, Greg? Show it.
>> You want me to You want me to do one?
>> Yeah, go for it.
>> He's got a profile ID there for you on
the question.
>> Oh, he does. The question is, did I
clean that up myself or did I leave it
there as an example?
>> Uh, well, let's go to Keen and let's
just see how keen you were.
>> Uh, okay. It doesn't look like there's
two things, but if we go into edit mode,
>> let's have a look. See,
there is biography sources.
>> But if you run,
>> if you run it, go ahead and run auto bio
so we can see what it looks like when
you do that. Uh, where's
>> it's under biography. There we go.
>> Autobio.
>> Oh, there we go.
>> And uh,
>> so it tells you it it tells you to
>> But it's not commented out.
>> Yeah,
>> there's a comment for the duplicate.
>> Ah, there's the comment you were talking
about.
>> Mhm.
>> Uhhuh. I thought it was for the
>> You thought it would You thought this
would go to the end.
>> Yeah.
>> So, if you just save it stays in, but
Okay.
>> Well, and and before you save, there is
a reminder. There it is.
>> Don't forget to delete the old bio.
>> But I'm going to save it anyways and
just say uh uh ask Allesh demo
will change back
honest.
Now, let's see what it looks like.
Biography sources. Biography sources.
Yeah, that's ugly.
Okay. So, if I if I understand what
you're suggesting, Patty, is that the
next time that suggestions gets run,
this should generate a suggestion that
says specifically
something about auto bio.
>> Yes.
>> For this from the suggestion. So if I
click suggestion now these suggestions
get run once a week, right?
>> Mhm.
>> So it's not going to pop up right away.
>> Well, for the uh unmmerge unclaned
profile after merge merge, I check only
if there are two uh sources
headings.
So that's the condition I use. So
>> um
>> I avoided biography because uh that's
not completely true in case of
multilingual biographies but sources is
usually
>> sources definitely in the only right
>> no they can translate sources into
German and so but that's rare
>> but wouldn't there would still only be
one sources section wouldn't there? M
yeah most likely
>> like
>> no actually it would be missed uh if
um if sources would be merged with the
German version of sources then it
wouldn't report it as an error but um
it's okay I don't think those there's
many such profiles so
>> yeah it's it's totally acceptable to
have multiple biographies if they're
different language biographies
>> um and I really like that when we have
those multilingual profiles. I think
that's very cool.
>> Um, have we had
>> Can you can you go and check uh this
profile with biocheck now after you made
the
>> Ah, good qu good point. Okay, let's move
this window
>> because we now have uh all the bio uh
bioche uh validations also on wik3 plus,
>> right? Okay. Uh, so the quickest way to
do that would be to go to can can I get
bio
>> copy copy wik tree ID and Uhhuh. Okay.
>> I was going to say is there a direct
link from here to biocheck
>> from here? No, but you can go to wik
tree plus find this profile and go to
bioche.
>> Okay. Yeah.
>> Plus w tree. Okay. not suggestions but
the second uh search
>> lubana switch to here
>> and analyze results in bioche client log
>> y
that's how I come to bioche
>> you always go through there yeah there
we go
>> okay uh sourced
six lines between sources and references
multiple biographies multiple sources
heading biography heading biography
heading before.
>> Okay. But even uh biotech doesn't
recognize this as autobio.
>> No, it doesn't
>> problem.
Well, we'll have to ask Kate to resolve
that.
>> Mhm.
Um if she I mean if she would recognize
such profiles uh then because now those
are available all bio checks are
available on wik3 plus
>> and uh
I will be possible to make suggestion
based of on those and so on but
>> um
I don't think there is an explicit
>> right
>> uh keyword for this case Right. So if K
can determine that a profile has both
the multiple bio and the multiple
sources.
>> No actually I think that text in between
uh giving instruction to do after um
what to do after merch should be the key
>> after the auto bio. Sorry
>> check the comment where wiki tree plus
can't. Is that it?
per week. I can see the comment but uh
uh I don't uh I don't base suggestions
on comments because that's something
that people live in for in for uh edit
mode to see if you are editing a profile
something and it's pointless to check
for those error those are not visible on
the profile. So I decided to complete
the bioche
>> when K in K's bioche app she go she
could she could look for this
>> right?
>> Yeah I mean me too because I'm now
running bioche on on all profiles each
week. So this could be an easy check
just to find this
>> uh autobio text in a comment and uh
report for that.
Um
okay what do I
>> you will have to I mean this is not what
we want to find. I mean,
um, I would need because if you
go back to the Victory Plus,
>> uh, okay.
>> Yeah. And click the help icon in text
search.
>> Okay.
>> And scroll down to the bioche section
a few pages. This one.
>> There we go.
>> So, these are all the uh bioche errors
that are reported for wikry plus. Mhm.
>> So we can add another one that has auto
bio duplicate or something like that.
>> Right. Right. Excellent.
>> Okay. Well, K will be happy we've just
made work for her.
>> If K will watch this, she can do it.
Otherwise, you'll have to ask her to.
>> Am I correct? Okay.
>> Am I correct in saying that when you
complete a merge, you don't end up with
two sources headings because
>> no process picks up the two bios and
sticks them under one bio heading and
picks up the two sources.
>> Oh, really?
>> Uhhuh. That that's no longer the case.
Really? Uhhuh. It's possible because the
merge was uh improved over the years,
but we have plenty of old unclean
profiles.
>> Well, what I'm going to say uh I'm going
to change the sources here
and I pause it that we're going and
actually I'll put I'll make those say
new
>> and then just do preview and you'll see.
>> Oh, right. All right. I don't even have
to save it again.
>> But you're not you're not doing a merge.
You're doing an auto bio.
>> Well, this this was what this is the
tech. I didn't change the text after the
auto buy at all. But I think that when
you do the preview, you will only see
one set of
>> No, you will see both
>> because you have it. They're completely
separate.
>> If one was before the other.
>> No, P was talking about the merch. I
think merge process now cleans up by
both biographies
and sticks sources together. I think in
the for the in the last few years.
>> Okay, well that's good.
>> I don't do many merges.
>> But the autobio doesn't.
>> Oh, the merge cleans up the sources into
one, but the autobio does not. Yeah,
Greg, if that biography was above that
other sources
>> with that ref tag,
>> then you'd have,
>> you know what I mean? It's because the
placement, right?
>> Yeah. But such profile
if it's not cleaned after autobio would
uh raise several uh suggestions. So
>> no I know I think he was just testing
the
>> it will
be included in the suggestion report. I
>> I think he was just testing about what
would show up in the sources based on
>> because I thought for sure that I had a
scenario like it's been a while. I was
working on it showing it separately.
Look, it is showing it separately and
old
>> but I had I had I was working on a
profile once and I can't remember the
exact specifics but I thought there was
two sources section and I could not find
the other set of sources. I thought why
are they not showing up?
Um,
>> oh, it might have been.
>> The key is the references line and since
you have two, the references line uh
shows only the sources from previous uh
from previous references line, let's
say.
>> Oh, okay.
>> It's because they're not in line. It's
because they're those ones aren't in
line. Those ones you put the new and the
old.
>> Yes,
>> you put new and old on James Franc. The
inline citation there.
>> The biography.
>> Yes. Yes. Yes. That's what There we go.
>> That's what you're trying to test.
>> That's what I'm trying to test. Okay.
>> So, that's the
>> Let's go new
in objecting that there were two refs
with the same name.
>> I'm most likely it does. Uh go to
suggestions for this profile.
>> Okay.
>> Old
email.
>> Okay. Now check.
>> And now check to see. But you're right.
There's the same name, too. So that's
going to be interesting.
>> So many things wrong with you. Don't
clean up your
>> I hope you know how to get that.
>> Look at that. There's no old inline
doesn't show up.
>> Yeah. But now because it's named the
same biography. But now take the old
biography and put it below the first
sources header.
>> Okay.
>> Like you had it before.
>> Like I had it before. Okay.
>> Yeah. So take that second one.
>> Grab that.
>> Okay. Wow. What a rabbit hole, Patty.
>> Now check. Now I'll do a preview.
>> Yeah, but what why are you doing all of
that? All you got to
>> We're just checking. We're just
checking. It still says
>> yes because you didn't rename the inline
citation. Both are death one.
>> Just do delete old bio.
>> Exactly.
>> I know, but we're just checking.
>> We're playing.
>> Just curious.
>> Oh, see.
>> Look at this. New inline for the first
one and then new inline and old inline.
>> We're just seeing how it works.
>> Yeah.
>> Functionality. How that how that all
works. We're We're just We're making
additional Warren underneath the rabbit
hole.
>> Yeah, you are.
>> Curious.
>> It's too early.
>> You need your tartis of coffee there,
Denise.
>> Yes, I do.
>> Only I don't do coffee.
>> How did you turn Wifred M Casey into
Wifred MK Casey? MK Casey.
>> How did that happen?
That's two more that
>> that second biography is what was there
originally.
>> Really funny.
>> So it was it was incorrect in the
original one.
>> Oh.
>> So when you did the auto bio, it cleaned
that up. And so that second one that you
guys are playing around with Yes.
>> is the one that was messed up to begin
with.
>> Yeah.
>> Okay.
So, we should leave the top part, you're
saying?
>> Yes.
>> And so, delete all the bio.
>> Yeah. When you delete the old bio, it's
going to take away all that other stuff
that was down there at the bottom. It
takes away the second one.
>> Okay.
>> And then everything is correct.
>> You were never here. No, don't do that.
>> The ask group. We're not here.
>> Okay.
>> No,
>> that's funny.
>> You still need to do delete old bio or
undo old bio before you get that
message.
>> See, I've got the regular bio.
Casey just once.
James died. And there's the sources.
>> Okay. And and still click
still click your delete old bio button.
>> Yeah. So I get rid of the
>> up at the top. See that little button up
at the top?
>> Oh, delete all bio.
>> Yes.
>> Yay.
>> But I did delete the old bio. That was
not really necessary because
>> you don't need to do it automatically if
you've done it manually.
>> Yeah, that's what I was thinking. But
anyways, okay. I'm saving it.
>> Yeah.
>> Okay. Now check change history.
>> Uh ask demo. We'll change back on all
fix. Nothing to see here.
>> Okay.
>> Okay. Go to edit the biography so we can
see what we changed.
>> Oh.
>> Mhm.
Okay. I think we're okay. I think. Are
we okay?
>> I think we're okay here.
>> Yeah.
>> Okay.
>> And previous was the other way around.
>> Okay. So, let's go back to James.
>> Next rabbit hole.
>> Next rabbit hole. September. Let's get
to September.
Uh Pamela. Pamela, if you've been
watching and thinking, why is it taking
44 minutes to get to my question?
I apologize. You can blame me. I'm the
king of rabbit holes. So, I have problem
with errors that have been corrected but
are continuing to show up as
suggestions. Uh, and then she has a good
suggestion. I have glass build as my
example. Uh, find a grave different
date. Researching this person, I
determined the birth date on wiki tree
was correct. And so on fandrave I
suggested an edit to the profile of the
manager correct the date on findrave.
And then I edited and changed the status
of the air to correct it. However, it
still shows up. I suggest I searched on
Wik Plus and I still see that it shows
the original incorrect birth date from
find a grave. Can you please explain why
this is?
So,
>> okay.
So,
>> so do you want to take over the screen
from here?
>> I did.
>> You did? Okay. Then I will stop my
screen sharing. Um so uh this is the
suggestion in question.
>> Mhm.
>> And as we can see here um so these are
the dates from Wikitry
>> and these are dates from find the grave.
So it's still and uh now if you check
this find the grave site it's probably
corrected.
So 1950
uh
>> which is the same as wik.
>> Yes. And this is 51. So here it's
obvious that um my data for find the
grave uh is not updated. Now um this
falls into the updating section of find
the grave,
>> right?
>> So I
we have 10 12 million links to
uh find the grave. So it's impossible to
check all of them each week or even each
year. M
>> um so I'm using um a few uh ways to
determine that uh the profile needs
updating. So I I I am updating the
oldest the the ones that were not
updated for the longest time and then
I'm also updating some where the um
child rel the profile relation on
uh doesn't match with the other uh find
the grave uh pro memorials.
Uh so I here these 200
memorials are not are needing update at
the moment. So I am I will run this
later today. Um
and I do uh so a few years ago, two or
three years ago, uh I made the updates
uh uh I update request bas based on
their site map. Uh but um in uh but they
stopped updating the site map in let me
check.
Uh so let's go here.
>> Whoa.
>> Uh
look at that.
>> So these are uh in the grave memorials
and as we can see they stopped updating
it in July. So in June. So since June I
don't have any updates uh of find a
grave site unfortunately. Um this
happened a few times before but then
after a few months they uh resumed the
operation. So um I'm waiting that they
will at the moment we don't have uh
changes from find the grave available to
us and site maps those are that's
something that is made for um search
engines to know what to check which
pages to check on the site and it seems
that the process that should create that
fails and no changes are recorded there.
It's bad for them and uh search engines,
but it's also bad for us because I don't
know what to update
with this uh operational
uh update on find a grave was seen was
visible on suggestions within a month or
two. Usually it took two months but now
it's not working for four months already
and I don't know where when it will
start to work. I'm sure when it will we
will catch up. I had before this was
available I had some other methods to um
uh validate profiles more reg with
suggestions more regularly. But um after
this was available I stopped that maybe
I should res uh start doing that because
the profess with with suggestions they
were like in this case correct it on
find the grave. So it would be uh good
to know that as soon as possible,
>> right?
>> Updated, undated all the updated
missing. Yeah, I even removed for it
from the menu,
but I'm sure I still have a code
somewhere to check for those,
>> right?
>> Yeah,
maybe I should reactivate that.
>> Mhm. So, basically, they're not giving
you the list of the updates.
>> Yeah, it's it's failing for them. it
they're showing still
>> uh like no changes on find the grave for
last four months.
>> Mhm.
>> And any other method is problematic
because they have 350 million memorials
and
>> um it's just impossible to scan all or
whatever
>> all of them all the time. Yeah,
>> I will uh I will look into reintroducing
the old update method which was a bit
better than we what we have now
>> since this is not working
>> right. Okay, thanks Alash. So in the
short term just marking it as correct is
what all we can do but then once
>> uh well actually uh this as I remember
marking making a comment on a suggestion
prioritize those so they were checked as
soon as possible.
>> Okay.
>> So like if you would click correct it I
would check it next week.
>> Excellent. Okay. uh because it's it is
possible that also find the grave was
corrected.
Okay, good. Uh let me refresh that page
and there are no more questions on the
GGD post. Um,
did any I don't see any questions in the
Zoom chat live, but do does anyone here
um want to ask a question that we
haven't answered or find a rabbit hole
we haven't yet gone down?
>> I just found an approved merge and
confirmed that there's only one sources
section, one biography section, but two
research notes sections and the merged
biography.
>> Oh, that's interesting. Sounds good. Oh,
something I wanted to mention is that if
somebody has a question, they could also
ask on the space page for Ascalles in
between cuz sometimes a G2G post for Ask
doesn't go up until a few days before.
So, that's another place somebody
>> could ask a question if they have one
come up.
>> Oh, Pam is with us. Oh, excellent.
Fantastic.
>> Okay. I was wondering since Allesia is
on the first Friday and October I mean
the source is on the first o in October
right this will not be on right
>> Friday is 2nd October so
>> oh
>> but it's Friday it's a long weekend
>> yeah source is the 2nd through the 5th
>> so okay then it will be 9th
>> okay
>> I think that's
>> October 9th work for you Greg in the
lift
>> well I mean it could be during during
the source. It doesn't have to
>> be rescheduled just because
>> just think of all the
will not be sourced due to escalation.
Come on, we can do this.
>> I know. I know. I'm just saying. I'm
just saying it's not like, you know,
we don't have a role in place.
>> What could possibly go wrong?
Uh
>> there are weekly Zooms for October Fest
in October anyway.
>> Yeah.
>> Yes, that's true.
>> But those are usually on Thursdays,
right?
>> They have Yeah. And I have to confirm
with you that um I think I'm free.
Uh yeah, it doesn't look like I've got
anything else scheduled for that Friday
the 9th. So yeah, we can move Asklesh to
Friday the 9th of October.
>> Okay. Well, we can check the uh my
flowchart of things to do on wik3 plus.
>> There we go. There's lots of rabbits
there.
>> Okay. Yes. Okay. So, October, we're
locked and loaded. Yeah.
>> Okay.
>> Good.
And
>> so, here is how I see if something
doesn't work uh on the week database.
I'm processing.
H.
>> Oh, it's just threats.
>> Wow.
>> Templates big.
>> Yeah, the report for big template it
didn't uh finish. So, let's put them to
the queue again.
And it's being processed. Now, it's blue
and green when it's done. But it takes
350 minutes to do it.
>> Wow.
>> That is so cool how you've got it
arranged that from a flow a simple
flowchart you can just start and stop.
>> It's very easy. I just start the dump
and first is I download the profiles,
marriages, links and so on. And then
after they are downloaded they are
imported. Then some things are exported
for other tools and so on.
>> And then here FTC are indexes being
built for the searching on wik3 plus. So
it's a lot of them
>> and
it is very cool. uh
>> then and then after the all the indexes
are built this is kind of first phase of
the uh data processing then I start the
suggestions calculation suggestion
calculations so this is usually uh
Sunday night or Monday morning for me um
so after 30 24 hours of for up until
here it takes 24 hours to complete. Then
all these are uh suggestion calculations
and then uh when that that's done uh
also report creations
all the reports that you can see each
week and here in at this point I uh
publish on uh G2G emails and everything
switch the data in the uh on the uh web
page and so here is actual act actual
release of the suggestions and then
after the release I repair all the uh
suggestions by uh location and uh
unconnect unconnected reports uns
unsourced reports some statistics and
update find the grave site and a few
more things. So these are done after the
uh
uh after the u release of the
suggestions.
>> Mhm.
>> Now do you have a schedule for your data
doctor challenges or do you just uh
>> uh well AI organizes that? Um we have a
group of um we have a group of 10
challenges approximately
>> that we are cycling at the moment. So
this is
um these are all the
uh challenges.
Um,
okay. So, here,
um,
>> so you're not just making those up
willy-nilly. A spelling.
>> No. Yeah, kind of something like that.
So we have here from so missing location
was the first instance of uh
>> challenge this week uh
>> and before uh this 10 or 11 now 11
challenges cycle
>> uh each week sometimes we swap to if it
happens I mean
>> right
>> usually unintentionals then gender is
used just for the uh uh woman uh just
once a year I think um
>> uh or twice once for a male once for
females I think something like that so
this is kind of the set of um repeatable
challenges then we have connect ones
>> and source they came as needed
>> how many um unsourced profiles are there
currently going into the source
>> it all uh it all depends Uh if you are
asking by uh uh category or bioche
bioche says more
>> does it
>> right? Yeah, I think it does. Uh, let's
see.
>> I was just curious and then I was
curious about how
>> Mhm.
>> the percentage of unsourced over the
years. Has it gradually been going down
overall?
>> But it was uh until now it was really
not complete picture because only the
profiles that got the category were
>> counted. But now with uh 4 million 4
million unsourced profiles, this is a
great number to track uh over time.
>> Mhm. Yeah, it'll be nice.
>> Mhm.
>> Out of how many sort profiles
altogether?
>> We have 40 million 46 I don't know
something like that.
>> Yeah.
>> Okay.
>> Oh, actually I know how many.
>> So it is less than 10%. Yeah.
>> 46,184,000.
>> Yes. But but but the ones with private
biography are excluded from this check.
So
>> Oh, right.
>> It's not really really that
>> um actually the only place would be to
check the statistics,
>> right?
>> And by uh unsourced profiles, I don't
think I have the new one. No, I mean uh
I just need the privacy something. This
would be
um so we have
currently we have 42 million profiles
that is uh excluding unlisted ones. So
are unlisted or not not here
>> seen here. So um and uh 300,000
uh I think 20 and 30 are private
biography.
So half a million uh of those uh are not
even validated. So we are at 42 million
profiles were just checked for u for the
biography.
>> Yep. Huh.
>> And 4 million are unsourced. So 10%
>> is a good estimate.
>> Mhm.
>> And it should go down over time.
We hope.
>> Yeah. Good.
>> Okay. So only four billion to do for the
source, right?
>> Yeah. Just for me.
>> We can do that.
>> No problem.
>> Oh, Asia, you are such a dreamer.
We just need like 10 times more people
to take part, right?
>> No, I think we should go for a new
record. Let's let's let's do 4 million
this time.
>> Let's do 4 million.
>> And we can we can discontin the phone
then.
>> Yeah. There we go.
>> You need to increase the amount of
people taking part, right? Because we
usually have about 600 to 700 people and
we do about what 55,000.
Sourceons. Yeah.
>> Yeah. Cool.
Uh, wow. It's 10:05 already.
>> Oh my god.
>> Um, so
>> implies on your bed.
>> It does.
>> It does. Yeah. Um, any other things you
want to share from your updates?
>> Not really. I just What's new?
>> Yeah. This section we did, I think this
in August. Mhm.
>> So we are from here on.
>> Yeah.
>> So bioche and sourced was already uh in
included in the uh rank calculations
uh content rank one and um the research
status was also included into uh rank uh
into the rank.
>> Nice. So those two things are changed.
Then I noticed that uh we don't it was
not possible to search by this uh
keywords on wikry plus. So I fixed that.
So you can uh we can see all uh gold uh
status profiles now. Um,
>> oh, so we can see how many profiles have
the different
>> Mhm.
>> So, research gold will get us 177
>> profiles with research gold status.
>> Is that going to be a group by field?
The research status.
>> Well, there still is a group by, but if
you that's the search keyword. Yeah,
then really do much.
>> If you did a search for your pro all of
your profiles,
then you could group by research status
and see how many different
>> ones. So, we can check Ljubljana.
>> There we go.
Easier for you to spell.
>> I'd have to refresh the status.
>> Nice. That's cool.
>> You get the statuses. So I set it on six
to silver, one unfinish, one one one
finished, and one that I need to review.
I think
>> something was not okay with sources on
this profile, so I just mark them like
this.
>> Very good.
>> Nice.
>> Very cool.
>> Um,
okay. What's new?
>> Escales. N. Oh,
>> you need to change the
>> uh
I removed the this suggestion because it
was a copy of the 600 one. Um, and since
600 is now done for all profiles,
there's no no longer a need to have it
as profile completeness. So,
>> right,
>> I just removed those two suggestions
and now we are working on surnames with
Chris quite a bit.
>> So, um, this is something that you will
see as part of the changes. So these are
uh this is a page where you will you see
uh all imper imperfections on written
profiles that needs to be done. So you
have uh for the for this surname there
are 190 unsourced unconnected unmerged
profiles then with low content rank and
with suggestions not all suggestions
just errors. So
>> that's awesome.
>> Those are kind of um priority to correct
>> also a part this will be also a part of
uh the new um
>> collaboration score.
>> Collaboration score. Yeah.
And here you get the start of the table.
Uh and then you can if you are
interested for unsourced you can
continue to page through it. But just
this page then and then just this part
is shown.
>> Wow.
>> That's cool.
>> Yeah,
>> that is.
>> So surname is a is a
word you're checking against. I mean
it's like a magic word or whatever you
call.
>> Yeah. I mean this is a surname. So now
query. Oh, this is here actually is not
uh uh this is uh this is a special page
done just for this but otherwise um it
is uh there is a new index surname
equals and you can use the last name
that uh finds only open profile with
this last name as at birth. So because
we excluded all not opened profiles from
the all these reports and um uh only
last name at birth is uh checked not the
other last name other or last name could
or current those are skipped
>> and it has to be spelled exactly that
right? Yeah. Well, not completely.
O'Reilly has a few variations that come
to the same uh
>> page because we actually ignore uh all
the separators. So, that's on
>> I'm checking for one name studies. Is it
checking the other variations when
>> that's what I was asking about? Yeah,
because I was thinking Douglas.
>> So, Peasley
>> could be a S or double S at the end.
Yeah.
>> Um not in concerning collaboration score
it will be just uh last name. So these
are the last name that are uh
>> okay so that so for instance if you go
to in to see one there
so all the Dutch variations are
represented like this one B. So um all
the spacing spacing is completely
ignored and also all special characters
are ignored and
>> um so these are just one
and O'Reillies are the other group with
a lot of
>> so these are
Odell O'Donnell
>> yeah Odonald So this is the name that is
used for all of those profiles.
Uh
>> look look at unknown and see what that
looks like.
>> Uh so this is the report for um for
surname collaboration scor that will be
>> yeah so unknown as the surname. There's
a lot of them out there.
>> Yeah. You can browse them by letter
starting letter or you can actually use
all of them and then sort by each
column. So we can check the ones that
have the best content rank
average content rank.
>> Okay. So you just make it unknown. Huh?
>> When the when the page is the full page,
it takes a while to change.
>> Yeah. It has a whole page has to load
its ID. Oh, it did already.
>> Okay.
>> Whoa.
>> Yeah, there's a lot of surnames.
>> Wow.
>> Yeah, I think. Is there a number? No,
it's not.
>> No.
Um
>> what's the one name studies when you
when you click on that
>> that's rolling up those variations.
>> No well one name study is done based on
the categories and category info box. So
uh multiple last name are joined into a
single report. So for instance, AMS also
includes these last names
>> right.
>> Um so here um the ones with one name
study and properly defined they
consolidate a few last names into a
single uh value into a single report.
>> Very good. We didn't completely decide
how this will look but um the data is
mostly uh the processing part of the
data is done. So so
>> where and how we will display this is
still to be seen.
>> And the second column there that you
have I guess it's the third one the wiki
tree plus errors.
>> Yes.
>> Do you want the number to be 100% or 0%.
>> Uh 100.
>> Okay. So it's actually errorree
measuring and here you are going for
unconnected and unsourced.
>> Uh actually I don't know no sourced are
sourced are
uh well I don't know maybe it's the
other way around. I really can't say
>> well cuz I'm looking like a lot of the
majority are have high numbers like I'm
looking at the Douglas which was my
>> Okay. So here I know the answer. So the
there is one suggestion one error for
this last name and that's 99.86 86%.
>> Okay.
>> And seven.
>> Okay. So that's the number of
suggestions in parentheses there. Okay.
>> So number of profiles without uh so the
percentages for the number of profiles
without errors.
>> Error free. So it's really more errorree
than errors. Percentage of error.
>> Okay.
>> So you want 100%. Yes,
>> you want you want you want 100% in all
of those these columns.
>> Okay.
>> And this one would be the hardest
because that would need to mean that all
profiles are in rank ranking rank rank
10
>> to have 100% here.
>> That would be hard. Yeah,
>> that's
>> I thought there was a limit of three
variants for a one name study, but
there's quite a few in that first column
of one.
>> Uh there is no limit, I think. It's just
a comma delimited uh comma separated
values, I think, and you can write as
many of them as you want.
>> Yeah, this the project has a limit. Huh?
Okay. Project maybe
>> is allowed for because there's only so
many that can be allowed for redirects
>> that that that's part of that.
>> Okay.
>> Um
>> but I think this this information is
taken from the category page and there
in category
information you can just uh stack them
as many as you wish.
>> Good to know.
>> Mhm.
>> Yeah.
So I can roll up my peas and paisley's
together. Okay.
>> And paisley's.
>> Very cool.
>> Yeah.
>> So this is something that will come in
the
>> may within a month. I'm not sure but
>> it's getting uh close. Yeah, there was a
lot of excitement when the surname I
gave a presentation about it to the
surname society and a lot of excitement
about it.
>> Fantastic.
>> I mean Chris is already preparing the
reports and page and I finished up all
the links to wik3 plus so that the parts
that are covered by wik3 plus will be
accessible directly from there from the
page. So this is already uh up
synchronized or um it's it were it's
working basically.
Um
uh
uh this is about this new surname index
that I mentioned where O'Brien is found
uh regardless of the apostro after the O
letter O. So that's uh because I I
implemented surname index for uh surname
collaboration score and why don't you
can all use it.
>> Why not use it? Yeah, perfect.
>> And the same is done on suggestions. So
you can also for on suggest suggestions
you can also use the surname index.
Um
and I added and another index that I
added was rank. This is this does not
use the magic words but it works just
like this like rank equals one. So if
you go to plus
>> um you search for
rank equals one and you will get all
rank one profiles
>> where rank 10 is the best and rank one
is the worst
>> in this case that's the so that's uh
>> three million of them
>> oh my
So here we don't have until now we used
it
something like this should be done but
now I decided that maybe this will be
better
>> right
>> or I will maybe make both possibilities.
>> Mhm.
>> Um
okay that's this news and we will have
zoom meeting today. We have it.
Excellent.
>> What do you do?
>> Hooray.
Fantastic.
Great. Well, I think the the Zoom I I
really like the interactivity of the
Zoom. I think this is works out uh
better for us for the Ask Allesh.
>> And correct me if I'm wrong because now
I've got, you know, I have a big large
screen monitor right next to me. So, I
can see I've always been able to see
Allesa's screen pretty well. But uh for
you folks who are normally just watching
on YouTube, is it is it clear for you?
>> Yes. Yes. Yes. Yes.
>> Giving a thumbs up. Denise is nodding
her head.
>> Looks good.
>> Although in on YouTube it was also quite
good, but you had to maximize the videos
window. But then you didn't see the mass
the chat. Yeah.
>> Right now. If you can see his if you can
see his little his uh flowchart there.
>> If you can see this then your vision is
perfect because I can't.
>> Okay, now here I can see it.
>> Yeah, that's better. Yeah,
>> that's good. Excellent. Well, thank you
very much. Um and thank you Azure for
joining us as and uh enabling all of
this. Um we couldn't do We couldn't do
almost well I wouldn't say we can't do
anything on week three without you but
we couldn't do a much a a great deal of
stuff without you Azure. So thank you so
much for everything
>> and everyone who's joined us and asked
questions and put up with us as we dived
in and out of the various rabbit holes.
Thank you for that.
>> That's my brother walking behind your
brother.
He's al co-author of the software that
we use.
>> Hello, Alish. Alles's brother.
>> Hello. Hello.
>> What's his name? Allesh.
>> Jiannis.
>> Jiannis. And is he younger or older?
>> Uh he's four years older.
>> Ah.
>> And now his son, my nephew, is also uh
working in our company. So
>> in the future he will run Wik 3 Plus
once I
>> decided to retire.
>> Okay. Well, hopefully that won't be for
many years still.
>> Yeah. Excellent. Well, that's great.
Very cool little dive into the family.
Um so, uh our next Ask will be October
the 9th. So, not the first Friday, but
the second Friday because the first
Friday we'll all be doing sourceing and
we'll be trying to get rid of those 4
million unsourced profiles.
>> Registration is now open.
>> Yeah, challenge put down. But before
then, there's a few other things that'll
be happening. So, um, the Wikked Tree
Challenge for this month, hope you might
be interested because our Wikked Tree
Challenge guest is Justin York who was
the very first Wiki Tree app developer.
So, come and help him out uh expand his
tree.
Um, and yes, do sign up for the source
thunk because that GG post is already
up, right?
>> Yes, it is.
>> Yes. Yes, it is.
>> Into the top of GTG.
>> Okay, fantastic. Uh and of course as
always there's the genealogy
collaboration hour which happens sun uh
Saturday afternoons um 5:00 pm Eastern
time. Uh tech talk Tuesday tech talk
Monday will be the last Monday of
September followed immediately by the
month of Htoberfest which happens the
eve of the source I believe. I think our
um well October 1st happened the year
before
>> and we are going to do have u weekly
>> uh chats on Thursday and um I have to
confirm but I think uh 1:00 on Thursdays
is that is that the time we had last
time?
>> I think so. Yeah.
>> Yeah. 1:00 works great because my
grandson is in bed by then or at least
he has been. Hopefully he still naps for
us.
Um so yeah. So, Thursdays at 1:00 uh
you'll be uh join us for those. And um
yeah, uh any anything else upcoming
Azure or Alashsh that I should we should
promote?
>> I I think Aen and I are going to be
doing a source howto.
>> Excellent.
>> Uh YouTube video. Uh don't have the date
yet, but we did it for the connectathon.
We're going to do it again for the
source. So,
>> that's excellent. That's a great great
>> And also Greg remember tomorrow f
is your Saturday roundup.
>> Oh well of course. Yes that's right. The
regular round up. Yes.
>> Yes. If you haven't had enough of me
yet.
Fantastic. Thanks again everyone and uh
have a great day. Bye
>> bye
>> bye.