Jump to content


Member Since 06 Aug 2006
Offline Last Active Yesterday, 06:37 PM

Posts I've Made

In Topic: A few enhancement requests

21 June 2017 - 10:57 AM

I ~believe~ Renee is talking about the "paging" of screens of individuals as one scrolls, re-sorts, or resizes the results pane that holds the columnar data fields in People view.


That concern would make sense. However, for the other views where WebHints appear, they often do not appear all at once. Sometimes you can see the light bulbs coming on one at a time. There is obviously a background and asynchronous process (probably a thread) that is searching the internet for the WebHints at the same time the user is interacting with RM.


I guess it would seem to me that for People View, this background process would have to be relaunched each time the people on the screen change, which is something that doesn't have to happen for Pedigree View, Family View, or Descendant View.  But given that there has to be a background and asynchronous process that is searching the Internet for WebHints, I don't quite understand why Descendant View can take so long to come up when WebHints are enabled. It's like it's processing all the WebHints for Descendant View at once, even though not all the people in Descendant View are on the screen at the same time.


In any case, it seems to me that WebHints for People View is a solvable problem without destroying the performance of RM. I hope that it gets at least looked at for RM8.



In Topic: Entering County Names

21 June 2017 - 10:44 AM

I should also mention that many genealogists support the use of the place name standard whereas many other genealogist criticize the place name standard and prefer not to use it. RM users can leave the County Check feature turned on or they can turn it off. The County Check feature is based on the place name standard.


Even if they leave County Check turned on, RM users can choose to make note of the recommendations made by County Check and then override the recommendation, for example by including the word County even though the word County is not included in the County Check recommendation. Besides the inclusion or exclusion of the word County, there are other aspects of the place name standard that are in dispute among many genealogists, such as the inclusion or exclusion of the country name when the country name is clear from context, and such as how the name or abbreviation of the country name is spelled. Another issue is modern vs. historical names for places and the resultant geo-coding of places.


Another option for RM users is to turn County Check off and nevertheless to seek guidance about place names from RM's Gazetteer feature. Like County Check, the Gazetteer feature is based on the place name standard but Gazetteer is not as intrusive in making suggestions as is County Check. Which is to say, County Check can pester you to death if you are not following its recommendations exactly, but Gazetteer only makes recommendations when you ask for them. And just as with County Check, you can choose to make note of Gazetteer's recommendations and still override those recommendations to meet your needs.



In Topic: Entering County Names

20 June 2017 - 07:30 PM

And beyond Tom's answer, County Check was created the way it was because the Place Name Standard does not include the word "County". RM is attempting to follow the standard.



In Topic: A few enhancement requests

20 June 2017 - 07:27 PM

We have to take into consideration using incremental search in People View. 


I had meant to follow up on this one. What is an incremental search in People View?



In Topic: What is the definition of a "Master Source"?

11 June 2017 - 11:22 AM

For the most part RM has also developed names for its datapoint independent of other concepts. When I see the term "Master Source" I have to relate that back to what I know more intimately since GEDCOM does not have that term anywhere. This would also be true about each individual data point.


I tend to think that the way nearly all genealogy programs handle sourcing information goes back to PAF and GEDCOM. My naive and overly simplified perception of the original PAF/GEDCOM model is that really only two fields were provided - book and page number. Well, book was sub-divided into author, title, and publishing information, and publishing information was sub-divided into publishing place, publishing date, and publishing company. Users of genealogy software were then forced to be very creative in figuring out how to map things like marriage certificates, death certificates, census records, etc. onto this book and page number model. The exact field names I'm describing aren't exactly the ones from GEDCOM, but I think the concepts I'm describing are very close to the data model from GEDCOM. To this day, RM's free form source template follows the data model I'm describing.