ANNEX 3. DATA SHEET DESIGN, USE AND PROCESSING

This annex gives details on the design and use data sheets. It provides a general table on decision-making in design, together with a narrative on each design issue. This is followed by a table on decision-making in the data sheet use and management, with an explanatory narrative. Two types of data sheet are discussed, logsheets (reporting) and socio-cultural datasheets (interviewing). Similar principles apply to developing data forms for other types of data.

Most fishery authorities throughout the world process at least some of the data collected into computerised databases for two purposes: fisheries administration and management, and scientific, operational and economic research. In general, the former requirement is for the immediate purposes of daily administration of licences, quota and effort control and the statutory elements of fisheries law. The latter purpose is much less urgent, but the entry of data to databases for research purposes is no less essential.

What is most important is the speed of processing and this entirely depends on the use of the information? Is it for quota/effort management in which case speed is of major concern? Or is it for analytical and general statistical research? In the latter case the addition of logsheet data to catch and effort time series is of less urgency, but even so, in the time between receiving data and processing it into useful information should rarely be delayed beyond 3 months to avoid backlogs, misplaced logsheets etc.

LOGBOOKS/LOGSHEETS

DESIGN

DECISION-MAKING IN DESIGN
DATA TYPES	ESSENTIAL	· Identifiers: logsheet, vessel and gear in use; date. · Retained catch and discards: total weight for all species, for target species and others, or for each species; or numbers and average weights. · Effort: location; total number of gear, amount of time used, distance; details by day or by set/haul, etc.
	DESIRABLE	· Production: processed product by species, product type, size grades; by weight or box numbers, plus box average. · Environment: wind (speed, direction, Beaufort scale); water temperature (surface, at-gear, and bottom); sea state, sky cover; water depth.
DATA PRECISION		· Weight/mass: 1, 10, 100 or 1000 kg units or metric tonnes; pounds/tons; other measure. Indicator whether weight is estimated or calculated using conversion factors from processing production. · Species or species group weight: actual weight or proportion of total weight. · Temperature: degree or decimal degree; centigrade or Fahrenheit. · Depth: metres, fathoms, or feet; to the nearest unit or decimal unit.
DATA CHECKING		· Effort: double recording through time and position of start and end, and through distance. · Weight/Mass: double recording through catch estimation and through production records with conversion factors.
STANDARDISATION		· Form choice: Choose from · Common form for all fisheries, or · Fishery specific form; and · Common headers on forms: identifiers, operations, catch, production, environment, confirmation, boxes for office use only
FORMAT		· Codes: use international standards or create codes for species, environment, operations, fishing gear, products, size grades, etc. · Language: use national/regional/foreign or combination. · Check Boxes: use as alternatives to codes or information descriptions where choices are limited.
COPIES AND NUMBERING		· Copies: how many and for whom - usually 3 copies for vessel, company, fishery authority, plus optional for research, municipality, etc. · Numbering: Logbook identifier on front cover, with sheets in numbered sequence. Logsheet identifier, including type, batch, sequential sheet number (use as primary key in logsheet data processing). · Batch: identifier for new year, new design, new print run. · Distribution: decide who keeps which copy; if whole book is to be submitted or appropriate logsheets. Estimate number of pages per logbook sufficient for trip/season and take into account processing speed requirements.
DATA PROCESSING DESIGN TO ASSIST DATA PROCESSING		· Information grouping: Information common to all fishery specific logsheets placed in similar boxes (position, size and shape) to correspond to data entry screens. · Identifiers: sheet, vessel, date and other key fields placed in same place on all logsheets. (If logsheet issue is registered sheet identifier can be used as primary key and can retrieve vessel details directly, for checking and less data entry.)
ADDITIONAL INFORMATION		· Radio Reports: transmission details · Associations: FADs, buoys, sharks, marine mammals, birds, etc. · Seabed: rough ground, wrecks, cables, etc. · Sketches: school shape, ground shape, etc. · Blank space: space to allow fishers to make own notes on crew, gear, vessel, supplies, etc.
ERGONOMICS		· Layout: ensure logical layout according to sequence of fishing operations or events. (get professional form designer, if possible) · Space: ensure sufficient overall size and space for each data item entry. · Identification of Space: ensure proper identification (words, codes or graphics) and delineation of data space, e.g. for check boxes, column heads, event numbers, etc. · Logbook: decide on external markings (vessel identifier, etc) and correct place for printing of instructions for completion and submission.
EASE OF USE AND DURABILITY		· Use: Ensure some form of completed form fold-away method. · Supply pre-addressed submission envelopes, or logsheet pre-printed on reverse for folding into an envelope. · Different copy logsheets should be readily identifiable by text or coloured papers. · Durability: Paper quality; should be carbon-less copy; might need to be water/grease resistance. · Supply sealable, reusable folders, or in hard cover logbooks.

Decision-making on data types

Following some decisions on what data is possible to collect from a fishing operation, it is then necessary to decide on what data is required, and what is only desirable. It is clear that the fundamental estimation of catch (or production) and effort for research and compliance control purposes is always likely to be essential, but it is still necessary to determine exactly how these data need to be collected. Should the position and depth of fishing activities and the time of gear use be collected on a haul-by-haul basis in trawl fisheries? Should catch estimation be aggregated as a total amount or dis-aggregated by species groups or species? Or separated only for target species, others and discards?

Much of this decision-making depends on the type of down-stream processing that will occur and the objectives of that processing. For example, with highly detailed haul-by-haul catch and effort information in demersal trawl fisheries it is possible to analyse census data for swept area/volume estimates of direct use in biomass assessment. Highly detailed species composition data also directly obtained from on-board records may offer support to studies of population dynamics and environmental and fisheries change. Production data that reveals detailed species, product and size grade information, together with other information, can reveal patterns of population structure also useful to stock dynamics and assessment. Thus, the characteristics of census data sets will also vary according to their use; the forms of analysis that are essential or desirable for fisheries research and management.

Degree of precision required

Once the type and extent of data have been decided it is also very important to assess the degree of accuracy required. This will have multiple effects; at the stages of 1) designing the recording form, 2) compiling and processing the data, and 3) carrying out later analyses. Should catch weight be measured in 1 kg, 10 kg, 100 kg or 1000 kg units? Should position be accurate to the nearest second of arc; should it be recorded in decimal minutes? Should a total estimated catch be qualified by estimation of relative proportions of the species/group composition; or should each species mass be estimated separately? Should production data be recorded for every species, product type and size grade; should 'box' weight be recorded as gross or net of packaging/non-fish material?

For environmental data, the measures may also be complicated by the type of data to be collected and the fact that codes may need to be used or developed to represent the data e.g. sea state, sea colour. Should water temperature be to the nearest degree or decimal degree?

Design

Although the extent of data types may be large for any one fishery, the key to successful logsheet/logbook system design is primarily the relative simplicity of their completion by fishers and enumerators. Secondarily, it is useful if the methods of data processing are reflected in the design and layout of the form. Lastly, the methods used for the management of the paper should be explicit in the forms themselves. Details of logsheet design in relation to databases are addressed in a later section. In this section general attributes of logsheets are reviewed including their design, use and submission.

Standardisation and use of common formats

Within a national or regional fisheries sector, efforts should be made to maintain single standards for data types and forms. The use of one standard form for all fisheries has often been attempted but, in so doing and given the demand for increasingly complex and extensive data coverage, it is often the case that for some fisheries the data on a standardised form is too simplistic for requirements. For other fisheries, the form may have data requirements that are too complex and may not be useful. Nevertheless, certain aspects of forms may be amenable to standardisation and the use of some common formats, and this can be taken into account when designing a logsheet form.

Fishery specific logsheets

While common formats for some groups of data on logsheets can be defined (see common headers and identifiers below), logsheets for specific fisheries should limit their data entry requirement to that required for the fishery. Thus, there is no reason to issue a logbook containing areas for production records if the vessels only land whole round fresh fish; similarly, if records are amenable to completion line by line on a daily basis (say for one week or one month on a single form), then a single logsheet for every day is not required.

Registration and copies

The demand that fishers maintain a fishing vessel log in a statutory form places a responsibility on fishery authorities to administer its reception and processing in ways that assure both the authorities and the fisher or company that he has completed his responsibility. In complex fisheries, where several types of logsheet are maintained and fleet numbers are high, the administration of daily and monthly logs can be very great. There is therefore no real alternative but to issue logbooks/logsheets against a vessel and to register their return to the fishery authority. This can be done in a number of ways. Individual logbook numbers can be pre-printed on books together with a hand completion of the vessel details. In addition, individual logsheets can also be pre-printed with numbers running in consecutive order, so that a batch of sheets within one book can be registered with a start and end number. The return of the whole logbook or individual sheets can then be controlled.

Decisions will also need to be made on the number of copies of each sheet, depending on the particular needs of the authority, the company and the fisher. Also, the retention of a completed book once all sheets are submitted needs to be decided. Will the logbook remain on board the vessel, or should the fisher retain only the copy of each sheet. In the former, the management of the paper on board is simpler in book form and inspection procedures can demand a whole book for review, rather than just the copies currently on board. However, this makes the management of the paper by the authority more difficult with the danger that single sheets may be lost before processing. Nevertheless, the submission of individual sheets in this case can provide the authority with immediate access to the information at first landing or on first inspection without waiting for the logbook to be completed before submission.

Thus, the management of the individual logsheets and logbooks needs to be carefully addressed prior to printing. If logbooks are to be retained by the vessel then individual sheets should be numbered; if logbooks are submitted complete to the authority then it may only be necessary to number the whole book.

It is often the case that additional information is required or that general design of logbook changes. To maintain the continuity of databases when data types and quantities vary in this way it will be necessary to identify the batch of a particular logsheet form for a fishery. For example, the identification sequence for a particular logsheet might be TLA00050 which identifies TL (Tuna Longline), A (first batch number), 00050 (sheet number). Similarly, a logbook serial number might be DWB00100-150, identifying DW (demersal wetfish), B (second batch number), 100-150 (consecutive sheet numbers in logbook). The additional advantage of such a scheme is that registered issue of logbooks/sheets against a vessel can be indexed through the database so that at data entry from a logsheet the primary logsheet identifier can be used to access vessel data (name, call sign, company etc.). The computerised vessel data can then be verified against the logsheet data and the data can be retrieved directly so that identification data need not be entered for each sheet.

Common headers and identifiers

It is desirable to develop logsheet designs (and hence databases) that reflect the particular information requirements from specific fisheries. However, there are many common features of logsheets that can be designed and used between different logsheets. In particular, common headers and identifiers that will work for all fisheries might include the following data.

Identifiers: Vessel name, company name, international radio, and call sign, licence number, trip number, etc.

Operational Headers:

· Fishing gear - description (through codes)

· Environment - water conditions (temperature, wave height, colour etc.) or climate conditions (air temperature, wind speed and direction etc.)

· Operations - activities and target species, fishing success (all identified by predetermined codes or descriptions).

· Production - species identification, product format with data based on pre-determined codes etc.

· access to the correct data entry program for a particular fishery;

· allow for validity and completeness checking; and

· provide a means for data entry operators to process similar data from a wide variety of forms in familiar ways, thus assisting in accuracy and efficiency.

The key features of ergonomics, durability and ease of use of logsheet/logbook designs are often overlooked. The layout of a logsheet design needs to take into account the working practices of the fisher and vessel. The space available for each data entry item needs to be adequate at the appropriate level of data precision; it also needs to be positioned in the appropriate place for the sequence of events during fishing to allow a logical continuity of data entry.

Logsheets need to be durable for the period they cover; daily, weekly, monthly or continuous (from sheet to sheet). Thus, paper quality can be important, in some circumstances perhaps water or grease resistant. They should also be easy to use both in terms of clarity about what is required (a detailed set of completion instructions should accompany the sheets) and, where multiple copies are required, the use of carbon-less copy paper and top/middle/bottom copies identified directly e.g. Copy 1 to Fishery Authority, Copy 2 to Company, Copy 3 to Fisher or by different coloured papers.

Ideally, durable and re-usable folders containing the logbook, instructions for completion, place for other stationary (notes, pre-addressed submission envelopes, pencil, calculator, calendar, diary, etc.) would provide a useful 'kit' which would assist fishers in managing the way logbooks are used and kept in good condition.

Language

In fisheries where there may be foreign operators/fishers from distant water fishing nations, in joint ventures or simply contracted foreign employees, it is desirable to offer some forms of assistance in language through logsheet design. This may be undertaken in a number of ways, including:

· minimization of required written descriptions through the use of codes;

· instructions for completion (with examples) in the foreign language;

· header and column/row identifiers in dual language; and

· the fisher's sheet, as copy 1, in the foreign language and copies 2 and 3 in the national language, so that top copy completion is easy for the fisher.

LOGBOOKS - DECISION-MAKING IN THEIR USE
REGISTRATION AND ISSUE	Purpose: To monitor logsheet returns against other sources of information on vessel activity e.g. trip management records, landings, port movement records. Method: · Register logbook/logsheet numbers in a paper register or preferably database by entering the identifier, including start and end sequence number. · Mark the outer cover of the logbook with the vessel identifiers, issuing authority or person and date issued. · Issue sufficient logbooks/logsheets in advance to cover fishing trip, fishing season or other period to be decided.
INSTRUCTION FOR COMPLETION	Purpose: To ensure vessel fishers (or others) know how to complete logsheets. Method: · Summary instructions for completion printed on the inside or back cover of the logbook and or insertions to provide a primary guide, in particular in relation to the specific codes used in the particular logsheet. · Detailed instructions for completion should be made available to fishers, fleet managers/shore fishers, company managers, observers and inspectors to provide all concerned with the precise manner in which they are to be completed.
TRAINING FISHERS AND USE AS FISHER'S LOG	Purpose: To satisfy fishers, companies and fishery authorities that all has been done to assist fishers in logsheet completion and submission. Method: · There are likely to be many methods depending on the fishery (formal, ad hoc, video/demo; through observers, inspectors or researchers.) · Train fleet managers who then train fishers. · Encourage fisher to use logsheet as primary vessel record to prevent transcription errors (see: provision of blank space for fishers notes in logsheet design).
DECLARATION BY FISHERS, OBSERVERS AND INSPECTORS	Purpose: Logsheets to be signed since they are (often) legal documents, which must be completed and submitted as a true representation of fishing activities. Method: · fishers to sign logsheet (all copies). · observers to check contents against independent observations (catch, effort, location, etc) and sign. · inspectors to sign, if inspected at sea or received on land.
SUBMISSION	Purpose: To return logsheets according to legal/administrative requirements. Method: · Distribution of copies: Decide on who gets which copy of the logsheet; does the logbook stay with the vessel, or is it submitted to the fishery authority as the complete logbook, and vessel keeps removable sheets, etc. · Timeliness: Decide appropriate time interval between return to port and logbook/logsheet submission, taking into account the method of submission and distance from reception centre i.e. to inspector/observer or office, or by post.
LOGSHEET RETURN REGISTRATION	Purpose: To maintain an audit trail of the paper between issuance and submission to ensure the legal/administrative requirement is satisfied; to ensure full data coverage. Method: Register logbook/logsheet identifier, return date/time and receiving person in paper register or preferably in licence database against the vessel.
LOGSHEET PROCESSING	Purpose: To update the database at appropriate time. Method: Enter data to database at appropriate time; decide whether data is needed for quota or other immediate management purposes (process quickly) or for research (short delay to processing allowable).

LOGBOOK USE

Registration and issue

Logbooks should be registered and issued to allow the fishery authority to monitor their rate of return. This offers a method for estimating data coverage, particularly where census data is needed for production statistics and forms the source information for analytical stock assessment methods. The 'paper chase' is often overlooked in administrative practices, but forms an essential part of fishery authority tasks. Although this can be relatively simple in small fisheries, in large fisheries when hundreds, perhaps thousands, of fishing vessels are involved, a daily mechanism to follow up outstanding logsheets becomes essential. Non-submission when logsheets are compulsory should lead to legal or administrative penalties and thus record keeping on their registration, issuance and submission will provide primary evidence for any legal action.

Instructions for completion and training of Fishers

Although simplicity is desirable on data types and daily data coverage, it may not always be possible and thus high quantities of data in complex forms may be required; codings may often be necessary as a way of capturing descriptions. Thus, detailed instruction to fishers on how to complete logsheet forms will always be required. This should be printed on cover pages of logbooks in separately issued instructions (and in appropriate languages). Ideally fishers should undergo some training in their completion both at initial introduction and when a new logsheet batch with altered contents or layout replace an original.

Maintenance of information and mechanisms to ensure active completion

Regulations usually require that logsheets are completed on a daily basis and submitted within a certain number of days following return to port. Procedures to ensure this revolve largely around active compliance control through reports by observers, inspectors and through a registration system. A register will enable identification of logsheets not returned after a certain period and prompt any follow up, including legal action.

Use as fisher's log

In large industrial fisheries most fishers will also keep their own log but in smaller scale operations this may not be done or even be feasible. Therefore, logsheets might offer an alternative to other forms of fishers logs, perhaps by including areas on the form in which special notes can be made only of relevance to his use e.g. crew, supplies, maintenance etc.

Catch and Production data

Catch data is usually based on the experienced estimate of the fisher at the time of landing the fish and will always only form an approximate guide to the true tonnage landed. It can be recorded by trap, by haul or other measure of effort but can also be estimated through production data, usually on a daily or processing shift basis. Data on processed fish will usually be in the form of boxes/weight by species, product type and size grade. (See later section for methods of recording these).

Effort verification

There are many ways to design logsheets to record and thus verify the fishing effort applied. In most cases, this relates to recording the amount of time that the gear has been actively fishing or the area/volume of water through which the gear fished. Both time and distance measures for the same operation should be recorded where this is possible.

SUBMISSION AND REGISTRATION

Checking by observers and inspectors

When observers are on board they will usually be tasked to make their own determinations of the data on logsheets, from area fished to effort applied, total catch and species composition. At regular intervals (daily, weekly or at landing) these officials should compare their information to the fisher's and reach agreement on the accurate completion of the logsheet to which they attach their signature.

Declaration by Fishers

When logsheets are legally required (in fisheries acts and regulations), it is important to ensure that fishers attest the accuracy of their completion by a signed declaration.

Timeliness of submission

Fishery authorities generally would wish to receive and process logsheet data at the earliest opportunity. The timing of this is dependent on a number of factors including:

· the operating characteristics of the fishery (trip length, remoteness of landing site and means of communication);

· the fishery authority requirements (individual logsheet submission at landing or return to port, or whole logbook submission when it has been completed), which in turn depends on the processing and analytical requirements: is the data used for quota/effort management or research?

Logsheet return registration

As part of the 'audit trial' that keeps control of the paper logsheets, registration that the logsheets have been received should be made. In this way, issued logsheets are immediately checked against returns, as part of the process to ensure complete fleet data coverage.

LOGSHEET DESIGN AND DATABASES

The processing of increasingly complex logsheet data sets can be a difficult task. Not only are large quantities of data being generated by fleets, but also these are submitted almost daily. Keeping a track on these records requires serious administrative effort, attention to detail and careful follow up if the census data that is received is not to accumulate into unprocessed piles or failure to submit is over-looked and the coverage of data is incomplete.

Design in relation to data entry screens

Data entry to processing systems, whether manual or computerised, should be made as simple and as accurate as possible. One way of doing this is to ensure that logsheet design in some ways mirrors the processing methods. A logical flow of data on the logsheet should be reflected in an equivalent 'view' in data processing. Data entry screens can be developed to capture the different areas of a logsheet, as follows;

Header information: the name, licence and IRCS of the vessel; fisher's name; trip number or trip start date, logsheet number, date (if daily catch log).

Fishing Gear and General Fishing Operations: identification of fishing gear used (that day), environment information, general fishing area if not identified as precise location for each fishing activity (haul, line or trap set).

Operations and Catch: for each fishing activity, the target species, date (if weekly, monthly or continuous catch log), start time and position, end time and position (latitude/longitude or grid square code or area code), gear and bottom depth, success, catch and discard weight or number (total, species group or species).

Production: for each day or shift and for each species, product type and size grade, the total box weight or number of standard boxes.

Standard codes and measures should be used wherever practicable. This enables simplified recording on logsheets but is also very useful in database design. They can be alphanumeric or simple numeric, and they can act as keys to data retrieval and verification. In some cases, there may be international standard codes that can be used; otherwise codes can be simply developed and used as long as their description and purpose are made clear in instructions to fishers.

Species: the 3-alpha species code used in many international species lists is the most useful since it can be set up in the database against scientific and local names in a number of languages.

Fishing Gear: There is no accepted standard coding perhaps because there are so many variations used, but it should be possible to develop a code list once fishery characteristics are known. These can be added to as new gears are introduced and perhaps should be alpha-numeric to enable variations on one type of gear to be identified e.g. DL01, where DL = demersal longline, 01 = hook spacing type 1, etc.

Gear Deployment: code to identify the way in which the gear has been set, the success of the set (hang-up, lost, etc.), type of bait used, escape panels/doors set, grids/TEDs, etc.

Product: code to identify the product type e.g. WR (whole round or green weight), GU (gutted), GG (gilled and gutted), HG (headed and gutted), HT (headed and tailed), FU (fillet untrimmed), FT (fillet trimmed), FM (fish meal), FO (fish oil), etc.; code to identify size grade - these may be industry or company standards, and in the latter databases can contain look-up tables to translate these as required.

Environment: international code for sea state; sky cover; wind direction, etc.

Standard measures should also be adopted for weight (kilograms or metric tonnes, pounds or tons), temperature (°F or °C), depth (fathoms or metres), vessel and wind speed (knots or kilometres), latitude and longitude (degrees, minutes and seconds or degrees and decimal minutes), etc.

Check boxes and their use

For some data types, it is possible to use check boxes or graphics that can be marked rather than descriptions or codes being entered. This simplifies recording but also simplifies data entry procedures e.g. for environment information such as sea state, wind direction, sky cover; or gear type and operation (in port, transhipping, steaming, fishing, broken down etc).

Serial numbers and their registration

If logsheets have serial numbers and their issue is registered against a vessel, then entering only the logsheet number should enable the system to index it against all the vessel details and so fill in much of the header information automatically. Data entry operators can then check these against the recorded details as a first level of error trapping.

Verification of activities against licence type and conditions

In addition to accepting data, a logsheet processing system can also provide for a range of preliminary analyses, in particular checking that the vessels activities as recorded in the logsheet are in accordance with its licence and general fishing conditions. The vessel identifier and date can be used immediately to assess if, in fact, fishing was allowed on that day, say in the case of limited effort fisheries with tie-up periods, or season open and closure dates. The vessel and fishing area will check whether the allowable area was fished. Fishing gear, target species, permissible by-catch, etc. can all be checked against licence conditions. Either the data entry for that logsheet could be terminated if anomalies are found, or be allowed to proceed but with a specific report generated after completion.

Error trapping and use of raising factors

Computer systems not only offer the ability to assess whether the fishing registered on the logsheet was allowable but also the scale and type of data entered. Data range checking should be implemented for all critical data to prevent such things as unlikely positions (latitude/longitude within the range of the fishery) or unlikely masses (tonnes instead of kilograms for example).

Raising factors applying to fish mass recorded can be applied at the time of data entry, or more usually at the time of analysis. The raw data should be stored as this is the record as agreed to by the fisher and could form the basis of argument if paper and database records are different because of the use of raising factors.

Electronic logbooks

Electronic logbooks can be used in a number of ways. They are still being developed. Essentially they can provide a simplified way of processing data that can be passed on to fishery authorities directly, thus avoiding errors and costs in transcription and data entry. They can also be used to simplify the data capture process in the first place. For example, during a whole fishing trip on a particular vessel there would be no need to enter the vessel identifiers, this would simply be added to the whole data file for that trip. The logbook could automatically move to the next day, or date and time stamp each data entry by the fisher, thus assisting in proper identification of fishing effort when it occurs over midnight.

Electronic logbooks also allow for greater use of automatic data capture through attachment to sensors, such as GPS, further simplifying data entry (see section on VMS).

Coding and measures

The same codes would be used as for logsheets and landings sheets. However, the data entry screen could easily be adapted to use specific front ends (user interfaces) that use greater descriptions while only entering the codes to the database. The measures used would be fixed within that system.

Interfaces to equipment sensors

Ideally, electronic logbooks would be integrated with other onboard systems including GPS, navigation software and equipment, and environmental and engineering sensors. Through a specific interface, for example, pressing one key (or clicking on the appropriate fishing position box on the screen) would automatically check and input the latitude and longitude directly from a GPS unit. To that event position, such as gear on bottom/gear being hauled, would be added the date and time, and it might be possible also to add surface water temperature, temperature at the gear, bottom and gear depth, or other environmental data.

Data storage and communications

Clearly, the harsh environment of a vessel's bridge is not the place for non-ruggedised computer equipment and care would need to be taken in storage of data through tape or disk backup procedures, although these of course can be automated. Even immediate printout and paper file storage would be a likely additional level of data security. Both printouts and data files could be supplied to fishery authorities immediately the vessel returns to port. However, modern communications methods, such as access to the Internet for electronic messaging may be a method for the future.

Summary outputs

One of the most attractive features of electronic logbooks would be their ability to prepare summary outputs directly for the vessel's records, the fisher's records and for the company or fishery authority, in addition to the detail offered in each logsheet. These might include fishing maps and environmental summaries and, of course, fishers may analyse their databases over time to assess/recall their favourite fishing ground.

SOCIO-CULTURAL QUESTIONNAIRES/INTERVIEWS

The three fundamental goals of socio-cultural research on fisheries are:

To understand the social and cultural value of the resource to harvesters and their communities. This involves describing and enumerating ways in which the resource and its harvesting and processing are perceived of and valued as a way of life. The fishery, its activities and products, may be intertwined with many details of daily life, such as how individuals spend their time, make a living, form families, friends, and/or a community, in what institutions they participate (e.g., schools, churches, clubs, government, etc.). Comparisons between and among different groups helps identify potential sources of conflict and compromise.

To describe the multiple communities (both discrete and overlapping) of which stakeholders consider themselves to be members. In addition to individual behaviour, it is important to understand the culture or society as a whole. This involves mapping the networks and institutions of stakeholders, assessing the degree of overlapping membership and goals both among harvester and/or processor dominated communities and between such communities and those less directly tied to harvesting and/or processing. It is also critical to evaluate the fishery management institutions, since their beliefs and perceptions are as critical to understanding the fishery and its behaviour as are those of the fishing industry and fishing communities. We need to understand these different spheres individually, but also how these spheres interact and influence one another.

To enhance the effectiveness of fisheries management. This involves identifying such cases as a) where resource access needs to be restricted in order to provide for future sustainability, the option or options that provide the least social and economic disruption and dislocation to the associated fishing population or community, b) in any circumstances, cases of differential impact or potential conflict and the perceived fairness of those impacts and c) promising local resource management regimes.

Socio-culture cannot be examined in isolation from economic and biological data and issues. Cultural beliefs interact with the state of the biological resource, social institutional constraints, and economic conditions. Thus, it is imperative that all socio-cultural forms include variables that allow linking to other data sets of biological, economic, and operational data.

These data are used primarily for policy analysis, to measure management indicators and for research. As such, they are generally gathered at most annually and sometimes at longer intervals (e.g. 3, 5, or 10 years). Once gathered, however, the data should be entered as quickly as possible into databases to facilitate data verification and validation. If long periods are allowed to pass before the data are computerised and initial analyses made, then it may be impossible to ascertain the source of or reason for any anomalous data.

OWNER/FISHER/CREW QUESTIONNAIRE/INTERVIEW

This questionnaire is administered to each vessel owner, vessel fisher and vessel crew member. It gathers several types of data, used for different purposes:

· Identifiers are of two types: 1) those which will allow these data to be linked to other datasets such as vessel registers, fisher licences, trip interview data (e.g. catch, effort, variable costs, value), and the household questionnaire; 2) those which allow the individual questionnaire to be followed through the data audit system, e.g. sample number, enumerator, encoder.

· Demographic data on the individual, which will 1) allow for general descriptions of the fishing population for country fishery profiles, 2) provide the base data for analysing patterns in the distribution of fishing income, dependence on fish for food, etc. by fishery, and 3) allow for analysis of changes in fishing pattern that may be linked to location of residence, ethnic background, age of the fisher, level of education, etc.

· Household data to serve as a cross-check for data in the household questionnaire. Adding these questions here also provides some very minimal household data in the event that Household Questionnaires are unavailable.

· Social data are one measure of the degree of social organisation within the fishing community and also the degree to which fishers are embedded within the larger society. These provide more detailed individual level data specifically on fishers than those requested on the household questionnaire, which are for the household as a whole.

· Employment data are important for analysing dependence on the fishery by both the individual and the household. They can also be used in assessing opportunity costs, since they provide data on the individual's experience in non-fishing employment and their likely choice of alternate occupation should that become necessary or desirable. They are a check against household questionnaire data and also provide a minimum set of data when household questionnaires are not available.

· Fishery data serve as a cross-check for data from trip interviews. And in the absence of a vessel register, these data may be the only way to link individuals to vessel types and fisheries. If this link to fishery types/fleets cannot be made then the data from this questionnaire are of limited use.

This questionnaire is administered in a fishing community to each household, which has at least one fisher as a member. The respondent should be an adult. It gathers several types of data, used for different purposes:

· Identifiers are of two types: 1) those which will allow these data to be linked to other data sets such as vessel registers, fisher licences, trip interview data, and the fisher/owner/crew questionnaire; 2) those which allow the individual questionnaire to be followed through the data audit system, e.g. sample number, enumerator, encoder.

· Demographic data on the household, which will 1) allow for general descriptions of the fishing communities for country fishery profiles, and 2) provide the base data for analysing patterns in the distribution of and dependence on fishing income, dependence on fish for food, etc. at the household and community level for impact analysis.

· Social data are one measure of the degree of social organisation within the fishing community and also the degree to which fishers are embedded within the larger society.

· Employment data are important for analysing household dependence on the fishery. These data also cross-check those gathered at the individual level in the owner/fisher/crew questionnaire.

· Food dependence data are used in assessing the relative dependence of different fishing households, fleets and communities on fish as a food source.

· Fishery data Vessel descriptive data are needed in the absence of a vessel register, in order to link individuals to vessel types and fisheries. If this link to fishery types/fleets cannot be made then the data from this questionnaire are of limited use. If vessel registers exist, then only the vessel registration number of the vessel each fisher is associated with need be collected.

· Infrastructure data enable evaluation of the quality of life of fishing households relative to the general state of infrastructure in the community as described by data from the fishing community infrastructure and institution questionnaire.

This questionnaire is conducted in each fishing community. The enumerator/observer will obtain some of the data by observation of infrastructure elements, and other data by visiting local vital statistics and fisheries offices. The questionnaire gathers several types of data, used for different purposes:

· Identifiers are of two types: 1) those which will allow these data to be linked to the fishing household questionnaire; 2) those which allow the individual questionnaire to be followed through the data audit system, e.g. sample number, enumerator, encoder.

· Demographic data noted here are summary vital statistics available from other agencies.

· Fishing and Fishing-Related Infrastructure & Institution data indicate the relative dependence of the community on fishing and are also useful for assessing the opportunities and potential need for investment in new infrastructure. The data on fishing and fishing-related institutions, such as fisher associations and co-operatives, will be important for analysing the management structure and potential interfaces for co-management.

· Educational Infrastructure & Institution data are needed for comparison with education data from the owner/fisher/crew questionnaire and the fishing household questionnaire in order to assess the status of fishers and fishing households in relation to the community as a whole.

· Transportation and Communications Infrastructure & Institution data are needed for comparison with data from the fishing household questionnaire in order to assess the status of fishers and fishing households in relation to the community as a whole.

· General Community Infrastructure & Institution data are needed for comparison with data from the fishing household questionnaire in order to assess the status of fishers and fishing households in relation to the community as a whole.