Suggestions News and Updates (August 30th 2020) [closed]

Question

News

• No news

Previous News

• EditBOT 13000 corrections to clear Global Cemetery 897 Deprecated parameter in template suggestions are now gone.
• After all complications with google, a new version of WikiTree+ Chrome extension is finally published. https://chrome.google.com/webstore/detail/wikitree%20/giodhdfeabddjnlhknbggojlgpnhanof It has a few new things also usable to DD. Changes in version is 0.3.5 are:
  • Finished Profile cleanup. It does everything EditBOT does and a few more things. That includes conversion of old Ancestry links to new ones, I also added automatic conversion of curly quotes to normal ones.
• Wikidata template got sameas parameter. It will function same as with FindAGrave template.
• In suggestion 897 Error in template parameters I added checking of parameters that link to WikiTree pages. It is done for Categories, Projects, Space pages and Project Needs categories.
• I added additional checking of template parameters. That was in suggestion 848. I created 4 new ones 894-897 that will cover all parameter problems.
• I prepared two new suggestions (591 FindAGrave - Possible father and 592 FindAGrave - Possible mother) that list all missing parent relations between existing profiles. The suggestion is based on FindAGrave relations. In cases where both profiles are linked to findagrave and there is a parent relation on findagrave and there is no parent on wikitree, it suggests the connection. Of course you should first check if both findagrave memorials represent the correct persons on wikitree. Then you should try to find a source for the parent claim and add the relation if everything checks out.
• Added new magic word SourceJunk to search engine. It finds profiles with text "Family Data Collection" or "Millennium File" on the profile. Those are present on 47000 profiles. Here is a list of profiles with SourceJunk. https://wikitree.sdms.si/default.htm?report=srch1&Query=SourceJunk
• I added new magic keyword UnmergedMatch to search for postponed merges in combination with any other text. https://wikitree.sdms.si/default.htm?report=srch1&Query=UnmergedMatch+Sweden
• I added new magic keyword PendingMerge to search for pending merges in combination with any other text. https://wikitree.sdms.si/default.htm?report=srch1&Query=PendingMerge+Sweden
• I added possibility to search template parameters. That enables you to search for any text inside curly brackets. To explicitly search template text, use templatetext=Andersson https://wikitree.sdms.si/default.htm?report=srch1&Query=templatetext%3DAndersson
• I added to Connection finder 2 new types of relation search. Paternal Lines and Maternal Lines. This can help in DNA queries to find a common father/mother. https://wikitree.sdms.si/default.htm?report=disp2&WikiTreeID1=+Whitten-1&WikiTreeID2=Whitten-819&relatives=4
• I exposed the actual data on which location suggestions are based. https://wikitree.sdms.si/function/WTShowTable/Table.htm?table=Countries Based on the changes we did last week in the table, there are some new 6x8 spelling suggestions and 612 Location too early ones.

Challenge

https://www.wikitree.com/g2g/1097897/challenge-of-the-week-clean-up-marriage-data

Comments

Hi Aleš,

There are 7 new Profile Completeness suggestions that just showed up this week on the suggestion list for profiles for which I'm manager: "456 Profile completeness - Birth date Status not set." The birth date status was set on each of these profiles about a year and a half ago, and they don't appear to have been modified since then, so I don't believe that these suggestions are being generated correctly (though maybe I'm missing something). Can you please take a look? Hopefully this WikiTree+ link will get you the list of the particular suggestions in question ...

https://wikitree.sdms.si/default.htm?report=err2&WikiTreeID=Peterson-9074+&ErrorID=456

Thanks!

---

Thanks for letting me know. This week the dump format changed and I had to adjust the import. After an error in first attempt, I manually updated the status fields, but it seems I got it wrong. I am updating it again.

---

This is now finally fixed.

---

Thanks, Aleš!