Database are characterized by a unique identifier (URI), a name, some notes and a set of properties. The database unique identifier must uniquely identify the database amongs all the registered ones on eviple website. Only one database with the same URI can be open in the application at a time. The best way to insure identifier uniqueness, is to give it a prefix that is specific to the database author. For instance, I use prefix http://www.eviple.com for all the databases created by me. URI is set throught the "URI" property. The URL is a readonly attribute that gives the database location. The name and notes can be defined for each language. They are displayed according to the current language selected in the application. The name is used to display the database in the tree view. |
| Property Name | Description | Read only |
|---|---|---|
| URI | Database unique identifier. | false |
| URL | Database URL (location). | true |
| Author | Name of the author. | false |
| Charset | Charset used to encode the file (UTF-8). | true |
| Copyright | Copyright notice. | false |
| Cover | URL of a picture that illustrate the content of the database. | false |
| Creation date | Creation date of the database. | true |
| last modification date | Last modification date of the database. | true |
| format | Database format and version (GED,IHX). | true |
| Writer version | Version of IN-HEH application that saved the database. | true |
| Source | Free text that gives the sources of the database. | false |
| Status | Status (draft,stable). | false |
| Version | Database version. | false |
IHX format is the native IN-HEH proprietary xml format that allows to store and share your work.
IN-HEH application supports a large part of the GEDCOM 5.5 standard. GEDCOM file 5.5 can be open and modified in the application. With saving database in GEDCOM you must take care that not all the possibilities of IN-HEH Timeline can be saved in that standard. For instance event hierarchy or multi-language naming. For that reason, you may lost data by saving IHX work to GEDCOM format.
Multi-language event naming is not supported by GEDCOM. The read events are created with name for the selected display language. Especially, birth and death events are created with translation corresponding to this language (if translation is not available, english is used by default).
GEDCOM structured person names (using slash separators) are maintained in IN-HEH Timeline but the slashes are hidden when displayed in views. Slashes can be edited in object properties dialog.
The feature allows to display the list of events matching a given sub-class value. The list is ordered by date of the matching events. E.g. Display list of US presidents by chronological order like in this page. List of event is displayed on embedded web view.
That display can be triggered from database folders popup menu of the tree view. Select choosen sub-class from "Display Filtered Content" menu. Only the database used classifications are proposed to user.
Contact: postmaster@in-heh.com
Copyright © 2007-2010 IN-HEH Ch.Pardon
