The POI database is an aggregated dataset from multiple source datasets. POI maintains links to the source data records.
1) Establish the rules of the road
i.e is POI readonly for all records with a source attribute - changes must occur first in the source database
editor tracking is required
...
2) Establish triggers in the source databases, to update POI when changes in the source occur.
Not possible for FGDB, but we can put all source database in the PDS on a watch list. They change very infrequently and only by the PDS Manager, so we can manually update POI as changes occur.
For SDE (only akr_facility2 at this point), we can add a new check in the QC process to identify issues.
if there is a linked record and the facility edit date is greater than the POI edit date, and either the name, type or shape column has changed, then update the POI record.
if a linked record is deleted, then delete the POI record (just check POI for orphans and delete)
if a new record is added to akr_facilities; issue a prompt to add to POI? or regularly, query facilities for records with a create date newer than last check and add any interesting records to POI. I don't see an easy way to automate this, especially since the POI type is subjective.
The POI database is an aggregated dataset from multiple source datasets. POI maintains links to the source data records.
1) Establish the rules of the road