Genealogy - Template

Included page "clone:genealogy-template" does not exist (create it now)

A) What is genealogy ?

Have a look on the famous wikipedia article Genealogy and (my favorite) Family Tree.

For the beginning I implement more or les a simple application for "Family Tree".

B) Family-Tree

Family_Tree_Sample.jpg

One of the outcome is not only the database-like wiki structure to surf through all the "family" and "persons" pages, but also a "familiy-tree" like presentation - see right side the JFK Family tree back to the grand-parents.
This wiki works in the same manner and deepness - from a given person on obne page showing her/his parents and grand parents.

Family_tree.svg

On the other side - the children - this wiki shows for a given person all her/his partner&families and all the "direct" children on the same page like this "Descendent-Tree" on the left side. This example shows only the direct descendets of one person.

All this is possible with this wiki… here is an example how a person on this wiki (Albert Einstein (1879-1955) ) looks on his page (with the Details "hidden"!):

Einstein_image_2.jpg

C) How is this done?

1. Datatruktur

is like a database and explained on Data-structure.

2. Documents- overview

_default ( see also page-categories on top menu)

There are some Control reports and Galleries existent for easier upload or usage of external and internernal images on this wiki

3. Database content

All examples are taken from Einsteins family: http://en.wikipedia.org/wiki/Einstein and http://en.wikipedia.org/wiki/Hermann_Einstein

3.1 Person

Every person is setup on a "per:##..##" page in the (autonumbered) category "per:" . Using the dataform-technic the hidden per:_template holds all the layout and the dataform fields; like

  • a free, speeking title which is important to hold the persons-name and dates (a.e.: "Albert Einstein (1879-1955)" later used to sort ascending the existing persons of a "family")
  • father-id (page name (id)of father - selected over pagepath tree from existing persons)
  • mother-id (page name (id) of mother - selected over pagepath tree from existing persons)
  • Names ( first (sur), family(last), birth ( maiden)
  • dates of birth and death
  • places of birth and death ( 5x! ..church, city, district,.country, state)

Important Note: All relevant links/Joins to another persons (like father & mother) are stored inside the person pages as pagepath fields - this means if you want to select in the selection list a father or mother to store it in the relevant "father-id/mother-id" fields , than these persons MUST Exists before you can select them. On the start of your input-seesion to create some person pages you will have some "open fields" for later edit - becaus of at the start there are not yet any father or mother setup.
The goodies of such "father/mother-id's" inside a page is the fact that "tags with their page-id's" are not really neccessary. All ListPages reading the database can now read page(s) by a field-content ! ( all children of my own are searched and found with the selection of "… _father-id="%%fullname%%" - where fullname euqals the person page-(id) of the page I am looking at the moment..

3.2. Family&Partners

Every family&partner(ship) is setup on a "fam:##..##" page in the (autonumbered) category "fam:". Using the dataform technic (like with the per: pages) the hidden fam:_template holds all the layout and the neccessary dataform fields like

  • a free , speeking title which is important to hold the family-name and dates (a.e.: "Albert Einstein und Mileva Marić"
  • person1-id (page name (id)of person1 - selected over pagepath tree from existing persons)
  • person2-id (page name (id)of person2 - selected over pagepath tree from existing persons)
  • dates of marriage and devorce
  • places of marriage and devorce ( 5x! ..church, city, district,.country, state)

3.3 Events of person

Every Event of a person is stored and setup on a "per-occu:#..##" page in the (autonumbered) category "per-occu:". Using the dataformn technic (like with the per:pages) the hidden per-occu:_template holds the layout and dataform fields like

  • a free title in form of "YYYY-MM-DD" (what ever is existing) which is later used to sort ascending the existing events of a person
  • belongs-to-person (page name (=id)of person - selected over pagepath tree from existing persons)
  • per-occu-text (free wiki text )

These Events of one person are inserted after his personal data on the left side by searching with the dataform field _belongs-to-person="%%fullname%%" ( which is the persons page-name/id ).
Therefore there are no tags neccessary
The parenting is build within the button "create/add an event to the person" - automatically to the persons page. This is not neccessary but usefull in case of a site map ( of a person).

3.4 Events of family

Every Event of a family&partnership is stored and setup on a "fam-occu:#..##" page in the (autonumbered) category "fam-occu:". Using the dataformn technic (like with the per:pages) the hidden fam-occu:_template holds the layout and dataform fields like

  • a free title in form of "YYYY-MM-DD" (what ever is existing) which is later used to sort ascending the existing events of a person
  • belongs-to-family (page name (=id)of family - selected over pagepath tree from existing families)
  • fam-occu-text (free wiki text )

These Events of one family are inserted after his personal data on the left side by searching with the dataform field _belongs-to-family="%%fullname%%" ( which is the family page-name/id ).
Therefore there are no tags neccessary
The parenting is build within the button "create/add an event to the family" - automatically to the dfamily page. This is not neccessary but usefull in case of a site map ( of a family).

3.5. Images of person

Every (later on their pages automatically inserted) image of a person is taken from the "gallery with external images" .
My idea is the usage of "data form" pages of category "image-ext:" with autonumbering of the pages.
This pages have (using the "image-ext:_template" page) as content only the:

  • "belongs-to-person" (per: pagepath Link to genealogy-person! )
  • URL of the images,
  • Heading
  • Caption
  • Copyright notices
  • Author
  • Date ( of creation)
  • Descritpions
  • a button to add new external images
  • a tagcloud of all tags of the same category

3.5. Avatar-Images of person

new version:

Every person page ( ("per:…" ) has one standard named file "avatar.jpg" attched - to reach and read this image with the standard name /pagename/avatar.jpg" . This makes it easier to insert at any level the attached image.
Using variablles like

  • /%%fullname%%/avatar.jgp ( on the pages itself insode _template or ListPages ) or
  • /%%form_raw{father-id}%%/avatar.jpg"
  • /%%form_raw{mother-id}%%/avatar.jpg"

old version :

This is more the place-holder of the image at the moment - to have defined a clear definition which image is the avatar-holder:

Every (later automatically inserted) image of a person is taken from the "Gallery With Avatar Images".
My idea is the usage of "data form" pages of category "avatar:" with autonumbering of the pages.
This pages have (using the "avatar:_template" page) as content only the:

  • "belongs-to-person" (per: pagepath Link to genealogy-person! )
    • File-name of the images (type=file),
    • Heading
    • Caption
    • Copyright notices
    • Author
    • Date ( of creation)
    • Descritpions
    • a button to add a new Avatar-image
    • a tagcloud of all tags of the same category

Regards
Helmut

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License