How Catch Effort data is processed

The Ministry of Fisheries contracts FishServe to enter and validate (correct errors in) Catch Effort information. The Ministry operates the Catch Effort computer system (including writing new error checks), and sets standards and specifications for data entry and validation. This page describes how a Catch Effort form is processed after it arrives at FishServe. 

The processing of New Zealand's Catch Effort information is centralised (there are not different computer systems for different regions or fisheries). Fishers send approximately 200,000 Catch Effort returns to FishServe each year (the vast majority are CELR forms). 

When a Catch Effort form arrives at FishServe, it is scanned and then entered into the Catch Effort database. Overnight the Catch Effort computer system runs automated checks across all of the new forms that have been entered into it that day (and any old forms that were altered that day). Approximately 130 types of checks are carried out on each form. Each type of form is subject to a different set of checks. The Catch Effort computer system runs over 1000 types of checks across all of the different types of Catch Effort form. The Catch Effort Data Quality Standards and Specifications (PDF Document) define what checks are carried out on each type of form. 

The next day the results of these checks appear on the computer screens of the people employed to validate Catch Effort information. For some types of errors the validators only check for data entry errors and allowable interpretations (PDF document). An allowable interpretation is a situation in which the validator is allowed to alter (within Catch Effort's FORM database) what the fisher wrote on the form. Validators may only perform interpretations of a type that have been documented (and approved by the Ministry of Fisheries). As a general rule interpretations are only made in cases where the fisher's intent was unambiguous. Validators are not fisheries scientists and it is not their role to make "educated guesses" about how the probable errors detected by the Catch Effort computer system should be fixed. The processing of probable errors that are classified as being of a low priority stops after the checks are done for data entry errors and allowable interpretations. This is referred to as "Procedure C" error processing.

Probable errors that are classified as being of a high priority, that have not been resolved as a result of data entry error and allowed interpretation checks, are queried with the fisher that provided the form. "Procedure A" errors require that no change be made to the data unless the fisher confirms the change in writing. "Procedure B" errors allow that a change may be made to the data if the fisher confirms the new value in a phone call, fax or email to the validator. 

These procedures are summarised in the Catch Effort information flow diagram (PDF Format). 

Note  1 - This page describes how Catch Effort forms have been processed since the year 2000. Forms processed before this were subject to a less sophisticated set of  checks and are more likely to still have errors on them.

Note 2 - The Catch Effort Data Quality Specifications and Standards are in the process of being updated. Some checks are performed which are not documented here.

Note 3 - The Catch Effort computer system also checks for registered fishers and vessels that have not submitted any returns in a month. Such fishers are sent a letter requesting their returns (which may simply be a declaration that they did not fish in the month).

5 Back to top

Back
Home PageTable Of ContentsSite Search