Preview of a new Tree App: One Name Trees (Update)

Question

For previous discussion of this app, please see here: https://www.wikitree.com/g2g/1715996/preview-of-a-new-tree-app-one-name-trees.

Since the previous post, I've added a few things to the app and I think it's nearly ready.  Some of these are mentioned in the comments of the G2G post, but just to bring it all together, here are some things I've added:

• Centuries box.  As some surnames have tens of thousands of results, we need to narrow down the dataset a little.  There was already a Location box for this, but I've added a 'Centuries' box to narrow it down to one or more century/centuries. 
• Migrants/Migration visualisation.  Go to the Statistics section and look for the Migrants button.  This shows how many migrants have been identified in the dataset. Click the button to see where people migrated from and to. Use the arrow buttons in the top left corner to see migrants from previous or subsequent periods.  Click a green or red dot to see who the lines represent.  (The migrants are identified simply from their having been born and died in different countries. It takes into account some cases like someone being born in Massachusetts Bay Colony and dying in the United States (for example)).
• Unsourced, Unconnected, and 'No connections' lists.  Also in the Statistics section, you'll find buttons to show lists of profiles with 'unsourced' templates or categories, those who are not connected to the big tree, and those with no parents, spouses, or children in the database.
• Period setting.  For the period statistics, you can choose how long you want a period to be (10 years, 50 years, 100 years, etc.).
• Last Name at Birth Only setting.  You can restrict the results to only those who were given the target surname(s) at birth.
• DNA tags.  For profiles that have DNA data attached to them, you can see the relevant data by clicking the tag.
• Surname variants.  As before, you can add your surname variants to the Google file, but now you can also put a comma-separated list of surname variants in the Name box without adding them to the Google file.

Please take another look and let me know if I've broken anything or missed anything or if you have any suggestions for improvement.  Thanks.

Here's the test page: https://apps.wikitree.com/apps/beacall6/tree_apps/#name=Brahms-2&view=oneNameTrees .

(This one will load quickly.  After it loads, please put whatever surname you're interested in in the Name box and hit 'Go'.)

Answer 1

Great app!

Answer 2

That migration view is amazing, and then also the ability to filter by location fields is soooooo amazingly good to clean up all the location fields (greetings from the Holy Roman Empire!)

Comments

When you say 'we' need to work on them, do you mean WT in general or do I need to work on that for the app (or both)?

---

I was just thinking how nice it would be to be able to create a file of correct locations (and dates) and match it against the generated list of locations (and dates) and identify where there are discrepancies.

---

I found a way to actually work on improving the locations, thanks to your app. This is A-M-A-Z-I-N-G!!!! Thank you!

---

Oh my god, this is even better! I can also see if a migration category is associated to the migrants...!

---

Tommy: Don't the DD Suggestions do something like that?

---

Ian, if it does, is that info that can be read and the locations highlighted in this app of a possible issue?

---

In order to do some of the things related to locations in the app, I needed to standardise locations to an extent and to identify which places should have 'United States' or 'United Kingdom' at the end and which shouldn't (depending on the birth date).  So... I've just added a button to help you (hopefully).  Now, if you go to the table view and click the 'Check Locations' button, it will highlight birth locations that the code has identified as non-standard.  This includes things like a missing 'United States', 'USA' instead of United States, missing commas, etc.  I can't promise that it will all be right, but if you hover over or click the highlighted birth locations, you can see what the code standardised the location to.  I hope this helps.

---

The "Checks Location" option is flagging most entries when in the 'Reverse Location' mode.

It's flagging 'Berks County, Pennsylvania' as 'Berkshire County, Pennsylvania'.

---

Ah! Good point.  I'll fix that. 

Edit:  The reverse location thing should be OK now.

---

I just tried it again and it is still flagging all the entries in the 'Reverse Location' mode.

Is there a version number somewhere that I can check to see which version of the app I am using?

---

No.              .

---

Is Check Locations only checking the "Birth" locations?

I see a couple of "USA" locations in the Death Place column that is not highlighted.

---

I did mention above that I've only done this for birth locations. Maybe I'll expand it.

---

I've added the checks for the death locations.  Again, though, I make no promises about how correct they are.  I think the ones for the UK and the US are quite good.