Difference between revisions of "Places Subject to Deletion"
(updated for TNG V11)
|Line 204:||Line 204:|
| Public site
| Public site
| NL, EN
| NL, EN
Revision as of 15:58, 16 April 2016
|The Places Subject to Deletion is an implementation of the Maintenance - Pooled Places with no Events report in the Admin >> Places.||
|Places Subject to Deletion|
|Summary||Provides a list of Places with no associated events|
|Download stats||View download statistics|
|Author(s)||Ken Roy with help from |
Mark Wonson and Warren S. Gilbert
|Homepage||Places Subject to Deletion|
|Mod Support||TNG Forums|
|Latest Mod||10.1.0.1 for TNG 10.1 and up|
126.96.36.199 for TNG v9.2.2 and up
|Min TNG V||9.2.2|
|Max TNG V||11+|
Purpose of the mod
This mod incorporates the code provided in the Maintenance - Pooled Places with no Events report of places that are not linked to any event that allows an easy way to delete these places from your TNG database.
The mod should detect all unused places whether they contain geocodes which were not deleted by TNG on an import since TNG V6.1 or because you are now Pooling Places since TNG V9 and thus places are no longer deleted before an import, since they are no longer associated with the tree being imported.
Note that before using the capability of this mod to delete any places you should create a backup of your TNG database.
- A working TNG installation.
- A backup of all affected files (see the list in the summary in the upper right corner of the page)
- A backup of your database tables before using the mod to delete locations.
- Download the appropriate zip file as shown in the summary in the upper right corner of the page.
- Extract the files and folder from the downloaded zip file into the mods folder or FTP the extracted files and folder to your mods folder.
- Follow the normal automated installation for Mod Manager, as shown in the example Mod Manager - Installing Config Files to install the mod.
|v10.1.0.1||13 January 2015||Updated for TNG 10.1 so no code follows the %location:% and %insert:after% directives which was causing a critical error.|
|v188.8.131.52||5 March 2014||Initial release of the mod|
An Approach to Using
The option to select only Places With no associated Events was added by the Places Subject to Deletion mod.
A recommended approach is to search for locations that contain part of the Place location name and then to check the box "With no associated Events" and search again.
If you want to spot check that the locations returned are truly without any event association, you could do the verify in a list of locations without the box checked.
When you are satisfied the list are those of Place locations without any associated events, you can then click the Select All button and the Delete Selected button to remove those locations that do not have any associated events.
However, you may want to use the Admin >> Places >> Merge capability so that if the new cleaned up location name does not have geocoded information the Merge process will update the Place record. See the Merge or Delete section below.
The returned list includes places with geocodes as well as those without geocodes that do no have any associated events.
Click on the Test icon in the returned list to open the Place in another window or tab, where you can then verify that no events are associated with the place.
You can modify the Maintenance - Pooled Places with no Events report to add the following at the bottom of the current SQL
AND place LIKE '%Maine%' ORDER BY place, gedcom, ID
where you would specify the same place location name that you are going to use in the Places Subject to Deletion search.
The results for both should be identical
Merge or Delete
Even though a Place name might not have any associated Events, you may want to use the Merge tab and search for the same Place name, since a merge will transfer the correct geocodes to a location that is not geocoded.
|TNG version:||≥ 9.0|
|TNG version:||≥ 10.0|
See also Places - Merging
Sites using this mod
If you download and install this mod, please add your site to the table below.
|Our Roy and Boucher Family||Ken Roy||Mod developer with help from Mark Wonson and Warren Gilbert||184.108.40.206/10.1.0.1||10.0.3/10.1.0 beta 3||English, French|
|Kemp(e) Family History||Andrew Kemp||see User:Kempons||see User:Kempons||English|
|Hooley Family Links||Rick Hooley||Public Site||10.1.0.1||10.1.1||EN|
|Chamberlain & Eidenbenz Genealogy||Graham Chamberlain||10.1.0.1||10.0.3/10.1.0beta3||EN,FR,DE,NL,ES|
|Robin's Genealogy Database||Robin Richmond||Public site||10.0.0.1||10.0.3||EN|
|MacomberKin||Rev. Clinton Macomber||Been using for a while: MUST HAVE for large site.||10.0.0.1||10.0.3+||EN|
|DJCM.DK||Claus Martinussen||Public site||10.1.0.1||10.1.3||DA,EN|
|Kleinmann Genealogy||John Kleinmann||10.1.0.1||11.0||EN|
|Bastiaans(s)en Genealogy||Jan Bastiaanssen||Public site||10.1.0.1||10.1.2||EN, NL ES|
|Wortelboer Genealogy||Bernard Wortelboer||Public site||10.1.0.1||11.0.0||NL, EN|
Places Subject to Deletion
- Original SQL - Luke Weerts
- Maintenance - Pooled Places with no Events by Mark Wonson and Warren Gilbert