Help: Repositories

Manage

This tab allows you to locate existing repositories, then edit or delete them.

Search for
Enter a keyword (or part of a word) matching all or part of the following fields: Repository ID, Repository Name. A cookie will store the value entered here for future searches. Click the Search button to execute the search. Click the Reset button to blank out the field. If the Search button is clicked with no search criteria, all repository records will be returned.

Tree
Select a tree from this dropdown box prior to clicking the Search button to restrict the results to repositories assigned to the selected tree.

Exact match only
Check this box prior to clicking the Search button to restrict the results to records where one of the fields named above matches the search criteria exactly.

Edit/Delete/Test
Click on the appropriate icon in the Action column to edit, delete or test (preview) the repository record listed on that row.



Add New / Modify Existing Repositories

To add a new repository, click on the Add New tab, then fill out the form. To edit an existing repository, click on the Manage tab, then locate the repository using the Search utility and click the Edit icon next to that repository.

Fields available on both the Add New Repository and Modify Existing Repository screens include:

Tree
Select one of your existing trees. Each repository must be assigned to a tree. The tree assignment may not be changed once a repository is created (instead, delete the repository and re-add it under another tree).

Repository ID
The Repository ID must be unique and should consist of an upper case "REPO" followed by a number. An available, unique ID will be supplied when the page is first displayed and whenever a different tree is selected, but you may enter your own ID if desired. To check if the ID you have entered is unique, click Check. A small pop-up window will tell you if the ID is in use or not. To automatically generate a new unique ID, click Generate. This will locate the highest number in your database and add 1. A small window may briefly appear and disappear. To ensure that the displayed ID is not claimed by another user before you can save your record, click Lock. NOTE: If you are using this software in conjunction with a PC/Mac-based genealogy program which also creates IDs for new records, it is HIGHLY RECOMMENDED that keep all IDs in sync between the two programs at all times. Failure to do this may result in collisions, and may also cause your repository associations to become unusable. If your desktop program creates IDs that do not conform to traditional standards (for example, the "S" is at the end, not the beginning), you can edit the "prefixes.php" file that came with TNG to change the convention TNG uses to match this.

Name
An abbreviated title for the repository.

Address 1, Address 2, City, State/Province, Zip/Postal Code, Country
The repository's location (all parts are optional).

Other Events
Use the buttons below the Other Events box to add, edit or delete non-standard events. The order in which these events are displayed is determined by date (if applicable), and by the event types' assigned priority. This priority may be changed when editing the event types. NOTES: Changes made here are written to the database as they are made, meaning that they are already saved before you save the rest of the Existing Repository information.



Delete Repositories

To delete one repository, click on the Delete icon next to that repository on the Manage tab. To delete more than one repository at a time, check the Select box next to each repository to be deleted, then click the Delete Selected button.



Merge

Click on this tab to review and merge repositories that may be slightly different but refer to the same material. You will decide whether multiple records are the same or not.

Find Matches
First, select a tree. You cannot merge repositories from different trees, so only one tree can be selected. After that, you have the option of selecting a repository as the starting point for your search (Repository ID 1), or letting TNG find the first match for you. If you'd rather let TNG find all matches, leave the Repository ID 1 field blank

If you selected a repository as Repository ID 1, you may also decide to manually select Repository ID 2. If you'd rather let TNG find duplicates for Repository ID 1, leave Repository ID 2 blank.

Match the following fields
These are the criteria TNG will use in determining possible matches. By default, Short Title and (Long) Title are selected, meaning that those fields must match in order for two records to be considered a possible match. If you also select Author, Publisher, Repository, or Actual Text, then those fields must also match.

Other Options
Combine Notes means that notes from Repository 2 will be added to the notes from Repository 1 for all merged fields. If this option is not selected and a field from Repository 2 is checked, the notes from Repository 2 for that field will overwrite those for the corresponding field from Repository 1. Combine Media means that media from Repository 2 will be kept and added to the media already existing for Repository 1 if the two are merged. If this option is not selected, all media links for Repository 2 will be deleted after the merge.

Warning! Once a merge has taken place, it cannot be undone! Please consider backing up your database tables before performing any merge operations, just in case you merge two individuals unintentionally.

Next Match
Find the next possible match that does not involve Repository 1. TNG traverses the list of possible repositories as ordered by Repository ID in string format. This means that "10" comes after "1" but before "2".

Next Duplicate
Find the next possible duplicate for Repository 1. If this results in no record being displayed for Repository 2, it means that a duplicate was not found.

Compare/Refresh
Compare Repository 1 and Repository 2. If that comparison is already displayed, clicking this button will cause the page to refresh.

Switch
Repository 1 becomes Repository 2 and vice versa.

Merge
Repository 2 is merged into Repository 1. The ID for Repository 1 will be retained, as will all other data for Repository 1 unless the corresponding box(es) for are checked for Repository 2. For example, if the box next to Author is checked for Repository 2, this data in this field will be copied from Repository 2's record to Repository 1's record during the merge. Corresponding data for Repository 1 will then be deleted. Boxes for Repository 2 are checked automatically when no corresponding data exists for Repository 1. If a data field is not displayed for either Repository 1 or Repository 2, then no data exists in that field for either individual.

Edit
Edit the record for that repository in a new window. If changes are made, you must click Compare/Refresh in order to see the changes in on the Merge screen.