Modifications

|__TOC__

|__TOC__

|}

|}

You can import media records into TNG by checking the box in front of '''Import media if  present''' in the TNG Admin >> Import/Export screen.

This is one of several ways to load new media files to TNG. (See [[Getting Media into TNG]]) This technique is available only to administrators, and is appropriate when you want to upload media files in conjunction with the upload of GEDCOM data.

'''Note'''  that TNG only imports the media links in a gedcom. You still have to  FTP the media to your site (unless your software uses the "BLOB" method  of encoding the actual media file into the GEDCOM file - this article is  NOT about this method).

# Configure TNG's media folders with the PC file paths that are used in your GEDCOM files. (One time)

# Upload your media files to the appropriate media folders, using [[FTP]] or a File Manager utility.

# Set the appropriate media collection for some of your files (as required).

# Create Thumbnails for your media files.

== Local Folder Setup ==

== Preliminaries ==

In  order to be able to import the media links in a GEDCOM file you need to  have a set of folders on your local computer that "mirror" the various media folders in your TNG setup. For example on your computer create a folder called "Genealogy Media" (in my examples below the folder is  called "ReunionPictures") and inside that a set of folders that matches  your TNG media folders. So for example:

 

In almost all cases, you must have a set of media folders on your PC (whether a Windows PC or a Macintosh) that match the media folders on your TNG server.  In  order to be able to import the media links in a GEDCOM file you need to  have a set of folders on your local computer that "mirror" the  media folders in your TNG setup.  You will typically have folders named "photos", "documents", "headstones", and "histories", and possibly others, depending on what custom collections you have defined.

 

shows  the 5 folders I have set up on my local computer to store the various  types of media item that are linked in my desktop genealogy software. These folders mirror the folders that are specified in the TNG Admin  >> Setup >> '''Import Settings''' >> Local foldername  Path(s)

===One Media Folder===

===One Media Folder===

Some  desktop programs, such as Family Tree Maker (which is associated with  Ancestry.com), cannot separate different types of media files into media  folders.  And, sometimes, the person managing a TNG site may decide not  to use separate media folders.  In those cases, there should be just one PC media folder and one one media folder on the server, and all of the media types in TNG Admin >> Setup >> '''Import  Settings''' >> Local foldername Path(s) will specify the same  folder name.

Some  desktop programs, such as Family Tree Maker (which is associated with  Ancestry.com), cannot separate different types of media files into media  folders.  And, sometimes, the person managing a TNG site may decide not  to use separate media folders.  In those cases, there whould be just one PC media folder and one one media folder on the TNG server, and all of the media types in TNG Admin >> Setup >> '''Import  Settings''' >> Local foldername Path(s) will specify the same  folder name.

 

A  media item in the GEDCOM file is represented by a block of lines that  might look similar to this.  Each line in a GEDCOM file is known as a  "segment" and is identified (not uniquely) by the keyword that follows the initial number. The three examples below represent the MacIntosh, a  Windows PC, and a local PC's simulated Linux environment.  The only  meaningful difference among the three is the FILE segment (on the second  line).

<pre>1 OBJE

A  media item in the GEDCOM file is represented by a set of lines that  might look similar to the examples just below.  Each line in a GEDCOM file is known as a  "segment" and is identified (not uniquely) by the keyword that follows the initial number. A GEDCOM "record" is a segment plus any subordinate segments (that start with larger numbers). The three examples below each show one hypothetical media record, and represent MacIntosh, a  Windows PC, and a local PC's simulated Linux environment.  The only  meaningful difference among the three is the FILE segment (on the second  line).

<pre>1 OBJE                             <span color="blue">Macintosh</span>                             

2 FORM jpg

2 FORM jpg

2 FILE ~/Documents/Documents/Genealogy/Roger/ReunionPictures/photos/people/RogerOval.JPG

2 FILE ~/Documents/Documents/Genealogy/Roger/ReunionPictures/photos/people/RogerOval.JPG

2 _SIZE 147.000000 193.000000</pre>

2 _SIZE 147.000000 193.000000</pre>

== Local Paths ==  

=== Local Paths ===  

 

Note that the GEDCOM media records specify a full file path and file name for the media file. There are two related complicating factors:# The file path from the device root to the collection folder will be different on the web server, and

You  have to tell TNG what your local paths for the media are in TNG Admin  >> Setup >> Import Settings screen as shown below. (Note that this screen shot is "doctored" to show the paths on multiple lines  so that the whole field contents can be seen.)

# The specified file path may include folders '''below''' the collection folder.

 

For instance, looking at the Macintosh example above, the partial path "~/Documents/Documents/Genealogy/Roger/ReunionPictures/people" represents the path to the collection folder (for photos, in this case), and the partial path "people/" indicates that the file is to be stored in a folder '''below''' the collection folder. As far as TNG is concerned, the filename is people/RogerOval.jpg.

To  determine what to put in these various path fields, open your GEDCOM file in a Text Editor and look for lines that start with "2 FILE" and  see what has been entered as the path to various folders that you set up as shown above. The path is everything after the "2 FILE " to the slash  (/ on Macintosh, \ on Windows) after the folder name (eg photos, headstones, documents etc). So for the first example above of the photo, the path is

 

<pre>~/Documents/Documents/Genealogy/Roger/ReunionPictures/photos/</pre>

while the item itself is

You have to tell TNG what your ''local'' paths for the media so that TNG can strip off that portion of the path when it imports the GEDCOM file.  You do that in the Administration >> Setup >> Import Settings screen as shown below. (Note  that this screen shot is "doctored" to show the paths on multiple lines  so that the whole field contents can be seen.)

<pre>people/RogerOval.JPG</pre>

If you know your local collection path, then you can just enter it in the form.  Or, you can look at a FILE segment of your GEDCOM file and extract the path to and including the collection folder ("photos", "documents", "histories", etc.).  

Some of these fields need multiple paths in them because desktop genealogy  software doesn't necessarily recognise all of the different media types  that TNG allows. So for example in the photos field I have entered the  path to the photos folder, and also the path to the headstones folder.  

Note that there is an entry (i.e. a field) on the form below for each standard TNG media collection, because it is generally assumed that you will separate the collections in different folders. But some of these fields need multiple paths in them because desktop genealogy  software doesn't necessarily recognise all of the different media types  that TNG allows. So for example in the photos field I have entered the  path to the photos folder, and also the path to the headstones folder.  

'''Note:''' separate multiple paths by a comma, do NOT include a space, but DO include the trailing / at the end of each path.

'''Note:''' separate multiple paths by a comma, do NOT include a space, but DO include the trailing / at the end of each path.