use metacat events to trigger spatial element creation
Currently, the creation of spatial elements used within the Metacat spatial
viewer is done through a call to an external harvester via a cron job. This
needs to change to a workflow that includes the creation of spatial elements
during metacat (insertion, update, deletion) transactions. Moreover, these
elements need to be more tightly coupled with Metacat (eg, Metacat needs to have
knowledge of the various elements stored and how these elements correspond to
data and metdata within Metacat).
#1 Updated by Matthew Perry about 15 years ago
Currently the metacat spatial harvester is triggered on servlet restart.
Doing it on every insert, update and delete could be very CPU intensive and might not scale very well.
As a alternate medium ground, we might want to consider a password-protected admin interface (bug 2190) where the site admin could manually trigger the harvester or set a regular interval at which the harvester was tiggered.
See also bug 2499 - rewriting the harvester with java components.
#2 Updated by Matthew Perry almost 15 years ago
Based on a discussion w/ Sid this morning, we determined that we'll need to tie the spatial harvesting trigger to the indexing mechanism. Because the most efficient way to query the spatial info comes from the xml_path_index table, we have to make sure indexing has completed before we trigger the spatial harvester to update that docid.