Data-Structure

This is the page explaining the used data and "indexes", the old 1. version (partly german) is data-structure-1
Here are the collection of all entities , which can be found on this genealogy tree-database.

1. Person

  • Persons (per:_template) autonumbered!
    • Title = "First-Name Last-Name (YYYY-YYYY)" ("Speeking Name" + ("birth-Year"-"death-year"))
    • Personal-data
      • Gender:
        • male
        • female
      • title of person (textfiled)
      • First name ( text)
      • last-name (=Family !) "perpage" category field - first search if exist, ort "create new"
      • birth-name (=mothers name!) "perpage" category field - first search if exist, or "create new"
      • Birth-data
        • birth-day (DD) "perpage" category field - first search if exist, or "create new"
        • birth-month (MM) "perpage" category field - first search if exist, or "create new"
        • birth-year (YYY) "perpage" category field - first search if exist, or "create new"
        • birth-church (Pfarre) "perpage" category field - first search if exist, or "create new"
        • birth-city(Stadt) "perpage" category field - first search if exist, or "create new"
        • birth-district (Bezirk) "perpage" category field - first search if exist, or "create new"
        • birth-county(area,BL) "perpage" category field - first search if exist, or "create new"
        • birth-state(Land) "perpage" category field - first search if exist, or "create new"
      • relations to parents: ( also over hidden tag _pper:##)
        • father (per:id) "perpage" category field - first search if exist, or "create new"
        • mother (per:id) "perpage" category field - first search if exist, or "create new"
      • Death-data
        • death-day (DD) "perpage" category field - first search if exist, or "create new"
        • death-month (MM) "perpage" category field - first search if exist, or "create new"
        • death-year (YYY) "perpage" category field - first search if exist, or "create new"
        • death-church (Pfarre) "perpage" category field - first search if exist, or "create new"
        • death-city(Stadt) "perpage" category field - first search if exist, or "create new"
        • death-district (Bezirk) "perpage" category field - first search if exist, or "create new"
        • death-county(area,BL) "perpage" category field - first search if exist, or "create new"
        • death-state(Land) "perpage" category field - first search if exist, or "create new"
      • comments ( text)
      • Avatar-page-link (txtfield with link to image)

2. Event of person

  • Event of person ( per-occu:_template ) child of per:id !)
    • Title => "YYYY-MM-DD" (sorted ascending later!)
    • belongs-to-person (per:id) "perpage" category field - first search if exist, or "create new"
    • Description of Event (free textfield)

3. Image-ext of person

  • Image-ext of Persons (image-ext:_template autonumbered!
    • Title => "YYYY-MM-DD" (sorted ascending later!)
    • belongs-to-person (per:id) "perpage" category field - first search if exist, or "create new"
    • image-link: (textfield/link) example: http://upload.wikimedia.org/wikipedia/commons/f/f5/Einstein_1921_portrait2.jpg
    • Heading: txt (example: "Albert Einstein 1921"
    • Caption: txt (example: "From Wikipedia, the free encyclopedia")
    • Date: YYYY-MM-DD (1921)
    • Author: txt (example "Ferdinand Schmutzer (1870–1928)")
    • Permission: selective field ( ("Public Domain)
    • Your comment(free textfield)

4. Family

  • Family fam:_template autonumbering!
    • Title = Name(pers1) - Name(pers2) ("speeking name" - "Sprechender Name"!)
    • persons
      • Person 1 ( per:id - "perpage" category field - first search if exist, or "create new"
      • Person 2 ( per:id - "perpage" category field - first search if exist, or "create new"
      • Marriage-data (Partnerschafts-Anfang,Eheschließung, WG,)
        • marriage-day (DD) "perpage" category field - first search if exist, or "create new"
        • marriage-month (MM) "perpage" category field - first search if exist, or "create new"
        • marriage-year (YYY) "perpage" category field - first search if exist, or "create new"
        • marriage-church (Pfarre) "perpage" category field - first search if exist, or "create new"
        • marriage-city(Stadt) "perpage" category field - first search if exist, or "create new"
        • marriage-district (Bezirk) "perpage" category field - first search if exist, or "create new"
        • marriage-county(area,BL) "perpage" category field - first search if exist, or "create new"
        • marriage-state(Land) "perpage" category field - first search if exist, or "create new"
      • Divorce-data (Partnerschafts-Ende,Scheidung, Trennung,)
        • Divorce-day (DD) "perpage" category field - first search if exist, or "create new"
        • Divorce-month (MM) "perpage" category field - first search if exist, or "create new"
        • Divorce-year (YYY) "perpage" category field - first search if exist, or "create new"
        • Divorce-church (Pfarre) "perpage" category field - first search if exist, or "create new"
        • Divorce-city(Stadt) "perpage" category field - first search if exist, or "create new"
        • Divorce-district (Bezirk) "perpage" category field - first search if exist, or "create new"
        • Divorce-county(area,BL) "perpage" category field - first search if exist, or "create new"
        • Divorce-state(Land) "perpage" category field - first search if exist, or "create new"
      • Comment ( textfield)

5. Ebent of family

  • Event of family ( fam-occu:_template ) child of fam:id !)
    • Title => "YYYY-MM-DD" (sorted ascending later!)
    • belongs-to-family (fam:id) "perpage" category field - first search if exist, or "create new"
    • Description of Event (free textfield)

6. Indexes

all used additional tags are "hidden" tags ( _per:##)

  • Every person has:
    • one "_p" + ### tag ( his own id !) ( to exclude in listpages)
    • one or more "_pp"+ ### tags - the ids of the parents! ( to exclude in listpages)
  • Every family has:
    • one or more "_p" + ### tag ( his own partners !) ( to exclude in listpages)
    • one "_fam"+ ### tags - his own id ( to exclude in listpages)

7. IFtags-Settags Technick

as Rob has written ( see http://community.wikidot.com/forum/t-419308/target-a-single-piece-of-data-form-info#post-1320497 ):

  • use the button settags to tag by an automated predefined button on the dataform:_template the missing tag(s) for such fields(data, images) - or use the %%fullname%% of the page to set the tags
  • use on the target page (where the "data" from this page is missed and to be inserted a litle listpages module - only searchng by this _%%form_raw{field}%% tag , or %%fullname%% or whatever you plan for this second unique index to find the page ).
At the moment there are 3 tags settings on the right column ov every person template - for the own id and the parents.
And on the family template the same with the two tags of partners and the own id.
This tag-settings is red if not yet done!
[iftags -_%%form_raw{field}%% ]]
**##red|Open## to tag with _%%form_raw{field}%%!**

[[button set-tags +_%%form_raw{field}%% text="set tag +_%%form_raw{field}%%"]]

[[/iftags]]

or tagging with the page-name itself ( Ubnique index! )

[iftags -_%%fullname%% ]]
**##red|Open## to tag with _%%fullname%%!**

[[button set-tags +_%%fullname%% text="set tag +_%%fullname%%"]]

[[/iftags]]

Issues with wikidot

Problem of Backup looses

With the standard backup of Wikidot there is the loss of all tags and parenting information today. (and forum posts)

Every index of hidden tags is lost. This is dangerous if a page ( like "Event" page with category "occu:" is hanging on its parent only with hidden tag "_%%fullname%%" ( of the parent) and the parenting itself.
if both is lost than every information is lost to which data page ( per, fam. a.s.o) the event belongs
This is not a problem with the dataform pages - where the parents (father, motherin per: or partners /in fam:) or relations are stored in dataform fields.

Since in the Listpages dataform fields can be searched for exact match all this is usefull and the backup usefull.

As long as in Listpages a specific page is hanging only with tags of parenting on another page - this is dangerous!

Example "events"

What at the moment exists is a simple text page - created with the autmatic parenting and tagging the "children" event with the %%fullname%% of the parent-page.
What I need is the automatic creation of a dataform field (= "parent") with the inserted %%fullname%% of the parent page and than I can search for events by using this dataform page and not using the tagging.

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