Suggestions News and Updates (September 13th 2020) [closed]

+19 votes
198 views

News

Previous News

  • Added a new magic word construct Creator_ + WikiTreeID to the search engine. It finds all profiles that were created by that user. Here is an example for all profiles created by me. https://wikitree.sdms.si/default.htm?report=srch1&Query=Creator_Trtnik-2 You can extend the search to find all profiles created by me and no longer managed by me by searching for Creator_Trtnik-2 NOT Trtnik-2 https://wikitree.sdms.si/default.htm?report=srch1&Query=Creator_Trtnik-2+NOT+Trtnik-2
  • Added new suggestion 421 Hidden marriage on public or open profiles. A marriage can be hidden from displaying on the profiles. This is used for additional privacy. But using it on open and public profiels is not its intent. It is causing problems with suggestions, where you don't see the marriage on the profile and have no idea of what is wrong until you enter the edit mode, where you can see the marriage.
  • A new version of WikiTree+ Chrome extension is 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 SourceJunkUnmergedMatchPendingMerge and templatetext=Andersson to WikiTree+ search engine.
  • 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

Challenge

https://www.wikitree.com/g2g/1105959/challenge-of-the-week-help-clean-up-problematic-dates

    closed with the note: Outdated
    in The Tree House by Aleš Trtnik G2G6 Pilot (484k points)
    closed by Aleš Trtnik

    3 Answers

    +4 votes
    Thanks Ales  ... great job
    by Lance Martin G2G6 Mach 9 (90.9k points)
    +1 vote

    Is there documentation somewhere on searching in WikiTree+? i.e. 

    • use of magic words
    • partial vs exact matching (especially on multi-word phrases, should we be using regex, MySQL LIKE syntax, something else)
    • best practices on use of indexed fields vs un-indexed text searches
    • how that is similar/dissimilar to the JSON query method to return a list of userIDs?
    by Jonathan Crawford G2G6 Mach 1 (15.3k points)

    Here https://www.wikitree.com/wiki/Help:WikiTree_Plus#Text_search_2 is all the documentation I have.

    • Magic words are documented there.
    • From help: 
      • The searches are not case-sensitive. 
      • Unicode characters are treated as similar letters (Š=S). 
      • Space between words assumes the AND operator. 
      • You can also use OR and/or NOT operators.
    • We do not use regex or like operators, since they would need to be checked on over 20 million records and that is just too slow. Only whole words can be searched for.
    • By using index field, you can get less false matches. but generally if you are just quickly looking for something, it doesn't really matter.
    • JSON query is exactly the same, just the result is formatted differently.
    +1 vote
    Nice job Ales, thank you!  I was wondering how many profiles I had created turns out 245, and how many I manage turns out is 486 (I adopted many).    This is very helpful to have, again thank you!
    by Loretta Morrison G2G6 Mach 8 (83.1k points)
    edited by Loretta Morrison

    Related questions

    +12 votes
    2 answers
    +11 votes
    2 answers
    +22 votes
    5 answers
    +10 votes
    1 answer
    +10 votes
    1 answer
    +21 votes
    5 answers
    +12 votes
    0 answers
    +12 votes
    0 answers
    +13 votes
    4 answers
    +10 votes
    1 answer

    WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

    disclaimer - terms - copyright

    ...