In RM10 I have just searched for Coldham, knowing it was a place where a chap is buried, but the reference did not pop up. What might I not be understanding please? (See images) It missed Coldham in the Burial place of the chap I was after but presented me with another guy, as the place mentioned in his death note.
No, it does not find everywhere but it did find a Place. Now you open the Place to find where it has been used. That reduced clutter in the results (the Place might be used by dozens of facts for many people) and is much easier to program.
1 Like
This is good case example of when a computer algorithm finds something it stops and moves on to next “case” statement it does not search for all possible eventualities this is bit confusing but it saves in processing time and clutter as Tom explained. Not sure if my explanation makes sense but basically you would not want the same find to be listed more than once in most cases.
I am with you now: thnak you. For anybody else who finds this thread, the next steps are as follows.
Click on Place to get to Place details screen for all the places (Place latitude Longitude Details).
Click on Details. I see that Coldham has only been used once (i.e. as a place) and is linked to the church.
On the right - under the map - find ‘Used’ (for me = 1)
Click on that and I get to the chap I was after.
Obvious once one knows, maybe not intuitive for folk like me.
Good description. The Help page talks about the hyperlinks in the results that you can follow to where the search string was found. What it does not talk about, understandably, is that Find Everywhere is likely built around SQLite’s Full Text Search functionality. FTS searches only those columns and tables specified by the programmer. Because it is a relational database, Places, Events, People, Sources et al are in different tables. That’s why the results are categorized and you link out from there to get to the context from which you can get to the appropriate edit screen.
1 Like