7th January 2022 at 5:14 pm #13718
Attempt to run Facts and Events > Custom Fact > Type: Common ancestor (or any other type of custom fact) and no results. (The results should be the records that I’ve so far found with Relationship info after the 1 NAME). Is this too a server capacity issue?
8th January 2022 at 11:01 am #13719
I’ve been looking at this, and can’t see what the problem is. Similar searches work OK on other sites I have access to.
Server resources is a possibility, but I can’t see any evidence of that. I tries a general search (using Search menu) for “Common ancestors” which ‘should’ find all those FACT entries PLUS any others where that term just appeared in a note or source or anywhere. It only found 378 individuals, which is not great number. So I suspect it is some other problem completely.
What I would like to try is running the SQL database query that search uses directly on the database itself. Any chance you could organise access to the database for A&D temporarily?
8th January 2022 at 6:59 pm #13720
Will review how I did the setup previously later today (too tired to think :). The two Custom Facts in question that I know I use are “Common ancestor” and “Relationship”. (I have FACT as managers so restrict use of it if I want people to see)
Another matter if you are in the SQL — I previously asked about a stuck tree. You did reply but I didn’t follow through. (Chicken). It was “The Kennedys” that’s in with my A-D. Could you remove it please? It doesn’t belong there.
11th January 2022 at 1:29 pm #13733
Okay, with images out of the way (I presume), did anything you saw answer why I can’t run F&E > Custom Fact > Common Ancestor?
11th January 2022 at 1:37 pm #13734
Yes. Confirmed it is a resource issue, but still working on ways to improve performance.
For most sites it only happens on common facts like BIRT For your data FACT is more common than birth! More than 11000 individuals have one or more. Creating the list is quick and easy, but preparing them for display, sorted, filtered, duplicates removed, privacy checked, etc is the problem.
For now try adding further limits to the query, such as date and or place.
11th January 2022 at 1:57 pm #13735
Not good news! Date/Place Filters don’t apply. I *think* there’s just over 500 so far with the FACT I’ve used. Not many with number of records I have but obviously takes far more than I imagined to report.
Trying to identify “core” family. Blood and marriage related. So far most are immediate to third/fourth ascending or descending relations. The ones kiwitrees identifies doesn’t have a “report” so created the custom fact. Others aren’t blood so identified in Reunion or Geni as connected.
Using F&E would allow me to sort on Details.
11th January 2022 at 2:19 pm #13737
11th January 2022 at 2:33 pm #13738
I might be able to improve it. But I’m not sure it will ever work with those numbers. Reports like that are a very inefficient solution for a web application.
The more dynamic Relationship chart is more appropriate for kiwitrees, and works well.
11th January 2022 at 2:42 pm #13739
But the Relationship Chart is one to one connection. I can’t view all. And it’s in chart form, not list which includes the Details part of the Fact. Which is why I ruled out using general search for “Common Ancestor”.
Of course, as a user, no idea what goes on behind scenes to make a report/list work. Seemed simple enough request to generate. Thought it was along the lines of showing Individuals where there could be large results.
What’s my alternatives for this endeavour?
- You must be logged in to reply to this topic.