G2G: Is there a docment for interfacing browser queries to WikiTree

Question

I'm trying to setup a search query from Legacy Tree Software, looking for any documentation on the Syntax Wikitree can expect and respond to. I can reach the search page, but currently have been unable to pass the  names to search for, as an example.

Currently Legacy can send a query to My Heritage, Family Search, and Ancestory, among numerous other sites. I am currently trying to get Legacy to include the its USER ID field (which can be populated with a Wikitree ID) in the list of supported data fields that can be inserted into a possible query, which would greatly simplify the task.

Meanwhile I would like to be able to format a substitute or other queries that might prove useful, such as a search by given and surnames.

Thanks for any assistance.

Comments

Hi Robert. I'm not sure I understand what you're looking for, but perhaps the WikiTree API can help. See

• https://github.com/wikitree/wikitree-api/blob/main/searchPerson.md
• https://apps.wikitree.com/apps/wikitree-api-examples/searchPerson/javascript.html

---

... though I see I suggested this in April, so maybe it's not what you want.

---

It may be significant for what you're trying to do that the WikiTree search person form uses HTTP POST not GET.

Answer 1

A Jim said, the standard WikiTree search page does not support query parameters in the URL.

There are ways to do the search using the WikiTree API or via a browser extension (as WikiTree Sourcer does).

If you need to do it via a URL query then WikiTree Plus is an option.

Here is an example search URL for WikiTree Plus. This was generated by using WikiTree Sourcer to search from a FamilySearch profile for a WikiTree profile.

https://plus.wikitree.com/default.htm?report=srch1&Query=FirstName%3DRalph+LastNameatBirth%3DPavey+B19141222+D19921106+BirthLocation%3DSt+Pancras+Middlesex+England+United+Kingdom+DeathLocation%3DRamsgate+Kent+England+United+Kingdom&MaxProfiles=500&Format=

WikiTree Plus documentation for this kind of search is here.

Answer 2

Jim, I thought I recognized your ID. Thanks again for the pointers last time. The problem this time is trying to work within the Legacy Software framework.

1st of all, Trying to get: https://www.wikitree.com/wiki/[WT Profile-ID] formatted to display the WT profile for the corresponding entry in my Legacy db through its internet search feature. I can hard code the WT Profile ID in the URL and it works fine, but the data field containing that info is not allowed for use (internally by Legacy), in the search function, so I can’t build a flexible URL string using that field. Hopefully I can harass Legacy into seeing the error of their ways.

Other WT search functions would, of course, be an added pleasure. Other sites can be searched with varying degrees of complexity, thus I have been experimenting. However, after peaking at the code for the WT page, I can see it is likely not an easy task and, not only has been way too long since I mucked around with web access to a db, I never was that good at it. I will, however, review the all information you and Rob Pavey have provided and see what I can utilize.

It is annoying to me that the differing genealogy sites strive to provide as little compatibility or interfacing with each other as they possibly can. I realize at some point bills have to be paid, but for the most part, it does the industry no favors. A user base striving for accuracy and continuity are just 2 of the reasons I use WT.

Thanks to you both, Jim and Rob!

Comments

As far as I know, Robert, there is no standard for dynamic interchange of information between genealogy systems. This makes what you are trying to do difficult. The normal approach is to use GEDCOM files, which do follow a standard (or many slightly conflicting standards), but are not dynamic. Mightn't it be easier just to download GEDCOM files from WikiTree and upload them into Legacy Family Tree?

A more radical approach would be to use a programming language and develop a tool acting as an intermediary between the WikiTree API and some format that Legacy would accept.