'''Experienced'''
5,069
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − <font color=gray><div align="center" style="text-align: center;font-size: 300%; font-weight: bold; margin: 10px auto;"> [[Image:20080723212748.jpg]] ''Glossary of Terms''</div></font> − <br> − − Line 24:
Line 20: − : In genealogy, a <i>branch</i> refers to two very different groups of relatives. An <i>ancestral branch</i> is a line of relatives diverging backward in time from a [[#L|Lineal Ancestor]]. For example, your Mother's Mother is the start of an ancestral branch of your family which blossoms backward in time. A <i>descendant branch</i> is a line of relatives diverging forward in time from a [[#C|Collateral Ancestor]]. For example, your Aunt and her descendants form one of the descendant branches of your family which blossom forward in time.+ − : + − : Branch is a specific TNG term for to a set of Individuals within a Tree that all share a common label. This label allows the administrator to restrict access to these labeled Individuals based on user permissions. [[Branches|More details]].+ + Line 33:
Line 30: − : Cemeteries in TNG are [[Places]] best understood as a special category of [[Repositories|Repository]] as they can provide valuable [[Sources]] by their registers and [[Headstones]]. They are treated as special because they form the emotional focus for remembrance of an individual or family regardless of any actual remains or record. [[Cemeteries|More details]].+ + + − + − + Line 50:
Line 49: − Line 56:
Line 54: − + − − Line 70:
Line 66: − : Documents is one of the [[Media_-_Collections|media collections]] or categories in TNG. Documents allows you to associate documents to a Person or Family in TNG.+ + + + + − + − + + + + − + − :In genealogy: traditionally, a social unit made up of a legally married couple and their registered children, allowing researchers to trace their ancestry through documents related to the marriage. Many variations exist in this pattern…+ + − ;Family ID+ − + + − + − : FTP stands for file transfer protocol, is a commonly used protocol for exchanging files over any network that supports the TCP/IP protocol. See [[FileZilla - FTP Client]] for a free client that can be used on multiple platforms.+ + + + − + − + − + + + + + − + Line 107:
Line 119: − + − + − ;History − : History is one of the [[Media_-_Collections|media collections]] or categories in TNG. History allows you to create media records that provide a historical narrative. − ;HTML − :Hyper Text Markup Language (HTML) is the predominant markup language for web pages. HTML is not a programming language, it is a markup language. A markup language is a set of markup tags. HTML uses markup tags to describe web pages. See [http://www.w3schools.com/html/html_intro.asp HTML Intro] on w3schools site. − + + + + + − + − + − + − + + + Line 131:
Line 145: + Line 143:
Line 158: + + + − ;Mod − :A TNG Mod is small bit of code packaged together into a configuration file, using the filename extension .cfg, that manages all the changes of code needed to implement the particular modification. Simply copy the .cfg file into the ''mods'' directory and the Mod Manager will see it is available to be installed if the file is correctly coded for the version of TNG currently used in the site. If so, it takes just two clicks to install the Mod and just two clicks to uninstall it if needed. There may be instances where other small changes need to be completed either before or after the installation of a Mod. + + + + + + + + + + − :The Person ID in TNG must be unique within the selected Tree and should consist of an upper case I followed by a number+ − + − + − + − − :PHP is a scripting language designed specifically for the web. It allows for the embedding of code into web pages that is executed by the server when the page is visited, making web pages interactive, unlike static HTML pages. Like HTML and MySQL, PHP is functional and versatile across platforms, a requisite for web sites. − + − + + + + − + Line 178:
Line 205: − + − + − + Line 190:
Line 217: + − + − + + − + − + − − + + + + − ;[[Setup - Tree|Tree]] − + + + − + − − + − Line 222:
Line 252: − : Formal TNG definition: Those persons approved by a website administrator to assist with the entry and maintenance of the data displayed on a TNG website. See [[Users and Guests]] for more details.+ − : Beware! - in some TNG-related literature the term <b>user</b> is simply a programmer's generic term for anyone <b>using</b> a program as in "be kind to inexperienced users", which could refer equally well to a TNG user or to a TNG [[#G|guest]].+
Restored some numbered lists for terms with more than one definition
The following is a Glossary of terms as used in TNG relating to genealogy, computing and archival organisation. The Glossary uses the titles of terms as they are displayed in TNG so as to facilitate . Definitions indicate where they differ from typical use and any possible confusions due to similar terms in other software and contexts.
The following is a Glossary of terms as used in TNG relating to genealogy, computing and archival organisation. The Glossary uses the titles of terms as they are displayed in TNG so as to facilitate . Definitions indicate where they differ from typical use and any possible confusions due to similar terms in other software and contexts.
----
----
==B==
==B==
;[[Branches|Branch]]
;[[Branches|Branch]]
# In genealogy, a <i>branch</i> refers to two very different groups of relatives.
#* An <i>ancestral branch</i> is a line of relatives diverging backward in time from a [[#L|Lineal Ancestor]]. For example, your Mother's Mother is the start of an ancestral branch of your family which blossoms backward in time.
#* A <i>descendant branch</i> is a line of relatives diverging forward in time from a [[#C|Collateral Ancestor]]. For example, your Aunt and her descendants form one of the descendant branches of your family which blossom forward in time.
# Branch is a specific TNG term for a set of Individuals within a Tree that all share a common label. This label allows the administrator to restrict access to these labeled Individuals based on user permissions. [[Branches|More details]].
;[[Database - Backup|Backup]]
;[[Database - Backup|Backup]]
==C==
==C==
;[[Cemeteries|Cemetery]]
;[[Cemeteries|Cemetery]]
# In most genealogy applications, including TNG, Places at which burial Events take place are often (but not always) cemeteries - and mausoleums, graveyards, etc. They may also be just a city, state, or country, if that is all that is known about the place of burial. Places have no attributes or relationships that distinguish Places tied to burial Events from other Places.
# TNG has a Cemeteries object that is separate from Places, and is intended to allow site adminstrators to focus on specific burial places of interest to them, and to treat them like real-world burial places. Distinctions between TNG Cemeteries and Places associated with burial events are explained in the Wiki article on [[Cemeteries|Cemeteries]].
;Chart
;Chart
:A chart is essentially a report of People (and generally Families) with graphical structure or indentation that helps to represent the relationship among the People and Families.
;Citation
;[[Citations|Citation]]
:In TNG, a <i><b>citation</b></i> is a reference to a previously defined [[#S|source]] which provides evidence about some aspect of an individual's record, for example, where you derived the date and place of their birth.
:In genealogy application, a <i><b>citation</b></i> is a reference to a previously defined [[#S|source]] which provides evidence about some aspect of an database record, for example, where the date and place of an Individual's birth is documented. [[Citations|More Details]]
:The same source can be cited multiple times. For example, a single source such as a death certificate can provide multiple pieces of evidence, such as a person's name, the date and place of death, the cause of death, and the age at death.
:The same source can be cited multiple times. For example, a single source such as a death certificate can provide multiple pieces of evidence, such as a person's name, the date and place of death, the cause of death, and the age at death.
;CSS
;CSS
:Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation semantics (the look and formatting) of a document written in a markup language. Its most common application is to style web pages written in HTML and XHTML. See [http://www.w3schools.com/Css/css_syntax.asp CSS Syntax Reference] for additional details.
:Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation semantics (the look and formatting) of a document written in a markup language. Its most common application is to style web pages written in HTML and XHTML. See [http://www.w3schools.com/Css/css_syntax.asp CSS Syntax Reference] for additional details.
==D==
==D==
;[[:Category:Data Protection|Data Protection]]=
;[[:Category:Data Protection|Data Protection]]
:Data Protection means having a complete [[Data Protection and Recovery Plan|data backup and recovery plan]] for all the content of your TNG site, your files, your configurations, your customizations, and your MySQL database, both the database structure and database table content. See the Category [[:Category:Data Protection|Data Protection]] for additional articles.
:Data Protection means having a complete [[Data Protection and Recovery Plan|data backup and recovery plan]] for all the content of your TNG site, your files, your configurations, your customizations, and your MySQL database, both the database structure and database table content. See the Category [[:Category:Data Protection|Data Protection]] for additional articles.
;[[dates|Date]]
;[[dates|Date]]
: A date records the calendar day on which an event took place (for example, 5 Jun 1987), or the series of sequential days over which an ongoing event or condition occurred (for example, FROM 3 Apr 1901 TO 31 Mar 1911). In TNG, uncertain dates may be qualified by the addition of date modifiers (for example, BEF 1835).
: A date records the calendar day on which an event took place (for example, 5 Jun 1987), or the series of sequential days over which an ongoing event or condition occurred (for example, FROM 3 Apr 1901 TO 31 Mar 1911). In TNG, uncertain dates may be qualified by the addition of date modifiers (for example, BEF 1835).
:See [[Dates]] for more details.
:See [[Dates]] for more details.
:See [[Inputting Dates - Eingabemoeglichkeiten]] on guidelines for inputting dates in a multi-language environment.
:See [[Inputting Dates - Eingabemoeglichkeiten]] on guidelines for inputting dates in a multi-language environment.
;Documents
;Documents
* 'Documents' is one of the TNG [[Media_-_Collections|media collections]] (aka Mediatypes). The Documents collection is generally used for Media Items that represent formal documents such as census, birth, marriage, and death records.
* 'Documents' (such as Word Documents or PDF files) that contain stories about a person or family are generally stored in the Histories collection. Researchers on different TNG sites (and possibly different trees on one site) may make different choices about creating custom collections for documents that represent wills, military records, censuses, birth records, and so on.
;<span ID="Dynamic Web Page">Dynamic Web Page</span>
:Unlike a static web page that physically exists on the website and never changes, a dynamic page is created by scripting on the server or in a browser, and it only exists for the period of time it is being viewed. When the browser finishes, the page is removed from memory and no longer exists. Because TNG consists of PHP programs, which generate HTML documents on-the-fly, all TNG pages are dynamic.
==E==
==E==
;Event=
;Event
:In genealogy: a significant happening, occurring at a specific time and place, that can be used to differentiate one's ancestors or descendants from non-relatives. Of particular interest are dates and places of birth, baptism, wedding, death, and burial.
:In genealogy: a significant happening, typically occurring at a specific time and place, that characterizes a person. In genealogical databases (including TNG) Person and Family data records consist of Events rather than Attributes. In general, even data elements like Name and Sex are often treated as Events. Of particular interest are dates and places of birth, baptism, wedding, death, and burial.
:Note that in TNG and the Gedcom standard, Events correspond to this general definition, but at a technical level, TNG Events and Gedcom Events are slightly different.
;Export
;Export
:Generally, saving data from an application's internal storage to a file format that can imported into another program - or, perhaps, that can be viewed by a person, or stored and later restored to the application.
:In TNG, this usually refers to exporting database data either for backup or to be transferred to another database, or to exporting genealogical data into a Gedcom files (at Admin >> Import/Export)
==F==
==F==
;Family=
;Family
# Traditionally, a social unit made up of one or two parents and their children, or any variations on that theme such as "immediate family", "nuclear family", "extended family", etc.
# In TNG and other genealogical applications, a "Family" is essentially a "couple", married or not. A Family record contains fields called "Husband" and "Wife", which point to Person records. Though children are logically part of a Family, at a technical level, Children are not part of a Family record; they are defined by a linking table that connects People to Families
:There is no nomenclature in TNG to distinguish the Family defined by a Family record from the larger notion of a Family as a set of all people in the database who are related.
:The Family ID in TNG must be unique within the selected Tree and should consist of an upper case F followed by a number
;FamilyID
:A FamilyID is the unique identifier of a Family record within a Tree. A FamilyID must consist of one capital letter (almost always 'F') and an integer number. To identify a Family records uniquely across all Trees in a TNG database, the FamilyID must be combined with a TreeID.
;[[File Transfer]]
;[[File Transfer]]
:Because TNG is installed on a [[Web Host]], installing and modifying TNG involves moving files between a person’s home computer and the web host's computer. Systems such as FTP and SSH have been developed to accomplish this file transfer securely. See [[File Transfer]] for more details.
:Because TNG is installed on a [[Web Host]], installing and modifying TNG involves moving files between a person’s home computer and the web host's computer. Systems such as FTP and SSH have been developed to accomplish this file transfer securely. See [[File Transfer]] for more details.
;[[FileZilla - FTP Client|FTP]]
;[[FTP]] ('''F'''ile '''Transfer''' '''Protocol''')
# A widely used protocol for exchanging files over any network (such as the Internet) that supports the TCP/IP protocol.
# 2. A program that uses the FTP protocol to transmit or receive files across a network.
# 3. The act of using FTP to transfer a file. ("You need to FTP that file to your server.")
: See the [[FTP]] article and the the article on [[FileZilla - FTP Client]], which is a free FTP client that can be used on most personal computers.
==G==
==G==
; GEDCOM=
; GEDCOM
:GEDCOM, an acronym for GEnealogical Data COMmunication, is a de facto specification for exchanging genealogical data between different genealogy software.
:GEDCOM, an acronym for GEnealogical Data COMmunication, is a de facto text file specification for exchanging genealogical data among different genealogy applications. It also, unintentionally, turns out to be a genealogical data model.
::See [http://www.tamurajones.net/AGentleIntroductionToGEDCOM.xhtml A Gentle Introduction to GEDCOM] for additional details.
:gedcom (in lower case) is the field name used in the TNG database for a [[#T|TreeID]]. It is a key value in most database tables. Its name derives from the fact that many TNG databases are built from one or more Gedcom files, and each Gedcom file can be associated with a Tree.
::See [[GEDCOM]] for additional details.
::See [[Import_Data]] for an approach to importing GEDCOM data.
::See [[Import_Data]] for an approach to importing GEDCOM data.
::See [[Setup_-_Tree#Prevent_GEDCOM_Downloads|Setup Tree]] for option on preventing anonymous GEDCOM downloads.
::See [[Setup_-_Tree#Prevent_GEDCOM_Downloads|Setup Tree]] for option on preventing anonymous GEDCOM downloads.
;[[Google Maps - Geocoding Places|Geocodes]]
: Geocodes are the latitude and longitude for a location (and sometimes, the zoom level applied to a map that includes that location). In TNG, Geocodes can be applied to Places, Cemeteries, and Media Item (where they generally represent the location where a photograph was taken) Geocodes are needed for Events and Places to be positioned on the maps that TNG generates.
;[[Google Maps - Geocoding Places|Geocoding]]
;[[Google Maps - Geocoding Places|Geocoding]]
: Geocoding is the process of coding a latitude and longitude that then allows the display of Google Maps in TNG. The TNG Admin interface to Places provides a geocoding capability see [[Google Maps - Geocoding Places]] for more details.
:The process of looking up the Geocodes for a location is known as "Geocoding". TNG provides a utility that takes Placenames and uses Google Maps to look up their geocodes. TNG users can also establish Geocodes by clicking on a place on a Google map. [[Google Maps - Geocoding Places]] for more details.
;[[Users_and_Guests|Guest(s)]]
;[[Users_and_Guests|Guest(s)]]
==H==
==H==
;Headstone=
;Headstones
: Headstone is one of the [[Media_-_Collections|media collections]] or categories in TNG. Headstone allows you to associate headstone or gravestone photos to a person or family in TNG that can also then be associated to a TNG [[Cemeteries]] record.
: 'Headstones' is one of the TN [[Media_-_Collections|media collections]] (i.e. MediaTypes). This collection is primarily for photos of headstones and cemeteries, and allows you to both to associate those photos with a TNG [[#C|Cemetery]], and to specify where the grave is within a Cemetery, and whether the grave has, in fact, been located.
:The internet connects computers of many different kinds having different operating systems and applications that are largely incompatible with one another. Just as ASCII is a universal text coding system allowing email to be read across platforms, HTML was created specifically to allow readability across platforms on the web. See [http://www.w3schools.com/tags/default.asp HTML Reference] for additional details.
;Histories
: 'Histories' is one of the TNG [[Media_-_Collections|media collections]] (i.e. MediaTypes). This collection is typically used for things like historical photos, scans of anecdotes from books, and stories that could be in text, PDF, and/or Microsoft Word format. [[Histories|more information]]
;<span id="HTML">HTML</span>
: Hypertext Markup Language (HTML) is the predominant markup language for web pages. HTML elements are the basic building-blocks needed by a browser to display a webpage. For a comprehensive article on this subject, see [http://en.wikipedia.org/wiki/HTML Wikipedia - HTML]. Additional details may be found at [http://www.w3schools.com/html/html_intro.asp HTML Intro] and [http://www.w3schools.com/tags/default.asp HTML Reference] on the w3schools website.
==I==
==I==
;Image Map=
;Image Map
: In HTML and XHTML, an image map is a list of coordinates relating to a specific image, created in order to hyperlink areas of the image to various destinations (as opposed to a normal image link, in which the entire area of the image links to a single destination). For example, in TNG you can use the Image Map section of Add or Edit Media record to create a link for an individual in a group photo to that individual's page within your TNG site. See [[Media_-_Add_New#Image_Map|Image Map]] for an example of how image maps are created in conjunction with the [[Tooltip Mod]]
: In HTML and XHTML, an image map is a list of coordinates relating to a specific image, created in order to hyperlink areas of the image to various destinations (as opposed to a normal image link, in which the entire area of the image links to a single destination). For example, in TNG you can use the Image Map section of Add or Edit Media record to create a link for an individual in a group photo to that individual's page within your TNG site. See [[Media_-_Add_New#Image_Map|Image Map]] for an example of how image maps are created in conjunction with the [[Tooltip Mod]]
;Import
;Import
: To bring external files or links into TNG. This can refer to [[Import Data|GEDCOM data]] or [[Media - Import|Media]].
: To bring external files or links into TNG. This can refer to [[Import Data|GEDCOM data]] or [[Media - Import|Media]].
;[[Individuals|Individual]]
;Individual
: Commonly refers to a unique subject of study in genealogy or a unique entry in database such as TNG. Note that due to lack of evidence or error more than one Individual may refer to the same person.
: A person (record) in a genealogy database. Due to lack of evidence or error more than one Individual could refer to the same actual person.
==L==
==L==
;Language=
;Language
# Natural Language - English, French, German, etc. TNG has been translated into over 20 languages through the use of Language Strings in TNG code. Languages strings are in the TNG subfolder named '''Languages'''.
# Computer Language - HTML, CSS, PHP, and JavaScript are the four computer languages that are fundamental to TNG. PHP and JavaScript are programming languages; they consist of statements that can be executed. HTML is a "markup language" that ''describes'' the document in which it is embedded. CSS is a 'formatting language'. It describes how HTML documents are to appear when they are rendered by a web browser.
;Lineal Ancestor
;Lineal Ancestor
;Log
;Log
: A file whose entries describe an action that has taken place. TNG logs are all text files, and, for the most part, one log entry is described on one line in the text file. TNG log filenames end with "log.txt".
==M==
==M==
;Merge
;Merge
:Merge in TNG means to combine records. In TNG, you can combine or merge [[People - Merge | People]], [[Places - Merging | Places]], [[Repositories - Merging |Repositories]], or Sources. Note that if you use a [[Import Data | gedcom import]] to replace your data, then merges made in TNG will be lost next time you do an Import.
:Merge in TNG means to combine records. In TNG, you can combine or merge [[People - Merge | People]], [[Places - Merging | Places]], [[Repositories - Merging |Repositories]], or Sources. Note that if you use a [[Import Data | gedcom import]] to replace your data, then merges made in TNG will be lost next time you do an Import.
;[[Mobile Mode Display|Mobile Mode]]
: TNG V10 added the automatic detection that it was being used on a mobile devices. It automatically sets the $sitever to mobile on smart phones and adjusts some of the displays. It automatically sets the $sitever to tablet for tablets but the displays continue to be in standard mode. Some mods like the [[Census Plus International]] mod reduce the size of the census transcript display when on a tablet so that the tables fit within the screen width.
;[[Mod Manager|Mod Manager]]
;[[Mod Manager|Mod Manager]]
:The Mod Manager (an administrative control built into TNG from v8 onwards) is a facility which provides an integrated way to install/remove and manage modifications (mods) to a TNG site installation using config files that have been coded according to its syntax rules. [[Mod Manager|More details]]
:The Mod Manager (an administrative control built into TNG from v8 onwards) is a facility which provides an integrated way to install/remove and manage modifications (mods) to a TNG site installation using config files that have been coded according to its syntax rules. [[Mod Manager|More details]]
;[[Mod Manager|Mod]]
: A TNG Mod is a package of files whose purpose is to change or add some aspect of TNG's functionality by modifying TNG files and/or installing new TNG files. The essential component of a TNG mod is a command file (with the filename extension .cfg) that tells the Mod Manager what changes to make to existing files, and where to install any other files packaged with the .cfg file. Mod .cfg files are normally referred to as "cfg files") to avoid confusion with the other meaning of [[#C|config files]]) in TNG.
;[[Database_-_Creating|MySQL]]
: MySQL (pronounced "My S-Q-L" or "My sequel") is a free, open source, Relational Database Management System (RDBMS). TNG is essentially dependent on MySQL as its database application. (MariaDB, which is a RDBMS that is designed as "plug-in" replacement to MySQL, is being used on a few TNG sites.)
==N==
==N==
;Note
;Note
: Formally, in TNG (and other genealogy databases), a Note is a record that consists of text and that is linked to some other kind of record - most often a person or event. There is no structure to a note, and notes cannot be linked directly to [[#S|Sources]], so notes often contain their own source information.
: In most genealogy applications, Event records have a text field that ''can be'', and too-often is used like a note, but that is 'supposed to be' just an Event value (such as the occupation associated with an Occupation event, or school name and/or degree associated with a Education or Graduation event).
==P==
==P==
;People
;People
: In TNG, the database table that contains information about [[#I|Individuals]] (i.e. People), is called the People table.
;Person ID
;Person ID
:The unique identifier of a Person (i.e. Individual) record within a Gedcom file or a TNG tree. It must consist of a single upper-case letter (almost always 'I') followed by an integer number. Note that TNG databases can consist of multiple '''[[#T|Trees]]''', so the actual unique identifier of a Person ''record'' in a TNG database consists of a Person ID and a tree identifier.
;<span id="PHP">PHP</span>
: PHP is an interpreted programming language designed to run on a web server, and to produce [[TNG Glossary#Dynamic Web Page|dynamic web pages]].
;PHP
: For almost all practical purposes, PHP runs only in the context of a web server. In particular, PHP programs cannot be compiled and run independently on a personal computer. For a comprehensive article on this subject, see [http://en.wikipedia.org/wiki/PHP Wikipedia-PHP]. <br />
:PHP is a server-side HTML embedded scripting language that was developed in C and is designed especially for working with relational database systems. See [http://www.php.net/ PHP net] for additional details.
:See [http://www.php.net/ PHP net] for additional details.
;Photos
;Photos
: Photos is one of the [[Media_-_Collections|media collections]] or categories in TNG. Photos allows you to associate photos to a Person or Family in TNG.
: In TNG, media items are assigned to [[Media_-_Collections|media collections]] (aka 'mediatypes'). One of those mediatypes is called "Photos", and, not surprisingly, is intended to contain photographs of people and families. (There are other collections for photos of other objects.)
;Place
;Place
: Place in TNG is the location where an event occurred. [[Places - Merging]] provides examples of using a wild card to select places to be merged.
: In genealogy applications such as TNG, a Place is the location where an Event occurred. Place values are known as Placenames. In TNG, Places are database records whose attributes include the Placename (of course), geographic coordinates (latitude and longitude), descriptive text, etc.
;Placename
: The text string that identifies a Place. Placename components (city, count, state, etc) are not divided into separate fields, but are all in the Placename string, where they are separated by commas. In TNG, Placename values are not taken from or checked against a "place authority" that is supposed to know all placenames in some jurisdiction. As a result, more than one Placename value can refer to one actual place. That is, for example, Placenames such as "Chicago, Illinois", "Chicago, IL", and "Chicago, Cook County, Illinois, USA" can all exist in the same tree (and in the tree's Places list).
==R==
==R==
;Recordings
;Recordings
: Recordings is one of the [[Media_-_Collections|media collections]] or categories in TNG. Recordings allows you to associate audio recordings to a Person or Family in TNG.
: 'Recordings' is one of the [[Media_-_Collections|media collections]] or 'MediaTypes' in TNG. Like all Media Items, Recordings can be associated with People and Families in the TNG Database.
;[[Users_and_Guests|Registered User(s)]]
;[[Users_and_Guests|Registered User(s)]]
;[[Reports|Report]]
;[[Reports|Report]]
:A '''TNG Report''' is a custom-built listing of people contained in your TNG database. Using the report builder you select which fields to display, which people to put in the report, and how to sort them.
: A '''TNG Report''' is a custom-built listing of people contained in your TNG database. Using the report builder you select which fields to display, which people to put in the report, and how to sort them.
:Optionally, a TNG Report can also use a raw mySQL <i><b>SELECT</b></i> statement to extract <i><b>any</b></i> data contained within a TNG database. For example, you could create a report giving the ID# of each record containing a citation of a certain source. The language of a mySQL statement can become quite convoluted and requires some studying before its full power can be realized. There are a number of examples to be found via a TNG Wiki search on the word "report". See [[Reports]] or [[:Category:Reports]] for more details.
: Optionally, a TNG Report can also use a raw [[#M|MySQL]] <i><b>SELECT</b></i> statement to extract <i><b>any</b></i> data contained within a TNG database. For example, you could create a report giving the ID# of each record containing a citation of a certain source. The language of a mySQL statement can become quite convoluted and requires some studying before its full power can be realized. There are a number of examples to be found via a TNG Wiki search on the word "report". See [[Reports]] or [[:Category:Reports]] for more details.
;[[Repositories|Repository]]
;[[Repositories|Repository]]
: A '''Repository''' is any collection of sources, physical or otherwise. TNG will automatically build the Repositories from the gedcom data import if they exist in your desktop software and are exported. [[Repositories|More details]]
: A '''Repository''' is a place where '''[[#S|Sources]]''' are stored, such as a public or private library, a county courthouse, a bookstore, a web site, or even an email system. Of course, many Sources exists at more than one Repository. It is not necessary for researchers to record where ''they'' obtained a source, but is generally best to record a Repository from which the Source can be obtained. [[Repositories|More details]]
;[[Database - Restore|Restore]]
;[[Database - Restore|Restore]]
;[[:Category:Setup|Setup]]
;[[:Category:Setup|Setup]]
:See the various articles in the [[:Category:Setup|Setup]] category in the left sidebar.
:See the various articles in the [[:Category:Setup|Setup]] category in the left sidebar.
;Settings
;Settings
;Source
:In TNG a <i><b>source</b></i> is defined as any form of evidence cited to prove or substantiate any part of your data. The same source may be cited multiple times for multiple individuals, families or events.
;[[Sources|Source]]
:In TNG a <i><b>source</b></i> is defined as any form of evidence cited to prove or substantiate any part of your data. The same source may be cited multiple times for multiple individuals, families or events. [[Sources|More Details]]
;SQL
;SQL
:Structured Query Language (SQL) is a database computer language designed for managing data in relational database management systems (RDBMS). See [http://en.wikipedia.org/wiki/SQL Wikipedia article on SQL] for history and [http://www.w3schools.com/sql/default.asp W3school for tutorial] on SQL.
: Structured Query Language (SQ; pronounced either S-Q-L or "sequel") is a database computer language designed for managing data in relational database management systems (RDBMS). TNG uses SQL for most of its database operations. for See [http://en.wikipedia.org/wiki/SQL Wikipedia article on SQL] for history and [http://www.w3schools.com/sql/default.asp W3school for tutorial] on SQL.
:Though SQL is a "standard" language, most RDBMSs implement some extensions or omit some functions. As a result, applications tend to be dependent on a specific RDBMS product. TNG uses an RDBMS called [[#M|MySQL]].
:SQL (pronounced either S-Q-L or "sequel") is a powerful database query language. It has been around for decades in numerous versions and editions on many platforms. If you learn one version well, you can probably move to another with ease. The TNG database is a MySQL database. MySQL (my-S-Q-L or "my sequel") is an open source relational database manager now owned by Oracle.
;SSH
;SSH
:[http://en.wikipedia.org/wiki/Secure_Shell SSH] or Secure Shell is a system of secure file transfer over the Internet using encryption. See [[File Transfer]] for more details.
: [http://en.wikipedia.org/wiki/Secure_Shell SSH] or Secure Shell is a system of secure file transfer over the Internet using encryption. See [[File Transfer]] for more details.
==T==
==T==
; Tablets
: TNG v10 automatically detects that it is running on a tablet and set the $sitever to '''tablet'''. The display continues to be in standard mode, but some mods like the [[Census Plus International]] mod reduce the size of the census transcript display when on a tablet so that the tables fit within the screen width. See[[Tuning for Tablet Display]]
;Timeline
;Timeline
: See [[Timeline - Setup]]
: See [[Timeline - Setup]]
: A Tree in TNG is a container for any independent set of family data. TNG allows you to support multiple Trees on your site, but since Trees are independent, you cannot link a person in one tree to any person or family in another tree. See [[Setup - Tree]] for more details on setting up a tree.
; [[Setup - Tree|Tree]]
: A Tree in TNG is a container for any independent set of family data. Trees do not just contain People, but also Families, Sources, Repositories, Notes, Media objects, and, usually, Places. The people in a tree do not necessarily all have to be related, but the reason for setting up separate trees is usually to separate one person in one tree to a person or family in another tree.
: Most TNG sites have only tree, though multiple trees are not rare. One common use for two trees is for a TNG administrator to set up separate trees for "his" ancestors and "her" ancestors. In such a case, any common descendants must either be recorded in both tree, or be missing from one tree. See [[Setup - Tree]].
;Tree ID
;Tree ID
: The Tree ID in TNG is a short, unique, one-word identifier for a tree. It can only contain alphanumeric characters. In TNG databases, the Tree ID field is universally named "gedcom", or a variant of "gedcom" when a record has more than on TreeID field)
:The Tree ID in TNG is a short, unique, one-word identifier for the tree. Do not include non-alphanumeric characters (stick to numbers and letters), and do not use spaces.
;Tree Name
;Tree Name
: The Tree Name in TNG is a short display name or phrase to identify this tree. This will appear in all tree selection boxes, and will be the name by which visitors know this tree.
:The Tree Name in TNG is a short display name or phrase to identify this tree. This will appear in all tree selection boxes, and will be the name by which visitors know this tree.
==U==
==U==
;[[Users_and_Guests|User(s)]]
;[[Users_and_Guests|User(s)]]
# Formal TNG definition: Those persons approved by a website administrator to assist with the entry and maintenance of the data displayed on a TNG website. See [[Users and Guests]] for more details.
# In some applications, and in some TNG documentation, the term <b>user</b> is simply a generic term for anyone <b>using</b> an application or web site - as in "be kind to inexperienced users", which could refer equally well to a TNG '''user''' or to a TNG [[#G|guest]].
;Utility
;Utility
