How to use Entity tree
The search field allows the input of Q-numbers and of Item Labels. If their are several Qs under the same label you will get the full selection with the descriptions to pick the right one.
The display's language can be changed at settings. The search can be defined through the pull down menu at the end of the input box - you will get here a selection of all the properties available on the item, which is quite cool as it offers you the opportunity to look at all kinds of genealogies, or, to be more precise, to look at all kinds of relations in a genealogical display.
Regular Family trees into both directions
The optimal search comes with the personal name and the "child(ren)" selection. You start with a display like this one for Friedrich Wilhelm Jacobs (Q97935) and you use the ˄ and ˅ signs to expand into the past or towards the present until there are no further options given. This will be the final result in our case (as of Oct 6 2021): this pedigree The links are uniform, you can create the standard start with any link like https://www.entitree.com/factgrid/en/Child(ren)/Q97935 - the link ends with the Q-nummber.
The program allows you to grab the entire image which you have created for your purpose with the link (use tinyurl if you need a shorter link).
Adding dimensions (for the wish list)
The case of Friedrich Wilhelm Jacobs (Q97935) is interesting as we can compare it with a hand made construct that was designed to show a particular network - here of two families in the publishing business.
The option to show all children is nice in the two standard visualisation of pedigrees - into the past, where each generation will ideally double the last with both parents added to the entire last line, but it does not allow to create particular networks, e.g. with a look at spouses and their relatives.
- One would love to be able to add wifes/husbands wherever one feels like it and one would love to be able to expand into the past and future on every person (where the information is available). Right now your presentation is deleted if you want to add options in the pull down menue. --Olaf Simons (talk) 17:50, 6 October 2021 (CEST)
- A cool feature could be a special query: you have two people and you want to know how they are related to each other. --Olaf Simons (talk) 17:52, 6 October 2021 (CEST)
Identity recognition (wish list)
Jesus of Nazareth, son of Joseph and Mary (Q1477) is known for his two competing lines of fathers stated with different successive statements in Matthew 1:16 ff and Luke 3:23 ff. Both lines diverge but also share protagonists every now and then. Here the complete picture:
- the picture extended from Jesus down to God (or rather down to the 17 Gods of the Abrahamitic religions)
- just the beginning of the same picture from God downwards, where Adam and Eve are immediately creating two different lines as the software dies not accept any inbreeding.
The software should be able to detect identical Qs and any individual entity should exist only once on a display.
- I agree, but the question is how to connect them with each other (gets even more difficult when they are on different levels). I made an issue. Martin Schibel (talk) 23:29, 7 October 2021 (CEST)
Stemmata and filial organisations
It is a bright feature that one can use the application just as well on all other statements, though it is not always useful (as in the case of "married to" statements - they create a weird data representation as we have here the mirroring a reciprocal statements Mary of Nazareth.
The feature is, however, a great step on our stemma upwards ("Preceding in stemma) property Property:P233. This particular property is used on everything that is produced with to link to its models and precursors. A good example is here the publishing history of Daniel DeFoe's Robinson Crusoe. The first edition came out on April 25 1719. The first vol. went through 6 editions, 3 piracies and a newspaper edition till 1722. DeFoe increased his income with two sequels appearing in 1719 and 1720 and going into their own editions. Translations into French, Dutch and German began to appear in 1720 - this is the series in a table. One would like to have this in a genealogy, and it is not that easy
The [visualisation we can get so far] ist not exactly show the dependencies.
- Sometimes an edition has two stemma upwards connections: Volume 2 of the Newspaper edition is both a continuation of volume 1 this very newspaper series and a reprint of the new volume 2 as it has appeared. It is extremely important here that an object exists only once in the visualisation.
- It would bee cool to add the Property:P234 qualifiers that detail the dependency.
- The entire visualisation should be upside down. Stemma upwards means getting back in time, with the oldest artefact on top.
Add missing image
so the message on each item. Our images are on Property:P189.