## Runs on interval (5 minutes (?)) ## Checks for new devices ## Checks for edited devices ## Constructs proper notifications and emails (needs history tables) # 1 Servlet (KG) ## Change instru view flag ### Pass in SSDS Device ID ### Set the flag on that device to allow it to show through the instru view # History Trigger on Device Table (KG)

# {html}{html}SQL to perform database normalization between BOG and SSDS{html}{html} (JG/AM) ## All XML in puckxml will have to have matching changes made # Create reporting SQL and schedule to send out reports of differences (AM) # Put links to CVS web xml in Device listing web page (KG) {tip} ---- {info:title=Details before combined table approach (deprecated)} # [Create New Device in Instru|http://oceana.shore.mbari.org:8081/display/AST/Use+Cases#Create%20New%20Device%20in%20Instru] ## Fire trigger on insert into instru table on BOG ## Search SSDS for matching device ## Insert of update device info in SSDS ## Update the BOG instru entry with SSDS ID ## Email SSDS admin of insert # [Edit Device in Instru|http://oceana.shore.mbari.org:8081/display/AST/Use+Cases#Edit%20Device%20in%20Instru] ## Fire trigger on update of instru table on BOG ## Search SSDS for matching device (match by ID) ## If found, update device table in SSDS ## If not found, throw flag to SSDS admin # [Create New Device in SSDS|http://oceana.shore.mbari.org:8081/display/AST/Use+Cases#Create%20New%20Device%20in%20SSDS] ## Need a new Create Device page in SSDS web application ### JSF validation ### Calls DAO to create new device ## Insert in device table in SSDS fires trigger ## Email is sent to OSG Operator ### OSG rejects, send email to SSDS admin (mailto: link in HTML email) ### OGS approves, link calls servlet that passes SSDS device ID and param to specify it is a call to create #### Servlet calls stored procedure that inserts new device in BOG # [Edit Device in SSDS|http://oceana.shore.mbari.org:8081/display/AST/Use+Cases#Edit%20Device%20in%20SSDS] ## Need to create new Device Edit page ### JSF Validation ### Calls DAO to update device ## Update on Device table fires trigger ### Email is sent to SSDS Admin ### If SSDS Admin clicks on reject link, he will be taken back to the edit page ### If SSDS Admin approves, servlet will be called (pass device ID) NOTE: Will need a history table on device to show differences #### If OSG approves, servlet is called, passing device ID and parameter to indicate update #### if OSG rejects: mailto: opens email to SSDSAdmin So based on these steps the following components need to be built: # Device Creation Page (KG) ## Authenticates against LDAP group ## JSF Validation # Device Edit Page (KG) # 4 Triggers (JG/AM) ## Fires when insert done on BOG instru table ## Fires when update done on BOG instru table ## Fires when insert done on SSDS_Metadata Device table ## Fires when update done on SSDS_Metadata Device table # 2 Stored procedures (JG/AM) ## synchBOGChangesToSSDS ### parameter: change or update ### searches SSDS for matching SSDS ID ### If nothing found and parameter was update, send error email to SSDS Admin (end) ### If nothing found and parameter was create, search for matching mfg name, model, serial number ### If no match, insert matching record into SSDS_Metadata device table and save SSDS ID ### If match, update entry in SSDS_Metadata Device table and save SSDS ID ### If BOG instru entry does not have SSDS ID, update entry to store saved SSDS ID ### Email results to SSDS Admin ## synchSSDSChangesToBOG ### parameters: SSDS ID and string create or update ### Query SSDS_Metadata Device table for device with SSDS ID ### If create, insert matching entry in BOG instru table ### If update, udpate matching entry in BOG instru table ### Send email to SSDS Admin # 2 Servlets (KG) ## Notify OSG Of Device Edit Servlet ### Pass in SSDS Device ID ### Grab old device information from history table ### Grab current device information from device table ### Construct email with differences report and approval/reject options ### Send email to OSG Operator ## Forward Changes to BOG from SSDS Servlet ### Parameters: SSDS ID and create or update ### Call stored procedure to push changes to BOG from SSDS and use parameters # History Trigger on Device Table (KG) # {html}{html}SQL to perform database normalization between BOG and SSDS{html}{html} (JG/AM) ## All XML in puckxml will have to have matching changes made # Create reporting SQL and schedule to send out reports of differences (AM) # Put links to CVS web xml in Device listing web page (KG) {info} h2. Notes: A proposal for an integrated set of database fields: [DatabaseFields] [AccessAppChanges] ---- During our design, questions were raised: # Does the Microsoft Access application have any validation (check for duplicate serial numbers, etc.)? _Generally speaking, no. Some fields (Mfg, Model, Device, ...)are regularized by using drop-downs on the new/edit dialog boxes._ ----]]> 861