Datzilla Overview / Workflow and Climate Tools from SRCC & SCIPP Kevin Robbins, Director Southern Regional Climate Center

Datzilla History and Background Datzilla began as a response to personal frustration in response to improper handling of an error report of an extreme rainfall event rejected by NCDC QA/QC. A successful web-based, open-source computer software error reporting and tracking system (Bugzilla) looked promising as a solution to data error reporting. The idea was presented to NCDC and dismissed… A prototype of Datzilla, modified from the Bugzilla system, was produced at the SRCC, demonstrated, and met with more enthusiasm Datzilla was finally adopted for trial and was eventually adopted as an operational system in March, It will have been in operation for 10 years next Spring. August

Datzilla Objectives Improve the quality of NOAA datasets Correct data observation errors Correct data processing errors Reduce systematic data errors Improve the response to user error submissions Ensure that user input is not overlooked or lost Provide users with resolution to submitted errors Make actions transparent to all users and data managers August

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment August

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment User Identifies Error Single observation error Group of missing data Product calculation error User interface problem Different data from different systems User submits error to Datzilla Specifies Source System, Data- Product, Problem Area, and describes the error The User may include attachment that further documents the problem by opening the error following the original submission A message is sent from the User to a Data Manger assigned by the combination of Source System and Data-Product The initial selection of the Data Manager is shown to the User prior to the error submission All communication is performed via and all messages are permanently stored within the Datzilla system August

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment The User waits for the Data Manager to examine the request The initial Data Manager looks at the request to decide a course of action Is the correct Source System, Data-Product selected? Is this a duplicate of a previous submission? Is this an actual problem? If everything is OK the Data Manager accepts the request and the system sends an to the User as an Assigned problem August

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment The User receives an assignment and continues to wait for the Data Manager to fix the request The Data Manager examines the request and begins work Categorize the error… Bad data value Data system synchronization Data-product error Problem with web browser Continued… User submission error … a more complicated problem that requires more information from User, elevation to a higher priority, or a deferment due to other pressing problems Or, the problem might be resolved. August

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment August When the Data Manager uncovers difficulty in understanding the nature of the data error, or needs to validate a User request, they often need to enter a dialog with the User to obtain additional information such as: Does the user have original source information that conflicts with the information they obtained from the Source System? Why does the User think that the original observation is not in error? Does the User have additional information that supports their confidence in the original observation? Sometimes the communication may involve multiple requests back and forth between the User and Data Manager

User identifies possible error User submits Datzilla ‘ticket’ Data Manager receives from Datzilla based on Source System and Data-Product Data Manager accepts, rejects or, reassigns error User is notified by Datzilla of error status User waits patiently for a resolution…. More information is needed from the User User receives request Check status… Data Manager request …..repeat as needed User response Automated Response Problem resolvedUser receives resolution Datzilla Workflow User receives request User may reopen ticket if not satisfied with response Data Manager ‘works’ the error assignment August At some point, a resolution on the User error is finalized and a message is sent from the Data Manager to the User. The resolution may include: Changes made to the observation, data processing method, or Data-Product user interface Changes made to some of the reported errors, but not to others No changes made to the “error” reported by the User Changes to larger issues in the “observation-to-dissemination” stream When a change to the data is made, the changes are propagated to NOAA data systems and to the RCC ACIS system to ensure data synchronization.

SCIPP & SRCC Tools Information Tools Developed With Stakeholder Input Southern U.S. Drought Average Monthly Temperature and Precipitation Historical Climate trends Climograph SURGEDAT Storm Surge Toolset Southern Climate Impacts Planning Program August

Datzilla or SCIPP Tools Questions? August