Gramps - User contributions [en]

Improving picture quality

2008-04-04T01:00:38Z

Sgpsaros: typo

{{languages}}

While researching your family tree, you will come along old sources that need careful handling. Pictures from these taking in an archive are often not optimal, and need cleaning up to make the text readable. Some pictures are snapshots of microfilm screenreaders.

Here we show how you can work on your picture to make the text come out better, improving readability. All with open source software, off course!

[[Category:Genealogy]]

== The sample picture 1==
[[Image:unclean_picture_example1.jpeg|thumb]]
The sample picture is a raw jpeg picture of 1.5Mb taken from a microfilm screenreader. The screenreader light is centered in the middle, getting darker at the edges as is common with these readers. The relevant section wanted has been placed in the centre of the screen, and a picture has been taken with a digital camera.

=== Viewing ===
A good application to view these files is ''Gwenview'' (KDE).

=== Cleaning 1: obtaining a nicer picture with GIMP===
==== Step 1 ====
To edit it, [http://www.gimp.org The Gimp] comes to the rescue.
# Open the file.
# Select the relevant portion with the <code>rectangular select tool</code>. Copy and paste into a new canvas: type respectively, CTRL+C, CTRL+N + click OK, CTRL+V
# Save the file in the GIMP xcf format

==== Step 2 ====
In Gimp, the Filters menu has the correctly named 'Enhance' submenu.
# Choose <code>2x2 Contrast Enhance</code>
# Select the <code>Destripe</code> option, and set the value to 50.
# Now, in the ''Tools menu'', go to the ''Colour Tools'' submenu, and choose ''Curves''. You can now play with the curve level to get a better contrast on the picture. <br />[[Image:adjust_colour_curve_example1.png]]<br /> We see here that the picture lacks in white and in black, but has a second peak of darkgrey pixels. We enhance the white to make the contrast larger, and we downgrade the importance of the darkgrey peak. We also cut out completely the black.
# As a last edit, select the centre highlighted region of the picture with the elliptic selection tool, and select in ''Tools menu--> Colour Tools'' the ''Brightness-contrast'' option, and reduce the brightness.

Now, save the result as png with maximum compression level.
The result:

[[Image:Unclean_picture_example1_step2.png|500px]]

=== Cleaning 2: Aiming for readability: Black and white with Digikam and Gimp ===
==== Step 1: Crop and auto-correction ====
[[Image:Unclean_picture_example1_digikam1.jpg|thumb|Step 1]]

Open the jpeg file with [http://www.digikam.org Digikam]. Via the crop tool you cut out the relevant section of the picture. Next you go in the ''Fix->Colors'' menu, and select ''Auto-correction''.

Choose as type: ''Equalise''

==== Step 2: brightness contrast improvement with GIMP ====
[[Image:Unclean_picture_example1_digikam2_gimp.jpg|thumb|Step 2]]
Digikam only allows brightness correction on the entire picture, so right-click on the picture of step 1, and open it with GIMP. In Gimp, we will make a rectangular selection of the different regions: left, center, right and bottom, and we adjust brightness/contrast separately via ''Tools menu--> Colour Tools'' then ''Brightness-contrast''

Note the vertical lines we introduced by this between the regions with changed brightness.

==== Step 3: Border detection ====
Now, with GIMP we invoke select ''Filters'', suboption ''Borders'', and choose as method ''Difference of Gaussians''. As radius 1 we choose 100, and as radius 2 we choose 0. The checkboxes with ''Normalize'' and ''Inverse'' are checked. This will make the letters stand out more.

The result:

[[Image:Unclean_picture_example1_digikam3_gimp.jpg|500px]]

=== Some information about the source ===
The picture was taken with a digital camera from a microfilm on a screenreader.
The microfilm had ref. #0293844 and contains the Parochial Register of a village called Onze-Liev-Vrouw-Waver, which is situated near the town of Mechelen, Prov. of Antwerp, Belgium.The register covers the birth acts from the periode 1657 - 1683.

:<code>line 1 </code> Manuele Baptizatorum ab anno 1657
:<code>line 2 </code> usquad annum 1683

This particular act was dated the 2nd of July 1657 (folio #46)
=== What does it say? ===
The reason of editing the picture is to have a nice picture going with the source. However, in some cases, cleaning up is paramount to be able to read the source. Here this is not really the case, but reading might nevertheless be enhanced by the sharper contrast.

Once you decipher how this priest writes ''B'' and ''P'' and ''s'', reading becomes possible.
The text of this source says:

:<code>line 1 </code> fac secunda Junij Baptiza-
:<code>line 2 </code> tus est petrus Leyns
:<code>line 3 </code> filius legitimus Guillielmus
:<code>line 4 </code> Leyns et Elisabetha op de
:<code>line 5 </code> Beke. Susceptores fuerent
:<code>line 6 </code> petrus Arts et Catharina
:<code>line 7 </code> van de Voorde

which translates to:

''I baptized on June the second Petrus Leyns legitimate son of Guillielmus Leyns and Elisabetha Op de Beke. Godparents were petrus Arts and Catharina Van de Voorde.''

=== Some comments on the name ===
Starting from the early 1600 the name changed with the different interpretations of the priests. The name was recorded orally. Lens, Lensen, Lenssen(s), Lenz(e), Lentz, Lensch, Linsing(h), Lince(ns), Len(t)zen and Leyns(e) all refer to the same name. Earliest recording date back to 1326. It is a patronymic name: origin : Laurentius.
== Tutorials on the internet ==
If you have found a nice tutorial on the net, add it here.

The following are for cleaning with the aim of getting a better result, not to make it more readable.
*[http://www.gimpguru.org/AskTheGuru/G20040808/ Cleaning an old sepia picture]
*[http://www.holoweb.net/~liam/pictures/howto/clean-up-a-scan/ Cleaning a scan of an engraving]

Why residence event and not Address?

2008-04-04T00:34:41Z

Sgpsaros: added punctuation (period)

The discussion of how to enter addresses in GRAMPS pops up from time to time, especially with new users. Let's give some reasoning on why to use the residence event for genealogical research, and not address.
[[Category:Tutorials]]

== Definition ==
You find a definition of an address in [[GRAMPS_Glossary#A|Glossary]], as well as for [[GRAMPS_Glossary#P|Place]]. So the address is for mailing, while the place is to indicate a point on a map. Mailing is in general not very useful for deceased people, the main focus of your research. So:

;What is an Address?:The GRAMPS concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there.

;What is a Place?:The GRAMPS concept of a Place is a particular location independent of time. Over time, the same Place may have different address information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. GRAMPS offers the ''alternate locations'' tab in the Place Editor, allowing to enter different address information of the place.

Apart from this, an ''event'' is important here: A defining moment in a person's life. Events can be coupled to places and are a central object in genealogy research, together with people, families and sources. They give a timeline on the life of a person, a timeline on which it is important to also indicate where a person lives.

== Why residence events ?==

So, what are the advantages of residence events then? Well:

# You can attach a place to it. This place will then be the effective address, with possible alternate locations (see the place dialog) indicating how eg this place is called today as opposed to when the event happened.
# You can share that place between people and families. With addresses there is no way to check if an address is already in your database - unless you remember it. That makes it unlikely to ''discover'' that two people actually lived at the same address. You can also filter on place city, eg give me all residence events that are in a place with city ''Berlin''.
# Hence, you can search places and see not just what happened in a certain city, but also who lived (resided) there. That's also not possible using the 'address' system. This is a timeline of a place with all events that happened there.
# On a timeline of a person you can see the event and infer details, eg a person marries before or after moving to a new house.
# Using a place for the address allows you to use this place for other events. Eg suppose Jim marries at home, then the Marriage event can be linked to the place indicating his home, just like the Residence event does.
# Just like the address field, events have full time control, so time spans and periods can be used and are recognized for reports.

What is a disadvantage:
# For a change in streetname, the address changes but the position on the map is the same. GRAMPS allows you to store this information in an alternate location, but alternate location has no date span, so you cannot indicate during which time frame an address for a place was in use.

Note that some researchers on the mailing list have expressed they like to store address changes in notes connected to a place, instead of in the alternate location tab. This because in general notes are exported to GEDCOM correctly and understood in other programs you might want to use the information.

It is important to note that you could use the Location event also, or make a custom event with a naming that suits you more.

== Try it out ==

There is no real correct method of storing addresses in GRAMPS. Try out the two methods, and use what works for you.

== Import/Export ==
Note the following:
* Address is not always well supported in other genealogy applications.
* Alternate location of place used in GRAMPS is not present in many other applications. You might consider recording this in notes instead.
* Events are supported by all programs you use, as is the default place location.

Why residence event and not Address?

2008-04-04T00:29:27Z

Sgpsaros: added punctuation (period)

The discussion of how to enter addresses in GRAMPS pops up from time to time, especially with new users. Let's give some reasoning on why to use the residence event for genealogical research, and not address.
[[Category:Tutorials]]

== Definition ==
You find a definition of an address in [[GRAMPS_Glossary#A|Glossary]], as well as for [[GRAMPS_Glossary#P|Place]]. So the address is for mailing, while the place is to indicate a point on a map. Mailing is in general not very useful for deceased people, the main focus of your research. So:

;What is an Address?:The GRAMPS concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there.

;What is a Place?:The GRAMPS concept of a Place is a particular location independent of time. Over time, the same Place may have different address information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. GRAMPS offers the ''alternate locations'' tab in the Place Editor, allowing to enter different address information of the place.

Apart from this, an ''event'' is important here: A defining moment in a person's life. Events can be coupled to places and are a central object in genealogy research, together with people, families and sources. They give a timeline on the life of a person, a timeline on which it is important to also indicate where a person lives.

== Why residence events ?==

So, what are the advantages of residence events then? Well:

# You can attach a place to it. This place will then be the effective address, with possible alternate locations (see the place dialog) indicating how eg this place is called today as opposed to when the event happened.
# You can share that place between people and families. With addresses there is no way to check if an address is already in your database - unless you remember it. That makes it unlikely to ''discover'' that two people actually lived at the same address. You can also filter on place city, eg give me all residence events that are in a place with city ''Berlin''
# Hence, you can search places and see not just what happened in a certain city, but also who lived (resided) there. That's also not possible using the 'address' system. This is a timeline of a place with all events that happened there.
# On a timeline of a person you can see the event and infer details, eg a person marries before or after moving to a new house.
# Using a place for the address allows you to use this place for other events. Eg suppose Jim marries at home, then the Marriage event can be linked to the place indicating his home, just like the Residence event does.
# Just like the address field, events have full time control, so time spans and periods can be used and are recognized for reports.

What is a disadvantage:
# For a change in streetname, the address changes but the position on the map is the same. GRAMPS allows you to store this information in an alternate location, but alternate location has no date span, so you cannot indicate during which time frame an address for a place was in use.

Note that some researchers on the mailing list have expressed they like to store address changes in notes connected to a place, instead of in the alternate location tab. This because in general notes are exported to GEDCOM correctly and understood in other programs you might want to use the information.

It is important to note that you could use the Location event also, or make a custom event with a naming that suits you more.

== Try it out ==

There is no real correct method of storing addresses in GRAMPS. Try out the two methods, and use what works for you.

== Import/Export ==
Note the following:
* Address is not always well supported in other genealogy applications.
* Alternate location of place used in GRAMPS is not present in many other applications. You might consider recording this in notes instead.
* Events are supported by all programs you use, as is the default place location.

Why residence event and not Address?

2008-04-04T00:07:59Z

Sgpsaros:

The discussion of how to enter addresses in GRAMPS pops up from time to time, especially with new users. Let's give some reasoning on why to use the residence event for genealogical research, and not address.
[[Category:Tutorials]]

== Definition ==
You find a definition of an address in [[GRAMPS_Glossary#A|Glossary]], as well as for [[GRAMPS_Glossary#P|Place]]. So the address is for mailing, while the place is to indicate a point on a map. Mailing is in general not very useful for deceased people, the main focus of your research. So:

;What is an Address?:The GRAMPS concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there.

;What is a Place?:The GRAMPS concept of a Place is a particular location independent of time. Over time, the same Place may have different address information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. GRAMPS offers the ''alternate locations'' tab in the Place Editor, allowing to enter different address information of the place.

Apart from this, an ''event'' is important here: A defining moment in a person's life. Events can be coupled to places and are a central object in genealogy research, together with people, families and sources. They give a timeline on the life of a person, a timeline on which it is important to also indicate where a person lives.

== Why residence events ?==

So, what are the advantages of residence events then? Well:

# You can attach a place to it. This place will then be the effective address, with possible alternate locations (see the place dialog) indicating how eg this place is called today as opposed to when the event happened.
# You can share that place between people and families. With addresses there is no way to check if an address is already in your database - unless you remember it. That makes it unlikely to ''discover'' that two people actually lived at the same address. You can also filter on place city, eg give me all residence events that are in a place with city ''Berlin''
# Hence, you can search places and see not just what happened in a certain city, but also who lived (resided) there. That's also not possible using the 'address' system. This is a timeline of a place with all events that happened there.
# On a timeline of a person you can see the event and infer details, eg a person marries before or after moving to a new house.
# Using a place for the address allows you to use this place for other events. Eg suppose Jim marries at home, then the Marriage event can be linked to the place indicating his home, just like the Residence event does.
# Just like the address field, events have full time control, so time spans and periods can be used and are recognized for reports.

What is a disadvantage:
# For a change in streetname, the address changes but the position on the map is the same. GRAMPS allows you to store this information in an alternate location, but alternate location has no date span, so you cannot indicate during which time frame an address for a place was in use.

Note that some researchers on the mailing list have expressed they like to store address changes in notes connected to a place, instead of in the alternate location tab. This because in general notes are exported to GEDCOM correctly and understood in other programs you might want to use the information

It is important to note that you could use the Location event also, or make a custom event with a naming that suits you more.

== Try it out ==

There is no real correct method of storing addresses in GRAMPS. Try out the two methods, and use what works for you.

== Import/Export ==
Note the following:
* Address is not always well supported in other genealogy applications.
* Alternate location of place used in GRAMPS is not present in many other applications. You might consider recording this in notes instead.
* Events are supported by all programs you use, as is the default place location.

Features

2008-02-27T04:40:48Z

Sgpsaros: Typo Correction

{{cleanup}}
[[Category:Documentation]]
==Features of GRAMPS 2.2==
* Easy to use. A well designed user interface makes entering data easy. Browser like controls allow you to navigate your family tree with ease.
* Nine different views for navigating your family:
{|cellspacing="0" border="1" align="center" width="95%"
|- valign="top"
|style="padding: 0.3em;" |'''People''' — A list of all individuals in the database. Filter the display using preset filters or a custom filter.[[Image:Mainwin.png|center|thumb|300px]]
|style="padding: 0.3em;" |'''Relationship''' — Display a family of parents, grandparents and children with the birth/death dates and relationships. Navigate to nearby relatives with a single click.[[Image:Relationship 2 2.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Family list''' — List all families in a single view. Double-click on each to edit, add notes, and to see parents and children in each family.[[Image:Family_List.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Pedigree''' — Display the family in the traditional pedigree view. Hold the mouse over individuals to see more information about them and to move to more distant parts of the tree[[Image:Pedigree.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Events'''[[Image:Events.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Sources''' — See all referenced sources in a single view. Double-click on each to edit, add notes, and to see which individuals reference the source.
|- valign="top"
|style="padding: 0.3em;"|'''Places''' — View all places referred to in the database and sort the list by half a dozen headings such as City, County or State.
|style="padding: 0.3em;"|'''Media''' — List all forms of media referenced by the database. Can be graphic images, videos, sound clips, spreadsheets, documents, etc.
|- valign="top"
|style="padding: 0.3em;"|'''Repository''' — List all source repositories in a single view. Double-click on each to edit, add notes, and to see which sources reference the repository.
|style="padding: 0.3em;"|
|}
* Bookmark favorite individuals for quick access. (The number able to be marked is unlimited)
* Custom filters. In addition to the numerous preset filters, create any number of selections based on interesting facts about your family to use for reports and data exports.
* Link any media or filetype to your GRAMPS family tree. Choose between copying or linking the file to the database.
* Privacy options allow restriction of any information marked with this option or information about living individuals. Data marked with this option can be excluded in reports and data exports.
* Multiple calendars and date ranges are supported. You can convert between Gregorian, Julian, Hebrew, French republican, Perzian and Islamic calendars from within GRAMPS via the Date selection window, and you can use fuzzy dates like about 1874, estimated 1905, ...
* Multiple languages and cultures support is mature.
** Translations exist for 15 languages (See the translations page)
** GRAMPS has been designed so that new translations can easily be added with little development effort. If you are interested in participating please contact us.
** Relationship calculators available in four languages
** Full unicode support. Characters for all languages are properly displayed.

==Reports==
Generate brief or detailed reports for the ancestors or descendants of an individual.

* Multiple styles of reports are currently available by default. Users can also create their own custom styles.
* Eight output formats are supported by GRAMPS: PDF, AbiWord, KWord, OpenOffice Writer, HTML, Rich Text Format (RTF), Latex, and plain text.
* Custom reports can be created by advanced users under the "plugin" system which allows the sharing of custom report styles between users.
* Book report allows the user to collect a variety of reports in a single document, which in turn is easier to distribute.

Charts and Graphs - Create graphical Ancestor and Descendent charts in several formats.
[[Image:RelationshipChartDescendants.png|right|thumb|200px|An example chart]]

* Box and Fan charts are available, see eg [[Howto: Make a relationship chart | here]].
* Multiple formats are supported by GRAMPS for charts and graphs: OpenOffice Draw, PDF, PostScript, and SVG.
* Custom charts can be created by users. We hope to add more in the near future through the contributions of users and developers.

Export to Web Pages -Select the entire database, family lines or selected individuals to a collection of web pages ready for upload to the World Wide Web.

==Tools==
A rich set of tools includes operations such as checking database for errors and consistency, as well as the research and analysis tools such as event comparison, duplicate people finding, interactive descendant browser, and others.

* Merge. Combine two seperate people into one. Very useful combining two databases with overlapping people.
* Soundex generator. Generate the standard codes commonly used in genealogy to compare similar sounding names even though spelled differently.

==File formats==
Import/Export support for serveral different formats.

* GEDCOM import and export. Extensive support for the industry standard GEDCOM version 5.5 so you can exchange GRAMPS information to and from users of most other genealogy programs.
* GRAMPS package import and export. A compressed file containing your family tree data and any other files used. Useful for backup or sharing with other GRAMPS users.
* Export to CD Burner. Export data and media directly to the GNOME file manager (Nautilus) for burning to CD.
* Web Family Tree export. Web Family Tree (WFT) allows you to display your family tree online with only a single file, instead of many html files the web page report generates. See [http://www.simonward.com/cgi-bin/page.pl?family/tree their homepage] for more information.

==Community==

* Active community involvement. Many current GRAMPS users contribute reports, suggestions, and feedback to the developers through various public mailing lists. The program is only a few years old and already has wide capabilities and features.
* Active development effort. New versions already in testing use an advanced database design that guarantee very fast access to many thousands of entries in the database. Other new features are being designed and coordinated by several active developers. Many additional participants assist through the mailing lists. Group effort shapes and tests GRAMPS constantly improving functionality and usability.
* Portable. GRAMPS is written in a computer language called Python using GTK and GNOME libraries. While only well supported in certain Unix and Linux environments, these are multi-platform development libraries, meaning that GRAMPS can be ported to any platform the required libraries are ported to.
* Free Software/Open Source development model means GRAMPS can be extended by any programmer since all of the source code is freely available under its license.
* GRAMPS is freely distributable under the GPL!

== Checklist ==
{| {{Prettytable}} style="width:235px; font-size:90%;"
|-
| ''' '''
|bgcolor="#8DA7D6" style="line-height:2.25em;"|'''GRAMPS 2.2.9'''
|-
|bgcolor="lightgray"|Price
|style="color:red;" |Free
|-
|Open Source
|yes
|-
|style="color:blue;" colspan="2"| '''Views'''
|-
|bgcolor="lightgray"|Individual
|Yes
|-
|bgcolor="lightgray"|Family
|Yes
|-
|bgcolor="lightgray"|Pedigree
|Yes
|-
|bgcolor="lightgray"|Source
|Yes
|-
|bgcolor="lightgray"|Event
|Yes
|-
|bgcolor="lightgray"|Place
|Yes
|-
|bgcolor="lightgray"|Media
|Yes
|-
|bgcolor="lightgray"|Repository
|Yes
|-
|bgcolor="lightgray"|Notes
|No
|-
|style="color:blue;" colspan="2"| '''Chart Types'''
|-
|style="color:blue;" colspan="2"| '''Reports'''
|-
|bgcolor="lightgray"|Books
|Yes
|-
|bgcolor="lightgray"|Family Group Sheets
|Yes
|-
|bgcolor="lightgray"|Individual Summary
|Yes
|-
|bgcolor="lightgray"|Henry Numbering
| /
|-
|bgcolor="lightgray"| D'Aboville numbering
| /
|-
|bgcolor="lightgray"|Calendar
|Yes
|-
|style="color:blue;" colspan="2"| '''Database'''
|-
|bgcolor="lightgray"|Native Database
|Yes (Berkeley DB)
|-
|bgcolor="lightgray"|Unlimited Size
|Yes (tested upto 250.000 people)
|-
|bgcolor="lightgray"| Open multiple Databases at once
|No (works for viewing, not supported !!)
|-
|style="color:blue;" colspan="2"| '''Multimedia'''
|-
|bgcolor="lightgray"|Audio
|Yes
|-
|bgcolor="lightgray"|Video
|Yes
|-
|bgcolor="lightgray"|Images
|Yes
|-
|style="color:blue;" colspan="2"| '''Remote'''
|-
|bgcolor="lightgray"|Remote Access
|Yes (linux, over X connection)
|-
|bgcolor="lightgray"|Collaboration
|No
|-
|style="color:blue;" colspan="2"| '''International'''
|-
|bgcolor="lightgray"|Unicode
|Yes
|-
|bgcolor="lightgray"|Languages
|English, Czech, Danish, German, Esperanto, Spanish, Finnish, French, Hungarian, Italian, Lithuanian, Norwegian, Dutch, Brazilian Portuguese, Russian, Slovak, Swedish
|-
|style="color:blue;" colspan="2"| '''Compatibility'''
|-
|bgcolor="lightgray"|GEDCOM 5.5
|Import/Export
|-
|bgcolor="lightgray"|HTML
|Export
|-
|bgcolor="lightgray"|XML
|GRAMPS XML
|-
|bgcolor="lightgray"|Backup
|On Exit, import possible
|-
|style="color:blue;" colspan="2"| '''Platform'''
|-
|bgcolor="lightgray"|Linux
|yes
|-
|bgcolor="lightgray"|Windows
|Yes (limited support)
|-
|bgcolor="lightgray"|Mac
|yes (user compile/install)
|-
|bgcolor="lightgray"|BSD
|yes (user compile/install)
|-
|style="color:blue;" colspan="2"| '''Additional Features'''
|-
|bgcolor="lightgray"|Match/Merge
|yes
|-
|bgcolor="lightgray"|Multiple relationships (adoptive-foster)
|yes
|-
|bgcolor="lightgray"|Relationship calculator
|yes
|-
|bgcolor="lightgray"|Soundex calculator
|yes
|-
|bgcolor="lightgray"|Spell check in notes
|yes
|-
|bgcolor="lightgray"|3th party plugin infrastructure
|yes
|-
|bgcolor="lightgray"|Check for Program Update
|No
|}

Recover corrupted family tree

2008-02-26T03:27:40Z

Sgpsaros: Change in Letter Case and Punctuation

{{languages}}

An attempt to explain GRDB corruption, how to recover from it, and how to avoid it in the future.
[[Category:How do I...]]

==Why this corruption?==
By far, the leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.

What happens is that the grdb file needs its database environment -- a directory with log files, lock files, temp files, etc. The current stable gramps releases store the environment for each file, under a tree in a <code>~/.gramps/env</code> directory. If your grdb file is <code>/home/user/genealogy/MyData.grdb</code> then its environment is in the <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory.

So moving, copying, or renaming the file will copy the file's bytes, but not its environment. This is why the moved file appears corrupted.

==What do I do now?==
The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your <code>.gramps</code> directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.

===The environment still exists===
If you have environment directory for that file, copy it under the above gudelines.
;Example: You copied <code>/home/user/genealogy/MyData.grdb</code> to <code>/home/user/genealogy/backup/BackupData.grdb</code> and the new file is not working.
;Solution: Copy <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory into <code>/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb</code> and this should fix the problem.

===The environment is lost===
If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, or some such. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.

Basically, you just dump the grdb into a text file, then create a new grdb from that text file:
$ db4.4_dump BackupData.grdb > somefile.txt
$ db4.4_load newfile.grdb < somefile.txt
and then cross your heart and hope that <code>newfile.grdb</code> will open in GRAMPS.

==How to prevent corruption?==
While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.

What is possible though is to backup the data regularly. The backups should be in XML format (the <code>.gramps</code> format). XML is machine- and human-readable. It is completely self-sufficient. It is also small. The following are good practices of backups:
# Export to XML from time to time, especially after large edits.
# Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM, merging records, running tools that may heavily modify the data, etc.
# Export to XML before upgrading GRAMPS to a newer version. Apparently, export to XML with old version before you install the new one!
# Export to XML before upgrading your OS.

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML.

==Can you guys not solve this ? ==
Yes we can! In the next version (GRAMPS 3.0/4.0) this part will be completely reworked, see [[Database Formats#The Future - GRAMPS_3.0|here]].

Recover corrupted family tree

2008-02-26T03:24:03Z

Sgpsaros: Grammar and Typo

{{languages}}

An attempt to explain GRDB corruption, how to recover from it, and how to avoid it in the future.
[[Category:How do I...]]

==Why this corruption?==
By far, the leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.

What happens is that the grdb file needs its database environment -- a directory with log files, lock files, temp files, etc. The current stable gramps releases store the environment for each file, under a tree in a <code>~/.gramps/env</code> directory. If your grdb file is <code>/home/user/genealogy/MyData.grdb</code> then its environment is in the <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory.

So moving, copying, or renaming the file will copy the file's bytes, but not its environment. This is why the moved file appears corrupted.

==What do I do now?==
The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your <code>.gramps</code> directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.

===The environment still exists===
If you have environment directory for that file, copy it under the above gudelines.
;Example: You copied <code>/home/user/genealogy/MyData.grdb</code> to <code>/home/user/genealogy/backup/BackupData.grdb</code> and the new file is not working.
;Solution: Copy <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory into <code>/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb</code> and this should fix the problem.

===The environment is lost===
If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, or some such. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.

Basically, you just dump the grdb into a text file, then create a new grdb from that text file:
$ db4.4_dump BackupData.grdb > somefile.txt
$ db4.4_load newfile.grdb < somefile.txt
and then cross your heart and hope that <code>newfile.grdb</code> will open in GRAMPS.

==How to prevent corruption?==
While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.

What is possible though is to backup the data regularly. The backups should be in XML format (the <code>.gramps</code> format). XML is machine- and human-readable. It is completely self-sufficient. It is also small. The following are good practices of backups:
# Export to XML from time to time, especially after large edits.
# Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM; merging records; running tools that may heavily modify the data etc.
# Export to XML before upgrading gramps to a newer version. Apparently, export to XML with old version before you install the new one!
# Export to XML before upgrading your OS.

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML.

==Can you guys not solve this ? ==
Yes we can! In the next version (GRAMPS 3.0/4.0) this part will be completely reworked, see [[Database Formats#The Future - GRAMPS_3.0|here]].

Recover corrupted family tree

2008-02-26T03:21:58Z

Sgpsaros: Changed letter case and removed repeated word

{{languages}}

An attempt to explain GRDB corruption, how to recover from it, and how to avoid it in the future.
[[Category:How do I...]]

==Why this corruption?==
By far, the leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.

What happens is that the grdb file needs its database environment -- a directory with log files, lock files, temp files, etc. The current stable gramps releases store the environment for each file, under a tree in a <code>~/.gramps/env</code> directory. If your grdb file is <code>/home/user/genealogy/MyData.grdb</code> then its environment is in the <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory.

So moving, copying, or renaming the file will copy the file's bytes, but not its environment. This is why the moved file appears corrupted.

==What do I do now?==
The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your <code>.gramps</code> directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.

===The environment still exists===
If you have environment directory for that file, copy it under the above gudelines.
;Example: You copied <code>/home/user/genealogy/MyData.grdb</code> to <code>/home/user/genealogy/backup/BackupData.grdb</code> and the new file is not working.
;Solution: Copy <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory into <code>/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb</code> and this should fix the problem.

===The environment is lost===
If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, or some such. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.

Basically, you just dump the grdb into a text file, then create a new grdb from that text file:
$ db4.4_dump BackupData.grdb > somefile.txt
$ db4.4_load newfile.grdb < somefile.txt
and then cross your heart and hope that <code>newfile.grdb</code> will open in GRAMPS.

==How to prevent corruption?==
While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.

What is possible though is to backup the data regularly. The backups should be in XML format (the <code>.gramps</code> format). XML is machine- and human-readable. It is completely self-sufficient. It is also smalll. Following are the good practices of backups:
# Export to XML from time to time, especially after large edits.
# Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM; merging records; running tools that may heavily modify the data etc.
# Export to XML before upgrading gramps to a newer version. Apparently, export to XML with old version before you install the new one!
# Export to XML before upgrading your OS.

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML.

==Can you guys not solve this ? ==
Yes we can! In the next version (GRAMPS 3.0/4.0) this part will be completely reworked, see [[Database Formats#The Future - GRAMPS_3.0|here]].

Recover corrupted family tree

2008-02-26T03:19:27Z

Sgpsaros: Grammar and Typo

{{languages}}

An attempt to explain GRDB corruption, how to recover from it, and how to avoid it in the future.
[[Category:How do I...]]

==Why this corruption?==
By far, the leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.

What happens is that the grdb file needs its database environment -- a directory with log files, lock files, temp files, etc. The current stable gramps releases store the environment for each file, under a tree in a <code>~/.gramps/env</code> directory. If your grdb file is <code>/home/user/genealogy/MyData.grdb</code> then its environment is in the <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory.

So moving, copying, or renaming the file will copy the file's bytes, but not its environment. This is why the moved file appears corrupted.

==What do I do now?==
The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your <code>.gramps</code> directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.

===The environment still exists===
If you have environment directory for that file, copy it under the above gudelines.
;Example: You copied <code>/home/user/genealogy/MyData.grdb</code> to <code>/home/user/genealogy/backup/BackupData.grdb</code> and the new file is not working.
;Solution: Copy <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory into <code>/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb</code> and this should fix the problem.

===The environment is lost===
If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, or some such. Whatever they are called, there should be be a dump tool and a load tool, and they should be version 4 or later.

Basically, you just dump the grdb into a text file, then create a new grdb from that text file:
$ db4.4_dump BackupData.grdb > somefile.txt
$ db4.4_load newfile.grdb < somefile.txt
and then cross your heart and hope that <code>newfile.grdb</code> will open in gramps.

==How to prevent corruption?==
While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.

What is possible though is to backup the data regularly. The backups should be in XML format (the <code>.gramps</code> format). XML is machine- and human-readable. It is completely self-sufficient. It is also smalll. Following are the good practices of backups:
# Export to XML from time to time, especially after large edits.
# Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM; merging records; running tools that may heavily modify the data etc.
# Export to XML before upgrading gramps to a newer version. Apparently, export to XML with old version before you install the new one!
# Export to XML before upgrading your OS.

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML.

==Can you guys not solve this ? ==
Yes we can! In the next version (GRAMPS 3.0/4.0) this part will be completely reworked, see [[Database Formats#The Future - GRAMPS_3.0|here]].

Howto: Make a genealogy website with Gramps

2008-02-15T08:02:47Z

Sgpsaros: Grammar Correction

This is a Howto on how to make a genealogy website with GRAMPS 2.2.x. and the NarrativeWeb plugin.

The website will be made with the narrative website report, of which the interface is described at: [[Generating Web pages]]. The goal is to offer a complete howto/tutorial on using this report, from conception, to uploading your genealogical website to an internet service provider (ISP).

[[Category:Tutorials|Make a genealogy website with GRAMPS]]

== Before you start ==

You can easily generate from within GRAMPS a nice looking Web Site.

Before you start you should have an idea about the data you want to have on the website. If you are not careful, and generate a webpage from your complete database, the amount of generated files can be '''huge''', as well as taking up a lot of space.

==How to limit the amount of data==

If you have a large database, it is wise to start with a [[filter]] to limit the amount of persons: In the People view of GRAMPS, go to the View menu, and activate the Filter sidebar. Next, go to ''Edit menu--> Person Filter Editor'', and make a suitable filter. Read the [http://gramps-project.org/gramps-manual/2.2/en/ch03s10.html#tools-util-cfe help manual] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.

==Make a Home Page, Introduction Page, and more==
===What?===
Before you use the plugin ''NarrativeWeb'', you should make some custom pages with the information not yet in GRAMPS:
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Custom footnote: the footnote to appear on the site
* Custom header: a custom header to appear on the top of every page
* Publisher info: extra information on you, the publisher of the page, to appear on every page

Note that GRAMPS works with stylesheets, so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).

===How?===
Go to the Media View in GRAMPS, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.

If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' GRAMPS media object.

Tip: if you are experienced with style, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.

==Choosing the layout==

GRAMPS has some nice standard layout schemes. Those are kept in so-called cascading style sheets (.css files). In GRAMPS 2.2.x, six are supplied. You are free to edit these files (other lettertypes, other colours, ...).

Whatever the style you choose, after generation, it will default to the ''narrative.css'' file which will be placed in the dir you indicate. If you have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours, etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error.

Examples of the 6 styles:
*Modern - See example [http://familiemalengier.be/ Malengier]
*Business - TODO
*Certificate - TODO
*Antique - See example [http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project]
*Tranquil - TODO
*Sharp - TODO

If you make a nice custom style sheet, please share with other GRAMPS users. You can do this by adding a link to your webpage in the examples below and adding to your css file that its copyright is creative commons alike, or you can send it to the developers on: gramps-devel <at> lists.sourceforge.net

==Generate the pages==

In the Report menu, choose ''Web Page-->Narrative Web Site''.

Chose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.

In the Report Options Tab, set the filter you created. Choose a '''GOOD''' title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding to Unicode (only use other encoding if you have very specific reasons). Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). '''Think about copyright!''' Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graph. Try different settings for this.

In the Page Generation Tab, choose the internal notes you created, as related above. I suggest you suppress the GRAMPS ID, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if 1) your site can be VERY big, 2) you extensively use the private marker on sensitive data'''. Many people have burnt themselves with this option, publishing private email conversations they stored for research reasons in GRAMPS, on the net without realising.

The Privacy Tab is last, but '''is one of the most important settings''' . Take the habit never to include private data, and restrict the information on living people. I suggest you set the ''years to restrict from person's death'' to a '''minimum of 25 years'''! This will prevent grave mistakes having sour consequences. Many genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also take into account local legislation (very strict in eg Italy, France).

Now you just click ok and GRAMPS starts generating your web page : a lot of files and directories will be made, so this will take some time. But when it is completed you will be the proud owner of a complete structure ready to publish on the WWW.

==Regeneration of your site==
Every time you change your database you need to regenerate your site to see the changes. Although GRAMPS will regenerate the entire site, '''only the pages with changed data''' will be different. You therefore need not republish all the website to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See further.

'''Limitation''': If you upgrade GRAMPS, changes might have happened to the website generation, meaning all pages will have changed. Investigate this before you upgrade, and consider the benefits of upgrading against this possible drawback.

==Publishing==

Now you can publish your work on the web.

===Size and provider===
First, check the size of your web page. Go to the directory where you stored the web site, and in a modern file browser, right-click and select properties. This normally allows to calculate the directory size. Write down this info, and check your webhosting contract. Above a certain size, you will need to pay extra. Investigate before you burn yourself! If your site is too large, you can make a filter which produces a smaller website, or disable images, or split your site in pieces, and host it with different providers.

There are some free providers around: eg Lycos , but there are maybe better alternatives. Also GRAMPS offers '''free''' hosting of family website. Check out [[GRAMPS:Webhosting|webhosting by the GRAMPS project]].

===Transfer your files===
*[http://www.lyra.org/sitecopy/ sitecopy]: This is generally the best option. Only changed pages are uploaded to the server hosting your website. You can install sitecopy with every distribution via the package manager. Read the manual, it is self-explanatory: type in a console <code>man sitecopy</code> (or in konqueror type address <code>man:sitecopy</code>). Please, add a wiki page to [[sitecopy]] if you have experience and want to help new users.
*rsync : This is for advanced linux users. It is a better solution than sitecopy, but you need full access to the webhost, which normal users normally not have. Rsync only uploads the changes to a file, whereas sitecopy uploads the entire file.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awefull lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider to learn sitecopy!

== Examples of websites==
Feel free to add your with GRAMPS generated website here. Please, remove missing links if you encounter those. Style is one of the GRAMPS styles, or custom.

{|{{prettytable}} align="center"
|- bgcolor="#8DA7D6" align="center"
|'''Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[http://familiemalengier.be/ Malengier] ||Modern || Dutch
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|-
|[http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project] ||Antique || English || version 2.2.6
|}

== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. GRAMPS website generation belongs in this category.

Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [http://www.phpgedview.net/ PhpGedview] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.

The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your GRAMPS generated website the option to send you feedback, like the example on [http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].

== Changes you can do - For more advanced Users==
===Changing your Home Page===
If you made your own "HomePage", which I recommend strongly, you can easily edit this HTML file. Use a standard text editor (gedit will do quite nicely), and you can change the content. The same applies off course to the "Footer" and "IntroPage". If you know your way around with HTML you can add divs and extra markup. Remember to also put the newly defined div and classes in your edited css file.

===Changing the narrative.css===

As mentioned, with a standard text editor (gedit) you can adapt your css file. Not happy with the colours or fonts? Change them! The beauty of the cascading style sheet is that if you make a change here, all your pages will change. Dada! Now one thing to watch out for is that if you make changes and you finally obtained a good style sheet, that you save a backup in another directory than the one GRAMPS made. Why? The next time you let GRAMPS generate some webpages, the program will re-install the default narrative.css and bye bye changes. You can on regeneration of your website select the option in GRAMPS to NOT use a css, but this is easily overseen, especially if you generate different websites with different requirements

===Go for the real thing===
If everything went according to plan, you can repeat all the steps with a larger number of people. However, be cautious But hold your horses for just a sec First check out the amount of Mb this first attempt generated. This is important as your host limits the amount of data you can put on his server. Lycos for example (the free as in beer version) allows you a nifty 50 Mb. But as your database can hold an unlimited amount of persons and pictures this is easily obtained. A very important parameter is the amount of images (media objects) you put on your site. If you have, say 50 images of 500 Kb then half of your diskspace is gone already.

===Splitting the database for hosting===

What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure GRAMPS generates does not change.

==Comments==
If you have any comments, remarks, suggestions or alterations/adaptations or plain questions send me an e-mail frederik.de.richter at pandora.be. You could also edit this wiki page, or use the Talk page. It's free source so use it.

{{languages}}

Howto: Make a genealogy website with Gramps

2008-02-15T07:59:56Z

Sgpsaros: Grammar and Punctuation Changes

This is a Howto on how to make a genealogy website with GRAMPS 2.2.x. and the NarrativeWeb plugin.

The website will be made with the narrative website report, of which the interface is described at: [[Generating Web pages]]. The goal is to offer a complete howto/tutorial on using this report, from conception, to uploading your genealogical website to an internet service provider (ISP).

[[Category:Tutorials|Make a genealogy website with GRAMPS]]

== Before you start ==

You can easily generate from within GRAMPS a nice looking Web Site.

Before you start you should have an idea about the data you want to have on the website. If you are not careful, and generate a webpage from your complete database, the amount of generated files can be '''huge''', as well as taking up a lot of space.

==How to limit the amount of data==

If you have a large database, it is wise to start with a [[filter]] to limit the amount of persons: In the People view of GRAMPS, go to the View menu, and activate the Filter sidebar. Next, go to ''Edit menu--> Person Filter Editor'', and make a suitable filter. Read the [http://gramps-project.org/gramps-manual/2.2/en/ch03s10.html#tools-util-cfe help manual] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.

==Make a Home Page, Introduction Page, and more==
===What?===
Before you use the plugin ''NarrativeWeb'', you should make some custom pages with the information not yet in GRAMPS:
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Custom footnote: the footnote to appear on the site
* Custom header: a custom header to appear on the top of every page
* Publisher info: extra information on you, the publisher of the page, to appear on every page

Note that GRAMPS works with stylesheets, so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).

===How?===
Go to the Media View in GRAMPS, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.

If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' GRAMPS media object.

Tip: if you are experienced with style, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.

==Choosing the layout==

GRAMPS has some nice standard layout schemes. Those are kept in so-called cascading style sheets (.css files). In GRAMPS 2.2.x, six are supplied. You are free to edit these files (other lettertypes, other colours, ...).

Whatever the style you choose, after generation, it will default to the ''narrative.css'' file which will be placed in the dir you indicate. If you have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours, etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error.

Examples of the 6 styles:
*Modern - See example [http://familiemalengier.be/ Malengier]
*Business - TODO
*Certificate - TODO
*Antique - See example [http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project]
*Tranquil - TODO
*Sharp - TODO

If you make a nice custom style sheet, please share with other GRAMPS users. You can do this by adding a link to your webpage in the examples below and adding to your css file that its copyright is creative commons alike, or you can send it to the developers on: gramps-devel <at> lists.sourceforge.net

==Generate the pages==

In the Report menu, choose ''Web Page-->Narrative Web Site''.

Chose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.

In the Report Options Tab, set the filter you created. Choose a '''GOOD''' title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding to Unicode (only use other encoding if you have very specific reasons). Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). '''Think about copyright!''' Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graph. Try different settings for this.

In the Page Generation Tab, choose the internal notes you created, as related above. I suggest you suppress the GRAMPS ID, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if 1) your site can be VERY big, 2) you extensively use the private marker on sensitive data'''. Many people have burnt themselves with this option, publishing private email conversations they stored for research reasons in GRAMPS, on the net without realising.

The Privacy Tab is last, but '''is one of the most important settings''' . Take the habit never to include private data, and restrict the information on living people. I suggest you set the ''years to restrict from person's death'' to a '''minimum of 25 years'''! This will prevent grave mistakes having sour consequences. Many genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also take into account local legislation (very strict in eg Italy, France).

Now you just click ok and GRAMPS starts generating your web page : a lot of files and directories will be made, so this will take some time. But when it is completed you will be the proud owner of a complete structure ready to publish on the WWW.

==Regeneration of your site==
Every time you change your database you need to regenerate your site to see the changes. Although GRAMPS will regenerate the entire site, '''only the pages with changed data''' will be different. You therefore need not republish all the website to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See further.

'''Limitation''': If you upgrade GRAMPS, changes might have happened to the website generation, meaning all pages will have changed. Investigate this before you upgrade, and consider the benefits of upgrading against this possible drawback.

==Publishing==

Now you can publish your work on the web.

===Size and provider===
First, check the size of your web page. Go to the directory where you stored the web site, and in a modern file browser, right-click and select properties. This normally allows to calculate the directory size. Write down this info, and check your webhosting contract. Above a certain size, you will need to pay extra. Investigate before you burn yourself! If your site is too large, you can make a filter which produces a smaller website, or disable images, or split your site in pieces, and host it with different providers.

There are some free providers around: eg Lycos , but there are maybe better alternatives. Also GRAMPS offers '''free''' hosting of family website. Check out [[GRAMPS:Webhosting|webhosting by the GRAMPS project]].

===Transfer your files===
*[http://www.lyra.org/sitecopy/ sitecopy]: This is generally the best option. Only changed pages are uploaded to the server hosting your website. You can install sitecopy with every distribution via the package manager. Read the manual, it is self-explanatory: type in a console <code>man sitecopy</code> (or in konqueror type address <code>man:sitecopy</code>). Please, add a wiki page to [[sitecopy]] if you have experience and want to help new users.
*rsync : This is for advanced linux users. It is a better solution than sitecopy, but you need full access to the webhost, which normal users normally not have. Rsync only uploads the changes to a file, whereas sitecopy uploads the entire file.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awefull lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider to learn sitecopy!

== Examples of websites==
Feel free to add your with GRAMPS generated website here. Please, remove missing links if you encounter those. Style is one of the GRAMPS styles, or custom.

{|{{prettytable}} align="center"
|- bgcolor="#8DA7D6" align="center"
|'''Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[http://familiemalengier.be/ Malengier] ||Modern || Dutch
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|-
|[http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project] ||Antique || English || version 2.2.6
|}

== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. GRAMPS website generation belongs in this category.

Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [http://www.phpgedview.net/ PhpGedview] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.

The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your GRAMPS generated website the option to send you feedback, like the example on [http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].

== Changes you can do - For more advanced Users==
===Changing your Home Page===
If you made your own "HomePage", which I recommend strongly, you can easily edit this HTML file. Use a standard text editor (gedit will do quite nicely), and you can change the content. The same applies off course to the "Footer" and "IntroPage". If you know your way around with HTML you can add divs and extra markup. Remember to also put the newly defined div and classes in your edited css file.

===Changing the narrative.css===

As mentioned, with a standard text editor (gedit) you can adapt your css file. Not happy with the colours or fonts? Change them! The beauty of the cascading style sheet is that if you make a change here, all your pages will change. Dada! Now one thing to watch out for is that if you make changes and you finally obtained a good style sheet, that you save a backup in another directory than the one GRAMPS made. Why? The next time you let GRAMPS generate some webpages, the program will re-install the default narrative.css and bye bye changes. You can on regeneration of your website select the option in GRAMPS to NOT use a css, but this is easily overseen, especially if you generate different websites with different requirements

===Go for the real thing===
If everything went according to plan, you can repeat all the steps with a larger number of people. However, be cautious But hold your horses for just a sec First check out the amount of Mb this first attempt generated. This is important as your host limits the amount of data you can put on his server. Lycos for example (the free as in beer version) allows you a nifty 50 Mb. But as your database can hold an unlimited amount of persons and pictures this is easily obtained. A very important parameter is the amount of images (media objects) you put on your site. If you have, say 50 images of 500 Kb then half of your diskspace is gone already.

===Splitting the database for hosting===

What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure GRAMPS generates does not change.

==Comments==
If you have any comments, remarks, suggestions or alterations and adaptations or plain questions send me an e-mail frederik.de.richter at pandora.be. You could also edit this wiki page, or use the Talk page. It's a free source so use it.

{{languages}}

Howto: Make a genealogy website with Gramps

2008-02-15T07:52:36Z

Sgpsaros: Grammar and Punctuation Corrections

This is a Howto on how to make a genealogy website with GRAMPS 2.2.x. and the NarrativeWeb plugin.

The website will be made with the narrative website report, of which the interface is described at: [[Generating Web pages]]. The goal is to offer a complete howto/tutorial on using this report, from conception, to uploading your genealogical website to an internet service provider (ISP).

[[Category:Tutorials|Make a genealogy website with GRAMPS]]

== Before you start ==

You can easily generate from within GRAMPS a nice looking Web Site.

Before you start you should have an idea about the data you want to have on the website. If you are not careful, and generate a webpage from your complete database, the amount of generated files can be '''huge''', as well as taking up a lot of space.

==How to limit the amount of data==

If you have a large database, it is wise to start with a [[filter]] to limit the amount of persons: In the People view of GRAMPS, go to the View menu, and activate the Filter sidebar. Next, go to ''Edit menu--> Person Filter Editor'', and make a suitable filter. Read the [http://gramps-project.org/gramps-manual/2.2/en/ch03s10.html#tools-util-cfe help manual] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.

==Make a Home Page, Introduction Page, and more==
===What?===
Before you use the plugin ''NarrativeWeb'', you should make some custom pages with the information not yet in GRAMPS:
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Custom footnote: the footnote to appear on the site
* Custom header: a custom header to appear on the top of every page
* Publisher info: extra information on you, the publisher of the page, to appear on every page

Note that GRAMPS works with stylesheets, so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).

===How?===
Go to the Media View in GRAMPS, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.

If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' GRAMPS media object.

Tip: if you are experienced with style, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.

==Choosing the layout==

GRAMPS has some nice standard layout schemes. Those are kept in so-called cascading style sheets (.css files). In GRAMPS 2.2.x, six are supplied. You are free to edit these files (other lettertypes, other colours, ...).

Whatever the style you choose, after generation, it will default to the ''narrative.css'' file which will be placed in the dir you indicate. If you have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours, etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error.

Examples of the 6 styles:
*Modern - See example [http://familiemalengier.be/ Malengier]
*Business - TODO
*Certificate - TODO
*Antique - See example [http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project]
*Tranquil - TODO
*Sharp - TODO

If you make a nice custom style sheet, please share with other GRAMPS users. You can do this by adding a link to your webpage in the examples below and adding to your css file that its copyright is creative commons alike, or you can send it to the developers on: gramps-devel <at> lists.sourceforge.net

==Generate the pages==

In the Report menu, choose ''Web Page-->Narrative Web Site''.

Chose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.

In the Report Options Tab, set the filter you created. Choose a '''GOOD''' title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding to Unicode (only use other encoding if you have very specific reasons). Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). '''Think about copyright!'''. Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graph. Try different settings for this.

In the Page Generation Tab, choose the internal notes you created, as related above. I suggest you suppress the GRAMPS ID, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if 1) your site can be VERY big, 2) you extensively use the private marker on sensitive data'''. Many people have burnt themselves with this option, publishing private email conversations they stored for research reasons in GRAMPS, on the net without realising.

The Privacy Tab is last but '''is one of the most important settings''' . Take the habit never to include private data, and restrict the information on living people. I suggest you set the ''years to restrict from person's death'' to '''minimum 25 years'''! This will prevent grave mistakes having sour consequences. Many genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also take into account local legislation (very strict in eg Italy, France).

Now you just click ok and GRAMPS starts generating your web page : a lot of files and directories will be made, so this will take some time. But when it is completed you will be the proud owner of a complete structure ready to publish on the WWW.

==Regeneration of your site==
Every time you change your database you need to regenerate your site to see the changes. Although GRAMPS will regenerate the entire site, '''only the pages with changed data''' will be different. You therefore need not republish all the website to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See further.

'''Limitation''': If you upgrade GRAMPS, changes might have happened to the website generation, meaning all pages will have changed. Investigate this before you upgrade, and consider the benefits of upgrading against this possible drawback.

==Publishing==

Now you can publish your work on the web.

===Size and provider===
First, check the size of your web page. Go to the directory where you stored the web site, and in a modern file browser, right-click and select properties. This normally allows to calculate the directory size. Write down this info, and check your webhosting contract. Above a certain size, you will need to pay extra. Investigate before you burn yourself! If your site is too large, you can make a filter which produces a smaller website, or disable images, or split your site in pieces, and host it with different providers.

There are some free providers around: eg Lycos , but there are maybe better alternatives. Also GRAMPS offers '''free''' hosting of family website. Check out [[GRAMPS:Webhosting|webhosting by the GRAMPS project]].

===Transfer your files===
*[http://www.lyra.org/sitecopy/ sitecopy]: This is generally the best option. Only changed pages are uploaded to the server hosting your website. You can install sitecopy with every distribution via the package manager. Read the manual, it is self-explanatory: type in a console <code>man sitecopy</code> (or in konqueror type address <code>man:sitecopy</code>). Please, add a wiki page to [[sitecopy]] if you have experience and want to help new users.
*rsync : This is for advanced linux users. It is a better solution than sitecopy, but you need full access to the webhost, which normal users normally not have. Rsync only uploads the changes to a file, whereas sitecopy uploads the entire file.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awefull lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider to learn sitecopy!

== Examples of websites==
Feel free to add your with GRAMPS generated website here. Please, remove missing links if you encounter those. Style is one of the GRAMPS styles, or custom.

{|{{prettytable}} align="center"
|- bgcolor="#8DA7D6" align="center"
|'''Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[http://familiemalengier.be/ Malengier] ||Modern || Dutch
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|-
|[http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project] ||Antique || English || version 2.2.6
|}

== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. GRAMPS website generation belongs in this category.

Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [http://www.phpgedview.net/ PhpGedview] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.

The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your GRAMPS generated website the option to send you feedback, like the example on [http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].

== Changes you can do - For more advanced Users==
===Changing your Home Page===
If you made your own "HomePage", which I recommend strongly, you can easily edit this HTML file. Use a standard text editor (gedit will do quite nicely), and you can change the content. The same applies off course to the "Footer" and "IntroPage". If you know your way around with HTML you can add divs and extra markup. Remember to also put the newly defined div and classes in your edited css file.

===Changing the narrative.css===

As mentioned, with a standard text editor (gedit) you can adapt your css file. Not happy with the colours or fonts? Change them! The beauty of the cascading style sheet is that if you make a change here, all your pages will change. Dada! Now one thing to watch out for is that if you make changes and you finally obtained a good style sheet, that you save a backup in another directory than the one GRAMPS made. Why? The next time you let GRAMPS generate some webpages, the program will re-install the default narrative.css and bye bye changes. You can on regeneration of your website select the option in GRAMPS to NOT use a css, but this is easily overseen, especially if you generate different websites with different requirements

===Go for the real thing===
If everything went according to plan, you can repeat all the steps with a larger number of people. However, be cautious But hold your horses for just a sec First check out the amount of Mb this first attempt generated. This is important as your host limits the amount of data you can put on his server. Lycos for example (the free as in beer version) allows you a nifty 50 Mb. But as your database can hold an unlimited amount of persons and pictures this is easily obtained. A very important parameter is the amount of images (media objects) you put on your site. If you have, say 50 images of 500 Kb then half of your diskspace is gone already.

===Splitting the database for hosting===

What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure GRAMPS generates does not change.

==Comments==
If you have any comments, remarks, suggestions or alterations and adaptations or plain questions send me an e-mail frederik.de.richter at pandora.be. You could also edit this wiki page, or use the Talk page. It's a free source so use it.

{{languages}}

Howto: Make a genealogy website with Gramps

2008-02-15T07:46:49Z

Sgpsaros: Added Punctuation

This is a Howto on how to make a genealogy website with GRAMPS 2.2.x. and the NarrativeWeb plugin.

The website will be made with the narrative website report, of which the interface is described at: [[Generating Web pages]]. The goal is to offer a complete howto/tutorial on using this report, from conception, to uploading your genealogical website to an internet service provider (ISP).

[[Category:Tutorials|Make a genealogy website with GRAMPS]]

== Before you start ==

You can easily generate from within GRAMPS a nice looking Web Site.

Before you start you should have an idea about the data you want to have on the website. If you are not careful, and generate a webpage from your complete database, the amount of generated files can be '''huge''', as well as taking up a lot of space.

==How to limit the amount of data==

If you have a large database, it is wise to start with a [[filter]] to limit the amount of persons: In the People view of GRAMPS, go to the View menu, and activate the Filter sidebar. Next, go to ''Edit menu--> Person Filter Editor'', and make a suitable filter. Read the [http://gramps-project.org/gramps-manual/2.2/en/ch03s10.html#tools-util-cfe help manual] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.

==Make a Home Page, Introduction Page, and more==
===What?===
Before you use the plugin ''NarrativeWeb'', you should make some custom pages with the information not yet in GRAMPS:
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Custom footnote: the footnote to appear on the site
* Custom header: a custom header to appear on the top of every page
* Publisher info: extra information on you, the publisher of the page, to appear on every page

Note that GRAMPS works with stylesheets, so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).

===How?===
Go to the Media View in GRAMPS, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.

If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' GRAMPS media object.

Tip: if you are experienced with style, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.

==Choosing the layout==

GRAMPS has some nice standard layout schemes. Those are kept in so-called cascading style sheets (.css files). In GRAMPS 2.2.x, six are supplied. You are free to edit these files (other lettertypes, other colours, ...).

Whatever the style you choose, after generation, it will default to the ''narrative.css'' file which will be placed in the dir you indicate. If have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error.

Examples of the 6 styles:
*Modern - See example [http://familiemalengier.be/ Malengier]
*Business - TODO
*Certificate - TODO
*Antique - See example [http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project]
*Tranquil - TODO
*Sharp - TODO

If you make a nice custom style sheet, please share with other GRAMPS users. You can do this by adding a link to your webpage in the examples below and adding to your css file that its copyright is creative commons alike, or you can send it to the developers on: gramps-devel <at> lists.sourceforge.net

==Generate the pages==

In the Report menu, choose ''Web Page-->Narrative Web Site''.

Chose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.

In the Report Options Tab, set the filter you created. Choose a '''GOOD''' title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding to Unicode (only use other encoding if you have very specific reasons). Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). '''Think about copyright!'''. Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graph. Try different settings for this.

In the Page Generation Tab, choose the internal notes you created, as related above. I suggest you suppress the GRAMPS ID, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if 1) your site can be VERY big, 2) you extensively use the private marker on sensitive data'''. Many people have burnt themselves with this option, publishing private email conversations they stored for research reasons in GRAMPS, on the net without realising.

The Privacy Tab is last but '''is one of the most important settings''' . Take the habit never to include private data, and restrict the information on living people. I suggest you set the ''years to restrict from person's death'' to '''minimum 25 years'''! This will prevent grave mistakes having sour consequences. Many genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also take into account local legislation (very strict in eg Italy, France).

Now you just click ok and GRAMPS starts generating your web page : a lot of files and directories will be made, so this will take some time. But when it is completed you will be the proud owner of a complete structure ready to publish on the WWW.

==Regeneration of your site==
Every time you change your database you need to regenerate your site to see the changes. Although GRAMPS will regenerate the entire site, '''only the pages with changed data''' will be different. You therefore need not republish all the website to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See further.

'''Limitation''': If you upgrade GRAMPS, changes might have happened to the website generation, meaning all pages will have changed. Investigate this before you upgrade, and consider the benefits of upgrading against this possible drawback.

==Publishing==

Now you can publish your work on the web.

===Size and provider===
First, check the size of your web page. Go to the directory where you stored the web site, and in a modern file browser, right-click and select properties. This normally allows to calculate the directory size. Write down this info, and check your webhosting contract. Above a certain size, you will need to pay extra. Investigate before you burn yourself! If your site is too large, you can make a filter which produces a smaller website, or disable images, or split your site in pieces, and host it with different providers.

There are some free providers around: eg Lycos , but there are maybe better alternatives. Also GRAMPS offers '''free''' hosting of family website. Check out [[GRAMPS:Webhosting|webhosting by the GRAMPS project]].

===Transfer your files===
*[http://www.lyra.org/sitecopy/ sitecopy]: This is generally the best option. Only changed pages are uploaded to the server hosting your website. You can install sitecopy with every distribution via the package manager. Read the manual, it is self-explanatory: type in a console <code>man sitecopy</code> (or in konqueror type address <code>man:sitecopy</code>). Please, add a wiki page to [[sitecopy]] if you have experience and want to help new users.
*rsync : This is for advanced linux users. It is a better solution than sitecopy, but you need full access to the webhost, which normal users normally not have. Rsync only uploads the changes to a file, whereas sitecopy uploads the entire file.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awefull lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider to learn sitecopy!

== Examples of websites==
Feel free to add your with GRAMPS generated website here. Please, remove missing links if you encounter those. Style is one of the GRAMPS styles, or custom.

{|{{prettytable}} align="center"
|- bgcolor="#8DA7D6" align="center"
|'''Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[http://familiemalengier.be/ Malengier] ||Modern || Dutch
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|-
|[http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project] ||Antique || English || version 2.2.6
|}

== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. GRAMPS website generation belongs in this category.

Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [http://www.phpgedview.net/ PhpGedview] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.

The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your GRAMPS generated website the option to send you feedback, like the example on [http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].

== Changes you can do - For more advanced Users==
===Changing your Home Page===
If you made your own "HomePage", which I recommend strongly, you can easily edit this HTML file. Use a standard text editor (gedit will do quite nicely), and you can change the content. The same applies off course to the "Footer" and "IntroPage". If you know your way around with HTML you can add divs and extra markup. Remember to also put the newly defined div and classes in your edited css file.

===Changing the narrative.css===

As mentioned, with a standard text editor (gedit) you can adapt your css file. Not happy with the colours or fonts? Change them! The beauty of the cascading style sheet is that if you make a change here, all your pages will change. Dada! Now one thing to watch out for is that if you make changes and you finally obtained a good style sheet, that you save a backup in another directory than the one GRAMPS made. Why? The next time you let GRAMPS generate some webpages, the program will re-install the default narrative.css and bye bye changes. You can on regeneration of your website select the option in GRAMPS to NOT use a css, but this is easily overseen, especially if you generate different websites with different requirements

===Go for the real thing===
If everything went according to plan, you can repeat all the steps with a larger number of people. However, be cautious But hold your horses for just a sec First check out the amount of Mb this first attempt generated. This is important as your host limits the amount of data you can put on his server. Lycos for example (the free as in beer version) allows you a nifty 50 Mb. But as your database can hold an unlimited amount of persons and pictures this is easily obtained. A very important parameter is the amount of images (media objects) you put on your site. If you have, say 50 images of 500 Kb then half of your diskspace is gone already.

===Splitting the database for hosting===

What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure GRAMPS generates does not change.

==Comments==
If you have any comments, remarks, suggestions or alterations and adaptations or plain questions send me an e-mail frederik.de.richter at pandora.be. You could also edit this wiki page, or use the Talk page. It's a free source so use it.

{{languages}}

Howto: Make a genealogy website with Gramps

2008-02-15T07:45:22Z

Sgpsaros: Changed Indefinite Article

This is a Howto on how to make a genealogy website with GRAMPS 2.2.x. and the NarrativeWeb plugin.

The website will be made with the narrative website report, of which the interface is described at: [[Generating Web pages]]. The goal is to offer a complete howto/tutorial on using this report, from conception, to uploading your genealogical website to an internet service provider (ISP).

[[Category:Tutorials|Make a genealogy website with GRAMPS]]

== Before you start ==

You can easily generate from within GRAMPS a nice looking Web Site.

Before you start you should have an idea about the data you want to have on the website. If you are not careful, and generate a webpage from your complete database the amount of generated files can be '''huge''', as well as taking up a lot of space.

==How to limit the amount of data==

If you have a large database, it is wise to start with a [[filter]] to limit the amount of persons: In the People view of GRAMPS, go to the View menu, and activate the Filter sidebar. Next, go to ''Edit menu--> Person Filter Editor'', and make a suitable filter. Read the [http://gramps-project.org/gramps-manual/2.2/en/ch03s10.html#tools-util-cfe help manual] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.

==Make a Home Page, Introduction Page, and more==
===What?===
Before you use the plugin ''NarrativeWeb'', you should make some custom pages with the information not yet in GRAMPS:
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Custom footnote: the footnote to appear on the site
* Custom header: a custom header to appear on the top of every page
* Publisher info: extra information on you, the publisher of the page, to appear on every page

Note that GRAMPS works with stylesheets, so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).

===How?===
Go to the Media View in GRAMPS, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.

If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' GRAMPS media object.

Tip: if you are experienced with style, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.

==Choosing the layout==

GRAMPS has some nice standard layout schemes. Those are kept in so-called cascading style sheets (.css files). In GRAMPS 2.2.x, six are supplied. You are free to edit these files (other lettertypes, other colours, ...).

Whatever the style you choose, after generation, it will default to the ''narrative.css'' file which will be placed in the dir you indicate. If have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error.

Examples of the 6 styles:
*Modern - See example [http://familiemalengier.be/ Malengier]
*Business - TODO
*Certificate - TODO
*Antique - See example [http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project]
*Tranquil - TODO
*Sharp - TODO

If you make a nice custom style sheet, please share with other GRAMPS users. You can do this by adding a link to your webpage in the examples below and adding to your css file that its copyright is creative commons alike, or you can send it to the developers on: gramps-devel <at> lists.sourceforge.net

==Generate the pages==

In the Report menu, choose ''Web Page-->Narrative Web Site''.

Chose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.

In the Report Options Tab, set the filter you created. Choose a '''GOOD''' title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding to Unicode (only use other encoding if you have very specific reasons). Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). '''Think about copyright!'''. Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graph. Try different settings for this.

In the Page Generation Tab, choose the internal notes you created, as related above. I suggest you suppress the GRAMPS ID, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if 1) your site can be VERY big, 2) you extensively use the private marker on sensitive data'''. Many people have burnt themselves with this option, publishing private email conversations they stored for research reasons in GRAMPS, on the net without realising.

The Privacy Tab is last but '''is one of the most important settings''' . Take the habit never to include private data, and restrict the information on living people. I suggest you set the ''years to restrict from person's death'' to '''minimum 25 years'''! This will prevent grave mistakes having sour consequences. Many genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also take into account local legislation (very strict in eg Italy, France).

Now you just click ok and GRAMPS starts generating your web page : a lot of files and directories will be made, so this will take some time. But when it is completed you will be the proud owner of a complete structure ready to publish on the WWW.

==Regeneration of your site==
Every time you change your database you need to regenerate your site to see the changes. Although GRAMPS will regenerate the entire site, '''only the pages with changed data''' will be different. You therefore need not republish all the website to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See further.

'''Limitation''': If you upgrade GRAMPS, changes might have happened to the website generation, meaning all pages will have changed. Investigate this before you upgrade, and consider the benefits of upgrading against this possible drawback.

==Publishing==

Now you can publish your work on the web.

===Size and provider===
First, check the size of your web page. Go to the directory where you stored the web site, and in a modern file browser, right-click and select properties. This normally allows to calculate the directory size. Write down this info, and check your webhosting contract. Above a certain size, you will need to pay extra. Investigate before you burn yourself! If your site is too large, you can make a filter which produces a smaller website, or disable images, or split your site in pieces, and host it with different providers.

There are some free providers around: eg Lycos , but there are maybe better alternatives. Also GRAMPS offers '''free''' hosting of family website. Check out [[GRAMPS:Webhosting|webhosting by the GRAMPS project]].

===Transfer your files===
*[http://www.lyra.org/sitecopy/ sitecopy]: This is generally the best option. Only changed pages are uploaded to the server hosting your website. You can install sitecopy with every distribution via the package manager. Read the manual, it is self-explanatory: type in a console <code>man sitecopy</code> (or in konqueror type address <code>man:sitecopy</code>). Please, add a wiki page to [[sitecopy]] if you have experience and want to help new users.
*rsync : This is for advanced linux users. It is a better solution than sitecopy, but you need full access to the webhost, which normal users normally not have. Rsync only uploads the changes to a file, whereas sitecopy uploads the entire file.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awefull lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider to learn sitecopy!

== Examples of websites==
Feel free to add your with GRAMPS generated website here. Please, remove missing links if you encounter those. Style is one of the GRAMPS styles, or custom.

{|{{prettytable}} align="center"
|- bgcolor="#8DA7D6" align="center"
|'''Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[http://familiemalengier.be/ Malengier] ||Modern || Dutch
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|-
|[http://ancestry.queervisions.com/ The Coy Yaeger Ancestry Project] ||Antique || English || version 2.2.6
|}

== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. GRAMPS website generation belongs in this category.

Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [http://www.phpgedview.net/ PhpGedview] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.

The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your GRAMPS generated website the option to send you feedback, like the example on [http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].

== Changes you can do - For more advanced Users==
===Changing your Home Page===
If you made your own "HomePage", which I recommend strongly, you can easily edit this HTML file. Use a standard text editor (gedit will do quite nicely), and you can change the content. The same applies off course to the "Footer" and "IntroPage". If you know your way around with HTML you can add divs and extra markup. Remember to also put the newly defined div and classes in your edited css file.

===Changing the narrative.css===

As mentioned, with a standard text editor (gedit) you can adapt your css file. Not happy with the colours or fonts? Change them! The beauty of the cascading style sheet is that if you make a change here, all your pages will change. Dada! Now one thing to watch out for is that if you make changes and you finally obtained a good style sheet, that you save a backup in another directory than the one GRAMPS made. Why? The next time you let GRAMPS generate some webpages, the program will re-install the default narrative.css and bye bye changes. You can on regeneration of your website select the option in GRAMPS to NOT use a css, but this is easily overseen, especially if you generate different websites with different requirements

===Go for the real thing===
If everything went according to plan, you can repeat all the steps with a larger number of people. However, be cautious But hold your horses for just a sec First check out the amount of Mb this first attempt generated. This is important as your host limits the amount of data you can put on his server. Lycos for example (the free as in beer version) allows you a nifty 50 Mb. But as your database can hold an unlimited amount of persons and pictures this is easily obtained. A very important parameter is the amount of images (media objects) you put on your site. If you have, say 50 images of 500 Kb then half of your diskspace is gone already.

===Splitting the database for hosting===

What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure GRAMPS generates does not change.

==Comments==
If you have any comments, remarks, suggestions or alterations and adaptations or plain questions send me an e-mail frederik.de.richter at pandora.be. You could also edit this wiki page, or use the Talk page. It's a free source so use it.

{{languages}}

Generating Web pages

2008-02-15T07:40:15Z

Sgpsaros: Added one Word

{{cleanup}}
[[Category:Documentation]][[Category:Tutorials]]
==Introduction==
GRAMPS 2.0.6 introduced the Narrative Web generator. The new tool provides considerably more functionality than the older web generator. Instead of using HTML templates to customize the pages, CSS style sheets are used.

More information is now displayed about each person, along with information about sources, places, and media objects. Introduction pages can be added to provide additional information, such as family history.

==Selecting the output==
Genealogy records can generate a lot of files. Many web servers have a difficult time with many files in a single directory. The Narrative Web Generator strives to keep the number of files per directory to a managable level. To do this, a hierarchy of directores is created. The generated files names are not intuitive, but are unique per person. Subsequent runs will geneate identical file names, making it easy to replace files.

By default, the output files are written to the specified directory. Because of the number of files and directories that are created, it may be difficult to transfer the files to an external web host. To aid in this, you may directly create a gzip'd tar file to more easily upload the data. This is the format that should be used if you would like to take advantage of the free genealogy page hosting at the GRAMPS web hosting site.

To select the gzip'd tar file, select the '''Store web pages in .tar.gz archive''' option.

==Applying a filter==
Like the previous web page generator, and most of the other GRAMPS reports, you can control what is included in the output by choosing a filter. Several default filters are provided for you, but you are free to use the '''Custom Filter Editor''' tool to create your own.

Any person matching this filter who is not excluded due to the privacy rules, will be included in the output. The default filter includes all people in the database.

==Applying a style sheet==
GRAMPS provides five built in style sheets for your web page. Each of these style sheets produces a unique look for your pages. The generated style sheet is named "narrative.css". You may edit this file if you wish to further customize your site.

If you make modifications to your style sheet, you need to be aware the regenerating the pages with the same output directory will overwrite your changes to this file. To prevent this from happening, make sure you choose '''No style sheet''' for subsequent runs.

==Character set encoding==
Because of GRAMPS internationalization ability, the default character set for the HTML pages is UTF-8. This provides support for virtually all characters.

The Apache web server is sometimes misconfigured to override the character set specified in an HTML page. This causes problems with the UTF-8 character set generated by GRAMPS, distorting characters on the screen.

If your web server is misconfigured and you do not have priveledge to fix the configururation, you may solve this problem by overriding the default character set to match what your web server may be expecting.

==Copyright notice==
International copyright law reserves all rights to your data. You own the data, and people must get your permission to use it. In genealogy, however, sharing data is a common ideal. It this case, you may wish to grant the user more rights.

While the default for GRAMPS is to place a notice indicating that all rights are reserved, we give you the option to place your site under one of several of the [http://creativecommons.org/licenses Creative Commons licenses]. With a Creative Commons license, you grant user's certain permission to use your data without requiring them to contact you directly for permission.

See the [http://creativecommons.org Creative Commons] web site for more information.

==Controlling page generation==
Three additional pages can be generated by the web page generator. The Home page is a page that will display an image and a whatever text you wish. To enable this page, choose a Media Object from the '''Home Media/Note ID''' menu on the '''Page Generation''' tab. If the media object contains an image, the image is displayed at the top of the page. If the Media Object contains a Note, the Note's text is used for the text of the page. A second page, the Introduction page, works similarly. Just choose the Media Object in the '''Introduction Media/Note ID''' menu.

If you choose to include a contact page, The researcher information stored in the database is displayed, along with the information specified in the '''Publisher contact/Note ID''' menu. Please use this page with caution, since you may consider your contact information to be private.

==Privacy==
Privacy of personal information is an important issue on the web today. GRAMPS tries to give you control over the information that is presented.

GRAMPS provides two options to control the privacy of your information. If you select the '''Do not include records marked private''' option, any data that is marked as private will not be displayed on the generated site. If you select '''Restrict information on living people''', GRAMPS will attempt to determine which people have the potential of still being alive, and will omit these people from the database. Some countries have laws that indicate that a certain number of years must pass after someone's death before information can be published. The '''Years to restrict from a person's death''' option allows you to specifiy how many years a person must be deceased before the information is included.

Please note that it is your responsibility to double check all information in the pages for any privacy information. GRAMPS cannot be held responsible for any privacy issues.

==Adding custom code your pages==
Note: If you are not interested in customizing your pages, you may skip the section.

The previous web generator allowed you to customize your pages using HTML templates. Your data would be substituted for certain markers in the code.

This method proved to be too cumbersome for most users. The Narrative Web Page Generator introduces a simpler mechanism. On the '''Page Generation''' tab, you may specify text (including HTML code) that will be inserted into each page.

To create this code, you need to create a Media Object marked as an '''internal note'''. To create this, add a new Media Object from the Media View, and select the '''internal note''' option. You may then enter your HTML code.

Two div sections are added to the page - userheader and userfooter. The corresponding HTML code is inserted into the HTML page surrounded by div markers. You can customize your style sheet to provide additional formatting and positioning information to control these sections.

==More Info==
* [[Howto: Make a genealogy website with GRAMPS]]: a detailed tutorial.

Installation

2008-02-14T09:42:43Z

Sgpsaros: Grammar Correction

{{languages}}

==Live CD==
If you are interested in GRAMPS, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://ubuntu.com Ubuntu 7.04 LTS] and GRAMPS from the CD anytime you like.

==Easy download and install of GRAMPS==
Before downloading, check if the version of GRAMPS in your distribution is not current:
* Mandriva: <code>
urpmi gramps</code>
* Debian, (K,X,Edu)Ubuntu, Mepis, Suse: <code>
apt-get install gramps</code>
* Fedora: <code>
yum install gramps</code>

==Upgrading to the latest version==
If your version of GRAMPS is not current, some users offer up to date packages for some distributions:

* '''Ubuntu''' and derivatives (Kubuntu, Mephis, ...): Ubuntu packages are available on [http://sourceforge.net/project/showfiles.php?group_id=25770 sourceforge].
** Gutsy (7.10) and Feisty (7.04) : download [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps_2.2.10-1_all.deb] and [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps-help_2.2.10-1_all.deb] , and install with your package manager. Standard you could use the [http://packages.ubuntu.com/gutsy/admin/gdebi gdebi] package.
** Dapper, Edgy and before: 2.2.10 is not available yet, for now download [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps_2.2.8-1dapper1_all.deb] and [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps-help_2.2.8-1dapper1_all.deb] , and install with your package manager.
* '''SuSE''': Richard Bos has been providing the GRAMPS releases for SuSE's apt repository. They are always last release in [http://software.opensuse.org/download/home:/rbos/ his repository]. See also [http://www.suseforums.net/index.php?s=22f80a050a1e3cffffd590db0813dea9&showtopic=28727&pid=152093&st=0&#entry152093. this forum entry].
* '''Mandriva''': Sometimes newer versions of GRAMPS are backported. For this, you must enable the ''backports'': see [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates Mandriva wiki]. You will then possibly be able to install more recent versions of software, hopefully also of GRAMPS. You could try ''contrib'' too. If the latest version of GRAMPS is not available, you must install from source (see below).
* '''Fedora''': If <tt>FC6</tt>, on sourceforge, [http://sourceforge.net/project/showfiles.php?group_id=25770 download gramps-zzz.fc6.noarch.rpm] if available, and install with your package manager, for <tt>FC7</tt> use the fc7 package. The alternative to installing from source (described below) is to [[fedora rpm|build a package]] from an rpm spec file, or install a binary from fedora testing.
* '''Debian''': the latest version is installed directly into unstable ([http://packages.debian.org/sid/gramps Sid Gramps]) and can be upgraded from your package manager. Testing is updated 10 days later (except near a new stable release), see [http://packages.debian.org/lenny/gramps Lenny Gramps].

''Note: Some Linux distributions may have a slightly different way to download and install packages for GRAMPS. Please read the installation instructions specific to your distribution before downloading.''

In all other cases, you must [http://sourceforge.net/project/showfiles.php?group_id=25770 download] the source package zzz.tar.gz, and install GRAMPS manually. See below for details.

==Windows, BSD, MacOs, Solaris==
For Windows, there is an experimental [[Windows installer]]. If this installer does not offer the most recent versions of GRAMPS in Windows, you need to wait until a new installer is made available.

For MacOSX, both the [http://finkproject.org Fink project] and [http://macports.org MacPorts] have Gramps as a installable package. Fink currently has it in the [http://www.finkproject.org/faq/usage-fink.php?phpLang=en#unstable unstable tree].

For BSD, MacOS, Solaris there are experimental install instructions below.

==Gnome and KDE==
You can use both, but GRAMPS fits in better with GNOME. For KDE there are some minor issues due to some (GTK) issues outside of GRAMPS. Check the [[KDE page]] to know what these problems might be.

=Additional software GRAMPS can benefit from=
GRAMPS does not rely on the following programs, however, having them will increase your productivity:

* '''Gnome-print''': It adds the ability to directly print, to preview, and to generate fully internationalized PS and PDF output. At this time, one needs to install gnome-python-desktop to obtain this package (it might be known under different names, eg on debian python-gnome2-desktop).
* '''Spell checking''': Installing python-gnome2-extras provides the gtkspell module, which adds spell checking in the notes
* '''Graphviz''', '''Inkscape''': Gramps can make nice Genealogical trees (relationship graphs). These are generated by the Graphviz package, which defines a code (dot), as well as programs to produce graphs (dotty, to be called from command line). This gives you as researcher most power over how your tree will look, but has a learning curve. Also, [https://gna.org/projects/kgraphviewer kgraphviewer] works fine with dot generated by GRAMPS. An alternative is to make a graphical report, converting the tree to an svg file, which you then can open/edit/refine in eg Inkscape.
* '''ttf-freefont''': Useful as a font that supports a large subset of the unicode and is a true type. This works well with both gnomeprint and graphviz output.

Other packages might also be usefull:

* '''Yelp''': Gnome help browser. This allows to call and read the GRAMPS documentation on your computer.
* '''desktop-file-utils''': see list of programs to open a media file on right click on an image

=Installing from source=
==General Requirements==

GRAMPS 2.0 requires python 2.3 and the gnome-python and pygtk2 packages. The gnome-python module should be 2.6.0 or greater. The pygtk package should be version 2.5.0 or greater.

Also librsvg2-common is needed. This is a common error at the moment in some packages. Without this library, the icons are not shown.

=== Linux Package Requirements ===
{|border="1" align ="center"
|-
|Debian /Ubuntu
|Fedora /Redhat
|Comment
|-
|python
|python
|Required (needs version 2.3 or later) [does 2.3 include set()?]
|-
|pygtk2
|pygtk2
|Required (needs 2.5.0 or greater)
|-
|gnome-python
|gnome-python
|Required (needs 2.6.0 or greater)
|-
|librsvg2-common
|librsvg2
|Required for building
|-
|
|librsvg2-devel
|Required for building
|-
|
|gnome-common
|Required for building
|-
|
|intltool
|Required for building
|-
|
|gnome-doc-utils
|Required for building
|-
|
|python-reportlab
|Optional
|-
|}

==Obtaining the source==

* The lastest stable version of GRAMPS can be downloaded from the [http://sourceforge.net/projects/gramps GRAMPS SourceForge page]. As of this writing, this is gramps-2.2.10.tar.gz. Extract this file into a directory: <code>
tar xzvf gramps-zzz.tar.gz
</code> and then go into this directory:<code>
cd gramps-zzz
</code>
* If you are interested in testing out the latest development version of GRAMPS, it can be obtained from SVN, see [[Brief introduction to SVN]]. The SVN version of GRAMPS is potentially very dangerous as it has not been extensively tested. It may be prone to crashing and cause extensive data loss. Please use with caution.

Please, now is the time to read the [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/INSTALL?view=markup INSTALL] and [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/README?view=markup README] files accompanying the code. They come with the most recent information.

==Installing from source code on Linux==

Debian users will have various editions installed on their kit. Invariably the installation of GRAMPS requires more files, libraries, etc, than are available in the installed Debian software. Additionally, that there will be dependencies to be addressed.

Debian 4 (Etch, the current "stable" edition) users should "extract" the downloaded gramps-2.8.8.tar.gz to its selected directory, then cd (as user) to that directory as GRAMPS needs to be configured in preparation for installation.

GRAMPS provides a script that can be used to prepare the code for building. This script automatically calls the standard configure script:<code>
./autogen.sh </code> as user

This script will report any missing dependencies. Install these (see also INSTALL file). Building from source code typically requires that the development versions of the required libraries be installed. You might consider setting a prefix path with autogen.sh, see the INSTALL file for instructions. Standard install is in /usr/local.

Once a successful run of autogen.sh has been completed, you can run the typical make procedure. <code>
make (as user)</code>

then <code>
make install (as root) </code>

==Installing from source code on BSD==

Installing on BSD is as straithforward as on linux, apart from some minor issues like tools having different names. See the [[BSD page]] for details.

==Installing from source code on Mac OS X==

Some users have successfully installed GRAMPS on Mac OS X. See the [[Mac OS X]] page for details. Please, add to the wiki if you successfully installed GRAMPS on OS X.

==Installing from source code on Windows==

Fortunately for users of Microsoft Windows, some users have made a [[Windows installer]]. So far there have not been any reports of serious differences between the official builds of GRAMPS and the Windows Installer, so the future looks promising. But please, use this at your own risk. The developers of GRAMPS provide the space for this install page, but are not responsible for it.

If the dependencies are in place, the development version can be tested by getting the source (see above), renaming the file const.py.in to const.py, and executing "python gramps.py" from within the src directory. Of course, this is a development version on an unsupported platform, so warnings apply even more to this case than when using the installer. (I have not managed to get a localized build working this way.)

==Installing from source code on Solaris==

Previous versions of GRAMPS have run on Solaris. No recent cases are known to us however. Should you have successfully installed GRAMPS on Solaris, please update the [[Solaris page]].

[[Category:Documentation]]

Installation

2008-02-14T09:38:36Z

Sgpsaros: Spelling Correction and Letter Case Change

{{languages}}

==Live CD==
If you are interested in GRAMPS, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://ubuntu.com Ubuntu 7.04 LTS] and GRAMPS from the CD anytime you like.

==Easy download and install of GRAMPS==
Before downloading, check if the version of GRAMPS in your distribution is not current:
* Mandriva: <code>
urpmi gramps</code>
* Debian, (K,X,Edu)Ubuntu, Mepis, Suse: <code>
apt-get install gramps</code>
* Fedora: <code>
yum install gramps</code>

==Upgrading to the latest version==
If your version of GRAMPS is not current, some users offer up to date packages for some distributions:

* '''Ubuntu''' and derivatives (Kubuntu, Mephis, ...): Ubuntu packages are available on [http://sourceforge.net/project/showfiles.php?group_id=25770 sourceforge].
** Gutsy (7.10) and Feisty (7.04) : download [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps_2.2.10-1_all.deb] and [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps-help_2.2.10-1_all.deb] , and install with your package manager. Standard you could use the [http://packages.ubuntu.com/gutsy/admin/gdebi gdebi] package.
** Dapper, Edgy and before: 2.2.10 is not available yet, for now download [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps_2.2.8-1dapper1_all.deb] and [http://sourceforge.net/project/showfiles.php?group_id=25770 gramps-help_2.2.8-1dapper1_all.deb] , and install with your package manager.
* '''SuSE''': Richard Bos has been providing the GRAMPS releases for SuSE's apt repository. They are always last release in [http://software.opensuse.org/download/home:/rbos/ his repository]. See also [http://www.suseforums.net/index.php?s=22f80a050a1e3cffffd590db0813dea9&showtopic=28727&pid=152093&st=0&#entry152093. this forum entry].
* '''Mandriva''': Sometimes newer versions of GRAMPS are backported. For this, you must enable the ''backports'': see [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates Mandriva wiki]. You will then possibly be able to install more recent versions of software, hopefully also of GRAMPS. You could try ''contrib'' too. If the latest version of GRAMPS is not available, you must install from source (see below).
* '''Fedora''': If <tt>FC6</tt>, on sourceforge, [http://sourceforge.net/project/showfiles.php?group_id=25770 download gramps-zzz.fc6.noarch.rpm] if available, and install with your package manager, for <tt>FC7</tt> use the fc7 package. The alternative to installing from source (described below) is to [[fedora rpm|build a package]] from an rpm spec file, or install a binary from fedora testing.
* '''Debian''': the latest version is installed directly into unstable ([http://packages.debian.org/sid/gramps Sid Gramps]) and can be upgraded from your package manager. Testing is updated 10 days later (except near a new stable release), see [http://packages.debian.org/lenny/gramps Lenny Gramps].

''Note: Some Linux distributions may have a slightly different way to download and install packages for GRAMPS. Please read the installation instructions specific to your distribution before downloading.''

In all other cases, you must [http://sourceforge.net/project/showfiles.php?group_id=25770 download] the source package zzz.tar.gz, and install GRAMPS manually. See below for details.

==Windows, BSD, MacOs, Solaris==
For Windows, there is an experimental [[Windows installer]]. If this installer does not offer the most recent versions of GRAMPS in Windows, you need to wait until a new installer is made available.

For MacOSX, both the [http://finkproject.org Fink project] and [http://macports.org MacPorts] have Gramps as a installable package. Fink currently has it in the [http://www.finkproject.org/faq/usage-fink.php?phpLang=en#unstable unstable tree].

For BSD, MacOS, Solaris there are experimental install instructions below.

==Gnome and KDE==
You can use both, but GRAMPS fits in better with GNOME. For KDE there are some minor issues due to some (GTK) issues outside of GRAMPS. Check the [[KDE page]] to know what these problems might be.

=Additional software GRAMPS can benefit from=
GRAMPS does not rely on the following programs, however, having them will increase your productivity:

* '''Gnome-print''': It adds the ability to directly print, to preview, and to generate fully internationalized PS and PDF output. At this time, one needs to install gnome-python-desktop to obtain this package (it might be known under different names, eg on debian python-gnome2-desktop).
* '''Spell checking''': Installing python-gnome2-extras provides the gtkspell module, which adds spell checking in the notes
* '''Graphviz''', '''Inkscape''': Gramps can make nice Genealogical trees (relationship graphs). These are generated by the Graphviz package, which defines a code (dot), as well as programs to produce graphs (dotty, to be called from command line). This gives you as researcher most power over how your tree will look, but has a learning curve. Also, [https://gna.org/projects/kgraphviewer kgraphviewer] works fine with dot generated by GRAMPS. An alternative is to make a graphical report, converting the tree to an svg file, which you then can open/edit/refine in eg Inkscape.
* '''ttf-freefont''': Useful as a font that supports a large subset of the unicode and is a true type. This works well with both gnomeprint and graphviz output.

Other packages might also be usefull:

* '''Yelp''': Gnome help browser. This allows to call and read the GRAMPS documentation on your computer.
* '''desktop-file-utils''': see list of programs to open a media file on right click on an image

=Installing from source=
==General Requirements==

GRAMPS 2.0 requires python 2.3 and the gnome-python and pygtk2 packages. The gnome-python module should be 2.6.0 or greater. The pygtk package should be version 2.5.0 or greater.

Also librsvg2-common is needed. This is a common error at the moment in some packages. Without this library, the icons are not shown.

=== Linux Package Requirements ===
{|border="1" align ="center"
|-
|Debian /Ubuntu
|Fedora /Redhat
|Comment
|-
|python
|python
|Required (needs version 2.3 or later) [does 2.3 include set()?]
|-
|pygtk2
|pygtk2
|Required (needs 2.5.0 or greater)
|-
|gnome-python
|gnome-python
|Required (needs 2.6.0 or greater)
|-
|librsvg2-common
|librsvg2
|Required for building
|-
|
|librsvg2-devel
|Required for building
|-
|
|gnome-common
|Required for building
|-
|
|intltool
|Required for building
|-
|
|gnome-doc-utils
|Required for building
|-
|
|python-reportlab
|Optional
|-
|}

==Obtaining the source==

* The lastest stable version of GRAMPS can be downloaded from the [http://sourceforge.net/projects/gramps GRAMPS SourceForge page]. As of this writing, this is gramps-2.2.10.tar.gz. Extract this file into a directory: <code>
tar xzvf gramps-zzz.tar.gz
</code> and then go into this directory:<code>
cd gramps-zzz
</code>
* If you are interested in testing out the latest development version of GRAMPS, it can be obtained from SVN, see [[Brief introduction to SVN]]. The SVN version of GRAMPS is potentially very dangerous as it has not been extensively tested. It may be prone to crashing and cause extensive data loss. Please use with caution.

Please, now is the time to read the [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/INSTALL?view=markup INSTALL] and [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/README?view=markup README] files accompanying the code. They come with the most recent information.

==Installing from source code on Linux==

Debian users will have various editions installed on their kit. Invariably the installation of GRAMPS requires more files, libraries, etc, than are available in the installed Debian software. Additionally, that there will be dependencies to be addressed.

Debian 4 (Etch, the current "stable" edition) users should "extract" the downloaded gramps-2.8.8.tar.gz to its selected directory, then cd (as user) to that directory as GRAMPS needs to be configured in preparation for installation.

GRAMPS provides a script that can be used to prepare the code for building. This script automatically calls the standard configure script:<code>
./autogen.sh </code> as user

This script will report any missing dependencies. Install these (see also INSTALL file). Building from source code typically requires that the development versions of the required libraries be installed. You might consider setting a prefix path with autogen.sh, see the INSTALL file for instructions. Standard install is in /usr/local.

Once a successful run of autogen.sh has been completed, you can run the typical make procedure. <code>
make (as user)</code>

then <code>
make install (as root) </code>

==Installing from source code on BSD==

Installing on BSD is as straithforward as on linux, apart from some minor issues like tools having different names. See the [[BSD page]] for details.

==Installing from source code on Mac OS X==

Some users have successfully installed GRAMPS on Mac OS X. See the [[Mac OS X]] page for details. Please, add to the wiki if you successfully installed GRAMPS on OS X.

==Installing from source code on Windows==

Fortunately for users of Microsoft Windows have some users have made a [[Windows installer]]. So far there have not been any reports of serious differences between the official builds of GRAMPS and the Windows Installer, so the future looks promising. But please, use this at your own risk. The developers of GRAMPS provide the space for this install page, but are not responsible for it.

If the dependencies are in place, the development version can be tested by getting the source (see above), renaming the file const.py.in to const.py, and executing "python gramps.py" from within the src directory. Of course, this is a development version on an unsupported platform, so warnings apply even more to this case than when using the installer. (I have not managed to get a localized build working this way.)

==Installing from source code on Solaris==

Previous versions of GRAMPS have run on Solaris. No recent cases are known to us however. Should you have successfully installed GRAMPS on Solaris, please update the [[Solaris page]].

[[Category:Documentation]]

Help:Skins

2008-02-14T09:28:46Z

Sgpsaros: Letter Case Change

While logged in, click on the '''my preferences''' link in the upper right. Then click on the '''Skin''' tab to change your skin. You can also preview the skin by clicking the '''(preview)''' links next to each skin.

== See also ==
* [[Help:Preferences]]

[[Category:Help|Skins]]

Help:Skins

2008-02-14T09:27:57Z

Sgpsaros: Grammar Correction

While logged in, Click on the '''my preferences''' link in the upper right. Then click on the '''Skin''' tab to change your skin. You can also preview the skin by clicking the '''(preview)''' links next to each skin.

== See also ==
* [[Help:Preferences]]

[[Category:Help|Skins]]

Merging people

2008-02-14T08:59:49Z

Sgpsaros: Letter Case Change

Description of the process GRAMPS uses to merge two people.
[[Category:GRAMPS Logic]]

==Definition==
GRAMPS provides a combination of automated and manual selections when merging people. Once two people have been merged, the combined person replaces all instances of the previous two people in the database.
==Merge Process==
During the merge process, two people are combined into a single person. It is necessary to select the "resultant person", or the person that remains after the merge is complete. This "resultant person" keeps
its primary data (such as name and GRAMPS ID).
;Primary Name:The "resultant person" keeps its primary name. The name of the other person is added as an alternate name.
;Birth Event:The "resultant person" keeps its primary birth event, unless the birth event does not exist. The other person's birth event is added as the "Alternate Birth" event if the "resultant person" has a birth event. otherwise, it is used as the primary birth event.
;Death Event:The "resultant person" keeps its primary death event, unless the death event does not exist. The other person's death event is added as the "Alternate Death" event if the "resultant person" has a death event. Otherwise, it is used as the primary death event.
;Parents:The user must select the preferred parents. The user may decide if the merged person is to remain as a child in the other set of preferred parents, or in any other set of parents.
;Spouses/Children:The user will be able to select the families in which the person should remain a parent. If the user chooses not to include the merged person in a family, the person will be removed from the family.
;GRAMPS ID:One and only one GRAMPS ID can be selected. The user will be given the option to store the unselected GRAMPS ID as a personal attribute ("Previous GRAMPS ID")
== Automatic Merges==
Many items will be combined from the original two people into the merged person. The user will be able to alter the information later by editing the person. This information includes:
* Addresses
* Source References
* URLs
* Events
* Attributes
* Media Objects
Notes will be combined into a single note, with the text separated by a blank line.

Import from another genealogy program

2008-02-14T08:56:29Z

Sgpsaros: Letter Case Change

[[Category:How do I...]]

There are several ways to import your family tree into GRAMPS from another program. The best way depends on what program you want to copy the information from.

== GRAMPS to GRAMPS==

This is the easy one. The simplest and safest method to move all your information from one GRAMPS program to another on a different computer is to choose ''' File -> Export ''' from the first GRAMPS. Follow the instructions, choosing {{man label|GRAMPS Package}} for the format to save.

Copy the file created by GRAMPS to the destination computer. Then in its GRAMPS, choose ''' File -> Import ''' and select the transferred file.

== Standard GEDCOM as transfer tool==

Most programs for family history can export and import [[GEDCOM]] (.ged) files.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# In GRAMPS, choose ''' File -> Import '''
# Locate the GEDCOM file created by your program, and choose {{man button|Open}}.

{{man warn| Check The Results |Check your data carefully once imported into GRAMPS. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. GRAMPS does its best to do the right thing with non-standard GEDCOM files, but it can't possibly cope with everything.}}

Take special attention that your media files are transferred too, and found by GRAMPS. In the menu ''' Tools -> Utilities ''', you will find the {{man label|Media Manager}}, with which you can change the path of your media objects to the new path if needed.

== Import instructions from different programs ==
=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information. If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps], though it is aimed at advanced users.

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into GRAMPS. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

=== Geneweb ===

GRAMPS can directly import from Geneweb. Choose ''' File -> Import ''', select your Geneweb database and choose {{man button|Open}}.

=== Ancestrologie ===

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into GRAMPS.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

* [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] .. script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

* [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] .. script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

* [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] .. script to fix various non-standard gedcom usage or gedcom extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"
* _ANCES_ORDRE .. considered non-critical, events classification
* _ANCES_XACTE .. non-critical (certificat found = 1)
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. a subdivision of place, is not our place but a division
* XTYPE .. these seem to be OBJE subordinates
* XIDEN .. considered non-critical, media object used for primary media (photo)
* XMODE .. " (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the gedcom 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime
becomes
1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

Add a witness

2008-02-14T08:49:57Z

Sgpsaros: Spelling Correction

This article explains how you add a witness to an event.

[[Category:How do I...]]

== Create the witness as person ==
We strongly suggest to add the witness to the persons in your database. So go to the person view, and add them. In many cases, the only information you have of that the person is his name, and a date on which he was certainly alive.

== Create the event ==
Create the event that has a witness. Eg the ''marriage event'' is added to a family, the ''will'' event to a person. These have the role 'Primary' in relation to the event (which can be set at the top of the event reference editor).

Now, share this same event with the witness if this person is in the
database. However, assign that person a "witness" role in the event. You can do this by going to the witness in the person view, going to the event tab in the person editor, and clicking the index button to select an existing event. Chose the event you just created, and set the role to ''witness''.

== Add all people to the baptize event ==
Normaly you know from a godfather/mother relationship from a baptize record. So create with the person that is baptized a baptize event. This person has role 'Primary' in the event. Now go to the events tab of the godfather/mother person, and click the index button to select an existing event. Select the baptize event you just made, and set the role of the person to godfather/mother.

The event is now a shared event.

== Alternative: don't create a person ==
Some people are averse to adding people to their family tree they only have a name of. First, allow us to point out why you should nevertheless make a person:
* GRAMPS supports this
* You might encounter the same person again in your research. Having him in the person view increases the likelyhood of you recognizing it is the same person as the one that appears as witness.
* The ''Find Duplicates'' tool has more information to work with.

If you nevertheless want to record the witness, without creating a person, use the attribute tab of the event instead. You can add to the event in the attribute tab, the attribute of type ''witness'', and with as value the name.

Alternatively, you can just record this information in a note attached to the event.

== See also ==
* [[Add a godfather-godmother]]

Add a witness

2008-02-14T08:47:09Z

Sgpsaros: Punctuation Correction

This article explains how you add a witness to an event.

[[Category:How do I...]]

== Create the witness as person ==
We strongly suggest to add the witness to the persons in your database. So go to the person view, and add them. In many cases, the only information you have of that the person is his name, and a date on which he was certainly alive.

== Create the event ==
Create the event that has a witness. Eg the ''marriage event'' is added to a family, the ''will'' event to a person. These have the role 'Primary' in relation to the event (which can be set at the top of the event reference editor).

Now, share this same event with the witness if this person is in the
database. However, assign that person a "witness" role in the event. You can do this by going to the witness in the person view, going to the event tab in the person editor, and clicking the index button to select an existing event. Chose the event you just created, and set the role to ''witness''.

== Add all people to the baptize event ==
Normaly you know from a godfather/mother relationship from a baptize record. So create with the person that is baptized a baptize event. This person has role 'Primary' in the event. Now go to the events tab of the godfather/mother person, and click the index button to select an existing event. Select the baptize event you just made, and set the role of the person to godfather/mother.

The event is now a shared event.

== Alternative: don't create a person ==
Some people are averse to adding people to their family tree they only have a name of. First, allow us to point out why you should nevertheless make a person:
* GRAMPS supports this
* You might encounter the same person again in your research. Having him in the person view increases the likelyhood of you recognizing it is the same person as the one that appears as witness.
* The ''Find Duplicates'' tool has more information to work with.

If you nevertheless want to record the witness, without creating a person, use the attribute tab of the event instead. You can add to the event in the attribute tab, the attribute of type ''witness'', and with as value the name.

Alternitively, you can just record this information in a note attached to the event.

== See also ==
* [[Add a godfather-godmother]]

Add a spouse

2008-02-14T08:44:15Z

Sgpsaros: Spelling Correction

[[Category:How do I...]]

= How do I add a spouse to a person? =

GRAMPS views a family as a relationship between two people. This relationship could be ''Married'', ''Unmarried'',
''Civil Union'', or ''Unknown''. The two principle people are labeled as ''Father'' and ''Mother''. However, these can be used to handle childless couples, couples with children, or even same-sex partners. A person can have multiple partners, but each is listed in a different Family.

Partners are added using the Edit Family form. You can bring up this form from two different views - the Relationship View and the Family View.

== Bringing up the Edit Family form from the Relationship View ==
[[Image:Hdi addspouse01.png|right|thumb|500px]]

To add a partner to ''John Smith'' from the Relationship View, make sure that ''John Smith'' is the active person and switch to Relationship View.

Your screen should look something like what is below:

Click on the {{man button|Add Partner}} button (in some earlier releases of GRAMPS, this button was labeled as '''Add Relationship'''). This will bring up the Edit Family form with ''John Smith'' listed as the Father in the family. Had the active person been a female, the person would have been listed as the Mother in the family. The Edit Family form can be seen below.

[[Image:Hdi addspouse02.png]]

Once the Edit Family form is displayed, you can add the partner by clicking one of the two buttons next to the Mother. The first button will allow you to select a person who is already in the database, and the second button will allow you to add a person who is not already in the database.

[[Image:Hdi addspouse03.png]]

== Alternate Method ==

You can also add a partner to a person from the Family View. Select the Family View, and click on the {{man button|Add}} button in the toolbar. This will bring up the Edit Family form with no people selected. In this case you must add both the father (''John Smith'') and the partner.

Add a child

2008-02-14T08:42:19Z

Sgpsaros: Spelling Correction and Grammar

[[Category:How do I...]]

= How do I add a child to a Person or Family? =

Children are not added to a Person. Children are added to a Family. A Child may belong to more than one family.

== Adding a child from the Relationship View ==

A child may be added to a family in several ways, depending on the context.

The Relationship View displays the active person. From this View, you may:

* Add the active person as a child of a family
* Add another person as a child of one of the families in which the active person is a parent

=== Adding the Active Person as a Child in a family ===

You may either add the Active Person as a child of a new family, or as the child of an existing family.

To add the Active Person as a child of a new family, select the {{man button|Add New Parents}} button from the toolbar (in older versions of GRAMPS, this button was simply called ''Add''). This will bring up a new Edit Family form with the Active Person listed as a child. You can then add parents by selecting existing people from the database or by creating new people.

To add the Active Person as a child of an existing family, select the {{man button|Add Existing Parents}} button from the toolbar (in older versions of GRAMPS, this button was simply called ''Share''). This will allow you to select an existing family, and adds the Active Person as a child of that family.

=== Adding a Person as a Child of the Active Person ===

You may add a child to a family in which the Active Person is a parent in one of two ways. If the family already exists, then it will appear in the {{man label|Family}} section of the display. Click on the {{man label|edit}} icon, and the exiting family will be displayed in the Edit Family form.

If the family to which you want to add a child is not displayed, then you should select the {{man button|Add Partner}} button (in older versions of GRAMPS, this button was simply called {{man label|Spouse}}). This will display an Edit Family form in which the Active Person is listed as either the father or the mother. At this point, you may add children and/or a spouse.

== Adding a child from the Family View ==
[[image:edit-rel.png|right|thumb|250px| Family view]]

If you wish to add a child to an existing family from the Family View, find the Family in the displayed list. You may either select the family by clicking on the {{man button|Edit}} button in the toolbar, or double-clicking on the family in the list. This will display the Edit Family form for this person. At this point, you may add the child.

If you wish to add a child to a new family (a family that does not yet exist in the database), click on the {{man button|Add}} button on the toolbar. This will bring up an Edit Family form. On this form, you may add parents and children.

= How do I add twins/triplets/etc? =
When you look at the list of children in a family, those with the same birthdate are obviously twins. But if you don't know the birthdate, or only know the year, you need some other way to indicate the relationship. You can do this by having them share a single birth event.

Take for example, the twins Thomas and Peter. When you create the Birth event for Thomas, make the {{man label|Description}} say "Birth of Thomas and Peter". Then add a reference to that same event to Peter's event list, either by drag and drop, or by using the {{man button|Share an existing event}} button. Set the {{man label|Role}} for that event for both people to "Primary".

Now when you view the event list for either Thomas or Peter, you will see the {{man label|Description}} reminding you that they are twins. And as you add details such as birth date to the birth event for either of them, those details will automatically display for the other as well.

= Adding other informations =
== Adding an occupation or other special informations ==
It is sometimes indicated in old documents that the person's activity was brewer, nails maker, woodchopper, etc. Edit the person and select the Attribute Tab. There add a new Attribute to add & select the wished information. Type what you want to add.

== Related articles ==
*[[Add a spouse]]
*[[Add a godfather-godmother]]
*[[Add a witness]]

Add a child

2008-02-14T08:38:03Z

Sgpsaros: Grammar Correction

[[Category:How do I...]]

= How do I add a child to a Person or Family? =

Children are not added to a Person. Children are added to a Family. A Child may belong to more than one family.

== Adding a child from the Relationship View ==

A child may be added to a family in several ways, depending on the context.

The Relationship View displays the active person. From this View, you may:

* Add the active person as a child of a family
* Add another person as a child of one of the families in which the active person is a parent

=== Adding the Active Person as a Child in a family ===

You may either add the Active Person as a child of a new family, or as the child of an existing family.

To add the Active Person as a child of a new family, select the {{man button|Add New Parents}} button from the toolbar (in older versions of GRAMPS, this button was simply called ''Add''). This will bring up a new Edit Family form with the Active Person listed as a child. You can then add parents by selecting existing people from the database or by creating new people.

To add the Active Person as a child of an existing family, select the {{man button|Add Existing Parents}} button from the toolbar (in older versions of GRAMPS, this button was simply called ''Share''). This will allow you to select an existing family, and adds the Active Person as a child of that family.

=== Adding a Person as a Child of the Active Person ===

You may add a child to a family in which the Active Person is a parent in one of two ways. If the family already exists, then it will appear in the {{man label|Family}} section of the display. Click on the {{man label|edit}} icon, and the exiting family will be displayed in the Edit Family form.

If the family to which you want to add a child is not displayed, then you should select the {{man button|Add Partner}} button (in older versions of GRAMPS, this button was simply called {{man label|Spouse}}). This will display an Edit Family form in which the Active Person is listed as either the father or the mother. At this point, you may add children and/or a spouse.

== Adding a child from the Family View ==
[[image:edit-rel.png|right|thumb|250px| Family view]]

If you wish to add a child to an existing family from the Family View, find the Family in the displayed list. You may either select the family by clicking on the {{man button|Edit}} button in the toolbar, or double-clicking on the family in the list. This will display the Edit Family form for this person. At this point, you may add the child.

If you wish to add a child to a new family (a family that does not yet exist in the database), click on the {{man button|Add}} button on the toolbar. This will bring up an Edit Family form. On this form, you may add parents and children.

= How do I add twins/triplets/etc? =
When you look at the list of children in a family, those with the same birthdate are obviously twins. But if you don't know the birthdate, or only know the year, you need some other way to indicate the relationship. You can do this by having them share a single birth event.

Take for example, the twins Thomas and Peter. When you create the Birth event for Thomas, make the {{man label|Description}} say "Birth of Thomas and Peter". Then add a reference to that same event to Peter's event list, either by drag and drop, or by using the {{man button|Share an existing event}} button. Set the {{man label|Role}} for that event for both people to "Primary".

Now when you view the event list for either Thomas or Peter, you will see the {{man label|Description}} reminding you that they are twins. And as you add details such as birth date to the birth event for either of them, those details will automatically display for the other as well.

= Adding other informations =
== Adding an occupation or other special informations ==
It is sometimes indicated in old documents that the person's activity was brewer, nails maker, woodchoper, ...
Edit the person and select the Attribute Tab. There add a new Attribute to add & select the wished information type you want to add

== Related articles ==
*[[Add a spouse]]
*[[Add a godfather-godmother]]
*[[Add a witness]]

Genealogy basics

2008-02-14T08:32:21Z

Sgpsaros: Clarification

[[Category:Genealogy]]
{{languages|Genealogy basics}}

A few recommendations in the practice of genealogy:

* '''Get the source.''' No matter how much information you some day obtain regarding your family tree, it will only be as good as the sources it came from. Spend the extra effort at the time of discovery to write down all the details.
* '''Research from what you know to what you do not.''' Record everything that is known before making conjecture. The facts at hand can suggest direction for more research. Don't waste time looking through thousands of records hoping for a trail when you have other unexplored options.
* '''Be descriptive.''' Don't limit your record to names, dates and places. Genealogy is not just a study or analysis of what happened, but why it did and how the descendants might have been shaped by the events they went through. Plus, a charming narrative here and there goes a long way to making your family as interesting to others as it is to you.
* '''Be as accurate as you can.''' Don't make assumptions when recording primary information. Write it exactly as you see it, and then use bracketed comments to indicate your insertions, deletions or side comments. Use of the Latin "[sic]" is standard to confirm the accurate transcription of an apparent error. You may find afterwards that what you thought was an abbreviation or misspelling was actually a handwriting variation common to the period or a distinction in two facts with similar spellings.
* '''Get everyone.''' Record all the individuals you find at an event. Families often lived, worked, and worshipped together, so the relatives of an individual can show up at events of siblings, neighbors, and local churches.
* '''Plan your efforts.''' Knowing what you are looking to accomplish saves valuable time. Special trips to see original documents, burial places, libraries, or to interview individuals can not be repeated. Make sure you get everything you come for and record as much as you can while you have the chance. It is unfortunate to return from a trip to find that you omitted an obvious piece of information that passed right under your nose.
* '''Look closely.''' Sometimes re-interpretation of a group of seemingly unconnected pieces of information suddenly reveal a colorful period in the line you never expected. Abrupt changes in a family, such as what happens at a move, immigration, a marriage, death, or birth can point the direction for more research.
* '''Qualify what you record.''' Include your theories or questions about information as you write it. There's nothing wrong with others understanding that you might not be comfortable in the accuracy of a certain fact or hypothesis. It can help others to understand your perspective and bring further information to bear as they try to make sense of questions or research in the same area. Be sure to use brackets or other notation technique to clearly distinguish your comments from those of the source.
* '''Respect the privacy of the living.''' Genealogy is not intended to invade people's privacy by revealing their current health conditions, their social security numbers, and other still-hidden secrets. Be sensitive when writing about issues that some family members might not be comfortable discussing.
* '''Back up your electronic information frequently.''' If you spend countless hours entering information into a genealogy program, take the extra five minutes every now and then to back up the files on a CD. Lable the disc with a description and date using a CD marker (not just any permanent marker!) and store it in a dark, cool and dry place.
* '''Take lots of pictures.''' Use photographs to remember details you don't have time to write down. Pictures of a cemetery stone can be useful, but you may also want a picture of the church that sits in front, a view from the road leading up to the site, views looking toward the stone from various positions, stones adjacent and otherwise interesting, a general overview of the place, even those who accompanied you on the visit. Later, these may help you find it and other areas for more research or simply remind you and others of the experience of that day.

Genealogy basics

2008-02-14T08:20:55Z

Sgpsaros: Word Omission

[[Category:Genealogy]]
{{languages|Genealogy basics}}

A few recommendations in the practice of genealogy:

* '''Get the source.''' No matter how much information you some day obtain regarding your family tree, it will only be as good as the sources it came from. Spend the extra effort at the time of discovery to write down all the details.
* '''Research from what you know to what you do not.''' Record everything that is known before making conjecture. The facts at hand can suggest direction for more research. Don't waste time looking through thousands of records hoping for a trail when you have other unexplored options.
* '''Be descriptive.''' Don't limit your record to names, dates and places. Genealogy is not just a study or analysis of what happened, but why it did and how the descendants might have been shaped by the events they went through. Plus, a charming narrative here and there goes a long way to making your family as interesting to others as it is to you.
* '''Be as accurate as you can.''' Don't make assumptions when recording primary information. Write it exactly as you see it, and then use bracketed comments to indicate your insertions, deletions or side comments. Use of the Latin "[sic]" is standard to confirm the accurate transcription of an apparent error. You may find afterwards that what you thought was an abbreviation or misspelling was actually a handwriting variation common to the period or a distinction in two facts with similar spellings.
* '''Get everyone.''' Record all the individuals you find at an event. Families often lived, worked, and worshipped together, so the relatives of an individual can show up at events of siblings, neighbors, and local churches.
* '''Plan your efforts.''' Knowing what you are looking to accomplish saves valuable time. Special trips to see original documents, burial places, libraries, or to interview individuals can not be repeated. Make sure you get everything you come for and record as much as you can while you have the chance. It is unfortunate to return from a trip to find that you omitted an obvious piece of information that passed right under your nose.
* '''Look closely.''' Sometimes re-interpretation of a group of seemingly unconnected pieces of information suddenly reveal a colorful period in the line you never expected. Abrupt changes in a family, such as what happens at a move, immigration, a marriage, death, or birth can point the direction for more research.
* '''Qualify what you record.''' Include your theories or questions about information as you write it. There's nothing wrong with others understanding that you might not be comfortable in the accuracy of a certain fact or hypothesis. It can help others to understand your perspective and bring further information to bear as they try to make sense of questions or research in the same area. Be sure to use brackets or other notation technique to clearly distinguish your comments from those of the source.
* '''Respect the privacy of the living.''' Genealogy is not intended to invade people's privacy by revealing their current health conditions, their social security numbers, and other still-hidden secrets. Be sensitive when writing about issues that some family members might not be comfortable discussing.
* '''Back up your electronic information frequently.''' If you spend countless hours entering information into a genealogy program, take the extra five minutes every now and then to back up the files on a CD. Write the description of what is on the disc with a CD marker (not just any permanent marker!) and the date and store it in a dark, cool and dry place.
* '''Take lots of pictures.''' Use photographs to remember details you don't have time to write down. Pictures of a cemetery stone can be useful, but you may also want a picture of the church that sits in front, a view from the road leading up to the site, views looking toward the stone from various positions, stones adjacent and otherwise interesting, a general overview of the place, even those who accompanied you on the visit. Later, these may help you find it and other areas for more research or simply remind you and others of the experience of that day.

Add a godfather-godmother

2008-02-13T17:30:51Z

Sgpsaros: Clarification and Grammar Correction

In many cultures children are watched over by a godfather and godmother. Here we explain how to add this relationship to a person.

[[Category:How do I...]]

== Add the godfather/mother ==
We strongly suggest to add the godfather and godmother to the people in your database. To do this go to the person view, and add them. In many cases, the only information you have for a godparent is thier name, and a date on which they were certainly alive.

== Add the relationship ==
The godfather/mother relationship can be added to a person in the associations tab of the person editor. So open the person that is the godchild, go to that tab, and add the godfather and godmother association by selecting godfather/mother and select the godfather/mother from the person list.

== Add all participants and attendees to the baptism ==
Normaly you know from a godfather/mother relationship from a baptism record. So create with the person that is baptized a baptism event. This person has role 'Primary' in the event. Now go to the events tab of the godfather/mother person, and click the index button to select an existing event. Select the baptism event you just made, and set the role of the person to godfather/mother.

The event is now a shared event.

== Alternative: don't create a person ==
Some people are averse to adding people to their family tree they only have a name of. First, allow us to point out why you should nevertheless make a person:
* GRAMPS supports this
* You might encounter the same person again in your research. Having him in the person view increases the likelyhood of you recognizing it is the same person as the one that appears as godfather.
* The ''Find Duplicates'' tool has more information to work with

If you nevertheless want to record the godfather/mother, without creating a person, use the attribute tab of the person instead. You can add to a person the attribute godfather/mother, with as value the name. You can do the same with the baptize event.

Reviews

2008-02-13T17:07:42Z

Sgpsaros: Grammar Correction and Removal of Punctuation for Consistency

[[Category:Documentation]]
Below is the list of the third party reviews of GRAMPS that we know of, in reverse chronological order (most recent first). If you happen to know about a GRAMPS review not listed here, please let us know so that we can add it to the list.

* [http://www.fullcirclemagazine.com Review: GRAMPS geneaology software], by Full Circle Magazine, June 2007 (Go to Downloads, Issue 1, and download the pdf).
* [http://www.linux.com/article.pl?sid=07/01/30/1938242 Track your ancestors with GRAMPS], by Alex Roitman, Linux.com, February 2007
* [http://www.requisitesystems.com/article.php?story=20070105123556883 Software Review - GRAMPS], by Tom Clark, Requisite Systems, January 2007
* [http://www.freesoftwaremagazine.com/articles/genealogy_with_gramps Genealogy with GRAMPS], by Ryan Cartwright, Free Software Magazine, December 2006
* [http://www.linux-mag.com/content/view/2383/ Family Trees with GRAMPS], by Scott Granneman, Linux Magazine, December 2005
* [http://www.linux-magazine.com/issue/59/Gramps_Genealogy.pdf Bloodlines - Managing your family tree with GRAMPS], by Kevin Donnelly, Linux Magazine, October 2005
* [http://www.svpafug.org/gramps_talk.htm GRAMPS for Silicon Valley Computer Genealogy Club], by Robert B. White, Silicon Valley Computer Genealogy Club, August 2005
* [http://eogn.typepad.com/eastmans_online_genealogy/2005/03/gramps_for_linu.html GRAMPS for Linux, UNIX and Macintosh OS X], by Dick Eastman, Eastman's Online Genealogy Newsletter, March 2005
* [http://software.newsforge.com/software/05/01/27/0237203.shtml?tid=130&tid=2 Tracking your GRAMPS], by Joe Barr, Newsforge, January 2005
* [http://www.eogen.com/SoftwareLinux GRAMPS 1.0.0, a Genealogy Program for Linux], by Dick Eastman, Eastman's Online Genealogy Newsletter, December 2004
* [http://tech2.nytimes.com/mem/technology/techreview.html?res=9807E3D8163AF931A15757C0A9629C8B63 From Shared Resources, Your Personal History], by Peter Wayner, The New York Times, April 2004
* [http://media.g4tv.com/video/ttv/thescreensavers/2002/ss021003a_165_0.asf The ScreenSavers]. Several years ago, GRAMPS was featured on the TechTV show, "The ScreenSavers". The video is available on line from G4TV, but it appears to be in a Windows Media format.

{{languages|reviews}}

Census

2008-02-13T16:53:21Z

Sgpsaros: Spelling, Grammar, and Punctuation Corrections

A census is the process of obtaining information about every member of a population. It has been performed from ancient times and continues today by civil leaders, so as to have an idea of the size and composition of the ''subjects''.

[[Category:Sources]]

== Census ==
A census is the determination by an official body of the size of a population of a certain area, most often a country, while at the same time certain other traits are investigated such as age, sex, religion, family situation, profession, etc.
In older times, the work was done by civil servants going from door to door.

Nowadays, many countries no longer organize censuses due to the widespread adoption of identity cards, giving the government all the data it needs. However, previously, a census was of great importance for the organizing authority to determine the size of a constituency, and hence, the amount of taxes collectable.

A census is of great value for genealogical research, being carried out at regular intervals (typically every 10 years), and all family members were documented. This allows to accurately track movements and family changes. However, genealogists view censuses as secondary [[sources]] of information; primary sources of information such as [[birth certificate]]s and even obituaries are viewed as more reliable. Still, census information often provides useful information for genealogists and clues on where to proceed to find further primary source documentation.

Researchers must use care when working with census records. Census taker handwriting varies from excellent to illegible. Information may be inaccurate due to spelling variants by the recorder. Some information, especially ages, may be incorrect due to vanity or confusion on the part of the information provider. Birthplaces may not be accurate depending on which family member gave the information. With these and other cautions in mind, census records can be very informative and useful.

== Through History ==

=== Ancient History ===
Ancient censuses exist, eg by the Persian Empire's military in the year 500-499 BC for issuing land grants, and taxation purposes, and also by the Maurya empire (c. 350-283 BC).

Rome conducted censuses to determine taxes and the Bible relates stories of several. The world's oldest extant census data comes from China during the Han Dynasty. Taken in the fall of 2 AD (57.5 million people were counted).

In the Middle Ages, the most famous census in Europe is the Domesday Book, undertaken in 1086 by William I of England so that he could properly tax the land he had recently conquered. In 1183, a census was taken of the crusader Kingdom of Jerusalem, to ascertain the number of men and amount of money that could possibly be raised against an invasion by Saladin, sultan of Egypt and Syria.

=== Censuses of genealogical interest ===

==== Belgium ====
[[Image:Conscriptielijst Belfeld 20 januari 1812.jpeg|thumb|Census record page, 1812]]
Belgium has had the tradition of doing censuses on average every 10 years, starting in 1846. In total, 14 censuses have been carried out, the last in 1991. See [[Belgium]] for details.

Before the independance, censuses where done by the ruling order, eg 1829 under Dutch rule.

==== Canada ====
The first census in Canada was taken by Jean Talon in 1666, when the age, sex, marital status and occupation of the colony's 3,215 inhabitants were recorded. From then, until 1871, 98 colonial or regional censuses were taken.

The first national census of Canada was taken in 1871 as required by the British North American Act. The act also required that a census be taken every ten years, a practice that was faithfully followed through 1951. Since then, censuses have been taken every five years, following a practice begun in the prairie provinces of Manitoba, Saskatchewan and Alberta in 1906.

Personal details of Canadian censuses are sealed by law for 95 years. Hence, the most current Canadian census currently available for viewing is that of 1911. The censuses of 1851-1852 (regional), 1871, 1881, 1901, 1906 (prairie provinces) and 1911 are available online at various levels of detail. Other censuses are available through Canadian Archive offices.

==== The Netherlands ====
In 1795 the first national census was held, and in 1971 the last. On 22 April 1879 it was decided by law to do a census every 10 years. The census was officially abolished in 1991 due to privacy concerns.

==== United Kingdom ====
The national UK census as it is known today started in 1801, partly to ascertain the number of men able to fight in the Napoleonic wars.
The census has been conducted every ten years since 1801 (except for 1941, when the nation was otherwise occupied) and most recently in 2001. The first four censuses (1801-1831) were mainly statistical (that is, they were mainly headcounts and contained virtually no personal information).

The 1841 Census, conducted by the General Register Office, was the first to record the names of everyone in a household or institution. However, their relationship to the head of the household wasn’t noted, although sometimes this can be inferred from the occupation shown (eg servant). Those under the age of 15 had their proper ages listed, but for those who were older the ages were supposed to be rounded down to the nearest five years, although this rule was not strictly adhered to. Precise birthplaces were not given - at best the birthplace can be narrowed down to the county in which the person was living.

From 1851 onwards, the census shows the exact age and relationship to the head of household for each individual; the place of birth was also listed, but with varying degrees of precision. Sometimes those who were born abroad have the annotation B.S. or British Subject.

The censuses are reasonably accurate. However, ages in particular are frequently shown incorrectly, though often the difference is only one year; in general the younger the individual the more accurate the age shown. Birthplaces often vary from one census to the next: a common error is to show the place where the census was taken as the birthplace, but most of the variations in birthplace can be accounted for by changes in geographical scale (for example, the nearest town being shown instead of the precise village, or a city being shown instead of the relevant suburb).

Inevitably, a small percentage of the population was not recorded for one reason or another, and in some cases the records are missing or damaged (notably in 1861). Furthermore, all censuses of Ireland before 1901 have been lost or destroyed.

All of the British censuses from 1841-1901 have been transcribed and indexed and are available online; there is a joint project between the National Archives of Ireland and Library and Archives Canada to digitize the 1901 and 1911 censuses for the whole of Ireland, and it is possible this will be completed by the end of 2007.

==== United States ====
The United States Constitution mandates that the census be taken at least once every 10 years, and that the number of members of the House of Representatives from each state be determined accordingly. In addition, Census Bureau statistics are used for apportioning federal funding for many social and economic programs.

The first U.S. Census was taken in 1790 by the local U.S. Marshals. Census-takers went door-to-door and recorded the number of people in each household, and the name of the head of the household. Slaves were counted, but for apportionment purposes each counted as only three-fifths of a citizen. American Indians being neither taxed nor considered during apportionment, were not counted. The first census counted 3.9 million people, the 2000 census counted over 281 million people.

By law (enacted on October 5, 1978), census records are sealed for 72 years. Thus, the most recent Census released to the public was the 1930 Census, released in 2002.

Indexes to some of the U.S. Censuses have been produced over the years, making the process of searching old census records much easier. Now, some are available online.

== Examples ==
=== UK census 1881 ===

[[Image:Census image 1.png|thumbnail|The Census return for John Martin in 1881]]

The image to the left shows the page from the 1881 Census of the family of John Martin.

This Census page records the following information about where the census was taken and where the page is located within the Census record:
* Piece number RG 11/2854
* Folio 17
* Page 27
* Civil Parish [or Township]: Wednesbury
* City or Municipal Borough: Not specified
* Municipal Ward: Not specified
* Parliamentary Borough: Wednesbury
* Town, Village or Hamlet: Not specified
* Urban Sanitary District: Wednesbury
* Rural Sanitary District: Not specified
* Ecclesiastical Parish or District: St. Bartholemew

Then each member of the household is listed, with information about them recorded in the following columns:
* Column 1 - No. of schedule, numbered from 1 consecutively per book
* Column 2 - Name of street, place or road, and name or number of house
* Column 3 - Houses; separate columns for inhabited and uninhabited or being built (entered as 'U' or 'B')
* Column 4 - Name and surname
* Column 5 - Relationship to head of family
* Column 6 - Condition; marital status
* Column 7 - Age last birthday; separate columns for males and females
* Column 8 - Rank, profession or occupation
* Column 9 - Where born; county/place
* Column 10 - Whether
** 1 - Deaf & dumb,
** 2 - Blind,
** 3 - Imbecile or idiot,
** 4 - Lunatic

==== [[Recording_UK_Census_data| Learn how to enter this data in GRAMPS 2.0.x]] ====

== External Links and sources ==
*[http://en.wikipedia.org/wiki/Census Wikipedia Census]
*[http://www.familysearch.org/Eng/Search/census/search_census.asp 1880 US census and 1881 censuses of Canada and the UK at familysearch.org]
*[http://automatedgenealogy.com Canadian censuses of 1851-1852, 1901, 1906 and 1911 at automatedgenealogy.com]
*[http://www.collectionscanada.gc.ca/archivianet/index-e.html Census Research Tools at the Canadian Archives]

Translating the Gramps User manual

2008-02-13T16:11:11Z

Sgpsaros: Typo and Grammar Correction

We explain how you can translate the GRAMPS manual, as offered [[User_manual|here]] in html and pdf format. This manual is also available from within GRAMPS using the F1 key, or from the help menu.
[[Category:Developers/Localization]][[Category:Developers/General]]

==Getting started==
Translating GRAMPS' documentation into a new language is a long, tedious, and boring process, just like with any complex text :-) However, the good news is that since version 2.2 the translations for our user manual are maintained using po files, just like with translating the [[Translating GRAMPS|UI strings]]. Technically, this amounts to three simple steps:
# obtaining the text to be translated,
# translating the text, and
# getting the translated file uploaded into gramps SVN repository.

==Obtaining the text==
* Obtain the source tree, either from GRAMPS SVN repository (see [[Brief introduction to SVN]], or from the [[Installation|released source tarball]] on sourceforge.
* Under <code>help</code> directory, there is a file named <code>gramps.pot</code>. Copy it to <code>help/zz/zz.po</code> (where <code>zz</code> is your language code).

==Translating==
With the po file ready, you can start translating.
* Use any editor or a po-file tool like [http://www.gtranslator.org GTtranslator] or [http://kbabel.kde.org/ KBabel] to translate strings in the po-file
* Figures: localized screenshots are nice in the localized manual
** If you can provide figures on your own this is great. Place them in the directory <code>help/zz/figures</code> (<code>zz</code> is your language code). Bear in mind that screenshots have to be '''indexed PNGs, not more than 510 pixels wide''', in order to satisfy the GNOME Documentation Style Guide.
** For screenshot: also make sure the print size fits on an A4/USletter printout in pdf. You can check this with GIMP in View Menu --> Info window
** A command to take screenshots that works for me, is by using imagemagick (should be installed with every linux distribution, if not, get it): <pre>import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png </pre>This creates a fully compressed (-quality 100), trimed screenshot after 2 seconds (-delay 200) of size 500 pixels wide (-resize 500), with resolution 100 (-density 100x100), with the window frame attached (-frame) in RGB mode (-channel RGB) and bbp 24 (-depth 8, for some reason on my machine depth 8 corresponds with bbp 24 and not 8). This creates images of 5 inches wide, which fit nicely on a book page, as well as on a html page.
** If it's too much trouble for you, just let us know and perhaps somebody else will do it for you. Fortunately, one does not have to speak the language to make screenshots :-)

==Uploading you work into gramps SVN==
All the files you have translated will need to be checked into GRAMPS SVN repository, under the <code>help/zz</code> directory. Also, certain makefiles will need to be modified to enable proper building and installation of your manual translation. Check your work into SVN if you have the permissions (add new files as necessary and modify Makefiles, if you know what to do) or oterwise, email it to [[Contact|Alex Roitman]].
* To quickly test your translation once the makefiles are updated to include your language, build the translated manual from the po file by running in the top-level source directory <code> make</code> and call up your manual with the gnome help browser: <pre>yelp help/xx/gramps.xml</pre>

==Making a html or pdf manual==
See [[Manual Generation]]. You need not do this, somebody of the developer team will generate the official manual and upload to the gramps-project website on [[User_manual]]. If you feel however that the version on the website is too old, mail the devel list, asking to upload a new version.

If you see strange things on the official version, generate the manual yourself locally as indicated in [[Manual Generation]], and see if you can improve on the methodology.

Genealogy Glossary

2008-02-13T16:04:38Z

Sgpsaros: Grammar Correction

Here you find a glossary of genealogical terms. For terms appearing in GRAMPS see [[GRAMPS Glossary]].

[[Category:Genealogy]]

;Anglicisation:
: process of making something English

;DNA:
# acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid
# a nucleic acid that carries genetic information

;GEDCOM:
# acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication
# a format for exchanging genealogy data

;matronym:
: personal name based on the name of one's mother

;patronym:
: personal name based on the name of one's father

;Romanization:
: linguistic representation of a word in the Roman (Latin) alphabet

{{languages|Genealogy Glossary}}

Indicate a divorce

2008-02-13T16:01:15Z

Sgpsaros: Grammar Correction

[[Category:How do I...]]

== How do I represent a divorce? ==

''I want to indicate that two people are divorced, yet GRAMPS does not have a Relationship type of Divorced. How do I represent this?''

GRAMPS does not consider ''Divorced'' to be a relationship type. Instead, it is an event that terminates the relationship. If two people are divorced, it does not change the fact that they had a relationship type of ''Married''. Divorce, like Death, is one way in which a marriage is terminated. Just as the death of a spouse does not change the fact that two people were married, a divorce does not change the fact that two people were married.

So to represent a marriage that ended in divorce:

# Create a family
# Add both spouses
# Set the relationship to ''Married''
# Add an Event of type ''Divorce''

Keyboard shortcuts

2008-02-13T15:57:49Z

Sgpsaros: Grammar Correction

Keyboard shortcuts can make your life easier.
[[Category:Tips]][[Category:How do I...]]

== General keybindings ==

The keybindings as available in GRAMPS, can be found in the [[user manual|User's Manual]].

== Speed up searching ==
If you are on a list view in GRAMPS, you can search an entry by simply typing the beginning letters.

;In the person view, if you want person Duchatel.:'''Solution:''' Click on the list view (clicking on a person will do). Now type ''Du'', and the list view will jump to people with the last name starting with ''Du''.

Note: The same can be achieved with the key combination <code>CTRL+F</code>, on the list view.

Documentation

2008-02-13T15:42:16Z

Sgpsaros: Change in Letter Case

__NOTOC__

This page enables you to find all the information you need about how to use GRAMPS. It covers an introduction to the main features of GRAMPS, the User Manual, reviews, tips, tutorials and much more.

== New Users ==

GRAMPS helps you track your family tree. It allows you to store, edit, and research genealogical data. GRAMPS attempts to provide all of the common capabilities of other genealogical programs, but, more importantly, to provide an additional capability of integration not common to these programs. This is the ability to input any bits and pieces of information directly into GRAMPS and rearrange/manipulate any/all data events in the entire data base (in any order or sequence) to assist the user in doing research, analysis and correlation with the potential of filling relationship gaps.

=== Features ===

* [[GRAMPS:About|About]]
* [[Features]]
* [[Screenshots]]
* [[Sample_reports|Examples of Reports]]
* [[Reviews]] GRAMPS has been [[Reviews|reviewed]] by a number of different on-line journals, including genealogy publications, Linux publications, and even some reviews from the point of view of Windows or Mac users.

=== User manual ===

There is a comprehensive [[User manual]] which is available in English, French, Dutch and Slovak. There is also a [[FAQ]].

== Existing Users ==

=== Tips and Tutorials ===

'''Tips''' : [[Keyboard shortcuts]] - '''[[:Category:Tips|More]]'''

'''Tutorials''' : [[Recording UK Census data]] - [[Howto: Make a genealogy website with GRAMPS|Make a website with GRAMPS]] - [[Howto: Change the language of reports|Reports in another language]]- [[Add Table of Contents or Index to Ooo reports|Add Table of Contents to reports]] - '''[[:Category:Tutorials|More]]'''

'''Examples''' : [[Example filters|Filters]] - '''[[:Category:GRAMPS Examples|More]]'''

'''GRAMPS logic''' : [[Merging People]] - '''[[:Category:GRAMPS Logic|More]]'''

=== GRAMPS terminology ===

GRAMPS uses the language of genealogists. Sometimes this might be a bit daunting. What follows gives an overview of terms used, with the meaning as used in GRAMPS, and with suggestions on how to work with these objects.
* [[Events in GRAMPS|Events]] - What is an event, how to use it, which events are predefined?
* [[Sources in GRAMPS|Sources]] - What is meant by a source, how to use a source reference?
* [[Repositories in GRAMPS|Repositories]] - Is your home a repository? The web?
* [[Places in GRAMPS|Places]] - How should you organize your places?
* [[Category:GRAMPS terminology|Overview of terms]] - Address, call name, ...

== I can't find what I'm looking for ==

If you have any questions on GRAMPS that are not solved by searching this wiki, then the [http://sourceforge.net/mail/?group_id=25770 Mailing Lists] are a good place to find help. Search the achives of the gramps-users mailing list first, and if you cannot find the answer, send your question to gramps-users@lists.sourceforge.net.

== Other references ==

'''[[GRAMPS:About|GRAMPS]]''' is an open source genealogical software program. It requires the help of it's users to make manuals and tutorials. Fortunately, many users have contributed to the project, by adding tips, tutorials, user guides and examples to this wiki. Your continued involvement to this wiki is required to allow new users to quickly understand GRAMPS, and find answers to their usability questions.

* If there is a particular point that you feel should be documented (or where the existing documentation should be improved) then please look at [[How you can help]]. Perhaps you can write a tutorial on a specific aspect, or improve this wiki, or help with the User Manual.

* For help on genealogy in general, see the [[Portal:Genealogy|Genealogy Portal]].

* If you want to help with coding, see the [[Portal:Developers|Developers Portal]], where you find tutorials to create your own reports.

* [[Installation]] See the main Installation page link in the sidebar.

* [[Support]] GRAMPS is a complex product that is developed entirely by volunteer effort.

* [[Contact|Contacting us]] Reporting bugs, requesting enhancements, the mailing lists, IRC and the GRAMPS Forum.

'''[[:Category:Documentation|All Documentation]]'''

Documentation

2008-02-13T15:36:30Z

Sgpsaros: Change in Letter Case

__NOTOC__

This page enables you to find all the information you need about how to use GRAMPS. It covers an introduction to the main features of Gramps, the User Manual, reviews, tips, tutorials and much more.

== New Users ==

GRAMPS helps you track your family tree. It allows you to store, edit, and research genealogical data. GRAMPS attempts to provide all of the common capabilities of other genealogical programs, but, more importantly, to provide an additional capability of integration not common to these programs. This is the ability to input any bits and pieces of information directly into GRAMPS and rearrange/manipulate any/all data events in the entire data base (in any order or sequence) to assist the user in doing research, analysis and correlation with the potential of filling relationship gaps.

=== Features ===

* [[GRAMPS:About|About]]
* [[Features]]
* [[Screenshots]]
* [[Sample_reports|Examples of Reports]]
* [[Reviews]] Gramps has been [[Reviews|reviewed]] by a number of different on-line journals, including genealogy publications, Linux publications, and even some reviews from the point of view of Windows or Mac users.

=== User manual ===

There is a comprehensive [[User manual]] which is available in English, French, Dutch and Slovak. There is also a [[FAQ]].

== Existing Users ==

=== Tips and Tutorials ===

'''Tips''' : [[Keyboard shortcuts]] - '''[[:Category:Tips|More]]'''

'''Tutorials''' : [[Recording UK Census data]] - [[Howto: Make a genealogy website with GRAMPS|Make a website with GRAMPS]] - [[Howto: Change the language of reports|Reports in another language]]- [[Add Table of Contents or Index to Ooo reports|Add Table of Contents to reports]] - '''[[:Category:Tutorials|More]]'''

'''Examples''' : [[Example filters|Filters]] - '''[[:Category:GRAMPS Examples|More]]'''

'''GRAMPS logic''' : [[Merging People]] - '''[[:Category:GRAMPS Logic|More]]'''

=== GRAMPS terminology ===

GRAMPS uses the language of genealogists. Sometimes this might be a bit daunting. What follows gives an overview of terms used, with the meaning as used in GRAMPS, and with suggestions on how to work with these objects.
* [[Events in GRAMPS|Events]] - What is an event, how to use it, which events are predefined?
* [[Sources in GRAMPS|Sources]] - What is meant by a source, how to use a source reference?
* [[Repositories in GRAMPS|Repositories]] - Is your home a repository? The web?
* [[Places in GRAMPS|Places]] - How should you organize your places?
* [[Category:GRAMPS terminology|Overview of terms]] - Address, call name, ...

== I can't find what I'm looking for ==

If you have any questions on GRAMPS that are not solved by searching this wiki, then the [http://sourceforge.net/mail/?group_id=25770 Mailing Lists] are a good place to find help. Search the achives of the gramps-users mailing list first, and if you cannot find the answer, send your question to gramps-users@lists.sourceforge.net.

== Other references ==

'''[[GRAMPS:About|GRAMPS]]''' is an open source genealogical software program. It requires the help of it's users to make manuals and tutorials. Fortunately, many users have contributed to the project, by adding tips, tutorials, user guides and examples to this wiki. Your continued involvement to this wiki is required to allow new users to quickly understand GRAMPS, and find answers to their usability questions.

* If there is a particular point that you feel should be documented (or where the existing documentation should be improved) then please look at [[How you can help]]. Perhaps you can write a tutorial on a specific aspect, or improve this wiki, or help with the User Manual.

* For help on genealogy in general, see the [[Portal:Genealogy|Genealogy Portal]].

* If you want to help with coding, see the [[Portal:Developers|Developers Portal]], where you find tutorials to create your own reports.

* [[Installation]] See the main Installation page link in the sidebar.

* [[Support]] Gramps is a complex product that is developed entirely by volunteer effort.

* [[Contact|Contacting us]] Reporting bugs, requesting enhancements, the mailing lists, IRC and the Gramps Forum.

'''[[:Category:Documentation|All Documentation]]'''

Sources

2008-02-13T15:30:39Z

Sgpsaros: English Correction

{{languages|sources}}

Sources play a key role in [[genealogy]].

[[Category:Sources]]

==Definition==
A source is a text (sometimes oral presentation, audio recording, video recording) from which (genealogical) information is derived.

Scientifically, one will make 3 distinctions:
#Primary source : text which is a firsthand written evidence of history, made at the time of the [[event]] by someone who has seen it happen. Eg: diaries, certificates, newspapers, ...
#Secondary source : Written accounts of history based upon the evidence from primary sources and other secondary sources, offering commentary and analysis. Eg: history books, genealogical publications,...
#Tertiary source : selection and compilation of primary and secondary sources. Eg: library catalogue, bibliographies, ...

== Most important genealogical sources ==

=== Official documents ===
* [[Birth certificate]]s
* Still births
* Marriage certificates
* Divorces
* Death certificates
* Official name changes
* Naturalization records

=== Religious documents ===
* [[Baptism record]]s
* Marriage records
* Burial records

=== Legal documents ===
* Court cases
* Notary documents
* Probate records

=== Migration ===

* Passenger lists
* Record of landing

=== Residences ===
* [[Census]] records
* Property documents
* Phone books
* City directories

=== Final resting places ===
* Cemetery list of interments
* War graves

=== Military ===
* Enlistment lists
* [[Draft lottery|Draft lottery documents]]
* Medals
* MIA - Missing in Action
* Deserters
* Pension applications

=== Personal Documents ===
* Diaries
* Correspondence
* Household bills

== Other Possible Sources ==
* Bibles
* Stories
* Publications
* Photos
* Employment information
* Medical records
* DNA
* Voter registration records
* Genealogical society records

Portal:Genealogy

2008-02-13T15:29:42Z

Sgpsaros: English Correction

{{languages|Portal:Genealogy}}

Welcome to the Genealogy Research Portal!

==Good practises for genealogical research==
* [[Genealogy basics]]

==Genealogical sources==
'''[[Sources]]''': [[baptism record]] - [[census]]

==Genealogy resources==
* [[Other genealogy software]] - programs to track your ancestry
* [[Other genealogy tools]] - tools to help you make a website, a genealogical tree, ...
* [[Resource and related sites]]
* [[Existing reports]]

==Around genealogy==
* Dictionaries:
**[[Latin_words_and_expressions/A|Latin in genealogy]]
* Storage of archives and documents management
**[[OCR|Optical character recognition]]
* Pictures:
**[[Improving picture quality]]: How-to on making pictures of documents more readable.

[[Category:Events]] [[Category:Places]] [[Category:Sources]] [[Category:Repositories]] [[Category:Genealogy|All articles]]

Baptise record

2008-02-13T15:25:47Z

Sgpsaros: Correction of English

Baptism records are an important source of genealogical information. In many countries, churches were the only institutions keeping records of baptisms, and hence of births.

[[Category:Sources]]

== The Baptism record ==
This record is normally a very short piece of text. However, important information can be learned from it: name of child, date of baptism, date of birth, parents' names, witnesses names, place of residence. Furthermore, from the signatures one can determine that the parents/witnesses had basic schooling.

== Through history ==
===Catholic Church===
The Catholic Church started to keep registries for the sacraments of baptism and marriage. This started in the 14th century in Italy and France. The oldest known registries are kept in the city of Geiry (France) and date back to 1334.

The Catholic Church decided during the Council of Trente on November 11, 1563 on the rules concerning the keeping of parish registries for baptisms and marriages. Since 1614 death records also became obligatory. These dates are hence the earliest dates one can realistically attempt to obtain in the creation of a family tree.

Note that the introduction of a civil office occurs in general in the period following the French Revolution. These documents, [[birth certificate]]s, are in general more easy to track than baptism records.

== Examples ==
=== 1748, Belgium ===
[[Image:Birthcert-1748-belgium.png|thumb]]
The image to the left is a birth certificate from 1748, found in a parish registry of a parish near Ghent, Belgium. The Latin text reads roughly:

:<code>10 jan bap(tizavi) adrianuam jacobam f(ili)am adriani van poeke et isabelle raeman conj(ugum) natam hodie 3 pom(eridiana):susc(eptores):Jacobus De geest et Adriana Meirlaens. J.B. van Hecke, vicep(astor)</code>

It's English translation is:
:<code>10 january I baptised Adriana Jacoba, daughter of Andreas Van Poecke and Isabella Raeman, married couple, born today 3 o'clock in the afternoon, witnesses Jacobus De Geest and Adriana Meirlaens. J.B. Van Hecke, vicepastor.</code>

Furthermore, the top of the page in the registry lists 1748.

From these few lines of text, a lot of information is available:
* the repository where the source is found
* the source where this record is located
* the page/number of the entry (if present), and the effective text (in original language and translated)
* father's name
* mother's name
* child's name
* date of baptism (and parish where it is performed)
* date and hour of birth (place of birth can sometimes be inferred)
* names of two witnesses
* name of priest

Screenshots

2008-02-13T14:37:57Z

Sgpsaros: Change in Letter Case

{{stub}}
== Main window ==
Views of the Main window in GRAMPS, following the text links will open a more detailed description.
<gallery>
Image:Mainwin.png|[[people screenshot|Person (People)]]
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]
Image:Gramps_sidebaricons_filter.png| People View with small left sidebar and filter sidebar
</gallery>

== Edit windows ==
<gallery>
Image:Edit-person.png|Edit Person
Image:Edit-media.png|Edit Media Properties
Image:Edit-family.png|Edit Family
Image:Edit-ev-ref.png|Edit Event Reference
</gallery>

==Edit Preferences ==
Tabs in Edit->Preferences dialog box, Version 2.2.6
<gallery>
Image:EditPreferencesGeneral226.png|General
Image:EditPreferencesDisplay226.png|Display
Image:EditPreferencesNameDisplay226.png|Name
Image:EditPreferencesIDFormats226.png|ID Formats
Image:EditPreferencesWarnings226.png|Warnings
Image:EditPreferencesResearcher226.png|Researcher
Image:EditPreferencesMarkerColors226.png|Marker Colors
</gallery>

[[Category:screenshots| ]]

Features

2008-02-13T04:53:46Z

Sgpsaros: Spelling Correction

{{cleanup}}
[[Category:Documentation]]
==Features of GRAMPS 2.2==
* Easy to use. A well designed user interface makes entering data easy. Browser like controls allow you to navigate your family tree with ease.
* Nine different views for navigating your family:
{|cellspacing="0" border="1" align="center" width="95%"
|- valign="top"
|style="padding: 0.3em;" |'''People''' — A list of all individuals in the database. Filter the display using preset filters or a custom filter.[[Image:Mainwin.png|center|thumb|300px]]
|style="padding: 0.3em;" |'''Relationship''' — Display a family of parents, grandparents and children with the birth/death dates and relationships. Navigate to nearby relatives with a single click.[[Image:Relationship 2 2.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Family list''' — List all families in a single view. Double-click on each to edit, add notes, and to see parents and children in each family.[[Image:Family_List.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Pedigree''' — Display the family in the traditional pedigree view. Hold the mouse over individuals to see more information about them and to move to more distant parts of the tree[[Image:Pedigree.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Events'''[[Image:Events.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Sources''' — See all referenced sources in a single view. Double-click on each to edit, add notes, and to see which individuals reference the source.
|- valign="top"
|style="padding: 0.3em;"|'''Places''' — View all places referred to in the database and sort the list by half a dozen headings such as City, County or State.
|style="padding: 0.3em;"|'''Media''' — List all forms of media referenced by the database. Can be graphic images, videos, sound clips, spreadsheets, documents, etc.
|- valign="top"
|style="padding: 0.3em;"|'''Repository''' — List all source repositories in a single view. Double-click on each to edit, add notes, and to see which sources reference the repository.
|style="padding: 0.3em;"|
|}
* Bookmark favorite individuals for quick access. (The number able to be marked is unlimited)
* Custom filters. In addition to the numerous preset filters, create any number of selections based on interesting facts about your family to use for reports and data exports.
* Link any media or filetype to your GRAMPS family tree. Choose between copying or linking the file to the database.
* Privacy options allow restriction of any information marked with this option or information about living individuals. Data marked with this option can be excluded in reports and data exports.
* Multiple calendars and date ranges are supported. You can convert between Gregorian, Julian, Hebrew, French republican, Perzian and Islamic calendars from within GRAMPS via the Date selection window, and you can use fuzzy dates like about 1874, estimated 1905, ...
* Multiple languages and cultures support is mature.
** Translations exist for 15 languages (See the translations page)
** GRAMPS has been designed so that new translations can easily be added with little development effort. If you are interested in participating please contact us.
** Relationship calculators available in four languages
** Full unicode support. Characters for all languages are properly displayed.

==Reports==
Generate brief or detailed reports for the ancestors or descendants of an individual.

* Multiple styles of reports are currently available by default. Users can also create their own custom styles.
* Eight output formats are supported by GRAMPS: PDF, AbiWord, KWord, OpenOffice Writer, HTML, Rich Text Format (RTF), Latex, and plain text.
* Custom reports can be created by advanced users under the "plugin" system which allows the sharing of custom report styles between users.
* Book report allows the user to collect a variety of reports in a single document, which in turn is easier to distribute.

Charts and Graphs - Create graphical Ancestor and Descendent charts in several formats.
[[Image:RelationshipChartDescendants.png|right|thumb|200px|An example chart]]

* Box and Fan charts are available, see eg [[Howto: Make a relationship chart | here]].
* Multiple formats are supported by GRAMPS for charts and graphs: OpenOffice Draw, PDF, PostScript, and SVG.
* Custom charts can be created by users. We hope to add more in the near future through the contributions of users and developers.

Export to Web Pages -Select the entire database, family lines or selected individuals to a collection of web pages ready for upload to the World Wide Web.

==Tools==
A rich set of tools includes operations such as checking database for errors and consistentcy, as well as the research and analysis tools such as event comparison, duplicate people finding, interactive descendant browser, and others.

* Merge. Combine two seperate people into one. Very useful combining two databases with overlapping people.
* Soundex generator. Generate the standard codes commonly used in genealogy to compare similar sounding names even though spelled differently.

==File formats==
Import/Export support for serveral different formats.

* GEDCOM import and export. Extensive support for the industry standard GEDCOM version 5.5 so you can exchange GRAMPS information to and from users of most other genealogy programs.
* GRAMPS package import and export. A compressed file containing your family tree data and any other files used. Useful for backup or sharing with other GRAMPS users.
* Export to CD Burner. Export data and media directly to the GNOME file manager (Nautilus) for burning to CD.
* Web Family Tree export. Web Family Tree (WFT) allows you to display your family tree online with only a single file, instead of many html files the web page report generates. See [http://www.simonward.com/cgi-bin/page.pl?family/tree their homepage] for more information.

==Community==

* Active community involvement. Many current GRAMPS users contribute reports, suggestions, and feedback to the developers through various public mailing lists. The program is only a few years old and already has wide capabilities and features.
* Active development effort. New versions already in testing use an advanced database design that guarantee very fast access to many thousands of entries in the database. Other new features are being designed and coordinated by several active developers. Many additional participants assist through the mailing lists. Group effort shapes and tests GRAMPS constantly improving functionality and usability.
* Portable. GRAMPS is written in a computer language called Python using GTK and GNOME libraries. While only well supported in certain Unix and Linux environments, these are multi-platform development libraries, meaning that GRAMPS can be ported to any platform the required libraries are ported to.
* Free Software/Open Source development model means GRAMPS can be extended by any programmer since all of the source code is freely available under its license.
* GRAMPS is freely distributable under the GPL!

== Checklist ==
{| {{Prettytable}} style="width:235px; font-size:90%;"
|-
| ''' '''
|bgcolor="#8DA7D6" style="line-height:2.25em;"|'''GRAMPS 2.2.9'''
|-
|bgcolor="lightgray"|Price
|style="color:red;" |Free
|-
|Open Source
|yes
|-
|style="color:blue;" colspan="2"| '''Views'''
|-
|bgcolor="lightgray"|Individual
|Yes
|-
|bgcolor="lightgray"|Family
|Yes
|-
|bgcolor="lightgray"|Pedigree
|Yes
|-
|bgcolor="lightgray"|Source
|Yes
|-
|bgcolor="lightgray"|Event
|Yes
|-
|bgcolor="lightgray"|Place
|Yes
|-
|bgcolor="lightgray"|Media
|Yes
|-
|bgcolor="lightgray"|Repository
|Yes
|-
|bgcolor="lightgray"|Notes
|No
|-
|style="color:blue;" colspan="2"| '''Chart Types'''
|-
|style="color:blue;" colspan="2"| '''Reports'''
|-
|bgcolor="lightgray"|Books
|Yes
|-
|bgcolor="lightgray"|Family Group Sheets
|Yes
|-
|bgcolor="lightgray"|Individual Summary
|Yes
|-
|bgcolor="lightgray"|Henry Numbering
| /
|-
|bgcolor="lightgray"| D'Aboville numbering
| /
|-
|bgcolor="lightgray"|Calendar
|Yes
|-
|style="color:blue;" colspan="2"| '''Database'''
|-
|bgcolor="lightgray"|Native Database
|Yes (Berkeley DB)
|-
|bgcolor="lightgray"|Unlimited Size
|Yes (tested upto 250.000 people)
|-
|bgcolor="lightgray"| Open multiple Databases at once
|No (works for viewing, not supported !!)
|-
|style="color:blue;" colspan="2"| '''Multimedia'''
|-
|bgcolor="lightgray"|Audio
|Yes
|-
|bgcolor="lightgray"|Video
|Yes
|-
|bgcolor="lightgray"|Images
|Yes
|-
|style="color:blue;" colspan="2"| '''Remote'''
|-
|bgcolor="lightgray"|Remote Access
|Yes (linux, over X connection)
|-
|bgcolor="lightgray"|Collaboration
|No
|-
|style="color:blue;" colspan="2"| '''International'''
|-
|bgcolor="lightgray"|Unicode
|Yes
|-
|bgcolor="lightgray"|Languages
|English, Czech, Danish, German, Esperanto, Spanish, Finnish, French, Hungarian, Italian, Lithuanian, Norwegian, Dutch, Brazilian Portuguese, Russian, Slovak, Swedish
|-
|style="color:blue;" colspan="2"| '''Compatibility'''
|-
|bgcolor="lightgray"|GEDCOM 5.5
|Import/Export
|-
|bgcolor="lightgray"|HTML
|Export
|-
|bgcolor="lightgray"|XML
|GRAMPS XML
|-
|bgcolor="lightgray"|Backup
|On Exit, import possible
|-
|style="color:blue;" colspan="2"| '''Platform'''
|-
|bgcolor="lightgray"|Linux
|yes
|-
|bgcolor="lightgray"|Windows
|Yes (limited support)
|-
|bgcolor="lightgray"|Mac
|yes (user compile/install)
|-
|bgcolor="lightgray"|BSD
|yes (user compile/install)
|-
|style="color:blue;" colspan="2"| '''Additional Features'''
|-
|bgcolor="lightgray"|Match/Merge
|yes
|-
|bgcolor="lightgray"|Multiple relationships (adoptive-foster)
|yes
|-
|bgcolor="lightgray"|Relationship calculator
|yes
|-
|bgcolor="lightgray"|Soundex calculator
|yes
|-
|bgcolor="lightgray"|Spell check in notes
|yes
|-
|bgcolor="lightgray"|3th party plugin infrastructure
|yes
|-
|bgcolor="lightgray"|Check for Program Update
|No
|}

Features

2008-02-13T04:06:17Z

Sgpsaros: Spelling Correction

{{cleanup}}
[[Category:Documentation]]
==Features of GRAMPS 2.2==
* Easy to use. A well designed user interface makes entering data easy. Browser like controls allow you to navigate your family tree with ease.
* Nine different views for navigating your family:
{|cellspacing="0" border="1" align="center" width="95%"
|- valign="top"
|style="padding: 0.3em;" |'''People''' — A list of all individuals in the database. Filter the display using preset filters or a custom filter.[[Image:Mainwin.png|center|thumb|300px]]
|style="padding: 0.3em;" |'''Relationship''' — Display a family of parents, grandparents and children with the birth/death dates and relationships. Navigate to nearby relatives with a single click.[[Image:Relationship 2 2.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Family list''' — List all families in a single view. Double-click on each to edit, add notes, and to see parents and chidren in each family.[[Image:Family_List.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Pedigree''' — Display the family in the traditional pedigree view. Hold the mouse over individuals to see more information about them and to move to more distant parts of the tree[[Image:Pedigree.png|center|thumb|300px]]
|- valign="top"
|style="padding: 0.3em;"|'''Events'''[[Image:Events.png|center|thumb|300px]]
|style="padding: 0.3em;"|'''Sources''' — See all referenced sources in a single view. Double-click on each to edit, add notes, and to see which individuals reference the source.
|- valign="top"
|style="padding: 0.3em;"|'''Places''' — View all places referred to in the database and sort the list by half a dozen headings such as City, County or State.
|style="padding: 0.3em;"|'''Media''' — List all forms of media referenced by the database. Can be graphic images, videos, sound clips, spreadsheets, documents, etc.
|- valign="top"
|style="padding: 0.3em;"|'''Repository''' — List all source repositories in a single view. Double-click on each to edit, add notes, and to see which sources reference the repository.
|style="padding: 0.3em;"|
|}
* Bookmark favorite individuals for quick access. (The number able to be marked is unlimited)
* Custom filters. In addition to the numerous preset filters, create any number of selections based on interesting facts about your family to use for reports and data exports.
* Link any media or filetype to your GRAMPS family tree. Choose between copying or linking the file to the database.
* Privacy options allow restriction of any information marked with this option or information about living individuals. Data marked with this option can be excluded in reports and data exports.
* Multiple calendars and date ranges are supported. You can convert between Gregorian, Julian, Hebrew, French republican, Perzian and Islamic calendars from within GRAMPS via the Date selection window, and you can use fuzzy dates like about 1874, estimated 1905, ...
* Multiple languages and cultures support is mature.
** Translations exist for 15 languages (See the translations page)
** GRAMPS has been designed so that new translations can easily be added with little development effort. If you are interested in participating please contact us.
** Relationship calculators available in four languages
** Full unicode support. Characters for all languages are properly displayed.

==Reports==
Generate brief or detailed reports for the ancestors or descendants of an individual.

* Multiple styles of reports are currently available by default. Users can also create their own custom styles.
* Eight output formats are supported by GRAMPS: PDF, AbiWord, KWord, OpenOffice Writer, HTML, Rich Text Format (RTF), Latex, and plain text.
* Custom reports can be created by advanced users under the "plugin" system which allows the sharing of custom report styles between users.
* Book report allows the user to collect a variety of reports in a single document, which in turn is easier to distribute.

Charts and Graphs - Create graphical Ancestor and Descendent charts in several formats.
[[Image:RelationshipChartDescendants.png|right|thumb|200px|An example chart]]

* Box and Fan charts are available, see eg [[Howto: Make a relationship chart | here]].
* Multiple formats are supported by GRAMPS for charts and graphs: OpenOffice Draw, PDF, PostScript, and SVG.
* Custom charts can be created by users. We hope to add more in the near future through the contributions of users and developers.

Export to Web Pages -Select the entire database, family lines or selected individuals to a collection of web pages ready for upload to the World Wide Web.

==Tools==
A rich set of tools includes operations such as checking database for errors and consistentcy, as well as the research and analysis tools such as event comparison, duplicate people finding, interactive descendant browser, and others.

* Merge. Combine two seperate people into one. Very useful combining two databases with overlapping people.
* Soundex generator. Generate the standard codes commonly used in genealogy to compare similar sounding names even though spelled differently.

==File formats==
Import/Export support for serveral different formats.

* GEDCOM import and export. Extensive support for the industry standard GEDCOM version 5.5 so you can exchange GRAMPS information to and from users of most other genealogy programs.
* GRAMPS package import and export. A compressed file containing your family tree data and any other files used. Useful for backup or sharing with other GRAMPS users.
* Export to CD Burner. Export data and media directly to the GNOME file manager (Nautilus) for burning to CD.
* Web Family Tree export. Web Family Tree (WFT) allows you to display your family tree online with only a single file, instead of many html files the web page report generates. See [http://www.simonward.com/cgi-bin/page.pl?family/tree their homepage] for more information.

==Community==

* Active community involvement. Many current GRAMPS users contribute reports, suggestions, and feedback to the developers through various public mailing lists. The program is only a few years old and already has wide capabilities and features.
* Active development effort. New versions already in testing use an advanced database design that guarantee very fast access to many thousands of entries in the database. Other new features are being designed and coordinated by several active developers. Many additional participants assist through the mailing lists. Group effort shapes and tests GRAMPS constantly improving functionality and usability.
* Portable. GRAMPS is written in a computer language called Python using GTK and GNOME libraries. While only well supported in certain Unix and Linux environments, these are multi-platform development libraries, meaning that GRAMPS can be ported to any platform the required libraries are ported to.
* Free Software/Open Source development model means GRAMPS can be extended by any programmer since all of the source code is freely available under its license.
* GRAMPS is freely distributable under the GPL!

== Checklist ==
{| {{Prettytable}} style="width:235px; font-size:90%;"
|-
| ''' '''
|bgcolor="#8DA7D6" style="line-height:2.25em;"|'''GRAMPS 2.2.9'''
|-
|bgcolor="lightgray"|Price
|style="color:red;" |Free
|-
|Open Source
|yes
|-
|style="color:blue;" colspan="2"| '''Views'''
|-
|bgcolor="lightgray"|Individual
|Yes
|-
|bgcolor="lightgray"|Family
|Yes
|-
|bgcolor="lightgray"|Pedigree
|Yes
|-
|bgcolor="lightgray"|Source
|Yes
|-
|bgcolor="lightgray"|Event
|Yes
|-
|bgcolor="lightgray"|Place
|Yes
|-
|bgcolor="lightgray"|Media
|Yes
|-
|bgcolor="lightgray"|Repository
|Yes
|-
|bgcolor="lightgray"|Notes
|No
|-
|style="color:blue;" colspan="2"| '''Chart Types'''
|-
|style="color:blue;" colspan="2"| '''Reports'''
|-
|bgcolor="lightgray"|Books
|Yes
|-
|bgcolor="lightgray"|Family Group Sheets
|Yes
|-
|bgcolor="lightgray"|Individual Summary
|Yes
|-
|bgcolor="lightgray"|Henry Numbering
| /
|-
|bgcolor="lightgray"| D'Aboville numbering
| /
|-
|bgcolor="lightgray"|Calendar
|Yes
|-
|style="color:blue;" colspan="2"| '''Database'''
|-
|bgcolor="lightgray"|Native Database
|Yes (Berkeley DB)
|-
|bgcolor="lightgray"|Unlimited Size
|Yes (tested upto 250.000 people)
|-
|bgcolor="lightgray"| Open multiple Databases at once
|No (works for viewing, not supported !!)
|-
|style="color:blue;" colspan="2"| '''Multimedia'''
|-
|bgcolor="lightgray"|Audio
|Yes
|-
|bgcolor="lightgray"|Video
|Yes
|-
|bgcolor="lightgray"|Images
|Yes
|-
|style="color:blue;" colspan="2"| '''Remote'''
|-
|bgcolor="lightgray"|Remote Access
|Yes (linux, over X connection)
|-
|bgcolor="lightgray"|Collaboration
|No
|-
|style="color:blue;" colspan="2"| '''International'''
|-
|bgcolor="lightgray"|Unicode
|Yes
|-
|bgcolor="lightgray"|Languages
|English, Czech, Danish, German, Esperanto, Spanish, Finnish, French, Hungarian, Italian, Lithuanian, Norwegian, Dutch, Brazilian Portuguese, Russian, Slovak, Swedish
|-
|style="color:blue;" colspan="2"| '''Compatibility'''
|-
|bgcolor="lightgray"|GEDCOM 5.5
|Import/Export
|-
|bgcolor="lightgray"|HTML
|Export
|-
|bgcolor="lightgray"|XML
|GRAMPS XML
|-
|bgcolor="lightgray"|Backup
|On Exit, import possible
|-
|style="color:blue;" colspan="2"| '''Platform'''
|-
|bgcolor="lightgray"|Linux
|yes
|-
|bgcolor="lightgray"|Windows
|Yes (limited support)
|-
|bgcolor="lightgray"|Mac
|yes (user compile/install)
|-
|bgcolor="lightgray"|BSD
|yes (user compile/install)
|-
|style="color:blue;" colspan="2"| '''Additional Features'''
|-
|bgcolor="lightgray"|Match/Merge
|yes
|-
|bgcolor="lightgray"|Multiple relationships (adoptive-foster)
|yes
|-
|bgcolor="lightgray"|Relationship calculator
|yes
|-
|bgcolor="lightgray"|Soundex calculator
|yes
|-
|bgcolor="lightgray"|Spell check in notes
|yes
|-
|bgcolor="lightgray"|3th party plugin infrastructure
|yes
|-
|bgcolor="lightgray"|Check for Program Update
|No
|}

Genealogy basics

2008-01-30T04:12:59Z

Sgpsaros: Spelling correction

[[Category:Genealogy]]
{{languages|Genealogy basics}}

A few recommendations in the practice of genealogy:

* '''Get the source.''' No matter how much information you some day obtain regarding your family tree, it will only ever be as good as the sources it came from. Spend the extra effort at the time of discovery to write down all the details.
* '''Research from what you know to what you do not.''' Record everything that is known before making conjecture. The facts at hand can suggest direction for more research. Don't waste time looking through thousands of records hoping for a trail when you have other unexplored options.
* '''Be descriptive.''' Don't limit your record to names, dates and places. Genealogy is not just a study or analysis of what happened, but why it did and how the descendants might have been shaped by the events they went through. Plus, a charming narrative here and there goes a long way to making your family as interesting to others as it is to you.
* '''Be as accurate as you can.''' Don't make assumptions when recording primary information. Write it exactly as you see it, and then use bracketed comments to indicate your insertions, deletions or side comments. Use of the Latin "[sic]" is standard to confirm the accurate transcription of an apparent error. You may find afterwards that what you thought was an abbreviation or misspelling was actually a handwriting variation common to the period or a distinction in two facts with similar spellings.
* '''Get everyone.''' Record all the individuals you find at an event. Families often lived, worked, and worshipped together, so the relatives of an individual can show up at events of siblings, neighbors, and local churches.
* '''Plan your efforts.''' Knowing what you are looking to accomplish saves valuable time. Special trips to see original documents, burial places, libraries, or to interview individuals can not be repeated. Make sure you get everything you come for and record as much as you can while you have the chance. It is unfortunate to return from a trip to find that you omitted an obvious piece of information that passed right under your nose.
* '''Look closely.''' Sometimes re-interpretation of a group of seemingly unconnected pieces of information suddenly reveal a colorful period in the line you never expected. Abrupt changes in a family, such as what happens at a move, immigration, a marriage, death, or birth can point the direction for more research.
* '''Qualify what you record.''' Include your theories or questions about information as you write it. There's nothing wrong with others understanding that you might not be comfortable in the accuracy of a certain fact or hypothesis. It can help others to understand your perspective and bring further information to bear as they try to make sense of questions or research in the same area. Be sure to use brackets or other notation technique to clearly distinguish your comments from those of the source.
* '''Respect the privacy of the living.''' Genealogy is not intended to invade people's privacy by revealing their current health conditions, their social security numbers, and other still-hidden secrets. Be sensitive when writing about issues that some family members might not be comfortable discussing.
* '''Back up your electronic information frequently.''' If you spend countless hours entering information into a genealogy program, take the extra five minutes every now and then to back up the files on a CD. Write the description of what is on the disc with a CD marker (not just any permanent marker!) and the date and store it in a dark, cool and dry place.
* '''Take lots of pictures.''' Use photographs to remember details you don't have time to write down. Pictures of a cemetery stone can be useful, but you may also want a picture of the church that sits in front, a view from the road leading up to the site, views looking toward the stone from various positions, stones adjacent and otherwise interesting, a general overview of the place, even those who accompanied you on the visit. Later, these may help you find it and other areas for more research or simply remind you and others of the experience of that day.