Gramps 5.2 Wiki Manual - Manage Family Trees/he
| הקודם | מפתח | הבא |
 |
שפות: |
English • Deutsch • español • suomi • français • עברית • italiano • македонски • Nederlands • polski • русский • shqip • svenska • slovenčina |
A detailed exploration of the day-to-day use of Gramps. In this Chapter we give a detailed overview of how you can manage your family trees, as well as share your data with other genealogists.
Contents
- 1 Starting a new Family Tree
- 2 Opening a Family Tree
- 3 Saving changes to your Family Tree
- 4 Opening a GEDCOM or XML database
- 5 Deleting a Family Tree
- 6 Renaming a Family Tree
- 7 גיבוי אילן־יוחסין
- 8 Archiving a Family Tree
- 9 Extracting a Family Tree Archive
- 10 Unlocking a Family Tree
- 11 Repairing a damaged Family Tree
- 12 Converting a BSDDB Family Tree to SQLite
- 13 Importing data
- 14 Exporting data
- 14.1 Export Assistant dialog
- 14.2 Comma Separated Values Spreadsheet(CSV) export
- 14.3 GEDCOM export
- 14.4 GeneWeb export
- 14.5 Gramps XML (family tree) export
- 14.6 Gramps XML Package (family tree and media) export
- 14.7 ייצוא אילן־יוחסין מרשתת
- 14.8 vCalendar ייצוא
- 14.9 vCard ייצוא
Starting a new Family Tree
To start a new Family Tree, choose the menu Family Trees ->Manage Family Trees... or select the toolbar 
Family Trees button or use the keybinding CTRL+O. This will open the Family Trees manager window.
Select the חדש button and to add a new Family Tree entry to the list of Family Trees. To change its name from the default Family Tree 1, select the name and press the Rename button then type in a new name.
To open the new, empty Family Tree select the Family Tree and either double click or press the Load Family Tree button to load.
Family Trees manager window
Clicking the Family Tree Manager button brings up the Family Trees manager windows this allows you to work with and manage your Family Trees.
The Family Tree Manager window allows the you to create a new Family tree, rename an existing Family tree, delete a Family tree, or load a Family tree or check information) about the Family tree. All the names of your Family trees appear in the list. If a Family tree is open, an icon will appear next to the name in the status column. The Database Type as well an indication of the date and time your family tree was Last accessed' is shown.
- New creates a new Family tree.
- Info shows information about the selected Family tree.
- Delete the selected Family tree, this will show a warning with a final confirmation for you to select.
- Rename the selected existing Family tree.
- Close the selected existing Family tree.
- Convert the selected family tree. This option only available for legacy BSDDB databases. See: Converting a BSDDB Family Tree to SQlite
- Repair the selected existing Family tree, only available if Gramps detects an issue.
- Archive option is only present if GNU Revision Control System (RCS) is installed.
- Extract used with the Archive button and the option is only present if GNU Revision Control System (RCS) is installed.
- Help - from this section.
- Close Window - dismisses the Family Tree manager windows
- Load Family Tree the selected existing Family tree.
Opening a Family Tree
To open a Family Tree, either choose the menu Family Trees ->Manage Family Trees... or click the Toolbar Family Trees button. The Family Tree Manager will appear and you will see a list of all the Family Trees known to Gramps. In the Status column an icon (looks like an open folder) will display beside any Family Tree that is currently open. Select the tree you want to open, and open it by selecting the Load Family Tree button. Alternatively you can double-click on the desired Family Tree.
To open a recently accessed Family Tree, choose either the menu Family Trees ->Open Recent or the down arrow next to the Toolbar Family Trees button and select the Family Tree from the list.
Read Only Mode
|
Read Only Mode If you do not have "write permissions" for the selected Family Tree, it will be opened in a Read Only mode. In this mode, the data may be viewed, but no changes will be made to the Family Tree. To indicate this mode, the title of the main window will be appended with (Read Only) text. |
The Tools menu will not be available.
Saving changes to your Family Tree
Gramps saves your changes as soon as you apply them. This means, for example, that any time you click OK when using Gramps, your changes are immediately recorded and saved. There is no separate "save" command.
You can undo changes you have made by selecting the menu Edit ->Undo. If you select this command repeatedly, your most recent changes will be undone one at a time. To roll back multiple commands at a time, you can use the menu Edit dialog.
If you want to return your Family Tree to the way it was when you opened it, select the menu Family Trees ->Abandon Changes and Quit. (This is just like quitting without saving in other programs.)
If you would like to save a copy of your Family Tree under a different name, you will need to export it and then import it into a new Family Tree. The Gramps XML database format is recommended for this purpose.
Opening a GEDCOM or XML database
Gramps allows you to open certain databases that have not been saved in Gramps own file format from the command line, see Command line references. These include XML and GEDCOM databases. But you should be aware that if the XML or GEDCOM database is relatively large, you will encounter performance problems, and in the event of a crash your data can be corrupted. Hence, it is normally better to create a new Gramps family tree (database) and import your XML/GEDCOM data into it.
|
Opening databases XML and GEDCOM databases require all data to be held in memory and don't contain indexes. Gramps native format is a database that only reads the data needed. Thus, for a large family tree the data can be accessed quicker and more efficiently by not using XML or GEDCOM. |
|
|
GEDCOM Editing Please keep in mind that some information in a GEDCOM file may be lost during import into Gramps as well as export back to GEDCOM. Simply opening and viewing the file will not change it. However, if any changes were made and they were not abandoned upon exit, exiting Gramps will save the data, with possible data loss. |
Deleting a Family Tree
Select the family tree you want removed, and click the Delete button.
This will completely remove the tree, with no possibility to retrieve the data. Consider taking a backup of your data by exporting to the GRAMPS XML format, and storing that file.
Renaming a Family Tree
You can rename a Family Tree (or an archive of it) by selecting the tree you want to rename and clicking Rename. You can also click on the name in the list of trees.
In either case, you just type in the new name to have it take effect.
|
|
Family Tree name Limitations There are some characters that are not allowed within a Family Tree name. They will be automatically replaced with the underscore character "_". The comma, double quote and vertical bar characters and these: "\:/<>][.+*?" |
גיבוי אילן־יוחסין
הדרך הבטוחה ביותר לגבות אילן־יוחסין בגרמפס היא לייצא אותו ללא הגבלת פרטיות ומסננים, לתסדיר גרמפס XML (או חבילת גרמפס XML כדי לכלול גם את כל פריטי המדיה שבגלריה) ולהעתיק/להעביר את הקובץ שנוצר למקום ממשי מרוחק ובטוח, לדוגמה באחסון ענן או על גבי החסן נייד בבית קרוב משפחה.
דו־שיח גיבוי
אל חלון דו־שיח גיבוי גרמפס XML ניתן להגיע מתפריט אילן־יוחסין ← יצירת גיבוי...". חלון הדו־שיח כולל את אפשרויות התיצור הבאות:
נתיב: – ניתן להזין את הנתיב שבו יאוחסנו הגיבויים בעת יצירת גיבוי באופן ידני או באמצעות הלחצן בורר נתיבים כדי להעלות את דו־השיח בחירת מחיצת גיבוי.
קובץ: – נתן להזין שם קובץ גיבוי באופן ידני או להשתמש בשם הקובץ שנוצר באופן אוטומטי.
מדיה: – ניתן לבחור לכלול או לא לכלול (ברירת מחדל) את כל קובצי המדיה שבגלריה באילן־היוחסין.
|
|
הערה זהו ייצוא XML רגיל, פרט לכך שנתונים לא מסוננים כלל. ניתן לייבא קובץ זה באופן רגיל בדומה לכול קובץ שיוצא. |
- ניתן להשתמש בתכונת הארכיון (כמתואר בסעיף הבא) כדי ליצור ואחסן צילום־חטף של אילן היוחסין . ניתן להשתמש בצילמי־חטף אלה כגיבויים פשוטים, תכונה זו שימושית במיוחד אם יש כוונה לנסות פעולות מסויימות שאולי יהיה צורך לבטל מאוחר יותר. יחד עם זאת אין להשתמש בשיטה זו לביצוע גיבויים תקניים, מכיוון שצילום־חטף כזה לא ישרוד במצב של קריסת כונן קשיח או את רוב ה'אסונות' האחרים שעלולים לפקוד מחשב.
- למשתמשים מתקדמים: כל מסד נתונים מאוחסן במחיצת משנה משלה, בסבבות דמוי לינוקס במחיצת ~/.gramps. למרות שניתן לבצע גיבוי ידני על ידי גיבוי של מחיצה זו, זה לא מומלץ. מומלץ בחום להשתמש בגיבוי XML של גרמפס במקום זאת.
גיבוי בעת יציאה
בלשונית העדפות אילן־יוחסין, ניתן להגדיר את גרמפס כך שייווצר גיבוי בכול יוצא מגרמפס. לתשומת לב הגיבוי שייוצר הוא רק לאילן־היוחסין הפעיל (הפתוח). אם אילן־יוחסין נסגר לפני היציאה מגרמפס, לא ייוצר קובץ גיבוי.
גיבוי אוטומטי
בלשונית העדפות אילן־יוחסין, ניתן להגדיר את גרמפס כך שייצןר גיבוי באופן אוטומטי, כל 15, 30 או 60 דקות.
לקריאה נוספת:
- הגדרות אילן יוחסין
- הגדרה מתקדמת של שם קובץ גיבוי – דפוס שמות שם קובץ הגיבוי ניתן אףהוא להגדרה.
- השמטות גיבוי - מה לא כלול בקובצי הגיבוי
Archiving a Family Tree
|
Note The Archive option is only present if GNU Revision Control System (RCS) is installed so that Gramps can use it. You normally need to install this on your computer separately from Gramps. |
You can Archive your family trees with Gramps to retain a copy before any major changes and be able to return to a known version.
To make an archive :
- load your Family Tree.
- click on the Toolbar Family Trees button (it displays Connect to a recent database when you hover over it).
- click on the family tree you have just loaded: the Archive button should appear.
- click on Archive and you will be able to enter in the Revision comment dialog a Version description for your archive.
After archiving, the list of family trees will now show your original family tree with a right-pointing triangle on its left.
- Click on the triangle to display the archive name.(Click again to collapse the archive list).
Archives can be Deleted, Rename(d) and Extract(ed).
Extracting a Family Tree Archive
To retrieve a version of a previously archived family tree in the "Family Tree" manager highlight the archive you want to restore, and select the Extract button.
The archive will then be restored into a new Family Tree and be listed in the family tree manager.
The Family Tree name is based on the original name and the archive name eg: <name of original tree>:<name of archive>.(see also Archiving a Family Tree)
This can be a useful way of preserving an archive, because archives disappear if the originating tree is deleted; and 'they are not incorporated into a Gramps XML export of the family tree.
Unlocking a Family Tree
Gramps is a single-user database application and identifies Tree database files as busy with a 
'lock' when in use. As Gramps opens a tree, it drops a lock file (which lists the username and domain) in the tree's subfolder in the grampsdb folder of the User Directory. Gramps refuses to let you (or anyone else) open that Tree at the same time. A second instance of Gramps will be able to open another family tree, but any tree that is already open will appear with the lock icon in the Status column of the Manage Family Trees dialog. Closing the tree in the first copy of Gramps deletes the lock file and will make the tree available to be opened in the second instance.
If you could open the same Family Tree in two instances of Gramps at once, it is likely your data would be damaged as the two overwrite each other's work.
See also:
|
|
Be careful Breaking Locks! Only do this if you are sure no other copy of Gramps is using the selected Family Tree. |
Break the lock on the "Family Tree name" database? dialog
In the unlikely event that Gramps crashes, the family tree will be left in a locked state (indicated by a lock icon in the Status column next to the Family Tree name)
To unlock the Family Tree during startup
- If the Family Tree Preferences have been set to open a tree automatically on startup, then you will see the Error parsing arguments dialog which remarks that the Database is locked. Click on the Close button then choose Manage Family trees... from the Family Trees menu.
- Otherwise, the Family Tree Manager will appear automatically as Gramps starts.
Click the Break lock button and the Family Trees (Manager) window should show that the lock icon has gone.
Choose the previously locked family tree and then click the Load Family Tree button to continue your work.
Repairing a damaged Family Tree
Should your Family Tree become damaged or corrupted in some way, Gramps Family Tree Manager will display a red Error icon in the Status column.
To have Gramps attempt to repair the damage, select the Family Tree and then click the Repair button.
This will attempt to rebuild your Family Tree from the backup files that are automatically created on exit.
See also:
Converting a BSDDB Family Tree to SQLite
|
|
From Gramps 5.2.x the default database is SQLite. Before following the conversion advice in this section, take the time to backup your family trees |
If you have an older legacy BSDDB format Database Type shown for any of your family tree's in the Family Trees (Manager) - Dialog, then selecting a family tree in the Family Trees (Manager) - Dialog will show the Convert button as available.
It is highly recommended that before doing the following you back up the family trees to be converted.
When ready select the Convert button and the Convert the 'Family Tree Name' database? dialog will be shown with the message Do you wish to convert this family tree into a SQLite database? you can select Cancel to stop or Convert to start the process, once completed the Family Trees (Manager) - Dialog will show a new entry for the converted copy of your Family tree but with the Database Type of SQLite, you should then open and backup the converted family tree.
You may then rename the original BSDDB family tree with the word OLD or you can Delete it to avoid confusion, then you can rename the new SQLite database.
|
|
This article's content is incomplete or a placeholder stub. |
Importing data
|
|
Importing vs. opening Please recognize that importing a Family Tree is different from opening a Family Tree. When you import, you are actually bringing data from another Family Tree into a Gramps Family Tree. When you open a file, you are editing your original file. |
Importing allows you to transfer data from other genealogy programs into a Gramps Family Tree. Gramps can import data from the following formats:
- Gramps XML (
.grampsfile extension) Gramps native data exchange format in uncompressed text and gzip compressed - Gramps XML Package (
.gpkgfile extension) Gramps .tar.gz archive compressed backup format - GRAMPS V2.x database (
.grdbfile extension) - CSV Spreadsheet - comma separated values (
.csvfile extension) - GEDCOM (
.gedfile extension) de facto standard file format for data interchange between genealogy programs - GeneWeb (
.gwfile extension) - GeneWeb is genealogy software with a web interface. - Pro-Gen (
.deffile extension) - Pro-Gen has been very popular in the Netherlands and North-West Germany. It is often used by people who started collecting and storing data as early as 1989. This was a DOS based program which has been patched to work with Win 10. - vCard (
.vcffile extension) - Virtual Contact File is a file format standard for electronic business cards. - JSON Import (
.jsonfile extension) - JavaScript Object Notation is a lightweight data-interchange format. - SQLite Import (
.sqlfile extension) - SQLite database format
דו־שיח ייבוא אילן־יוחסין
|
|
לתשומת לב: ניתן לייבא נתונים רק לאילן־יוחסין (מסד־נתונים) קיים לכן, בהגירת נתונים מתוכנה אחרת, או לייבוא קובץ גיבוי אילן־יוחסין גרמפס, נידרש ליצור תחילה אילן־יוחסין ריק חדש לפני ייבוא נתונים שטרם אומתו, לתוכו. לאחר ייבוא הנתונים, חשוב לטפל בכול הרשומות הפגומות ואי התאמות שנטענו מקובץ הייבוא. |
תחילה יש ליצור אילן־יוחסין חדש וריק, ולהזין שם לאילן־היוחסין. לאחר מכן מתפריט אילן־יוחסין ← ייבוא או באמצעות צרוף המקשים CTRL+I לפתיחת חלון דו־שיח ייבוא אילן־יוחסין לבחירת קובץ ולהתחיל בתהליך ייבוא נתונים מקובץ שנתקבל מתוכנה אחרת או כדי לשחזר קובץ גיבוי אילן־יוחסין של גרמפס שנשמר קודם (מגרסה ישנה יותר של גרמפס או מהגרסה הנוכחית).
בעת ניסיון לייבא נתונים לאילן־יוחסין שהוא לא ריק, יפתח חלון דו־שיח בטול אזהרת היסטוריה. זוהי רק תזכורת לבצוע גיבוי לפני ייבוא, במקום זאת יש לייצור אילן־יוחסין חדש, אלא אם הכוונה היא למזג ביודעין נתונים משני אילנות־יוחסין.
גרמפס משתמש בברר קבצים GTK לבחירת קובץ הנתונים לייבוא. אופן הניווט לקובץ מוכר וברור בדומה לשימוש במנהל הקבצים או סייר קבצים תקני.
אפשרות מצג ברירת המחדל לנתיב הקובץ היא להציג כל רמת מחיצה כלחצן בר הקשה בסיגנון ניווט סימני־דרך . ניתן להזין את הנתיב בתיבת המלל שנועדה לעריכה על ידי שימוש בצרוף המקשים CTRL+L.
אפשרות זיהוי אוטומטי על פי סיומת סוג הקובץ תזהה את תסדיר הקובץ ותמיר אותו לתסדיר מסד הנתונים המקורי. ניתן לעקוף זאת על ידי בחירה באחת מאפשרויות הזמינות כמו בחירת סוג קובץ:או כל הקבצים ולסנן את רשימת הקבצים.
במקרים בהם נדרש לחזור על פעולת הייבוא שוב ושוב (למטרת עדכונים שוטפים או להכללת מחקר יוחסין), ניתן 1068/5 להתאים את תיבת ־דו־השיח בהתאמה אישית על ידי הוספת לחצנים לנתיבי המחיצות מסומנות על ידי הקשת עכבר ימנית על שם מחיצה ובחירה מהתפריט הצץ באפשרות הוספה לסימניות.
|
|
אובדן נתונים בתסדירים מסוימים חשוב לציין שאין התאמה ישירה ומלאה (אחד לאחד) בין כל התכונות בגרמפס לאלו הנתמכות בתקן GEDCOM הבסיסי ובין תסדיר קובצי נתונים של תוכנות כמו GeneWeb או Pro-Gen. לכן, קטעי נתונים בלתי מזוהים עלולים ללכת לאיבוד בעת פעולת הייבוא מכל אחד מהתסדירים הללו. לפרטים נוספים על התכנות אבדן נתונים בסיכון הגבוהה ביותר בייבוא מקובץ GEDCOM מתוארים להלן. |
|
|
מיון אירועים שנוצרו על ידי תוכנות אחרות ייתכן שחלק מהתוכנות מהן יובאו נתונים לא ממינותאירועים לפי תאריך כפי שניתן היה לצפות, והם יופיעו בסדר בו הם מופיעים בקובץ הייבוא (כפי שיוצאו על ידי התוכנית האחרת). גרמפס מספק דרך לסייע בסידור מחדש של אירועים בהתאם לצורך. לקריאה נוספת: מיון ארועים. |
GRAMPS V2.x database import
GRAMPS V2.x database (.grdb): Prior to Gramps Version 3.0, this native Gramps database format was a specific form of the Berkeley database (BSDDB) with a special structure of data tables. This format was binary and architecture-dependent. It was very quick and efficient, but not generally portable across computers with different binary architecture (e.g. i386 vs. alpha).
Import from the GRAMPS V2.x database format is only supported by Gramps version 3.0.x. Import of V2.x into Gramps V3.0.x will not loose any data.
|
|
Import from the Gramps V2.x format is not supported by Gramps 5.2. If you have an old V2.x database, then you must import it into Gramps V3.0.x, export it from there to Gramps XML (or Gramps XML Package), and then import it into Gramps 5.2. |
Moving a Gramps 2.2 databases to Gramps 3.x
To move your Gramps data from version 2.x to version 5.2.x you must import the v2.x database into an earlier Gramps v3.0.x program and then either save the database and import it into Gramps 5.2.x, or export the database in XML format from the earlier Gramps version and import it into Gramps 5.2.x.
Please refer to the User Manual for earlier versions of Gramps for instructions on the import of v2.x databases into Gramps v3.x.
Gramps XML and XML Package import
The Gramps XML and Gramps XML Package database are the native Gramps formats. There is no risk of information loss when importing (restore) from or exporting to these formats.
- Gramps XML (.gramps): The Gramps XML file is the standard Gramps data-exchange and backups format, and was also the default working-database format for older (pre 2.x) versions of Gramps. Unlike the GRAMPS V2.x grdb format, it is architecture independent and human-readable. The database may also have references to non-local (external) media objects, therefore it is not guaranteed to be completely portable (for full portability including media objects in the Gramps XML package (.gpkg) should be used). The Gramps XML database is created by exporting (Menu Family Trees ->Export...) to that format.
- Gramps XML package (.gpkg): The Gramps XML package is a compressed archive containing the Gramps XML file and all media objects (images, sound files, etc.) to which the database refers. Because it contains all the media objects, this format is completely portable. The Gramps XML package is created by exporting ( Menu Family Trees ->Export... ) data in that format.
If you import information from another Gramps database or Gramps XML database, you will see the progress of the operation in the progress bar of Gramps main window. When the import finishes, a feedback window shows the number of imported objects. If the imported data originates from the very family tree in which you import the data, the import feedback gives suggestions about what could be merged; the merge is not done automatically for you. If you want to merge basic genealogy data automatically, consider CSV Spreadsheet Export/Import.
Gramps CSV import
- The Gramps CSV Spreadsheet format allows importing and exporting of a subset of your Gramps data in a simple spreadsheet format. See CSV Import and Export for more information.
ייבוא GEDCOM
כפעולה מקדימה לייבוא קובץ נתונים, נדרש לייצור אילן־יוחסין חדש ריק. לאחר מכן לבחור מתפריט אילן־יוחסין ← ייבוא או על ידי שימוש בצרוף המקשים CTRL+I לפתיחת חלון תיבת דו־השיח ייבוא אילן־יוחסין מחלון דו־שיח זה ניתן לבחור את קובץ ה־GEDCOM אותו מעונינים לייבא, כתלות בסוג קובץ ה־GEDCOM, ייתכן שתוצג התווית קידוד GEDCOM.
בעת ייבא מידע מקובץ GEDCOM, החלון הראשי של גרמפס יציג סרגל התקדמות תהליך הייבוא. כאשר ייבוא קובץ ה־GEDCOM יסתיים, חלון |סטטיסטיקת ייבוא וחלון דוח ייבוא GEDCOM: יוצגו חלונות אלו מציגים את תוצאות תהליך הייבוא או אזהרות הקשורות לנתוני הייבוא.
דו־שיח קידוד GEDCOM
תיבת דו־השיח קידוד GEDCOM תוצג כאשר קובץ GEDCOM המיובא מזדהה כקובץ בתסדיר קידוד ANSEL. לפעמים זה רק טעות בזיהוי קידוד הקובץ, אך אם לאחר שתהליך ייבוא קובץ ה־GEDCOM הסתיים, והנתונים באילן־היוחסין מכילים תווים חריגים, יש לבטל את הייבוא ולעקוף את ערכת התווים על ידי בחירת קידוד זמין שונה מרשימה הבחירה.
קידוד:
- ברירת מחדל
- ANSEL
- ANSI (iso-8859-1)
- ASCII
- UTF8
Import Statistics dialog
Shows details of the import statistics.
GEDCOM import report dialog
|
|
This article's content is incomplete or a placeholder stub. |
The GEDCOM import report details most of the GEDCOM lines that were either ignored or could not be understood. These are most likely because they are not part of the GEDCOM 5.5.2 standard. (See Addon:GEDCOM Extensions.) The contents of the GEDCOM line (or lines where there are continuation lines) are also shown. In some cases, the lines may not be exactly what is contained in the input GEDCOM file, because the line is reconstructed following some processing.
Reading the report
Gramps uses a more advanced 'data model' than GEDCOM, therefore some data in GEDCOM cannot be imported into Gramps. (See Gramps and GEDCOM.) The main exceptions are:
- Some GEDCOM attribute structures are treated as Gramps Attributes and therefore many of the GEDCOM Primitive Elements cannot be stored.
- The DATA elements of a SOURCE_RECORD (indicating the events recorded and responsible agency) are ignored.
- Any source citations on notes are ignored.
- Many GEDCOM Primitive Elements do not have exactly corresponding data elements in Gramps, and they are therefore stored as Attributes with appropriate names, normally the GEDCOM tag. This applies particularly to the header, submitter and submission GEDCOM records and particular fields like REFN, RFN, RIN and AFN.
Where data is listed as 'ignored', its omission is reported in the feedback at the end of import, and it is included in a Note attached to a relevant object with a custom type of GEDCOM import. See, for example, the Source object in the example screenshot.
Where data is listed as 'silently ignored', it is not reported and not included in a note. At present this may be regarded as something that has been missed by Gramps and should be raised as an issue.
GEDCOM import limitations
This section describes any GEDCOM data that cannot be directly represented in Gramps, and how it is handled. For additional information on the limits of GEDCOM imports (and exports), please read the section on Gramps and GEDCOM.
HEADer, SUBMitter and SUBmissioN
Gramps has no direct representation of this data, and hence all information there has to be stored in other objects. Depending on a General preferences setting, a 'default source' object may be created. If this is created, then much of the data is stored in that Source, or in Repositories attached to that source.
HEADer
HEADER:=
n HEAD {1:1}
+1 SOUR <APPROVED_SYSTEM_ID> {1:1} (Data item of the 'default source')
+2 VERS <VERSION_NUMBER> {0:1} (Data item of the 'default source')
+2 NAME <NAME_OF_PRODUCT> {0:1} (Data item of the 'default source')
+2 CORP <NAME_OF_BUSINESS> {0:1} (Repository of the 'default source')
+3 <<ADDRESS_STRUCTURE>> {0:1} (Repository of the 'default source')
+2 DATA <NAME_OF_SOURCE_DATA> {0:1} (Data item of the 'default source')
+3 DATE <PUBLICATION_DATE> {0:1} (Data item of the 'default source')
+3 COPR <COPYRIGHT_SOURCE_DATA> {0:1} (Data item of the 'default source')
+1 DEST <RECEIVING_SYSTEM_NAME> {0:1*} (Data item of the 'default source')
+1 DATE <TRANSMISSION_DATE> {0:1} (Data item of the 'default source')
+2 TIME <TIME_VALUE> {0:1} (Data item of the 'default source')
+1 SUBM @<XREF:SUBM>@ {1:1} (Data item of the 'default source')
(Also used to determine the SUBMITTER_RECORD)
(that should be stored as the database owner)
+1 SUBN @<XREF:SUBN>@ {0:1} (ignored)
+1 FILE <FILE_NAME> {0:1} (Data item of the 'default source')
+1 COPR <COPYRIGHT_GEDCOM_FILE> {0:1} (stored as the Publication information of the 'default source')
+1 GEDC {1:1}
+2 VERS <VERSION_NUMBER> {1:1} (Data item of the 'default source')
+2 FORM <GEDCOM_FORM> {1:1} (Data item of the 'default source')
+1 CHAR <CHARACTER_SET> {1:1} (Data item of the 'default source')
+2 VERS <VERSION_NUMBER> {0:1} (Data item of the 'default source')
+1 LANG <LANGUAGE_OF_TEXT> {0:1} (Data item of the 'default source')
+1 PLAC {0:1}
+2 FORM <PLACE_HIERARCHY> {1:1} (see below)
+1 NOTE <GEDCOM_CONTENT_DESCRIPTION> {0:1} (note attached to the 'default source')
+2 [CONT|CONC] <GEDCOM_CONTENT_DESCRIPTION> {0:M}
* NOTE: Submissions to the Family History Department for Ancestral
File submission or for clearing temple ordinances must use a
DESTination of ANSTFILE or TempleReady.
The PLAC FORM is stored internally and used to govern the interpretation of places (in accordance with the GEDCOM specification).
SUBmissioN
The SUBMISSION_RECORD (there should be only one, but this is not checked) is stored as a Data item of the 'default source'
SUBMISSION_RECORD:=
n @<XREF:SUBN>@ SUBN {1:1]
+1 SUBM @<XREF:SUBM>@ {0:1}
+1 FAMF <NAME_OF_FAMILY_FILE> {0:1}
+1 TEMP <TEMPLE_CODE> {0:1}
+1 ANCE <GENERATIONS_OF_ANCESTORS> {0:1}
+1 DESC <GENERATIONS_OF_DESCENDANTS> {0:1}
+1 ORDI <ORDINANCE_PROCESS_FLAG> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
SUBMitter
SUBMITTER_RECORDs (there may be more than one) are stored as Repository records attached to the 'default source' except as indicated in bold below. The SUBMITTER_RECORD that corresponds with the SUBM record in the HEADER is used to set the database owner and can be copied to the Researcher Information tab if required.
SUBMITTER_RECORD:=
n @<XREF:SUBM>@ SUBM {1:1}
+1 NAME <SUBMITTER_NAME> {1:1}
+1 <<ADDRESS_STRUCTURE>> {0:1}
+1 <<MULTIMEDIA_LINK>> {0:M}
+1 LANG <LANGUAGE_PREFERENCE> {0:3}
+1 RFN <SUBMITTER_REGISTERED_RFN> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- Mutimedia link is ignored
- LANG is ignored
- RFN and RIN are ignored
INDIvidual
The INDIVIDUAL_RECORD is stored as a Gramps Person record, except as indicated in bold below.
INDIVIDUAL_RECORD: =
n @<XREF:INDI>@ INDI {1:1}
+1 RESN <RESTRICTION_NOTICE> {0:1}
+1 <<PERSONAL_NAME_STRUCTURE>> {0:M}
+1 SEX <SEX_VALUE> {0:1}
+1 <<INDIVIDUAL_EVENT_STRUCTURE>> {0:M}
+1 <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>> {0:M}
+1 <<LDS_INDIVIDUAL_ORDINANCE>> {0:M}
+1 <<CHILD_TO_FAMILY_LINK>> {0:M}
+1 <<SPOUSE_TO_FAMILY_LINK>> {0:M}
+1 SUBM @<XREF:SUBM>@ {0:M}
+1 <<ASSOCIATION_STRUCTURE>> {0:M}
+1 ALIA @<XREF:INDI>@ {0:M}
+1 ANCI @<XREF:SUBM>@ {0:M}
+1 DESI @<XREF:SUBM>@ {0:M}
+1 <<SOURCE_CITATION>> {0:M}
+1 <<MULTIMEDIA_LINK>> {0:M}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 RFN <PERMANENT_RECORD_FILE_NUMBER> {0:1}
+1 AFN <ANCESTRAL_FILE_NUMBER> {0:1}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- Link to submitter, ancestor interest and descendent interest indicators are silently ignored.
- The alias indicator ("An indicator to link different record descriptions of a person who may be the same person") is stored as an Association called 'Alias'.
- The REFN and REFN:TYPE are stored as Attributes of the Person, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.
Handling of the INDIVIDUAL_ATTRIBUTE_STRUCTURE is rather complicated. The following tags:
- EDUC (Scholastic achievement),
- NMR (Count of marriages),
- OCCU (Occupation),
- PROP (Possessions),
- RELI (Religious affiliation),
- RESI and
- TITL (Nobility title)
are all treated as Gramps Events and the associated information is stored in the event structure. The details following the main tag (shown in brackets in the list above) are stored as the Description of the Event. The <EVENT_DESCRIPTOR> following the TYPE tag will overwrite the Description if the <EVENT_DESCRIPTOR> is not the attribute name.
The following tags:
- CAST (Caste name),
- DSCR (Physical description),
- INDO (National ID Number),
- NATI (National or tribal origin),
- NCHI (Count of Children) and
- SSN (Social Security Number)
are all treated as Gramps Attributess and most of the fields except the details following the main tag (shown in brackets in the list above), the source citation and the note structure are ignored, as indicated in bold below.
INDIVIDUAL_ATTRIBUTE_STRUCTURE: =
n CAST <CASTE_NAME> {1:1}
+1 <<EVENT_DETAIL>> {0:1}
etc.
EVENT_DETAIL: =
n TYPE <EVENT_DESCRIPTOR> {0:1}
n DATE <DATE_VALUE> {0:1}
n <<PLACE_STRUCTURE>> {0:1}
n <<ADDRESS_STRUCTURE>> {0:1}
n AGE <AGE_AT_EVENT> {0:1}
n AGNC <RESPONSIBLE_AGENCY> {0:1}
n CAUS <CAUSE_OF_EVENT> {0:1}
n <<SOURCE_CITATION>> {0:M}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 <<MULTIMEDIA_LINK>> {0:M}
n <<MULTIMEDIA_LINK>> {0:M}
n <<NOTE_STRUCTURE>> {0:M}
- Individual attribute structure, type, date, place structure, address structure, age, agency, cause and multimedia link are all ignored.
FAM_RECORD
The FAM_RECORD is stored as a Gramps Family record.
FAM_RECORD:=
n @<XREF:FAM>@ FAM {1:1}
+1 <<FAMILY_EVENT_STRUCTURE>> {0:M}
+1 HUSB @<XREF:INDI>@ {0:1}
+1 WIFE @<XREF:INDI>@ {0:1}
+1 CHIL @<XREF:INDI>@ {0:M}
+1 NCHI <COUNT_OF_CHILDREN> {0:1}
+1 SUBM @<XREF:SUBM>@ {0:M}
+1 <<LDS_SPOUSE_SEALING>> {0:M}
+1 <<SOURCE_CITATION>> {0:M}
+1 <<MULTIMEDIA_LINK>> {0:M}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- The link to submitter is silently ignored.
- The REFN and REFN:TYPE are stored as Attributes of the Family, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.
SOURCE_RECORD
The SOURCE_RECORD is stored as a Gramps Source record, except as indicated in bold below.
SOURCE_RECORD:=
n @<XREF:SOUR>@ SOUR {1:1}
+1 DATA {0:1}
+2 EVEN <EVENTS_RECORDED> {0:M}
+3 DATE <DATE_PERIOD> {0:1}
+3 PLAC <SOURCE_JURISDICTION_PLACE> {0:1}
+2 AGNC <RESPONSIBLE_AGENCY> {0:1}
+2 <<NOTE_STRUCTURE>> {0:M}
+1 AUTH <SOURCE_ORIGINATOR> {0:1}
+2 [CONT|CONC] <SOURCE_ORIGINATOR> {0:M}
+1 TITL <SOURCE_DESCRIPTIVE_TITLE> {0:1}
+2 [CONT|CONC] <SOURCE_DESCRIPTIVE_TITLE> {0:M}
+1 ABBR <SOURCE_FILED_BY_ENTRY> {0:1}
+1 PUBL <SOURCE_PUBLICATION_FACTS> {0:1}
+2 [CONT|CONC] <SOURCE_PUBLICATION_FACTS> {0:M}
+1 TEXT <TEXT_FROM_SOURCE> {0:1}
+2 [CONT|CONC] <TEXT_FROM_SOURCE> {0:M}
+1 <<SOURCE_REPOSITORY_CITATION>> {0:1}
+1 <<MULTIMEDIA_LINK>> {0:M}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- DATA and its subsidiary records are ignored
REPOSITORY_RECORD
The REPOSITORY_RECORD is stored as a Gramps Repository record, except as indicated in bold below.
REPOSITORY_RECORD: =
n @<XREF:REPO>@ REPO {1:1}
+1 NAME <NAME_OF_REPOSITORY> {0:1}
+1 <<ADDRESS_STRUCTURE>> {0:1}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- REFN, REFN:TYPE and RIN are ignored
MULTIMEDIA_RECORD
The MULTIMEDIA_RECORD is stored as a Gramps Media record, except as indicated in bold below.
MULTIMEDIA_RECORD:=
n @<XREF:OBJE>@ OBJE {1:1}
+1 FORM <MULTIMEDIA_FORMAT> {1:1}
+1 TITL <DESCRIPTIVE_TITLE> {0:1}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 <<SOURCE_CITATION>> {0:M}
+1 BLOB {1:1}
+2 CONT <ENCODED_MULTIMEDIA_LINE> {1:M}
+1 OBJE @<XREF:OBJE>@ /* chain to continued object */ {0:1}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
- It is expected that there will be a 'FILE' tag to indicate the file holding the multimedia object. This usage is taken from GEDCOM 5.5.2, but the ability in GEDCOM 5.5.2 to have more than one <MUTIMEDIA_FILE_REFN> and having the FORM, TYPE and TITL subsidiary to the FILE gedcom_line is not supported (a later FILE may overwrite an earlier one - there is no error checking).
- BLOB is ignored
- REFN, REFN:TYPE and RIN are ignored
NOTE_RECORD
The NOTE_RECORD is stored as a Gramps Note record, except as indicated in bold below.
NOTE_RECORD:=
n @<XREF:NOTE>@ NOTE <SUBMITTER_TEXT> {1:1}
+1 [ CONC | CONT] <SUBMITTER_TEXT> {0:M}
+1 <<SOURCE_CITATION>> {0:M}
+1 REFN <USER_REFERENCE_NUMBER> {0:M}
+2 TYPE <USER_REFERENCE_TYPE> {0:1}
+1 RIN <AUTOMATED_RECORD_ID> {0:1}
+1 <<CHANGE_DATE>> {0:1}
- source citation ignored
- REFN, REFN:TYPE and RIN are ignored
Exporting data
|
|
Export is saving a copy When you export, you are saving a copy of the currently opened database. Exporting creates another file with a copy of your data. Note that the database that remains opened in your Gramps window is NOT the file saved by your export. Additional editing of the currently opened database will not alter the copy produced by the export. |
To export data, choose Menu Family Trees ->Export... or the keybinding Ctrl+E or Command ⌘+E on Apple Mac's. This will bring up the Export Assistant dialog.
Exporting allows you to share any portion of your Gramps Family Tree(database) with other researchers as well as to enable you to transfer your data to another computer.
Gramps can export data to the following file formats:
- Comma Separated Values Spreadsheet (CSV)
- GEDCOM
- GeneWeb
- Gramps XML (family tree)
- Gramps XML Package (family tree and media)
- Web Family Tree
- vCalendar
- vCard
Export Assistant dialog
The Export Assistant pages will guide you through the output file format selection, and then the export options specific to that file format. After the Final confirmation page, the export will be performed according to the choices you have made. At any time, you can click the Back button and revise any selection, and then go forward to redo the export.
Saving your data
General information about exporting from Gramps.
Select the Next button to continue.
|
|
This article's content is incomplete or a placeholder stub. |
Choose the output format
Select the file format to export your data to:
- Comma Separated Values Spreadsheet (CSV)
- GEDCOM
- GeneWeb
- Gramps XML (family tree)(default)
- Gramps XML Package (family tree and media)
- Web Family Tree
- vCalendar
- vCard
Then select the Next button to continue.
Export options
After you have adjusted your options in the two sections.
- Top unlabeled section: Filters and privacy
- Bottom unlabeled section: File format specific options
Select the Next button to continue.
Filters and privacy
Gramps allows you to export your selected Family tree into common file formats.
The following filters provide options that allow you to fine tune your export.
Filters allow you to export a limited amount of data, based on the criteria you select.
Privacy Filter:
[✓] Do not include records marked private: Check this box to prevent private records from being included in the exported file. (Checkbox checked by default)
Living Filter:
These option restrict data and help limit the information exported for living people. This means that all information concerning their birth, death, addresses, significant events, etc., will be omitted in the exported file. For example, you can choose to substitute the word Living for the first name (see your settings); you can exclude notes; and you can exclude sources for living people.
Sometimes, it is not always obvious from the data if someone is actually alive. Gramps uses an advanced algorithm to try to determine if a person could still be alive. Remember, Gramps is making its best guess, and it may not always be able to guess correctly all the time. Please double check your data.
Select from the following options:
- Include all selected people (default)
- Replace given names of living people
- Replace complete name of living people
- Do not include living people
Person Filter:
Select from the following options:
- Include all selected people (default)
- Descendants of [Active Person]
- Descendant Families of [Active Person]
- Ancestors of [Active Person]
- People with common ancestor with [Active Person]
- Create a custom filter by selecting the Edit icon to show the Define filter dialog.
Note Filter:
Select from the following options:
- Include all selected notes (default)
- Create a custom filter by selecting the Edit icon to show the Define filter dialog.
Reference Filter:
Select from the following options:
- Include all selected records (default)
- Do not include records not linked to a selected person
File format specific export options
Depending on the file format chosen, you may find a number of file format specific export options to choose from listed underneath the "Filters and privacy" section.
See the relevant section for each of file formats listed that have specific export options:
|
|
This article's content is incomplete or a placeholder stub. |
Select save file
Enter a export file Name: Untitled_1.<file format extension>(default) and choose the folder location to save the export file to (normally your Documents folder.
Then select the Next button to continue.
If you don't have permission to save the file to that location you will see the Could not create <file location and export file name> warning dialog and then the Export Assistants Saving failed wizard dialog, select the Close button and start the export again this time choosing a suitable folder.
Final confirmation
The Export Assistants Final confirmation wizard dialog allows you to check the summarized details (Format/Name/Folder) of the export file to be created.
At this point you can press Back to revisit your options or Cancel to abort.
Or select the Apply button to continue.
Summary
The Export Assistants Summary wizard dialog shows the Filename: and confirms that you export data has been saved successfully.
Select the Close button to exit the Export Assistant.
Comma Separated Values Spreadsheet(CSV) export
Comma Separated Values Spreadsheet(CSV): Allows exporting (and importing) a subset of your Gramps data in a simple spreadsheet format.
See CSV Import and Export for additional information and examples.
Comma Separated Values Spreadsheet(CSV) has the following file format specific export options:
- Include people -
- Include marriages -
- Include children -
- Include places -
- Translate headers -
Also, see Export (List) View as Spreadsheet.
GEDCOM export
|
|
Gramps supports the GEDCOM 5.5.2 version last updated 15 November 2019. |
Gramps allows you to export a database into the common legacy GEDCOM format.
GEDCOM export has no file format specific export options but you can change the following:
- Make sure you add your Researcher information to create a valid GEDCOM file, this can be also be done with the Edit Database Owner Information tool.
- In the General Gramps settings section of the General tab in preferences you can also choose to Add default source on GEDCOM import and also Add tag on import both can significantly slow down the importing of your data.
|
|
If you have installed the third party addon Addon:GEDCOM Extensions(.GED2) it will have its own specific file format specific export options. |
For more information on the GEDCOM format see: :
- https://en.wikipedia.org/wiki/GEDCOM
- https://www.familysearch.org/developers/docs/guides/gedcom
- https://www.familysearch.org/developers/docs/gedcom/
See Gramps and GEDCOM for details of data which is not exported when exporting to GEDCOM (Use Gramps XML for a full family tree export/backup).
GeneWeb export
GeneWeb export will save a copy of your data to the GeneWeb genealogy format.
To find out more about GeneWeb and its format, visit:
GenWeb has no file format specific export options
Gramps XML (family tree) export
|
|
Privacy Filters It is important to verify your privacy options on Exporter. Do not enable filters or privacy options for Gramps XML backups. |
Gramps XML (family tree) export (.gramps): This format is the standard format for data-exchange and backups (see the related .gpkg format below for full portability including media objects). Exporting into Gramps XML format will produce a portable database. As XML is a text-based human-readable format, you may also use it to take a look at your data. Gramps guarantees you can open XML output of older versions of Gramps in newer version of Gramps (not the other way around though!).
If a media file is not found during export, you will see the same מדיה חסרה dialog you encounter with GEDCOM export.
Gramps XML (family tree) has the following file format specific export options:
- Use Compression -
מה לא כלול:
The Gramps Package backup only contains your family tree and (when the 'include media' backup option is selected) your media.
The following settings in Gramps are not transferred:
- Any changes you have manually made to
gramp.ini - Any custom settings for reports (
report_options.xml) you have made. - Any custom Books (
books.xml) you have created. - Any custom holiday sets or country calendars (
holidays.xml) you have created. - Any changes you have made to the dictionary for spell checking e.g.: new or excluded words.
- Gramps exports objects in the Tree. So any added Tags or custom types that have not been applied to at least one record, the Tag or Type will have no place to be included in the backup.
- Any custom filters (
custom_filters.xml) you have created.
|
|
Custom Filter migration Keep your collection of custom filters through a minor updates to patch Gramps (e.g., from version 5.1.0 to 5.1.2) by manually copying your custom_filter.xml from Gramps User Directory to the corresponding directory in new gramps_version_number. |
You can keep your custom settings by manually copying each of the *.xml files from the Gramps User Directory to the corresponding directory in the new gramps_version_number directory. Be aware that (due to changes in different versions of Gramps) the settings may no longer work. So be diligent that you test.
Gramps XML Package (family tree and media) export
|
|
Privacy Filters It is important to verify your privacy options on Exporter. Do not enable filters or privacy options for Gramps XML backups. |
Gramps XML Package (family tree and media) export (.gpkg): Exporting to the Gramps package format will create a compressed file that contains the Gramps XML database and copies of all associated media files. This is useful if you want to move your database to another computer or to share it with someone.
If a media file is not found during export, you will see the same Missing Media dialog you encounter with GEDCOM export.
Gramps XML Package (family tree and media) has no file format specific export options
מה לא כלול:
The Gramps Package backup only contains your family tree and (when the 'include media' backup option is selected) your media.
The following settings in Gramps are not transferred:
- Any changes you have manually made to
gramp.ini - Any custom settings for reports (
report_options.xml) you have made. - Any custom Books (
books.xml) you have created. - Any custom holiday sets or country calendars (
holidays.xml) you have created. - Any changes you have made to the dictionary for spell checking e.g.: new or excluded words.
- Gramps exports objects in the Tree. So any added Tags or custom types that have not been applied to at least one record, the Tag or Type will have no place to be included in the backup.
- Any custom filters (
custom_filters.xml) you have created.
|
|
Custom Filter migration Keep your collection of custom filters through a minor updates to patch Gramps (e.g., from version 5.1.0 to 5.1.2) by manually copying your custom_filter.xml from Gramps User Directory to the corresponding directory in new gramps_version_number. |
You can keep your custom settings by manually copying each of the *.xml files from the Gramps User Directory to the corresponding directory in the new gramps_version_number directory. Be aware that (due to changes in different versions of Gramps) the settings may no longer work. So be diligent that you test.
ייצוא אילן־יוחסין מרשתת
אילן־יוחסין מרשתת export creates a text file that can be used by the אילן־יוחסין מרשתת program.
To find out more about Web Family Tree and its format, visit
http://www.simonward.com/cgi-bin/page.pl?family/tree- linkrot. see 2016 Internet Archive snapshot
אילן־יוחסין מרשתת has no file format specific export options
vCalendar ייצוא
vCalendar export saves information in the format used in many calendaring applications, sometimes called PIM for Personal Information Manager.
For more information on the vCalendar format see:
vCalendar has no file format specific export options
vCard ייצוא
vCard פעולת הייצוא תשומר מידע במבנה מקובל ביישומי ספרי־כתובות רבים, ישומונים אלו נקראים לפעמים גם (PIM (Personal Information Manager.
מידע נוסף על אודות מבנה vCard ניתן למצוא בקישור:
ל־vCard אין אפשרויות לייצוא למבנה קובץ מסויים
| הקודם | מפתח | הבא |
|
שפות: |
English • Deutsch • español • suomi • français • עברית • italiano • македонски • Nederlands • polski • русский • shqip • svenska • slovenčina |
|
|
הודעת מיוחדת בעיינן זכויות יוצרים: כל העריכות בדף זה צריכות להיות במגבלות שני רישיונות זכויות יוצרים שונים:
רישיונות אלה מרשים למיזם גרמפס להשתמש באופן מירבי במדריך ויקי זה כתוכן חופשי בגרסאות גרמפס העתידיות. אם אינכם מסכים עם כפול רישיונות זה, אל תערוכו דף זה. אתם רשאים לקשור רק עמודים אחרים בתוך הויקי שנמצאים תחת רישיון GFDL ורק באמצעות קישורים חיצוניים (באמצעות התחביר: [https://www.gramps-project.org/...]), לא באמצעות קישורים פנימיים. |
