Changes between Version 217 and Version 218 of ippToPsps

Timestamp:

Apr 2, 2012, 1:46:25 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -4 +4 @@
 [[PageOutline]]
 
-{{{ippToPsps}}} is the interface between IPP and PSPS. At the highest level, its job is to create FITS files, generated from a multitude of IPP data-sources, and then publish them to a datastore in the form of ''batches''. On the PSPS side, the {{{DXLayer}}} polls the datastore, collects batches when they become available, then converts the contents to {{{csv}}} files before sending them on to SQL Server loader software, which ''merges'' them into the relevant PSPS database. 
+{{{ippToPsps}}} is the interface between IPP and PSPS. It creates FITS files generated from a multitude of IPP data-sources then publishes them to a datastore in the form of ''batches''. On the PSPS side, the {{{DXLayer}}} polls the datastore, collects batches when they become available, then converts the contents to {{{csv}}} files before sending them on to SQL Server loader software, which ''merges'' them into the relevant PSPS database. 
 
 The binary tables in the FITS files generated by {{{ippToPsps}}} match the PSPS database schema perfectly, the consequence being that any alterations to the PSPS database schema will only affect {{{ippToPsps}}} code, and not the {{{DXLayer}}}. A certain amount of data validation is performed by {{{ippToPsps}}} before publication, with more validation occurring at the loading and merge stages on the PSPS side.
@@ -10 +10 @@
 Simultaneously to loading data, {{{ippToPsps}}} polls PSPS to inquire after the status of the batches it has loaded. Batches that failed can then be reloaded. The status of every batch is maintained in a MySQL database local to {{{ippToPsps}}}. The various temporary copies of the batches are deleted once the ODM reports that they have been successfully loaded or merged.
 
-Some notes prepared for the PSPS operational readiness review can be found [wiki:ippToPspsOrr here].
 
 = Batch types =