Suggestions News and Updates (February 6th 2022) [closed]

Question

Here is a late report since I was skiing yesterday.

News

• I added a new subreport for Australia and the Netherlands named Unknown region, that consolidates the profiles where the region is not recognized. That makes a report of all profiles, that are not reported in any other regional report. That makes the country report unneded, since all profiles are included in one or more regional reports.

Added or changed some magic words in general search:

• MissingLocation: represents all profiles, that are missing a location. You can limit the query to each location field like BirthLocation=MissingLocation or DeathLocation=MissingLocation or MarriageLocation=MissingLocation or general one with Location=MissingLocation which is the same as MissingLocation for any missing location.
• UnknownCountry: Limits results to locations where country is not recognized based on the locations table. It is used as: BirthCountry=UnknownCountry or DeathCountry=UnknownCountry or MarriageCountry=UnknownCountry and Country=UnknownCountry (for unknown country in any field) which is the same as UnknownCountry (just as global magic word)
• UnknownRegion: Limits results to locations where country is recognized, but the region isn't. That is based on the locations table. It is used as: BirthCountry=UnknownRegion or DeathCountry=UnknownRegion or MarriageCountry=UnknownRegion and Country=UnknownRegion (for unknown region in any field) which is the same as UnknownRegion (just as global magic word)
• UnofficialLocation: Limits results to locations that are marked as no for accepted spelling in the locations table. It is used as: BirthCountry=UnofficialLocation or DeathCountry=UnofficialLocation or MarriageCountry=UnofficialLocation and Country=UnofficialLocation (for unofficial location in any field) which is the same as UnofficialLocation (just as global magic word)
• Err616, Err617 and Err618: Limits results to locations that are marked as suggestion for accepted spelling in the locations table. It is used as: BirthCountry=Err616 or DeathCountry=Err616 or MarriageCountry=Err616 and Country=Err616 (for suggestion in any field) which is the same as Err616 (just as global magic word)

Previous News

• I prepared a few new Profile Completeness suggestions 468-479. Those are all existing suggestions with certain limits. First 3 suggestions are limited to 3 or more cases while here they are reported for 1 or 2 cases. 471 suggestions are calculated only for Orphan profiles and here they are calculated also for your managed profiles.
• The "Correct" button, that appears on some suggestions didn't work. Now it does again.
• Have a look at profiles added during Connect-a-Thon: https://www.wikitree.com/g2g/1365903/map-of-added-profiles-during-connect-a-thon-2022-1
• Refined a few German locations in the location table. https://wikitree.sdms.si/function/WTShowTable/Table.htm?table=Countries&filter=DEU&Histogram=1
• I created new table to review badge activity and badged members activity. https://wikitree.sdms.si/function/WTShowTable/Table.htm?table=Badges
• Refined Scotland locations in the location table. https://wikitree.sdms.si/function/WTShowTable/Table.htm?table=Countries&filter=SCO&Histogram=1
• I finished synchronization of Statuses from WikiTree+ to WikiTree.com (statuses on edit page). That mean you don't need to set status on both ends. They are now synced in both directions within 5 minutes.
• I made some adjustments of the new suggestions as requested by users. One was to take the headings into accout for missing links calculation and the other were some exceptions about SPAN CLASS= and SPAN STYLE=
• Added Span formatting related suggestions. Error 951: Not recommended tag SPAN CLASS=, Error 952: Not recommended tag SPAN STYLE=
• Added Span linking related suggestions. Error 943: Duplicated span Anchors, Error 944: Missing span Anchors, Warning 945: Unused Span Anchors and Warning 946: Too many inpage links
• Added reports by county for Ireland.
  • Unsourced reports
  • Unconnected reports
  • Suggestion reports
• I updated Ancestors and Descendants reports on WikiTree+. See https://www.wikitree.com/g2g/1347445/suggestion-for-wikitree?show=1347790#c1347790 for details.
• FindAGrave update is caught up. The permanent gap will be 1 month. That means a change on FindAGrave will reflect in suggestions within a month.
• This week I connected many profiles with a link to wikipedia or wikidata, that were not connected automatically on a weekly check. That is the reason for slight increase in Wikidata suggestions. BTW: There are 232.129 profiles connected from Wikidata.
• Another new suggestion is about Free Space Pages included into the profiles. That is not allowed on WikiTree. Error 892: Space page used as template and Error 893: Space page used as transclusion
• I Aded suggestions Warning 419: Unmarried parents with no marriage and Warning 420: Unmarried parents with other marriages. Those are possible missing marriages on parents profiles.
• I added new Magic keyword, that finds profiles without specific relations.
  • noparents: Limits results to profiles, that have no parents.
  • nofather: Limits results to profiles, that have no father.
  • nomother: Limits results to profiles, that have no mother.
  • nochildren: Limits results to profiles, that have no children.
  • nospouses: Limits results to profiles, that have no spouses.
• Newest addition to search is a capability to search in subcategories. SubCat0, SubCat1, ..., SubCat9 defines the number of subcategory levels to include in the results. The Category name should be enclosed in double quotes if it includes spaces. Just add:as a keyword:
  • subcat1="Asia, Unsourced Profiles"
  • subcat9="Unsourced Profiles" Not subcat0="Unsourced Profiles" This returns all profiles in Unsourced Profiles subcategories, that are not in the Unsourced Profiles Category itself.

Challenge

We are starting new type of challenge 

https://www.wikitree.com/g2g/1371274/challenge-missing-connections-between-existing-profiles

Answer 1

Thank you for all the improvements you have been making, both in magic words and locations. I have a few questions about totals on the reports you generate and how to match those totals in wikitree+.

1) I have been tracking Netherlands statistics since this fall and I thought I had the correct search for the total unsourced Netherlands. However this week (and possibly earlier) the total profiles I found from this search  country=netherlands or CategoryFull=Netherlands,_unsourced_profiles (which currently gives 566404, slightly more than the country=netherlands total of 563165) is quite different than the total listed on the unsourced NLD page 532729 -- a number that is lower than the total for country=Netherlands. Our total unsourced seems correct -- it is only the number at the bottom with the table prepared details that seems odd.

2) I am interested in replicating the total you list on the Netherlands provinces pages, but I can't quite figure it out. Looking at https://www.wikitree.com/wiki/Automated:DD_Unconnected_List_NLD_NH the total profiles for Noord-Holland is 65863. My search for country=Netherlands noord-holland gives 74570 ; my search for country=Netherlands country=noord-holland gives 68189 ; my search for country=Netherlands birthlocation=noord-holland gives 42286. What search can I do in Wikitree+ to get get the same total as used in this official count?

Thank you very much for this clarification.

Comments

1) country=netherlands returns 563165 
CategoryFull=Netherlands,_unsourced_profiles returns 33675 

There are 30436 profiles, that repeats in both queries: country=netherlands CategoryFull=Netherlands,_unsourced_profiles

If you do union, the result set is 566404: country=netherlands or CategoryFull=Netherlands,_unsourced_profiles

The report https://www.wikitree.com/wiki/Automated:DD_Unconnected_List_NLD says Condition to prepare list (Country is Netherlands). Profiles: 563165, which is the same as country=netherlands I don't know where you found 532729 

2) country=Netherlands noord-holland is performed as country=Netherlands ALL=noord-holland

country=Netherlands country=noord-holland Is better to use. Recently I added optimization to do this query using double quotation country="Netherlands noord-holland" It is less writing and also querying is faster.

using location= is not a good solution, since it can give many false matches in different regions. That is extremely noticable in location='new south wales' or 'south australia'

In reports I use a trick to make the matches as good as possible. I search for birthcountry="Netherlands noord-holland" or deathcountry="Netherlands noord-holland" or marriagecountry="Netherlands noord-holland" which returns 65863 profiles. That is the number on the report. But this kind of search is new from last week.

---

Thank you very much. The number you couldn't find comes from https://www.wikitree.com/wiki/Automated:DD_Unsourced_List_NLD

Table prepared at 09.02.2022 10:09:26 (Slovenian time). Condition to prepare list (Country is Netherlands). Profiles: 532729

---

I checked and the number is the number of Netherlands profiles  excluding profiles in Category:Netherlands, Unsourced Profiles.

So correct WT+ condition for that number would be 

country=netherlands Not CategoryFull=Netherlands,_unsourced_profiles

---

Thank you

Answer 2

I have found several profiles where parents and / or spouses that have been added to profiles, WITHOUT sources being added to profiles or sources were not on profiles, other than Find a Grave.  That is NOT a valid source by itself to create relationships.

Comments

I have run into the same thing. I have to stop connecting and source the profile so I will know for certain they should be connected.

Also, did you know at the very bottom of a Find a Grave Memorial there is a link to the full citation, just copy and paste. In the middle of the citation it list everything needed to make our template work! This is so much better than just the template alone or just a url. :)