SOUTH PACIFIC COMMISSION

A MANUAL FOR THE TAGGING DATABASE SYSTEM OF THE REGIONAL TUNA TAGGING PROJECT

Kevin Bailey, Peter Williams and Russell Price

Tuna and Billfish Assessment Programme Technical Report No. 30

Printed with financial assistance from the Sixth European Development Fund

of the European Community

Noumea, New Caledonia 61/93 1993

11

®Copyright South Pacific Commission, 1993 The South Pacific Commission authorises the reproduction of this material, whole or in part, in any form, provided

appropriate acknowledgement is given.

Original text: English

South Pacific Commission Cataloguing-in-publication data

Bailey, Kevin A manual for the tagging database system of the Regional

Tuna Tagging Project / Kevin Bailey, Peter Williams and Russell Price

(Technical report / Tuna and Billfish Assessment Programme ; no. 30)

1. Tuna fisheries ~ Research -- Oceania 2. Fish tagging -Oceania - Handbooks, manuals, etc. 3. Fish tagging ~ Databases I. Williams, Peter II. Price, Russell III. South Pacific Commission IV. SPC Regional Tuna Tagging Project V. Title VI. Series

639.2758 AACR2 ISBN 982-203-308-7

Prepared for publication and printed at

South Pacific Commission Headquarters, Noumea, New Caledonia, 1993

I l l

ABSTRACT

During the course of the SPC Regional Tuna Tagging Project, a database system was developed by the Tuna and Billfish Assessment Programme for the efficient entry, editing, collating and reporting of tag releases and recoveries. This system is designed for use on IBM-compatible laptop and PC computers and has received extensive testing at sea on various tuna fishing vessels in the western Pacific as well as considerable use in the office. The system software is available free of charge from the Tuna and Billfish Assessment Programme; however, copies of FOXPRO, LOTUS 123 and WordPerfect software need to be purchased by the potential user before the system is fully operational. The system software, excluding data files, requires 2.8 Mb of memory and the commercial software an additional 20 Mb.

The database system is divided into two major interactive sections. The release section contains records of all tags used in a project, regardless of whether a tag was inserted in a tuna that was subsequently released into the sea, lost overboard, damaged and discarded, or used in a seeding experiment. The recovery section includes records of all recovered tags that have been physically returned to SPC. Within each section, there is provision for entry of standard tag data, such as fish length, species, location, and date, as well as measures of the credibility or reliability of these data. An extensive reporting menu allows the user to carry out basic collating and analysis of the data, including print-outs of daily input, length frequency compilation, distance travelled and time-at-large calculations, and rudimentary mapping of numbers of releases and direction of travel of recoveries. There are also backup and consolidation options that allow for data storage and transfer of information between computers. This manual describes the daily use of the database system in detail.

RESUME

Dans le cadre du projet r6gional de marquage des thonidgs, les services du programme devaluation des thonides et marlins ont constitue" un reseau de bases de donnees qui doit optimiser la saisie, la mise en forme, la compilation et la presentation de donnees sur les thons marques puis recaptures. L'exploitation se fait sur ordinateur portatif et ordinateur personnel compatibles IBM; le systeme a etc" frgquemment mis a l'essai en mer a bord de divers thoniers dans le Pacifique occidental, tout en etant utilise au bureau de facon intensive. La CPS distribue gratuitement le logiciel d'application, mais le futur utilisateur devra se procurer les logiciels FOXPRO, LOTUS 123 et WordPerfect pour rendre le systeme tout a fait operationnel. U faut 2,8 Mo de memoire pour le logiciel d'application, a l'exclusion des fichiers de donnees, et 20 Mo pour le logiciel du commerce.

La base de donnees comporte deux grands segments interactifs. Le segment Marquage contient le releve" de toutes les marques utilises dans le cadre d'un projet, ind6pendamment du fait que la marque ait 6t6 pos6e sur un individu relach6, tombe a la mer, endommage" et rejete" ou utilise dans le cadre d'une experience de faux marquage. Le segment Recapture contient le releve" de toutes les marques qui ont ete materiellement recupe>6es par la CPS. Chaque segment comporte un espace pour la saisie de donnees de base, notamment la taille et l'espece du poisson, l'endroit et la date de sa capture ainsi que des indicateurs de la vraisemblance ou de la fiabilite" des donnees. Un important menu des rapports permet a l'utilisateur d'effectuer la compilation et l'analyse el&nentaires des donnees, notamment de produire un imprime des donnees saisies chaque jour, de faire une compilation du nombre de prises selon la taille, de calculer la distance parcourue et le temps passe en liberte, d'etablir des cartes rudimentaires du nombre de poissons reaches et de la direction de defacement des thons recupeYes. GrSce aux options de sauvegarde et de fusion, il est egalement possible d'entreposer les donnees et de transferer l'information entre ordinateurs. Le lecteur trouvera dans cet ouvrage une description d6taill6e de l'utilisation courante du reseau de bases de donnees.

v

CONTENTS Page

1. INTRODUCTION 1

2. OVERVIEW OF TAGGING DATABASE SYSTEM 1

3. MAIN MENU 3

4. ENTER RELEASES MENU 4 4.1 Tag Release records 4 4.2 Cruise Data records 8 4.3 School Data records 9 4.4 Tagger Data records 11

5. VERIFYING AND EDITING RELEASES 12

6. ENTERING AND EDITING RECOVERIES 13

7. DAILY POSITIONS AND SCHOOL SIGHTINGS 15 7.1 Entering positions and school sightings 16 7.2 Editing positions and school sightings 18 7.3 Reporting positions and school sightings 18

8. PRODUCING REPORTS 19 8.1 Releases 19

8.1.1 Release school type 19 8.1.2 Weights of releases 20 8.1.3 List releases 20 8.1.4 Summarise releases by tagger 21 8.1.5 Length frequency of releases 21 8.1.6 Summarise releases by 5-degree square 24 8.1.7 Tags used list 24 8.1.8 Tally releases by gear type 25

8.2 Recoveries 25 8.2.1 Taggers 25 8.2.2 Returns by gear 26 8.2.3 Time at large 26 8.2.4 Usable recoveries 26 8.2.5 Distance travelled 26 8.2.6 Recoveries by cruise 26 8.2.7 Recoveries vs releases; numbers by species and length interval 26 8.2.8 Recovery and release information for tag letter creation 26 8.2.9 Recoveries to date by vessel flag and gear 26 8.2.10 Recoveries to date by country and place recovered 27 8.2.11 Distance travelled, by association 27 8.2.12 Mean displacement 27

9. ERROR CHECKS AND POST-ENTRY PROCESSING 27 9.1 Tag codes 28 9.2 Estimate missing lengths 28 9.3 Re-index data files 28 9.4 Check release files for garbage data and duplicates 28 9.5 Check release tally by school, tagger and species 28 9.6 Update species codes in release and recovery files 29 9.7 Update EEZs in recovery file 29 9.8 Update double tag recovery flag 30

VI

CONTENTS (continued)

10. HOUSEKEEPING 30 10.1 Backup 31 10.2 Restore 31 10.3 Consolidate releases 31 10.4 Distribute new recoveries 33 10.5 Import new recoveries 33 10.6 Archive cruise 33 10.7 Load cruise from archive 34 10.8 Maintenance archive 34 10.9 Transfer to text for Oracle 34 10.10 Transfer recoveries for Oracle 34 10.11 Change tag exclusion ranges 34 10.12 Extract data for range of cruises 35

11. LIST CRUISE / SCHOOL INFORMATION 35

12. PRODUCING MAPS 35 12.1 Create map recoveries 35 12.2 Map recoveries 36 12.3 Create map releases 36 12.4 Map releases 36

12.5 Printing larger maps 36

ACKNOWLEDGEMENTS 37

APPENDICES

I. RTTP Tagging Database System documentation 39

II. Quick reference to RTTP Tagging Database System codes 47

III. Checklist of at-sea computer-related duties 49

Vll

LIST OF TABLES

Table Page

1. The Release School Type listing 19 2. The Weights of Releases listing 20 3. The List Releases listing 20 4. The Summarise Releases by Tagger listing 21 5. The Summarise Releases by 5-Degree Square listing 24 6. The Taggers listing 25 7. The Check Release Tally listing 29

LIST OF FIGURES

Figure

1. Flowchart of organisation of the RTTP Tagging Database System 2 2. The main menu of the RTTP Tagging Database System 3 3. A completed Tag Release Data record 4 4. A completed Cruise Data record 8 5. A completed School Data record 9 6. A completed Tagger Data record 11 7. The Edit Release menu 12 8. A completed Tag Recovery Data record 13 9. A completed Positions Data record 16 10. A completed Sightings Data record 17 11. The Release Reports menu 19 12. Length Frequency Histogram selection screen 22 13. An example of the length frequency histogram screen and printout 23 14. The Recovery Reports menu 25 15. The Error Checks and Post-Entry Processing menu 27 16. Recovery file double tag field update criteria 30 17. The Housekeeping menu 30 18. The Backup menu 31 19. Daily housekeeping routines for field data entry operations 32 20. A completed Tags Exclusion list 33 21. The Tagging Mapping menu 35 22. Map templates available for mapping releases and recoveries 36

V l l l

# ' •

*m ,/*

The Tagging Database System in use under difficult conditions: the bridge floor of pole-and-line vessel Soltai 12 during the Solomon Islands in-country tagging project.

1

1. INTRODUCTION

The Regional Tuna Tagging Project (RTTP) is a three-year project designed to provide estimates of yellowfin tuna (Thunnus albacares) population parameters in areas of intense fisheries in the western tropical Pacific, and to estimate the interactions between tuna fisheries in areas where several different fisheries operate concurrently. A secondary objective is to update the estimates of skipjack tuna (Katsuwonus pelamis) population parameters in the western tropical Pacific in areas where fishing has increased since 1980. The RTTP is being implemented by the Tuna and Billfish Assessment Programme (TBAP) of the South Pacific Commission (SPC) and is funded by the Sixth European Development Fund of the European Community. Field work for the project began in December 1989 and finished in December 1992. Analyses of tag recovery data will take a further 1—2 years.

During the field-work component of the RTTP and related in-country tagging projects, a database system evolved for the efficient entry, editing, collating and reporting of tag releases and recoveries. The database system is designed for use on IBM-compatible laptop and PC computers both at sea and in the office, and has been tested extensively on various commercial tuna fishing vessels and at SPC headquarters in Noumea. The aims of this manual are to describe the daily use and capabilities of the database system, and in so doing illustrate what is involved in obtaining high-quality tag release and recovery data.

The tagging database system in its present form has been used by TBAP staff tagging yellowfin, skipjack, bigeye (Thunnus obesus), longtail (Thunnus tonggot) and albacore (Thunnus alalunga) tuna from purse seine, pole-and-line, troll and handline vessels, and is therefore considered to be immediately transferable to most other tagging projects that involve tuna and other schooling pelagic fishes. The tagging database system software is available free of charge from the TBAP. However, the potential user will need to purchase two pieces of commercial software to run the system, namely 'FOXPRO' (version 2.0 or later) and 'LOTUS 123' (version 2.2 or later). It is also recommended that 'WordPerfect' (version 5.1 or later) be purchased in order to have access to some of the optional features of the system as well as this document in native form.

The database system software, excluding data files, requires 2.8 megabytes of memory. The three pieces of commercial software require a total of 20 Mb but can be stripped of non-essential files by an experienced computer user if hardware space is limited.

2. OVERVIEW OF TAGGING DATABASE SYSTEM

The tagging database system was primarily designed to provide an efficient means of storing, managing and subsequently retrieving tagging data for analytical purposes. In the design phase of the database system development, it was necessary to identify the key objects for which data were collected during the operational stage of the tagging project. These objects, once identified, became the fundamental databases of the system; each database is linked or related to at least one other database in this system by key attribute fields.

The structure and relationships of the tagging database system are illustrated in the flowchart overleaf (Figure 1), while Appendix I describes the attributes of each database in detail. The following description attempts to define each database and its relationship(s) with other database(s) in a way that reflects the operation of the tagging project.

At the top of the database structure is the Project, which can be described as an independently funded or goal-oriented operation that can be readily distinguished from other projects. During the period of the RTTP, a number of specific in-country tagging projects independent of the main project occurred. The specification of a Projects database satisfied this requirement by making the distinction between such independent projects. The database structure, however, caters for access to all tagging data where specific analyses do not have to distinguish between projects.

2

Within each project there may be one or many Cruises. A cruise is defined as a discrete period of activity during the tagging project, usually defined by the cruise leader as a period between port calls or entrance into new Exclusive Economic Zones or areas. This provides a means of distinguishing tagging activities of different areas or time periods within a project. The system is flexible enough to handle cases where tagging during a designated cruise did not take place even though searching effort occurred.

One Project has one or many daily positions related by PROJECT

Position

fight

One recovery has one or no note related by TAG, 'C

Recovery

One daily Position record has one, many or oo school sightings related by PRO JECT, DATE

One school Sighting has one or no tagged school related by PROJECT, SCHOOL

One release has one or no note related by TAO, %'

One release has one or no recovery related by TAO

One Project has one or many cruises related by PROJECT

One Cruise has one or many schools related by PROJECT, CRUISE

One School has one or many taggers related by PROJECT, CRUISE,

SCHOOL

One Tagger has one or many releases

related by PROJECT, CRUISE, SCHOOL and TAGGER

Figure 1. Flowchart of organisation of the RTTP Tagging Database System

Within each project there may be one or many daily Position records. A daily position record contains the vessel position and basic meteorological data recorded at 0600, 1200 and 1800 hours for each day of activity. The number of hours searching and steaming are also recorded for each record. Position records may exist for days where no tagging activity took place; these data are used to show vessel tracks and also to determine effort, measured in days or hours spent at sea or searching.

The fishing techniques employed (i.e. pole-and-line, handline and troll) and the schooling behaviour of the target species in the operational area of the RTTP enable die useful definition of a school to represent the occurrence of an identifiable body or aggregation of tuna that was spatially distinct at the time it was fished or sighted. For each day spent searching (identified in the system by a Position record), there may be one, many or no school sightings. The Sight database is used to record information on every tuna school encountered by the tagging vessels, regardless of whether fish were caught and tagged. Details on the position where the school was encountered, the size and species composition of the school and the number of fish caught and tagged are included in this database. The database containing only those schools that yielded fish for tagging (i.e. the School database) is essentially a subset of the school sightings database (Sight). Both databases use a sequential school number for unique identification.

For each school where tuna were tagged and released, one or many taggers may have been involved in die tagging process. The Tagger database contains information on the identification of each tagger and his assistant, as well as the cradle position on the vessel and the first tag used by each tagger during each school.

3

For each tagger one or many tags (Releases) may be used during a period of fishing. It is important to note that each record in the Release database does not necessarily represent a released tag, nor does it represent one fish release. Instead, the primary purpose of this database is to account for each tag that was made available to the tagger, whether it was successfully released as a single or one of a double set of tags, or was lost, damaged or used in a seeding experiment. The attributes of this database include the unique tag number, the species and size of the recipient tuna (if applicable), the quality of tag placement, the condition of the tuna tagged (if applicable) and double-tagging information (if applicable).

When a tagged fish is recaptured and the tag returned to SPC, information relating to area, time, recapture vessel type and attributes of the tagged fish are recorded in the Recovery database. For each release record, there may or may not be an associated recovery record; there are never any recovery records for lost or damaged tags. The structure of the release and recovery databases is based on tag number, making reporting and analysis far simpler than if the structure were centred on individual fish releases.

For each tag release and recovery, text of up to 40 characters can be stored to describe any unusual or special features of the tag. This information is stored in the Notes database. An attribute in mis database indicates whether the stored text refers to the release or recovery of a particular tag.

The database structure has been described above using a technique called the top-down approach. It is also possible to describe the same structure in the reverse fashion (i.e. the bottom-up approach). As an example, we can look at this structure beginning with a particular tag. Thus, we view the structure in terms of a released tag coming from a particular tagger who operated during the fishing period of a particular school; this tagged school was encountered during a particular cruise, which was part of an overall project.

3. MAIN MENU

To enter the RTTP Tagging Database System, the user should type the word Tags at the root directory prompt (C:\>) on the laptop or personal computer being used. After a short period of time the main menu for the system will appear on the screen (Figure 2). The options listed are entered by typing the respective number or letter.

1 2 3

4 5 6

7 8 9

RTTP Tagging Database System

Enter Releases Edit Releases Report Releases

Enter Recoveries Edit Recoveries Report Recoveries

Enter Schools sighted Edit Schools sighted Report Schools sighted

E Error Checks

H Housekeeping

L List Cruise/School Information

M Mapping

Q Quit to Foxpro

Figure 2. The main menu of the RTTP Tagging Database System

4

4. ENTER RELEASES MENU

Type 1 to enter this menu. The user will then be prompted with the command to enter the desired project. The database is currently divided into nine tagging projects, namely AB, FJ, KO, KA, KI, PH, RT, SB, and SE. The first project refers to albacore tagging by the TBAP and other agencies in the southern waters of the South Pacific Ocean. The remaining eight projects come under the umbrella of the RTTP. The FJ, KO, KI, KA, and SB projects are small-scale in-country programmes using local vessels and local Government staff and fishermen, with TBAP assistance. The initials refer to Fiji, Kiribati (KO and KI), Kapingamarangi Atoll (in Pohnpei State of the Federated States of Micronesia) and Solomon Islands respectively. The PH project is used to indicate data from the Philippines Tuna Research Project. The RT project refers to tagging on the chartered pole-and-line vessel MV Te Tautai, which involves the main field-work component of the RTTP and includes the majority of tag releases. SE refers to tag seeding experiments on various commercial tuna fishing vessels in the RTTP study area.

After entering the desired project, the database moves directly into the Tag Release Data entry screen. If the software detects any changes in pertinent data from the last record entered, such as a change in cruise, school number, or tagger's initials, there will be additional prompts to enter specific information pertaining to the changed field(s).

4.1 Tag Release records

Each time this menu is first entered, the user is taken to a Tag Release Data record, with the tag number automatically inserted. This number will be the next number from the last tag number entered the previous day or by the previous person to enter data. The user should always ensure that this number coincides with the tag number desired. The number can be changed by simply typing over the one already in place, ensuring that the cursor is in the tag number field. The tag number also has to be changed when a tagger finishes one block of 100 tags, and begins a new block that does not follow in sequence, e.g. after using tags numbered X04501 to X04600, the tagger begins a block that starts with tag X04701.

A typical Tag Release Data record, after data entry, is shown in Figure 3.

TAG RELEASE DATA

Project Cruise Tag number Fork length Species Species reliability School Gear type Tagger Quality Condition FL reliability Double tag Notes

Record 14,354

RT TET009-90 XI8623 31.0 Y

98 PL FMV 2 1 1

TAG TOO FAR FORWARD

To quit, enter Q or blank in Tag number

Figure 3. A completed Tag Release Data record

5

The codes used in Tag Release Data records are defined below.

Project A two-letter code indicating the tagging project responsible for releasing the tag. Examples are: FJ for the Fiji In-Country Tagging Project, PH for the Philippines In-Country Tagging Project, and RT for the RTTP.

Cruise A nine-character code consisting of a three-character vessel identification code, a three-digit consecutive cruise number, a dash, and a two-digit year, e.g. TET051-91 (which stands for Te Tautai cruise 51, conducted in 1991). On the RTTP vessel, the cruise number changes when the vessel leaves a port for fishing or moves into a new area or country EEZ (e.g. 001-89 around Guadalcanal, followed by 002-89 around Santa Isabel). The cruise number does not revert back to 001 at die start of a new year, but carries on from the last cruise of the previous year.

Tag The one-letter prefix and five-figure number stamped on each tag. Different letter prefixes number are used to differentiate between projects and different sizes of tags. Tags with X and Y

prefixes are the mainstay of the RTTP, are 13 cm in streamer length and are used on fish measuring at least 35 cm in fork length. Z- and T-prefixed tags are also used in the RTTP but are only 10 cm long and reserved for fish between 25 and 34 cm in length. In addition, T tags are orange, rather than the standard yellow, and are used on fish that have been injected with oxytetracycline for the purpose of ageing studies. A-prefixed tags are identical to X and Y tags but are used exclusively on albacore. P and S tags have been used in the Philippines during the PH project.

The program has an automatic tag number increment feature so that only the first tag number of the day or tag block has to be entered if it differs from that already showing.

Fork The fork length of the tagged fish in centimetres. It is unnecessary to type the decimal place, length unless the fish has been measured to millimetres, e.g. the number 54 will be entered as 54.0

whereas 54.5 will need to be entered completely. A number of length checks are built into the program. If, on entering a fork length, the length check queries the entry, press any key then type Y if the entry is correct or N to re-enter the correct number.

Species A one-letter code for the species of tuna being tagged, as follows:

S Skipjack Y Yellowfin B Bigeye A Albacore 0 Other

If this code is used, enter the species name in the Notes field at the bottom of the Tag Release Data record.

U Unknown This may be necessary if there was a fault with the tape recorder or if the tagger forgot to record the species.

Species A number code indicating how the species was determined. Users should leave this field reliability blank, unless the species was guessed. Section 9.6 describes how this field is used.

(blank) Species recognised and recorded by tagger (or recoverer if in Recovery database) 1 Species assigned from School default 2 Species assigned to Recovery from Release 3 Species assigned to Release from Recovery 4 Species not recorded but guessed by tagger

6

School This is a consecutive school number, starting from 1 at the beginning of cruise 01 of a specific project. This number carries on from cruise to cruise, and does not revert to 1 at the start of a new cruise. In a multi-tagging station operation, it is important that a tagger's school number agrees with that of other taggers working on the same school. School numbers are determined by the cruise leader or scientist-in-charge. At the start of a new school, after the first release has been entered, the program will note that a new school has been entered and will move to a new School Data record (see Section 4.3). This record has to be completed. Following this, the program will note that a new tagger has been entered and will move to a new Tagger Data record, also to be filled in. Once these two records are completed, the next release record will appear on the screen.

Gear type The type of fishing gear used to catch the fish. This field defaults to the last gear type entered. Two-letter codes are used for the gear type, as follows:

GL HL LL OT PH PL PS RN SH ST TR UN

Gillnet Handline Longline Other Pole and handline (Coral Sea) Pole-and-line Purse seine Ring net Skiff handline Skiff troll Troll Unknown

Tagger The initials of the tagger. This field can be up to three characters long. The same system of initials is used for the Assistant field in the Tagger Data record. The tagger at a specific cradle can change during a period of tagging from a particular school by simply altering the tagger field in the relevant Tag Release Data record. The change in tagger will be noted, and a new Tagger Data record will show on the screen to be completed. Once this is done, the next Tag Release Data record will show on the screen with the new tagger listed, and will remain this way in subsequent records until the tagger is again changed.

Quality This refers to the quality of each tag release. Seven codes are used, as follows:

1 Good (default code) 2 Badly placed

Specify in the Notes field why the tag was badly placed, e.g. inserted too deep or too shallow, too low, too high, too far forward, or too far back on the fish's body.

3 Too slow Used if tagging a fish takes longer than about 15 seconds.

4 Tag rejected Used if the tag is cut in half by the applicator needle during insertion or is damaged in any way, and therefore not released.

5 Tag lost If tag is not in the needle, or is lost overboard or somewhere on the deck. Ensure that this is recorded, so that a reward is not paid for a tag that may have been stolen from a block or found on the deck, pocketed and returned at a later stage as a legitimate recovery.

6 Tag seeded Tag used in seeding experiment.

7 Unknown

7

Condition Physical condition of the fish being tagged. Eight codes are used, as follows:

1 Good (default code) 2 Bleeding

Specify in the Notes field where the fish is bleeding. Do not tag fish that are bleeding heavily, particularly if there is dark red blood seeping from the gill covers.

3 Tail damage Not used often as fish with damaged tails are usually not tagged.

4 Mouth damage Minor hook damage. Do not tag fish with dislocated jaws or badly ripped mouths.

5 Dropped on deck Only tag fish that have touched or been gently placed on to the deck. Do not tag those that have hit the deck with any force.

6 Hit side of boat This happens occasionally, either as the fish is pulled on board or after the fish has been tagged and thrown over the side. Do not tag fish that have hit the side heavily.

7 Shark bite Refers to fish that have minor wounds inflicted by the cookie-cutter shark (Isistius brasiliensis). Do not tag fish that have been obviously attacked and damaged by large sharks.

8 Unknown

FL reliability Reliability of the fork length measurement:

1 Good Measured on tagging cradle. This is the automatic default code for all Tag Release Data records.

2 Measured but inaccurate or unclear Specify reason in the Notes field.

3 Guess 4 Average of tagged fish in school

If no length has been inserted in the Fork Length field, a program in the Error Checks menu called Estimate Missing Lengths (see Section 9.2) can be used to calculate the average of the tagged fish from the specific school and species. This program will then insert the average value in the empty Fork Length field(s).

5 Average of untagged fish in school As for Code 4, a length can be entered manually in the Fork Length field by manually calculating the average length of a species from fish that were too damaged to be tagged but were measured during routine biological sampling.

6 Unknown 7 Calculated from weight

In case a situation should arise where the weight but not the length was taken.

Double tag This field is left blank if only one tag is placed in the fish. The number 1 is entered if the tag in the tag number field is the first tag used in double tagging. The second or companion tag is then entered in the Notes field. If the latter is not done, the program will ask for the companion tag number. When the next Tag Release Data record appears on the screen (which usually should be the companion tag for the previous tag), a program will automatically enter the length and other data of the previous tag and also put a figure 2 in the Double tag field and the previous tag number in the Notes field. All that needs to be done then is to change any fields in the second tag, such as Quality, that are not the same as the previous tag. This system ensures that both tags in a fish that has been double tagged are identified with each other even though they have separate records.

8

The database system is designed around the premise that each tag has one and only one record. Even though a tag may be lost or rejected and not used in a fish it is noted down as a legitimate record. In this way it is possible to keep track of every tag used. If a tag number that has already been recorded in the database is accidentally re-entered, the system will flag it and not allow the user to proceed without correcting this entry.

The program will move the user down the Tag Release Data record automatically as each field is filled with information. A number of fields have a default, i.e. the codes or characters that will be most commonly used are automatically entered once the new record appears (e.g. Quality, Condition and Fork Length reliability are all coded 1 for Good and Species Reliability is blank for Known). These defaults allow the experienced tagger to move quickly through the records because in most cases the only data needed to be entered will be the length of each fish and possibly the species. A short-cut built into the database allows the user to enter the length and species, then finish that record, if all the defaults are correct, by pressing the Enter key followed by the Esc key. This short-cut can be used at any time to leave a record. The record can also be left at any point by using the Page Down key.

When the species code is changed, this new code will automatically be retained in the next record, and will remain until the code has to be changed again.

The record can also be exited by keying through all the fields with the Enter or Down Arrow key. The program will then run a check on the data, ensuring that the tag number has not been entered before, that the codes are all legitimate, and that the fork length is within acceptable bounds. The user will then be asked to confirm the record. If a mistake has been made during entry, the user enters the letter N and the record is available for editing. If the record is acceptable, enter the letter Y. The next record will then show on the screen.

To leave the Enter Releases menu when data entry has been completed, type the letter Q in the Tag Number field or delete the entire tag number, then press the Enter key followed by the Esc key. This will return the user to the main menu.

4.2 Cruise Data records

At the beginning of each cruise, or after some significant event (such as crossing into the waters of a different country), the cruise leader will prepare a data sheet containing the information to be entered for the new cruise. The cruise leader (or each tagger) will then enter the new cruise number into the cruise field of the release data entry screen on each of the computers being used in a tag data entry capacity. The software detects the change in cruise number and responds by bringing up a cruise data entry screen. This ensures that only one cruise record exists on the database for each unique cruise. A completed Cruise Data record is shown below (Figure 4).

CRUISE DATA - Record 176

Project Cruise Vessel name Vessel flag Principal vessel gear Notes

RT TET009-90 TE TAUTAI TV PL GUADALCANAL, SOLOMON ISLANDS

Figure 4. A completed Cruise Data record

9

The following codes are used in this record:

Project Identical to that used in Tag Release records.

Cruise Identical to that used in Tag Release records.

Vessel name The full name of the ship used during the tagging operation.

Vessel flag A two-character code indicating the country the vessel comes from. See Appendix II section 2 for a list of these codes and their meanings.

Principal Identical to Gear Type used in Tag Release records. vessel gear

Notes Notes the user may feel useful concerning the cruise, particularly with regard to area fished.

4.3 School Data records

At the end of each tagging day, the cruise leader will compile a list of the schools successfully fished and the relevant school data. This information need only be entered by the first tagger to enter data on each computer in use for data entry. The software ensures that only one school record exists on the database for each unique school. A completed School Data record is shown below (Figure 5).

SCHOOL DATA •

Project Cruise School Country Date Latitude Longitude Start time Stop time Detection method School type Association

- Record 252

Percentage Yellowfin Total catch Notes

RT TET009-90 98 SB 04-03-90 0941S 15928E 1431 1518 5 1 3 72 0.3

Default species Y Sea surface temperature 32.5

GOOD BITE ON BAMBOO PAYAO NO. STL 56

Figure 5. A completed School Data record

The following codes are used in this record:

Project Identical to that used in Tag Release and Cruise Data records.

Cruise Identical to that used in Tag Release and Cruise Data records.

School Identical to that used in Tag Release Data records.

10

Country The country code of the EEZ that the ship is operating in, or closest to if working in international waters. Appendix II includes a list of country codes used in the RTTP.

Date Automatically defaults to today's date, in day-month-year format, but can be altered if

incorrect.

Latitude Degrees and minutes south or north (S or N), using satellite navigation system or radar plot.

Longitude Degrees and minutes east or west (E or W).

Start time Time when fishing on the school began, in 24-hour format.

Stop time Time at end of fishing.

Detection Five codes to explain how the school was detected, as follows: method

1 Visual surface By sight.

2 Birds By bird sightings.

3 Trolling First fish caught with trolling gear.

4 Sounder or sonar Subsurface schools detected with electronic equipment.

5 Via association Found by initially locating a floating object (Fish Aggregation Device (FAD), log, whale, shark) or oceanographic feature around which the fish have aggregated.

School Type Six codes to define the type of tuna school, as follows:

1 Subsurface No fish signs on surface.

2 Jumper Occasional fish jumping out of the water.

3 Breezer/Rippler School appears like a breeze rippling across the surface, although no fish are visible.

4 Splasher Fish are active and splashing.

5 Boiler School is very active and water has appearance of boiling.

6 Foamer Boiling school is so active that foam rises in the air.

Association Eleven codes to describe the association the school has with an animate or inanimate object:

1 Unassociated 2 Log

Naturally occurring material such as trees, palms, branches. 3 Anchored FAD

Artificial raft or object anchored to sea floor. 4 Drifting FAD

As for 3, but drifting free. 5 Marine mammal or whale shark

If possible, identify whale using whale guides, and record species in the Notes field.

11

Percentage Yellowfin

Total catch

Notes

Default species

Sea surface temperature

6 Tagging vessel Fish may aggregate under the vessel while it drifts at night.

7 Current line A current boundary, identifiable at the surface by a sea temperature change or by the accumulation of floating debris.

8 Seamount A subsurface pinnacle or mountain.

9 Island or reef Schools aggregating within 10 nautical miles of islands and reefs.

0 Other Record type in the Notes field. Birds are not an association.

A Coral Sea Aggregation Seasonal aggregation of large yellowfin and bigeye in the north-west Coral Sea.

Percentage of yellowfin in total catch of vessel for the school.

In tonnes, to one decimal place.

Any notes the user may feel useful concerning the school.

Specify in this field the most common species tagged during the school.

Temperature of surface water in degrees Celsius, to one decimal place.

4.4 Tagger Data records

Once the School Data record is completed, the Tagger Data record will appear for each new tagger.

TAGGER DATA - Record 697

Project Cruise School Tagger Cradle Assistant Tag type First tag

RT TET010-90 102 ETP SB PGW H13 X18783

Figure 6. A completed Tagger Data record

The following codes are used in this record:

Project Identical to that used in Tag Release, Cruise, and School Data records.

Cruise Identical to that used in Tag Release, Cruise, and School Data records.

School Identical to that used in Tag Release and School Data records.

12

Tagger Tagger's initials, as used in Tag Release Data and School Data records.

Cradle Position of tagging cradle on vessel:

Assistant

Tag type

BM MS PB PM PS SB SK SM SR SS

Bow mattress Mid-stern Port bow Port midships Port stern Starboard bow Skiff mattress Stern mattress Stern rack Starboard stern

Initials of assistant to U

Tag manufacturer's inil

First tag

classified as Hll for Hallprint 11 cm long tags, while tags X07001 - X99999 and Y00001 Y40000 are HI3s. Z- and T- prefixed tags are HlOs.

The first tag number entered by the tagger for the specific school.

A quick reference to the codes described in the preceding three sections is included in Appendix II.

5. VERIFYING AND EDITING RELEASES

Once the day's releases have been entered by a tagger, a printout of the data can be made following the instructions in Section 8.1.3. The user should then check this printout against the original transcribed data. Errors in data entry can be edited by using the Edit Releases menu. This menu is entered from the main menu by typing the number 2.

1

2

3

4

Release

Cruise

School

Tagger

Edit Release Menu

Q Quit

Figure 7. The Edit Release menu

The user can edit individual Tag Release, Cruise, School and Tagger Data records by selecting one of the four choices in the Edit Release Data menu shown above. When a selection is made, the user will be prompted with two questions which ask how to locate the desired record:

Locate record by RECORD NUMBER? (Y/N) Locate record by TAG? (Y/N)

13

If the answer is Y to any of these questions, the user will be prompted with a blank field to fill out. If the answer is N, he will be taken automatically to the last record entered. Note that if, for example, the user answers Y to Locate record by TAG, the database will be displayed in tag number order. Otherwise, it is displayed in the order in which the data were entered.

The user can move through the records by typing T to go the top of the records (i.e. the first record entered), B for the bottom or last record, N for the next record, and P for the previous record. S for skip allows the user to search through as many records as desired by specifying the exact number to move, either forward by any number or back by a negative number (e.g. —124).

Once the record that requires editing is located, type E. The user will then be asked whether he wants to delete the record. Type N and the entire record will be ready for editing whichever field needs to be corrected. The fields can be moved through in exactly the same way as when entering data. Once a record has been corrected, the user can move on to the next record that needs to be edited.

If the record has to be deleted from the database, type Y. The user will then be asked again whether the record is to be deleted. It is essential at this point for the user to be sure that he wants to delete it. Type Y to do so, otherwise N to retain the record in the database.

6. ENTERING AND EDITING RECOVERIES

To enter a Tag Recovery, type 3 while positioned in the main menu. A blank Tag Recovery Data record will then appear on the screen. An example of a completed record is shown below (Figure 8).

TAG RECOVERY DATA - Record 6770 Tag number Date found Date cred. Place Latitude Longitude Area cred. Species

Species cred. Fork length Length cred. Weight Weight cred. Finder Date received Orig. data Vessel flag Cntry of rec.

X48750 15.06.91 Caught 01.06.91 4 OUTSIDE RARUMANA 0815S 15700E 2 S

46.0 1

4 ALPINO NINIPUA 15.07.91 N SB SB

Vessel Gear type School asc

Place cde EZ Notes

SOLTAI 27 PS 1

SB

TAG RELEASE DATA Project Length Species Spcs cred. School Tagger Quality School asc Notes

RT 46.0 S

407 FMV 1 1

Fish meth PS

• Cruise: TET036-91 Country Date rel Lat. Lon. Condition FL rel. Double tag

PG 02.02.91 1045S 14924E 1 1

Figure 8. A completed Tag Recovery Data record

The recovery database is interactive with the release database, so that once a recovery is entered, the relevant release data pertaining to that tag are collected and displayed in the Tag Release Data window in the record. This information will only be displayed if the release record is in the database in use. Laptop computers used at sea are often of restricted storage capacity and operating speed, so that only data from recent cruises are stored on the hard disks. If a recovery is entered on such a machine and the respective release record is not available, then the message 'This tag number not released' will appear in the window.

14

Many of the codes entered in the Tag Recovery Data record have been described in previous sections. The following codes are new.

Date found Date tag was recovered (or noticed).

Date caught Date fish was actually caught by the fishing vessel.

Date cred. Codes to determine how accurately the date of tag recovery is known:

1

2 3 4 5 6 7 8

Day This is the default, i.e. the exact day is known. Week Fortnight Month Quarter year Half year Year Unknown

Place General area where tagged tuna was recovered.

Area cred. Codes to determine how accurately the area of recovery can be specified:

1 Minute This is the default, and is to degrees and minutes of latitude and longitude.

2 30-minute square 3 One-degree square 4 Five-degree square 5 Five-degree by 20-degree rectangle 6 Unknown

For Date cred. and Area cred., if the code is not 1, then the values in the Date found, Latitude and Longitude fields represent the midpoints to the stratifications indicated in the credibility codes (e.g. an Area cred. of 2 means that the latitude and longitude values are in the centre of a 30-minute square).

Species cred. Code to indicate how accurate the species code is suspected to be. Uses the same codes as Species reliability in the Release file (see Appendix II).

Length cred. Uses the same codes as used in the Release records for Fork length credibility.

Weight Weight of the fish to the nearest 0.1 kg.

Weight cred. Five codes to define how the weight of the recovered fish was determined:

1 Whole weight 2 Gilled and gutted weight 3 Guess 4 Calculated from length 5 Unknown

Finder The full name of the person who found and returned the tag.

Date Date on the covering letter accompanying the tag. If the letter is undated, enter the date that received it was received at SPC.

15

Orig. data Indicate with a Y or N whether SPC has the tag and the original accompanying letter. This may not always be the case, especially with regard to in-country projects where local Fisheries Department staff handle some of the returns.

Vessel flag Country for which vessel is fishing.

Cntry of rec. Country actually reporting the tag recovery.

Vessel Name of the fishing vessel that recovered the tag.

Fish meth. If the actual fishing method used to catch the tagged fish differed from the principal gear on the vessel, type in the method using the relevant gear type code.

School asc. Use the same codes as in the Release records to indicate the type of object that the fish recovered was associated with.

Place code Codes to indicate where the tag was actually noticed:

(blank) On board the catcher vessel C In the cannery

EZ Exclusive Economic Zone fish was caught in, using the following country codes:

blank AS AU CK FJ FM GU HB HW ID II JP JT JV KI KR

Unknown A. Samoa Australia Cook Is Fiji FSM Guam Howland/Baker Is Hawaii Indonesia International Japan Johnston Atoll Jarvis I. Kiribati Korea

LN MH MI MR MY NC NF NR NU NZ PF PG PH PN PR PU

Line Is Matthew & Hunter Is Marshall Is Northern Marianas Malaysia New Caledonia Norfolk I. Nauru Niue New Zealand French Polynesia Papua New Guinea Philippines Pitcairn Puerto Rico Palau

PX PY SB SG SU TH TK TO TV TW US

vu WF

WK WS

Phoenix Is Palmyra Is Soiomon Is Singapore Russia Thailand Tokelau Tonga Tuvalu Taiwan USA Vanuatu Wallis & Futuna Wake I. W. Samoa

Notes Any special notes on recovery.

The Edit Recoveries option works along similar lines to the Edit Releases option, described in Section 5.

7. DAILY POSITIONS AND SCHOOL SIGHTINGS

Options 7, 8 and 9 in the main menu incorporate data from two log forms completed on a daily basis on the tagging vessel. The Daily log includes position and environment data, while the School sightings/Fishing log lists not only schools from which fish were tagged but also those that were fished unsuccessfully or were sighted but not fished. This information is included in the tagging database to assist in plotting vessel movement, documenting tagging success rate, and relating catch to environment parameters.

16

7.1 Entering positions and school sightings

At the end of each day, once all Tag Release, Tagger and School Data records have been entered and checked, the cruise leader will enter the daily position details from the Daily log and the school sightings information from the Sightings log. The user is first prompted to enter the relevant project code, followed by the cruise and the date. The first screen that will appear is the Positions Data record (Figure 9).

POSITIONS DATA - Record 123

Date Time

Latitude Longitude Activity Wind Sea cond. SST Air temp. Cloud

05.09.91 0600

0024N 17353E AA 095/2 C 30.1 30.8 5

Running time total Searching time total

Time

Latitude Longitude Activity Wind Sea cond. SST Air temp. Cloud

17.9 11.1

1200

0016N 17424E SF 110/10 C 30.1 30.5 20

Time

Latitude Longitude Activity Wind Sea cond. SST Air temp. Cloud

1800

0004S 17457E SF 060/8 C 30.4 30.5 5

Figure 9. A completed Positions Data record

The fields for latitude, longitude, SST (sea surface temperature) and air temperature have been described in Section 4. Entries for the remaining fields are listed below.

Activity A two-letter code that describes the activity at the specific time of day:

IP DF SF BT SH AA ST

In port Drifting Searching and fishing Baiting Sheltering At anchor Steaming

(blank) No recording

Wind Describes the wind direction in degrees and the strength in knots. The format for this field is ddd/kk, where ddd is degrees and kk is knots.

Sea cond. Describes the sea condition at that time:

Cloud

C S M R

Calm Slight Moderate Rough

(blank) No recording

Estimated cloud cover expressed as a percentage.

17

Running time Total number of hours that vessel spent in steaming that day.

Searching Total number of hours spent in searching and fishing mat day. time

Once the Positions Data record has been completed and confirmed, the user will be prompted with the question:

Generate records for TAGGED schools and edit these? (Y/N)

If the answer is 'Yes' to this question, a program will extract the relevant school information from the School Data records and copy it to Sightings Data records (Figure 10).

SIGHTINGS DATA

Date Start time Stop time Sighted school no. RTTP school no. Latitude Longitude Country code Size of school Type Association Detection method Chummed? (Y/N) Responded? (Y/N) Sea surface temp.

- Record 353

17.08.91 1330 1500 2 659 0006N 17339E KI M 2 7 2 Y Y 30.2

School species Skipjack tagged Yellowfin tagged Bigeye tagged Other species codes Other sp. tagged

Skipjack poled Yellowfin poled Bigeye poled Other species codes Other sp. poled

M 570 176 0

, , 0

143 29 0 T,M,R 25

Notes CURRENT LINE S OF KURIA, FAST BITING

Figure 10. A completed Sightings Data record

In addition, the program will calculate the numbers offish for each species that were tagged. These numbers can men be verified against manual additions for each school. The program will check if this process has already been done and will not overwrite or produce duplicate records for these schools if they already exist.

The user is then required to edit each of the tagged schools, using the procedures described in Section 5. A number of fields need to be filled out, namely the Sighted school number, Size of school, School species and the fields relating to the species poled.

Once the user quits the editing mode, he will be put into entry mode to enter the schools that were sighted during the day but did not yield any tag releases. The following fields have not been described in previous sections:

Sighted school Chronologically numbered schools sighted, reverting to 1 for the first school of each day. no. This number should not be confused with the School Data record School number that refers

to tagging schools and does not revert to 1 at the start of each day.

RTTP school no.

Identical school number to that used in the School Data record. This field is automatically filled in by the program that generates the records for tagged schools.

18

Size of school The estimated size of the school, using the following codes:

S Small (less than 10 tonnes) M Medium (10-50 tonnes) L Large (50-100 tonnes) V Very large (over 100 tonnes)

School species

Other species codes

This describes the species composition of the school, and is normally a species code (e.g. S or Y). It may also be M for a mixed school of skipjack and yellowfin. The value U is used if the species composition is unknown.

The first occurrence of this field in the Sightings Data record refers to other fish species that were tagged, while the second refers to species that were caught but not tagged. The following codes are used:

A Albacore B Barracuda C D Dogtooth tuna F Frigate tunas I K Kyphosus sp. L Lobotes sp. M O Longtail tuna P Pelagic whitetip shark R S Silky shark T Ocean triggerfish W X Platax sp. Y Yellowtail (Seriola sp.)

Caranx sexfasciatus Island bonito Mahi mahi Rainbow runner Wahoo

Other sp. tagged

The only 'Other species' to be tagged during the RTTP was the longtail tuna. Most of the species listed here are by-catch from fishing around logs and FADs.

Total number of fish of other species that were tagged.

Skipjack, The numbers of each tuna species that were too damaged for tagging and remained on deck Yellowfin, at the end of fishing and tagging. Bigeye poled

Other sp. The total number of fish of other species that were caught but not tagged. poled

If the answer to the question about generating records for tagged schools is 'No', i.e. no tagging took place on the specific day, the user will be taken to a blank Sightings Data record, ready for data entry. Once the sighted schools are entered, the user can leave this option by pressing the Enter and Esc keys while positioned in the Start Time field of a blank record.

7.2 Editing positions and school sightings

The user should type the number 8 while in the main menu, and then either 1 or 2, depending on whether one wishes to edit a position record or a sightings record. The records are edited using procedures identical to those used for correcting release and recovery records. After editing a sightings record, the user is returned to that record. The next record can then be called up by typing N, for next.

7.3 Reporting positions and school sightings

This is a simple report that prompts for the Project and the date of the desired record, and provides a print­out of that date's position and sightings data. Type the number 9 while in the main menu to obtain this report.

19

8. PRODUCING REPORTS

There are two report menus, one each for releases and recoveries. Release reports generally report both numbers of tags used and numbers offish tagged, while recovery reports usually only report numbers offish tagged. Furthermore, all recovery reports ignore tags identified as being lost, rejected or used in seeding experiments.

8.1 Releases

The Release Reports menu is entered by typing 3 while positioned in the main menu. Seven report options are available in this menu, as shown in Figure 11.

1

2

3

4

5

6

Release Reports

Release school type

Weights of releases

List releases (check data entry)

Summarise releases by tagger

Length frequency of releases

Summarise releases by 5-degree square

7 Tags used list

8 Tally releases by gear type

Q Quit

Figure 11. The Release Reports menu

8.1.1 Release school type

This option summarises the numbers of releases by species and school association, after the user is prompted to select Project and Cruise range. To obtain a summary for one cruise, the full cruise number has to be entered in both range fields (i.e. TET036-91 to TET036-91). An example of this report for two cruises is shown in Table 1 below.

Table 1. The Release School Type listing

Assn

Unass.

Log

Anch. FAD

Mam Mml

Curr. Line

Tagged fish releases

Yellowfin

188

120

1,386

0

2

3%

2%

19%

0%

0%

Bigeye

2

61

125

0

0

0%

1%

2%

0%

0%

- School type -Cruises TETOOl-89

Skipjack

761

335

3,966

211

7

11%

5%

55%

3%

0%

Species - Project to TET002-89

Albacore

0

0

0

0

0

0%

0%

0%

0%

0%

RT - 13.09.91

Other

0

0

0

0

0

0%

0%

0%

0%

0%

Unknown

0

0

0

0

0

0%

0%

0%

0%

0%

Total

951

516

5,477

211

9

13%

7%

76%

3%

0%

Total 1,696 24% 188 3% 5,280 74% 0 0% 0 0% 0 0% 7,164 100%

20

8.1.2 Weights of releases

The Weights of releases option calculates the weights of a day's releases for each species using length-weight regression equations from the literature. The values of each species are also calculated, based on a specified dollar value per kg of fish, and summarised in a table (Table 2). This option is used when tagging is being done from a commercial vessel and compensation is paid for the fish released. The user is prompted to enter the project, cruise number, the day's date and the required dollar value per kg.

Table 2. The Weights of Releases listing

Sch.

659 660

Total

SNo.

570 15

585

Weights for

S Wt

2,394.30 52.22

2,446.52

Project -

YNo.

176

176

RT - Cruise TET056-91 -

Y Wt

723.19

723.19

Tot. No.

746 15

761

17.08.91

Tot. Wt

3,117.49 52.22

3,169.71

Value

12,469.96 208.88

12,678.84

This option will run if there are missing lengths in the relevant Tag Release Data records, but will notify the user of missing data. If the system complains of missing data, it is recommended that the Estimate Missing Lengths option in the Error Checks menu (Section 9.2) be selected to replace missing lengths in the data with the average length of the particular species from the school. After that process has been run for the data set, the weights of releases option may be selected again to produce an estimate of the weight of the day's releases.

8.1.3 List releases (check data entry)

This option produces a table of releases for a specific school, day range or tag range (Table 3). List Releases is used at the end of each tagging day to provide each tagger with a hard copy of his tagging data for editing against the original transcribed data.

The user is prompted for Project, the tagger's initials, and the form of tag selection, i.e. all releases, by a specific school, date range or tag range. To obtain a printout for editing, it is common to select the data range, which defaults to the current date. For all cases, except when selecting by tag range, the tag releases are grouped by School and Tagger. The Tag range selection, however, produces an output of releases without the attendant School and Tagger information. The codes shown in Table 3 are abbreviations of those described fully in Section 4.

Table 3. The List Releases listing

School 453 Cruise RT TET038-91 Date 22.02.91 Time 1117-1206 Pos 0314S 15053E

Detect. 2 Birds Type 3 Bree. Assoc. 8 Sea. YFT Catch SST 29.3

Tagger KNB Cradle PB Assist. ED Type H13 First X60239

No. Rec. Tag Sp. Qual. Cond. FL Cred. GR DB Notes

1 2 3 4 5 6

12226 12227 12228 12229 12230 12231

X60239 X60240 X60241 X60242 X60243 X60244

S S S Y Y S

1 1 2 1 1 1

1 1 1 2 2 7

47.0 47.0 44.0 41.0 41.0 39.0 1

I PL I PL 1 PL I PL I PL

PL

1 2

1 2

X60240 X60239 Tag too low X60243 Bleeding mouth X60242 Bleeding mouth Small cookie cutter bite

21

8.1.4 Summarise releases by tagger

Option 4 in the Release Reports menu provides a table summary of the number of single and double tag releases by species for project, cruise and tagger (Table 4). It also summarises tags that were not used, for various reasons, during the cruise. The user is prompted to enter desired projects and cruises. A report summarising all projects may be obtained by entering AL in the project field, while a report summarising all cruises for a specific project can be produced by selecting the entire range of cruises (the default) for each project. Finally, the user is prompted to enter an inclusive date. This will control the cutoff date for data selection, in case some data from the last cruise selected are to be excluded from the report.

Table 4. The Summarise Releases by Tagger listing

Tag Releases 09.02.91 - By tagger - up to 09.02.91 - Cruise RT TET036-91

Yellowfin Skipjack Bigeye Albacore Other Total Tags not Total Tagger releases releases releases releases releases tagged used tags

ADL

ETP

FMV

KNB

U O

TOT

341

171

564

240

4S4

1,800

(52)

(1)

(42)

0) (8)

(104)

964

1,491

796

1,180

875

5,306

() () (6)

() (20)

(26)

55

25

35

29

74

218

(20)

() (4)

(3)

(3)

(30)

() ( () (

() (

() ( () (

() (

) 1,360

) 1,687

) 1,395

) 1,449

) 1,433

) 7,324

(72)

(1)

(52)

(4)

(31)

(160)

8

5

1

3

17

1,368

1,687

1,400

1,450

1,436

7,341

The numbers listed under each species in Table 4 represent the total number of tags used by specific taggers for that species, with the numbers in brackets showing the number of double tag releases. To obtain the actual number of fish released, subtract the figure(s) in brackets from the relevant release number(s): e.g. for Cruise RT TET036-91 above, 1,800 tags were used for yellowfin releases, 104 of which were double tags, therefore 1,696 yellowfin were actually released. Furthermore, as 104 yellowfin received two tags each, 1,592 yellowfin were single tagged (1,696 minus 104).

The Other releases column in the table lists the number of releases where the species was not recorded by the individual taggers: in this example, there were none.

The Tags not used column counts tags that were lost or rejected during the tagging operation, or were used in tag seeding experiments on commercial tuna fishing vessels. Occasionally, tags are missing from the packets supplied by the manufacturer; such events are treated as rejected tags.

8.1.5 Length frequency of releases

This option produces a length frequency histogram, via LOTUS 123, of fork lengths of tuna tagged and released. This information is also stored in a text file of lengths and associated numbers (or frequencies) of fish. A number of specific steps must be followed to produce the histogram.

When the user first enters the option, he is prompted with the screen shown in Figure 12 that lists the selection criteria options available for extracting the data to be graphed. Data can be extracted by species, project, a single cruise, a specific date, one to five categories of school association, and up to ten ranges of school numbers. The user can enter values in any of the fields or leave them blank, depending on the amount of data he wishes to extract. Valid species are S for skipjack, Y for yellowfin and B for bigeye. The project may be a specific project or blank for all projects. The cruise also may be a specific cruise or blank for all cruises within the project. The association categories are identical to the codes used in Release Data records.

22

At this stage, it is useful to work through an example, namely to produce a histogram of skipjack tagged from anchored FAD-associated schools in Papua New Guinea waters during 1991 RTTP operations. The project vessel made two visits to PNG in 1991, and in that time completed eight cruises. As the program can only select one cruise at a time, it is more appropriate to select the data by a series of relevant RT school number ranges. As these ranges will probably include schools that had other association-types, we also have to specify the association required, using the appropriate association code. The completed selection screen for this example is shown below (Figure 12).

LENGTH FREQUENCY HISTOGRAM Enter Species Enter Project Enter Cruise Enter Date Enter School Range

Enter Heading for Graph Enter Output File Name

S RT

-.

from from from from from from from from from from

Proceed to LOTUS 123 (Y/N)

404 584

- SELECTION CRITERIA

Enter Association(s) 3, , , , to to to to to to to to to to

447 604

PNG FAD ASSOCIATED SJ - 1991 PNGFADSJ N

Figure 12. Length Frequency Histogram selection screen

At the bottom of the selection screen there is space to specify a heading or title for the graph. When printed, the selected heading will appear in large type above the histogram. A smaller sub-heading that lists the species, number offish in the sample, and selected association(s) will appear below the heading (Figure 13).

In the selection screen, the user is also prompted to name the output file that will be generated by the extract program. This name is critical, as it forms the prefix to two files used to generate the histogram and the file in which the histogram is saved. These three files are created in the LOTUS work directory (C: >\WKS). File names should not exceed eight characters (to conform to DOS conventions) and should make it easy for the user to identify the contents immediately. In the example, the file prefix of 'PNGFADSJ' provides the country code, school association and species selected for graphing.

The final question for the user is whether he wishes to proceed into LOTUS 123 to produce the graph after the data have been extracted. If a number of extracts are required, e.g. for other species, school ranges and associations, then the user should type N in the last field. The Release Reports menu will then reappear on the screen and the next extract can be initiated. When the final extract is made, or if only one is required, the answer should be Y, which will result in LOTUS 123 being opened.

For the PNG example, the extract program will generate the following files:

C:\WKS\PNGFADSJ.TXT (A text file containing the two headings for the graph) C:\WKS\PNGFADSJ.DAT (A text file containing the length frequency data)

23

At the end of each extract, a window appears on the screen that shows the sample size, minimum and maximum lengths, mean length and standard deviation of the length data that have been extracted. This window disappears when any key is pressed.

Instructions on how to proceed into LOTUS 123 and to produce the graph are then displayed. Press any key to open LOTUS, followed by the Enter key to move into 1-2-3 and the worksheet mode. Once in this mode, the user will be able to call up the two files listed above and generate the histogram. To do this, the user must follow the instructions listed below.

(a) First, the user must retrieve the template file that is designed to hold the text and data for the graph. Type /F to select File in the 1-2-3 menu, then R (for Retrieve). A number of file names will then appear on the screen. Use the left and right arrow keys to locate and highlight a file called LF_TEMPL. Once located, press Enter to retrieve the file. The template will then appear on the screen as a standard LOTUS worksheet.

(b) The next step is to retrieve the text file that holds the two headings for the graph. Type /F followed by I (for Import). Then press T (for Text) and type in the name of the file to be retrieved, ensuring that the name includes the suffix .TXT. The appropriate file for the example is PNGFADSJ.TXT. Then press the Enter key. The program will respond by inserting the heading specified in the histogram selection screen in cell A2 of the worksheet and the species and sample size heading in cell A3.

(c) At this point, it is important to move the cursor down to cell A3 using the down arrow key, so that it is in position for retrieving the length frequency data.

(d) To retrieve the data, type /F, I, and N (for number). The file name to enter at this point should include the suffix .DAT. For the example, the file name is PNGFADSJ.DAT. After entering the file name, a list of lengths and their respective frequencies will appear below the headings in the worksheet.

(e) To generate the graph, simply type /G. This will open the Graph menu. The histogram can be viewed on the screen by typing V. The histogram for the example is shown below as it appears on screen and as a printout (Figure 13).

PNG FAD ASSOCIATED SJ - 1991 SKIPJACK RELEASES (N-4060) Assoc 3, , , ,

T ^ T # 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100

Pork Length (cm)

Figure 13. An example of the length frequency histogram screen and printout

24

(f) To save the graph as a file, first press Enter to return to the Graph menu, followed by S (to save). Then type in the file name, which should be the same as that specified in the histogram selection screen, but without a suffix. This would be PNGFADSJ, using the example above. The graph will be saved in the C:\>WKS directory as PNGFADSJ.PIC

(g) Now type Q (to quit) to return to the worksheet screen. If other graphs are to be generated, retrieve the template as per (a) and repeat instructions (b) - (f), remembering to use the appropriate file names. When all the graphs are ready, return to the worksheet and type /Q to quit 1-2-3 and return to the LOTUS 123 entry screen.

In doing this, the program prompts the user with the question 'Are you sure?'. Answer Y to this. The following question about saving the worksheet should be answered with a N, otherwise the current worksheet will overwrite the template. If the worksheet is accidentally saved, the template can be recovered from the backup file using the DOS copy command (COPY C:\WKS\LF_TEMPL.BAK C:\WKS\LF_TEMPL.WK1).

(h) Once in the LOTUS 123 entry screen, the user can enter PrintGraph by typing P. Once entered, type I (for Image Select). A list of files will then appear on the screen. Scroll down this list with the down arrow key to locate the required file for printing (e.g. PNGFADSJ). Select the file by pressing the Enter key when the cursor highlights the file name.

(i) The histogram can then be printed by pressing G (for Go). Once this is done, press E (to Exit Printgraph) and E (to Exit LOTUS). The user will then return to the Release Reports menu.

8.1.6 Summarise releases by 5-degree square

This option prompts for Project and Cruise range, and then produces a summary of numbers of releases by species for the selected data to the nearest five-degree squares of latitude and longitude (Table 5). The reference point for each five-degree square is the lower left-hand corner of the square.

Table 5. The Summarise Releases by 5-degree square listing

Tag releases 08.09.91 - By

5-deg. lat.

OOOON 0500S 0500S 1000S

Totals

5-deg. Ion.

17000E 17000E 17500E 17500E

5-degree lat./lon. - Project RT - Cruises TET035-91 to TET036-91

Number Skipjack

373 153 101 86

713

Number Yellowfin

8 0 0 0

8

Number Bigeye

0 0 0 0

0

Number Albacore

0 0 0 0

0

Number Unknown

0 0 0 0

0

Number Total

381 153 101 86

721

8.1.7 Tags used list

This option provides a list of tag ranges used over a specified period and in a specific EEZ, by prompting for date range and country code. In selecting a date range which may include a number of visits to the country required, plus visits to neighbouring countries, the country code selection filters out the tags used in the neighbouring countries. A blank in the country code field provides a printout for tags used in all countries visited over the date range. This list is generated primarily for the preparation of cruise reports but can also be useful for checking tags used on a daily basis.

25

8.7.8 Tally releases by gear type

This option provides a count of releases by species and fishing gear used for capture. The program prompts for Project, Cruise, and date range.

8.2 Recoveries

The Recovery Reports menu, entered by typing 6 in the main menu, offers twelve report options (Figure 14). For the best results, these options should be used with complete release and recovery databases. The tables generated by all of the options show numbers of fish rather than numbers of tags.

1

2

3

4

5

6

7

Recovery Reports

Taggers

Returns by gear

Time at large

Usable recoveries

Distance travelled

Recoveries by cruise

Recoveries vs releases; numbers by species and length interval

8

9

A

B

C

Q

Recovery and release information for tag letter creation

Recoveries to date by vessel flag and gear

Recoveries to date by country and place recovered

Distance travelled, by association

Mean displacement

Quit

Figure 14. The Recovery Reports menu

8.2.1 Taggers

The Taggers option produces a table on the total numbers of releases and recoveries made by individual taggers, and computes their recovery rates (Table 6). The user is prompted for Projects, and whether to use all data for projects selected, or to use a cruise or school range. He is then asked whether he wishes to calculate the numbers of recoveries from only those schools in the school range that have had at least one recovery or from all schools in the range, irrespective of whether there have been any recoveries.

Table 6. The Taggers listing

Tag recoveries Tagger 13.10.92 Project(s) RT Cruise ranges TET036-91 to TET036-91

Tagger Releases % Recoveries % Rate

ADL 1,360 19 399 22 29.3 ETP 1,687 23 452 25 26.8 FMV 1,395 19 358 20 25.7 KNB 1,449 20 278 16 19.2 U O 1,433 20 302 17 21.1

Total 7,324 1,789 24.4

26

8.2.2 Returns by gear

This option lists the numbers of recoveries by the type of fishing gear used to catch the tagged fish. Seeded tags are not included in this report. Recoveries in Solomon Islands are broken down by the Solomon Islands fishing companies of Solomon Taiyo (SOLTAI) and National Fisheries Development (NFD) to determine the difference in reporting rate of the two companies.

8.2.3 Time at large

This option lists the minimum, maximum and mean days at large, by species, for tag recoveries with usable recovery dates. It also produces a Days-at-large frequency table for each species.

8.2.4 Usable recoveries

This option summarises the quality of the recovery data. It excludes seeded tags and gives numbers of recoveries with usable/unusable data relating to species, recovery dates, recovery positions, fork length, weights and gear type of the recovery vessel.

8.2.5 Distance travelled

This option lists the minimum, maximum and mean distances travelled, by species, for tag recoveries with usable recovery positions. It also produces a distance travelled frequency table for each species.

8.2.6 Recoveries by cruise

Enter the desired project(s), and whether all releases are desired, or only those for a specific cruise range, school range, or date range. The program then generates a report tallying recoveries vs releases by species for the project, or cruise (by cruise), or for the school/date range (by school). The data are sent to a file in \TAGS\DOC named Trproject-name-school-range.TXT.

8.2.7 Recoveries vs releases; numbers by species and length interval

Enter the desired project(s) and the program will tally the length frequency of releases and recoveries by species. This report only displays to the screen, so if a printout is desired the user must either do a screen dump, or use the utility 'Snipper', which allows selected parts of the screen to be captured to a file when invoked with the key combination <ALT>W.

8.2.8 Recovery and release information for tag letter creation

This option allows the user to generate standard tag recovery letter data to be sent out to people sending in tags. The user is allowed to generate tag recovery information either over a specified date range, or for manually entered tags. The data are sent to a file called TAGLET.TXT in \TAGS\DOC.

8.2.9 Recoveries to date by vessel flag and gear

Enter the project(s), species, and date received range for tag recoveries desired. The program sums tag recoveries for the selected criteria and reports them by gear type and vessel flag for the selected interval,

27

and for all dates prior to and including the selected interval (the total for the project and species up to the final date specified). Output is sent to a file in \TAGS\DOC named TRBGNmonth-number-of-final-date-species-character . TXT.

8.2.10 Recoveries to date by country and place recovered

Enter the project(s), species, and date received range for tag recoveries desired. The program sums tag recoveries for the selected criteria and reports them by place of recovery (vessel, cannery), and the countries the tags were recovered in for the selected interval (and the total for the project and species up to the final date specified). Output is sent to a file in \TAGS\DOC named TRBRCmonth-number-of-final-date-species-character.TXT.

8.2.11 Distance travelled, by association

Enter the project. The program will produce a report using all valid releases and recoveries for that project, listing the mean distances fish travelled, by 60-day time interval at large, object of association, and species. In addition, the program will show the minimum and maximum distances travelled, and the number of tags that were usable by the program for calculating the statistics. Output is sent to \TAGS\DOC\DIST60.txt.

8.2.12 Mean displacement

Enter the project, and either a cruise range or a cruise and a school range. A listing will be produced showing the calculated mean daily rate of movement in nautical miles for each species, by association of the school of release. Also, the program will list the total number of tags used for each calculation, along with the total distances travelled, total days at liberty, and the minimum and maximum distances travelled. Output is sent to \TAGS\DOC\MNDISP.txt.

9. ERROR CHECKS AND POST-ENTRY PROCESSING

The Error Checks and Post-Entry Processing menu (Figure 15), entered from the Main menu by typing E, offers a number of options to check for possible errors in the release and recovery data and to update various fields that are otherwise time-consuming to complete manually.

1

2

3

4

5

Error Checks and Post-Entry Processing

Tag codes

Estimate missing lengths

Re-index data files

Check release files for garbage data and duplicates

Check release tally by school, tagger and species

6

7

8

Q

Update species codes in release and recovery files

Update EEZs in recovery file

Update double tag recovery flag

Quit

Figure 15. The Error Checks and Post-Entry Processing menu

28

9.1 Tag codes

The Tag Codes option searches for and lists any recovered tags not in Tag Release Data records, i.e. recoveries of tags that were not actually placed in tuna released to the sea. This option is only useful if the computer being used contains the complete release and recovery databases.

9.2 Estimate missing lengths

The Estimate Missing Lengths option searches in the Tag Release Data records for any Fork Length fields with no measurements. If any are found, this program will calculate the average length of the fish from the length data stored for that species in that particular school. This calculated figure will then be inserted in the particular FL field. This option is most often used in conjunction with the Weights of Releases option (Section 8.1.2), which requires that all fork length fields have valid measurements before calculating the weights of releases.

9.3 Re-index data files

All of the database files depend on a special set of files that tell the database system where to quickly find information needed. These are the index files, and there is one for each database table. Unless these index files are up to date with the database tables, look-up requests may not be fulfilled correctly and information can actually be lost. Therefore, if any editing is done to any of the database tables outside the normal menu system, or if the system is behaving in an anomalous manner (i.e. records that definitely exist cannot be found), use this menu option to re-index all the database tables automatically.

9.4 Check release files for garbage data and duplicates

It is remotely possible for FOXPRO and DOS to conspire together to lose track of data. This is potentially disastrous because neither FOXPRO nor DOS will give warning when it has happened. The only way to check for this kind of problem is to scan through the database files every so often in the Browse mode, and check to see if there are 'garbage' characters in the fields, such as smiling faces, triangles and squiggly lines. Since this is a tedious task, a menu item has been created to get the computer to do it. The Release, Notes, Cruise, School, Tagger, Sight, Position and Recovery files are scanned for garbage in several key fields. Anything in the record that appears to qualify (e.g. contains unusual characters or figures) is listed on the screen, along with the record number.

If this check should turn out positive for any of the files, it will be necessary to edit the file in the Browse mode to repair the damaged data by hand. Alternatively, if an up to date backup of the file exists, delete the damaged one from the hard disk and restore the backup version. This solution assumes that the backup is undamaged. If the garbage data are still present after the restoration, it is best to restore an earlier backup version if it exists, and then re-enter the damaged data if necessary.

The program also scans the database for duplicate records that may have been accidentally added to the database subset in use. Any reported duplicates should be examined and resolved by the cruise leader or designated database manager.

9.5 Check release tally by school, tagger and species

This option provides a count of the numbers of single and double tags released by school, tagger and species, and is used at the end of each tagging day to compare the numbers of tags entered with hand tallies. Discrepancies in numbers can then be narrowed down to individual taggers and schools, and errors in counts

29

or data entry quickly located. The option prompts the user for Project and a school range over which to prepare the report. An example of the report is shown in Table 7.

Table 7. The Check Release Tally listing

Tally of tags released for Project RT

Proj

RT

RT

RT

RT

RT

RT

Sch

585

585

585

585

585

585

Summary of Tallies (over

Subtotal for:

Subtotal for:

Subtotal for:

Subtotal for:

Totals:

Tagger

BC

ED

ED

KNB

KNB

U O

actual school

Cruise TET071-91

Sp

S

S

Y

S

Y

S

1 range

B

Y

S

0

STags

19

1

0

16

1

54

585 to 585)

0

1

90

0

91

Generated 10.06.91

DTags

92

60

2

96

2

20

0

4

268

0

272

TTags

111

61

2

112

3

74

0

5

358

0

363

Tags that have been rejected, lost or used in seeding experiments are not included in this calculation. Thus the figures generated in this report list the numbers of valid tag releases. However, the number of double tags has to be halved to obtain the number of fish released with two tags. In the above listing, for instance, 91 fish were released with single tags and 136 with double tags, for a total of 227 releases.

9.6 Update species codes in release and recovery files

This option checks the release and recovery files for unknown species, and resets them to the best estimate of species available, setting the species reliability code as appropriate. The program checks each Tag Release Data record; if the Species code in a record is blank or U the system checks to see if the Default species field in the appropriate School Data record is blank. If not, it sets the Tag Release Data record species to the school default, and sets the Species Reliability code to 1. The program then searches for a Tag Recovery Data record for that tag number. If there is one, and the recovery species is blank or U, it will check the release record species for a valid code. If one is present, it sets the recovery species code to that of the release species code and sets the species reliability code for the recovery to 2. If there is no valid release species code, it checks the school species default. If there is a valid default, it sets the recovery species to that of the school default, and sets the recovery species reliability code to 1. In some cases, it may be desirable to set the release species code to that found in the recovery record. In such a case, the user should ensure that the release reliability code is reset to 3, denoting what has been done. The user is prompted to enter the project, cruise and release date range interval to be checked when using this option.

9.7 Update EEZs in recovery file

This option will check the Tag Recovery Data records for unknown EEZ codes and update those that are missing by assigning an EEZ code (identical to Country code) based on the latitude and longitude of the recovery. The user is prompted to enter the required Project.

30

9.8 Update double tag recovery flag

After prompting the user for a project, this option attempts to set the double tag or 'DB' field of the recovery data file according to how many tags were recovered from a fish that was initially released with two tags, i.e. was 'double tagged'. The DB field is set using the criteria shown in Figure 16. As an example, if only the first tag of a double tag pair has been returned, then this program will insert a figure 3 in the relevant DB field in the Recovery database.

Program checks Release file DB flag and tag number

Release file DB value detected by program

(blank)

1

2

Program gets Recovery file tag number and sets the Recovery file DB field

Corresponding tag number found in recovery file

(does nothing)

1 entered in DB field

2 entered in DB field

Corresponding tag number not found in recovery file

(does nothing)

3 entered in DB field

4 entered in DB field

Figure 16. Recovery file double tag field update criteria

This field does not show up on the Tag Recovery Data record screen but is the final column in the corresponding FOXPRO file. It can be checked by opening the file through FOXPRO and using the Browse option.

The DB field is used by various reporting programs that calculate statistics involving the recovery file, so it should be updated periodically when data entry operations are being conducted to that file. Failure to do so can result in erroneous recovery file reports.

10. HOUSEKEEPING

The Housekeeping menu provides a variety of options that allow the user to copy or transfer data to diskettes and other computers (Figure 17).

B

R

F T

D I

A

Housekeeping Menu

Backup

Restore

Consolidate releases FROM Consolidate releases TO

Distribute new recoveries Import new recoveries

Archive cruise

L

M

0 C

E

X

Q

Load cruise from archive

Maintenance archive

Transfer to text for ORACLE Transfer recoveries for ORACLE

Change tag exclusion ranges

Extract data for range of cruises

Quit

Figure 17. The Housekeeping menu

31

10.1 Backup

The copying or backup of data from computer hard disk to diskette is an essential part of the daily routine, and helps to ensure that no information will be lost in the event of hardware or software failure. To backup a day's data, enter the housekeeping menu and type B. The Backup menu will then appear, giving the user options for files to be copied (Figure 18).

1

2

3

Backup Menu

PRG programs and templates

DBF data files

MAP files Q Quit

Figure 18. The Backup menu

Type 2 to backup the data (or DBF) files. The user will be asked whether he wishes to format a new diskette or erase the one to be used, followed by a query as to whether all the data on the diskette should be deleted. Answer Y or N for the first question, and Y for the second question. After placing the diskette in the A drive of the computer, the user will again be queried about deleting any data on it, and again the answer should be Y. The relevant files are first compressed using the PKZIP utility and then copied to the diskette using the SLICE utility. This compresses the data to reduce the number of disks used and then ensures that if the total number of bytes of the data to be backed up still exceeds the capacity of one diskette, there will be an orderly storage of data to as many diskettes as needed.

It is recommended that three or four separate sets of backup diskettes be used in rotation, with the oldest backup being used for the next backup, so that in the event of a data corruption problem no more than two or three days of data entry work will be lost.

10.2 Restore

This option is used to restore a backup to a laptop in case of file corruption. It is also used to copy a backup of the data held on one computer to other computers. On entering this option, the user will first be prompted with the Restore menu, which is similar to the Backup menu, with options available to restore programs and templates, data files and map files. Once the option is specified, the user will be asked to insert the backup diskette in the A drive and press any key. The relevant files to be restored are first taken off the diskette using the SPLICE utility and then uncompressed using the PKUNZIP utility. The user must stay at the computer and answer Y to the queries as to whether each file should be replaced with the new version.

10.3 Consolidate releases

Since more than one computer is often used to enter release data, it is important to designate one machine as the main one (or Master), to hold a complete set of all data that is entered each day. Data entered on other computers (or Slaves) then need to be transferred to the Master. A Backup and Restore from the Slave to the Master will not achieve this, as any data entered on the Master will be overwritten. Correct transfer requires that any new data be compared with those already on the Master, and then appended if the comparison process concludes that the data are not already part of the existing data set.

32

Two options in the Housekeeping menu are used to achieve data transfer: the Consolidate Releases FROM option to copy data from the Slave to diskette, and the Consolidate Releases TO option to copy data to the Master from diskette and carry out a comparison before storing new data. The first option is only used on Slave machines, while the second option is only used on the Master.

In order to consolidate the day's release data from the Slave, type F, and define the required Project and Cruise. The relevant data are then extracted, and the user is prompted to insert a diskette for data transfer. This diskette should be clearly labelled for Consolidation Transfer.

Once the transfer from the Slave has been made, remove the diskette and insert it in the A drive of the Master laptop. Type T while positioned in the Housekeeping menu on the Master. The program will then prompt for the Project and Cruise to consolidate and proceed to add all new data from the diskette to the Master computer database.

Once the consolidation is complete, a backup of the Master computer (labelled Consolidated Backup) should be made and restored to all other computers. Figure 19 summarises the housekeeping routines that need to be completed each day while conducting field data entry operations, to ensure that tag release data are backed-up and consolidated.

Master computer

B

1 ackup

1 Daily Backup

diskette

Houseke eping for a

Slave computers

B

1 ackup

[ Daily Backup

diskette

II taggers

Master Computer

3. Bi

1 ickup

1 Consolidated Backup

diskette

2. Consolic

4. Re

ate TO

Housekeeping for Cri

sstore

lise Lea<

Slave computers

1. Consolida

1 te FROM

[ Consolidation Transfer

diskette

ler

Figure 19. Daily housekeeping routines for field data entry operations

33

10.4 Distribute new recoveries

This option enables the distribution of the recoveries database, via diskette, to other computers: e.g. distribution of data from SPC to the tagging vessel or from the Solomon Islands Fisheries Department to SPC. Recoveries held in a database are copied onto a formatted diskette.

10.5 Import new recoveries

The information created in Section 10.4 can be merged onto other computers that already hold recovery data by using this option. The user is prompted to load the diskette containing the new recoveries. These data are then compared to data already existing on the hard disk of the computer to determine whether they are to be appended or skipped. Data not found by key search in the existing set are subsequently appended.

10.6 Archive cruise

This option enables part of the Release database (by Project and Cruise) to be archived onto diskette. It can be used when the database has grown to a considerable capacity and reference to the cruises to be archived is not necessary. The program basically stores the cruise details from each database file onto a diskette and removes this information from the active database files on the computer. It is recommended that the diskette(s) be labelled with the cruise numbers that have been duly archived. The program prompts for the Project and Cruise to be archived.

When the archive for that cruise is completed, the program will ask to delete the index it has created to do the archive. If more cruises are to be archived at this time, do not allow the index to be deleted, since the program will use the index for the next cruise to be archived and it speeds up the archival process if the program does not have to rebuild the index each time. When finished, allow the program to delete the index, otherwise the redundant index will be kept and may cause problems in the future.

Although the School Data records of the cruise are copied to the archive diskette, they are not deleted from the School database on the hard disk. This ensures that all school records for the Project are accessible to other database systems that interact with the School database.

Before the archive of a cruise is initiated, the user is prompted with the Tags Exclusion list. This is a table of ranges of tags that is used to ensure tag numbers are not duplicated during data entry. Two main ranges and eight sub-ranges are included in the overall exclusion range (Figure 20).

Set tag ranges

Main Range Main Range

Range #1 Range #2 Range #3 Range #4 Range #5 Range #6 Range #7 Range #8

to check for exclusion

From X00001 to X80000 From Z00001 to Z07000

From X80001 to X80056 From X80101 to X80135 From X80301 to X80425 From X80501 to X80572 From Z07001 to Z07005 From Z07201 to Z07289 From Z07401 to Z07467 From Z07801 to Z07835

Figure 20. A completed Tags Exclusion list

34

The main ranges cover the main body of tags that have been released (and can be conveniently summarised into single ranges, e.g. X00001-X80000), while the sub-ranges include tags that have been released from blocks of tags that are still in use. When a new tag is entered into a Release Data record, two checks are made: the first to see whether the tag is already in the on-line database, and the second to see whether it falls within the ranges of tags in the Tags Exclusion list. If either happens, the user is told that the tag has already been entered and cannot be entered again. The Exclusion list is designed primarily for the field, where it is not practical to store the complete release database on the computers being used.

Although eight sub-ranges are available, they do not have to be filled in to ensure adequate checking on tag numbers. This can be achieved by allocating one range for the X tags and one range for the Z tags in the Main Range fields that overlap with existing tags in the on-line database. This means that all tags that have been released exist either in the Exclusion range or in on-line data, so that there is no chance of entering a tag that has already been used.

When archiving cruises, take care to archive each vessel on a separate set of diskettes. Since different vessels operating concurrently can have the same project, cruise, and year identifiers, the archival file names from different vessels with the same relative cruise can be identical. It is therefore possible that files being copied to the same diskette can overwrite other files and data be lost.

10.7 Load cruise from archive

This option enables previously archived cruises to be loaded from diskette into the active database files on the computer. The user is prompted for Project and Cruise to be loaded from Archive, before inserting the appropriate diskette.

10.8 Maintenance archive

This option is similar to the Archive Cruise option of Section 10.6, but differs in that all School data pertaining to a specified project and cruise are removed from the database as well. This option should be used with care.

10.9 Transfer to text for Oracle

This option is used in conjunction with data communications software and hardware to copy release and recovery data from microcomputer to the SPC minicomputer for data analysis and plotting.

10.10 Transfer recoveries for Oracle

This option is used in conjunction with data communications software and hardware to copy recovery data from microcomputer to minicomputer.

10.11 Change tag exclusion ranges

As noted in Section 10.6, ranges of tag numbers can be set so that the data entry system will check a tag number against a range of tag numbers before allowing it to be added to the release database. A tag that falls within one of these exclusion ranges will be considered a duplicate, and cannot be appended as a valid tag release using the normal data entry process. This menu item allows the exclusion ranges to be set separately from the archive process.

35

10.12 Extract data for range of cruises

Occasionally it is useful to be able to create a subset of the tagging database for distribution to colleagues or for analytical purposes. This option allows a complete set of data tables to be created and copied to diskette, containing release and recovery data from a specific project and cruise range. The following files will be created on the target diskette, with Pr being the project code selected:

PrR.DBF PrC.DBF PrS.DBF PrU.DBF PrT.DBF PrN.DBF PrP.DBF PrG.DBF

(the RELEASE.DBF extract) (the RECOVERY.DBF extract) (the SCHOOL.DBF extract) (the CRUISE.DBF extract) (the TAGGER.DBF extract) (the NOTES.DBF extract) (the POSITION.DBF extract) (the SIGHT.DBF extract)

11. LIST CRUISE / SCHOOL INFORMATION

This menu item provides information on cruise, school and date ranges for any project in the database system. Many of the reporting programs in the database system allow the user to restrict the scope of a query to certain cruises, schools or dates. This option may be used to provide a listing of valid ranges to be supplied as options to those reports.

12. PRODUCING MAPS

The Tagging Mapping Menu (Figure 21) is entered from the main menu by typing M, and allows for the printing of low resolution maps of releases and movements of recoveries. The release map option is particularly useful on a tagging vessel when planning cruises and deciding on areas that need to be visited or require further coverage.

1

2

3

4

Tagging Mapping Menu

Create map recoveries

Map recoveries

Create map releases

Map releases Q Quit

Figure 21. The Tagging Mapping menu

12.1 Create map recoveries

This option generates a map data file used by the Map Recoveries option. The user is prompted to enter the Project and the Cruise of the releases. The program will then locate any recoveries of tags held on the Recovery database that were originally released in the selected Project and Cruise.

36

12.2 Map recoveries

This option displays a map of the journey of the tagged fish from release to recovery, depending on the selection criteria previously selected in the Create Map Recoveries option. The program prompts the user to select a map template from those shown in Figure 22. To print the map, enter P; otherwise press the Enter key to return to the Mapping Menu. The map produced is of low resolution, and it is recommended these maps be produced on a high resolution graphics plotter.

12.3 Create map releases

This option generates a map data file of releases used by the Map Releases option. The user is prompted to enter the Project and the Cruise. A blank entered in the Cruise field will mean all cruises will be accessed.

Select the template MAP

F

P

S

W

Q

Enter

Federated States of Micronesia (ION, 130E -

Papua New Guinea (OC

Solomon Islands (05S,

Western Pacific (ION,

Quit

your choice

1, 140E

155E-

115E-

- 105

10S,

10S,

5, 155E)

165E)

180)

00, 165E)

Figure 22. Map templates available for mapping releases and recoveries

12.4 Map releases

This option displays a map of the releases, depending on the selection criteria used in the Create Map Releases option. The user is prompted to select a map template that is appropriate to the area fished during the selected cruise. The map produces square plots representing the number of releases, by school. The number of releases for the largest square size is indicated on the map (i.e. MAX = ...). To obtain a rough print of this map, type P; otherwise, press the Enter key to return to the Mapping menu.

12.5 Printing larger maps

If the user desires a larger version of the map displayed on the screen, he should follow the instructions below. The memory resident WordPerfect utility GRAB.COM must be loaded into memory for this set of instructions to apply.

(a) Bring the map up on the screen, according to the instructions provided in Section 12.4.

(b) Hold down the Alt and Shift keys and press the F9 function key. A box will appear on the screen.

37

(c) Adjust the positions of the top and left-hand margins of the box using the arrow keys so that they correspond with, or are slightly larger than, the top and left-hand limits of the map.

(d) Bring in the bottom and right-hand margins of the box using the Shift and arrow keys held down together so that they correspond with the bottom and right-hand limits of the map.

(e) Press the Enter key to capture the screen.

(f) Exit the Tagging Database System menu system.

(g) Make sure that the printer is on, that paper is loaded, and that the computer-to-printer selection switch is set to the computer in use.

(h) At the DOS C:\ > prompt, type the word TAGMAP, followed by the Enter key. WordPerfect will load and print the map automatically.

(i) When the print job is complete (as shown by the status screen), hit any key and WordPerfect will delete the bit map image file created during the screen grab of the map, and exit back to the C:\> prompt.

ACKNOWLEDGEMENTS

The authors would like to thank all Tuna and Billfish Assessment Programme staff who have contributed to the evolution of the RTTP Tagging Database System. These people include Chief Fisheries Scientist Dr Antony Lewis, Principal Fisheries Scientist Dr John Hampton, Fisheries Scientists David Itano and Joel Opnai, Fisheries Experimental Officers Filipe Viala and Etimoni Palu, Fisheries Research Officer Veronica Logez, and Computer Systems Manager Jeffrey Stander. Special thanks are due to Fisheries Statistician Tim Lawson for his original system design and programming in the early days of the RTTP. The editing and proof-reading skills of SPC Publication Officers Caroline Nalo and Roslyn Sharp greatly improved the manuscript. The RTTP was funded by the Sixth European Development Fund of the European Community.

39

Appendix I

RTTP TAGGING DATABASE SYSTEM DOCUMENTATION

1. Database file lay-outs and relationships

(a) Cruise

The Cruise database contains a record for each cruise. There may be one or more School records for one Cruise, though there can be Cruises listed for which no fish were tagged if Position or Sighting data records were entered.

Field

1 2

3 4 5 6

Field Name

PROJ CRU

VESSEL FL GR AREA

Type

Character Character

Character Character Character Character

Width

2 9

30 2 2 30

Description

Project code (RT, etc.) Cruise code (VVVNNN-YY) Vessel name Vessel nationality Vessel gear type Area of cruise

Note: VVV = Unique vessel name code; NNN = Consecutive cruise number for vessel; YY = Year. The order of the fields given in this case is that presented to the user. In the database file, the order of storage is actually VVVYY-NNN. This is done to simplify index generation, where the natural order is Vessel, Year, and Cruise Number.

(b) School

The School database contains a record for each tuna school from which at least one fish was tagged. There are one or many Tagger records for one School.

Field

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Field Name

PROJ CRU SCH CO DATE START STOP LAT LON SST DET TYPE ASSOC YFT CATCH SP NOTES

Type

Character Character Numeric Character Date Character Character Character Character Numeric Character Character Character Numeric Numeric Character Character

Width

2 9 4 2 8 4 4 5 6 4,1 1 1 1 3 4,1 1 40

Description

Project code Cruise code School number Country code Date school fished Start time of fishing Stop time of fishing Latitude of school Longitude Sea surface temperature School detection code School type School association Yellowfin in catch (%) Total catch in metric tons Default species for school Comments

40

(c) Tagger

The Tagger database contains a record for each tagger who tags one or more fish in a school. There are one or more Release records for one Tagger.

Field

1 2 3 4 5

6

7 8

Field Name

PROJ CRU SCH TAGGER CRADLE

ASSISTANT

TAG TYPE FIRST TAG

Type

Character Character Numeric Character Character

Character

Character Character

Width

2 9 4 3 2

3

3 6

Description

Project code Cruise code School number Initials of tagger Cradle position tagger Initials of the assistant Type of tag used First tag number the school

for the

tagger's

used in

(d) Release

The Release database contains one record for each tag available to the tagger. The tag may be used, lost, rejected or seeded, and one fish may have more than one tag. There may be one and only one Notes record per Release record.

Field

1 2 3 4 5

6 7 8 9 10 11 12 13

Field Name

PROJ CRU SCH TAG GR

TAGGER SP SPCRED QUAL COND FL CRED DB

Type

Character Character Numeric Character Character

Character Character Character Character Character Numeric Character Character

Width

2 9 4 6 2

3 1 1 1 1 5,1 1 1

Description

Project code Cruise code School number Tag number Gear type used to catch fish Initials of tagger Species of tuna tagged Species credibility Quality of tagging Condition of fish tagged Fork length of fish Fork length credibility Flag for double tagging

41

(e) Recovery

The Recovery database contains one record for each tag recovered. There is always one and only one Release record for each Recovery record.

Field

1 2

3 4 5

6

7

8

9

10

11

12 13 14

15 16

17

18 19

20 21

22

23 24 25 26

Field Name

TAG ORIGDATA

DATE CDATE DREL

LAT

LON

EZ

AREL

PLCODE

PLACE

SP SPCRED FL

FREL WT

WREL

FINDER RDATE

VESSEL GR

FMETH

ASSOC FLG CO DB

Type

Character Character

Date Date Character

Character

Character

Character

Character

Character

Character

Character Character Character

Character Numeric

Character

Character Date

Character Character

Character

Character Character Character Character

Width

6 1

8 8 1

5

6

1

1

1

35

1 1 1

1 5,1

1

20 8

30 2

2

1 2 2 1

Description

Tag number Indicator. Does SPC have the tag? Date of recovery Date fish was caught Reliability of date of recovery. Latitude position of recovery Longitude position of recovery Exclusive Economic Zone of recovery Reliability of position of recovery. Code indicating where tag was actually found Description of place of recovery Species of fish recovered Species reliability code Fork length of the fish recovered Fork length reliability Weight of the fish recovered Reliability of weight of the recovered fish Finder of the tag Date of covering letter sent with tag. If this is missing, date of receipt at SPC. Name of recovery vessel Gear type of recovery vessel Fishing method used to recover tag School association Flag of recovery vessel Country tag was found in Double tag recovery status flag (set by Update Double Tag Recovery Flag option in Housekeeping menu)

42

(f) Notes

The Notes database may contain one and only one record for each Release and Recovery record.

Field Field Name Type Width Description

1 TAG Character 6 Tag number 2 MODE Character 1 R for Releases, C for

Recovery 3 NOTES Character 40 Text for notes

(g) Position

The Position database may contain one and only one record for each day.

Field Field Name Type Width Description

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

PROJ CRU PDATE LAT6 LON6 ACT6 WIND6 SEAC6 SST6 TEMP6 CLD6 LAT12 LON12 ACT 12 WIND 12 SEAC12 SST12 TEMP12 CLD12 LAT18 LON18 ACT18 WIND 18 SEAC18 SST18 TEMP 18 CLD18 RUN SEARCH

Character Character Date Character Character Character Character Character Numeric Numeric Numeric Character Character Character Character Character Numeric Numeric Numeric Character Character Character Character Character Numeric Numeric Numeric Numeric Numeric

2 9 8 5 6 2 6 1 4,1 4,1 3 5 6 2 6 1 4,1 4,1 3 5 6 2 6 1 4,1 4,1 3 4,1 4,1

Project code Cruise code Date 0600 Latitude 0600 Longitude 0600 Activity 0600 Wind 0600 Sea condition 0600 Sea surface temp. 0600 Air temperature 0600 Cloud cover 1200 Latitude 1200 Longitude 1200 Activity 1200 Wind 1200 Sea condition 1200 Sea surface temp. 1200 Air temperature 1200 Cloud cover 1800 Latitude 1800 Longitude 1800 Activity 1800 Wind 1800 Sea condition 1800 Sea surface temp. 1800 Air temperature 1800 Cloud cover Hours running Hours searching/fishing

43

(h) Sight

The Sight database may contain many records for each day.

Field Field Name Type Width Description

1 2 3 4 5 6 7 8

9 10 11 12 13 14 15 16 17

18

19 20 21 22 23 24

25

26

27 28

29

PROJ CRU SCH SDATE SSTART SSTOP CO SNO

LAT LON SZE TYPE ASSOC DET SST CHUM RESP

SPCOMP

STAG YTAG BTAG OTCDE OTAG SPOLE

YPOLE

BPOLE

OPCDE OPOLE

NOTES

Character Character Numeric Date Character Character Character Numeric

Character Character Character Character Character Character Numeric Character Character

Character

Numeric Numeric Numeric Character Numeric Numeric

Numeric

Numeric

Character Numeric

Character

2 9 4 8 4 4 2 2

5 6 1 1 1 1 4,1 1 1

1

4 4 4 5 4 4

4

4

5 4

40

Project code Cruise code Tagged school number Date Start time Stop time Country code Chronological daily school number Latitude Longitude Size of school School type School association School detection method Sea surface temperature School chummed (Y/N) School responded to chumming Species composition of school No. of skipjack tagged No. of yellowfin tagged No. of bigeye tagged Other species code(s) No. of other species tagged No. of skipjack poled (caught) to the deck No. of yellowfin poled (caught) to the deck No. of bigeye poled (caught) to the deck Other species code(s) No. of other species poled (caught) to the deck Comments

44

2. Database indexing definitions

(a) Cruise

index name: CRUISE.cdx Definition: INDEX ON Proj + Cru TAG PrCr

INDEX ON Proj + SUBSTR(Cru,l,3) TAG Vsl UNIQUE

(b) School

Index name: SCHOOL.cdx Definition: INDEX ON Proj + Cru + STR( Sch, 4 ) TAG PrCrSc

INDEX ON Proj + Cru + DTOS(Date) + STR( Sch, 4 ) TAG PrCrDtSc

(c) Tagger

Index name: TAGGER.cdx

Definition: INDEX ON Proj + Cru + STR(Sch, 4) + Tagger TAG PrCrScTg INDEX ON Proj + Tagger TAG PrTg UNIQUE INDEX ON Proj + Cru + STR(Sch, 4) + Tagger TAG UPrCrScTg UNIQUE INDEX ON Tagger + Proj + Cru + STR(Sch, 4) TAG TgPrCrSc UNIQUE

(d) Release Index name: RELEASE.cdx Definition: INDEX ON Tag

INDEX ON Tagger INDEX ON Proj + Cru + STR(Sch,4) INDEX ON Proj + Cru + STR(Sch,4) + Tag INDEX ON Proj + Cru + STR(Sch,4) + Sp INDEX ON Proj + Cru + STR(Sch,4) + Tagger INDEX ON Proj + Cru + STR(Sch,4) + Tagger

(e) Recovery

Index name: RECOVERY.cdx Definition: INDEX ON Tag TAG

INDEX ON DTOS(Date) TAG Date INDEX ON DTOS(Rdate) TAG Rdate

(f) Notes

Index name: NOTES.cdx Definition: INDEX ON Tag + Mode TAG TaMd

(g) Position

+ +

TAG TAGTg TAG PrCrSc TAG PrCrScTa TAG PrCrScSp

Tag TAG PrCrScTgTa Sp TAG PrCrScTgSp

Index name: POSITION.cdx Definition: INDEX ON Proj + Cru + DTOS( Pdate ) TAG PrCrDt

45

(h) Sight

Index name: SIGHT.ndx Definition: INDEX ON Proj + Cru + DTOS( Sdate ) + Sstart TAG PrCrDtSt

INDEX ON Proj + Cru + DTOS( Sdate ) + Sstart + STR(Sno,2) TAG PrCrDtStSn INDEX ON Proj + Cru + STR(Sch,4) TAG PrCrSc

3. Database directories

(a) \TAGS\DBF

This directory contains all the Database files and permanent indexes to these database files for the Tagging system.

(b) \TAGS\DOC #

This directory contains the output text files produced from the tagging report programs. The user may reprint these by using the DOS Print command.

(c) \TAGS\LUT

This directory contains the necessary software and look-up tables needed to support certain types of database code updates. One look-up table that resides here is the EEZ code assignment system.

(d) \TAGS\MAN

This directory contains copies of the Tagging Database manual in both WordPerfect 5.1 format, and plain text format.

(e) \TAGS\MAP

This directory contains all the Pascal mapping programs and text files generated for these programs.

(f) \TAGS\PASCAL

This directory contains the Turbo Pascal compiler (Version 4.0) necessary to compile the Pascal mapping programs. It also contains some example programs.

(g) \TAGS\PRG

This directory contains the programs for the Tagging Database system.

(h) \TAGS\TMP

This directory contains the temporary index and database files used during the processing stages of reports, etc. Normally this directory is empty.

(i) \TAGS\UTL

This directory contains miscellaneous software required to do various housekeeping tasks, such as compression and decompression of backup files, and copying single large files on to multiple floppy disks.

•

47

Appendix II

QUICK REFERENCE TO RTTP TAGGING DATABASE SYSTEM CODES

Codes for Tag Release and Recovery Data records

Species

s Y B A O U

Skipjack Yellowfin Bigeye Albacore Other Unknown

Species reliability Blank Good 1 Assigned from School 2 Assigned from Release 3 Assigned from Recovery 4 Not recorded but guessed

Quality 1 Good 2 Badly placed 3 Too slow 4 Tag rejected 5 Tag lost 6 Tag seeded 7 Unknown

Double tag Blank Single tag 1 First tag of double 2 Second or companion

Con 1 2 3 4 5 6 7 8

dition Good Bleeding Tail damage Mouth damage Dropped on deck Hit side of boat Shark bite Unknown

tag of double

Geai GL HL LL OT PH PL PS RN SH ST TR UN

•type Gillnet Handline Longline Other Pole-handline Pole-and-line Purse seine Ringnet Skiff handline Skiff troll Troll Unknown

FL Reliability 1 2 3 4

5

6 7

Good Inaccurate or unclear Guess Average of tagged fish from school Average of untagged fish from school Unknown Calculated from weight

Codes for School Data records

Country/EEZ/Vessel flag blank AS AU CK FJ FM GU HB HW ID II JP JT JV KI KR

Unknown/Unspecified American Samoa Australia Cook Islands Fiji Federated States of Micronesia Guam Howland and Baker Islands Hawaii Indonesia International waters Japan Johnston Atoll Jarvis Island Kiribati Korea

LN MH MI MR MY NC NF NR NU NZ PF PG PH PN PR PU

Line Islands Matthew and Hunter Marshall Islands Northern Marianas Malaysia New Caledonia Norfolk Nauru Niue New Zealand French Polynesia Papua New Guinea Philippines Pitcairn Puerto Rico Palau

PX PY SB SG SU TH TK TO TV TW US

vu WF WK WS

Phoenix Islands Palmyra Solomon Islands Singapore Russia Thailand Tokelau Tonga Tuvalu Taiwan United States of America Vanuatu Wallis and Futuna Wake Island Western Samoa

48

Dete 1 2 3 4 5

ction method Visual surface Birds Trolling Sounder or sonar Via association

School type 1. 2 3 4 5 6

Subsurface Jumper Breezer/Rippler Splasher Boiler Foamer

Association 1 2 3 4 5

6 7 8 9 0 A

Unassociated Log Anchored FAD Drifting FAD Marine mammal or whale shark Tagging vessel Current line Seamount Island or reef Other Coral Sea aggregation

Codes for Tagger Data records

Cradle position BM Bow mattress MS Mid-stern PB Port bow PM Port midships PS Port stern SB Starboard bow SM Stern mattress SR Stern rack SS Starboard stern

Tag type H10 10 cm long C-, S-, Z- and T-prefixed tags H l l 11 cm long X-prefixed tags H13 13 cm long A-, P-, X- and Y-prefixed tags H15 15 cm long K-prefixed tags

Tag prefixes 0 Releases of Kiribati In-Country Tagging Project, 1988 A Releases of Albacore Tagging Project C Strontium chloride-injected fish released during 1992 RTTP releases in Coral Sea E Releases of Kiribati In-Country Tagging Project, 1988 K Releases of Kapingamarangi Tagging Project P Releases of Philippines Tuna Research Project S Releases of Philippines Tuna Research Project (small fish) T Oxytetracycline-injected fish released during RTTP operations X Releases of RTTP Y Releases of RTTP Z Releases of RTTP (small fish)

Additional codes for Recovery Data records

Date credibility 1 2 3 4 5 6 7 8

Day Week Fortnight Month Quarter year Half year Year Unknown

Place code blank C

On catcher vessel In cannery

Weight credibility 1 Whole weight 2 Gilled & gutted weight 3 Guess 4 Calculated from length 5 Unknown

Area credibility 1 2 3 4 5

Minute 30-minute square One-degree square Five-degree square Five-degree by 20-degree square Unknown

49

Appendix III

CHECKLIST OF AT-SEA COMPUTER-RELATED DUTIES

Daily duties

All taggers:

1. Enter release data onto computer after transcribing data to tag release forms. 2. Print out entries using day range in List Releases option of Reports menu, and edit carefully against

original release forms. 3. Edit any releases that are incorrect, and print out the new version. Note on this version that entries are

correct and place in appropriate folder. 4. Backup the release data using Daily Backup diskette with master and slave computers.

Cruise leader:

1. Consolidate all data from the slave computers) to the master computer. 2. Run the Tally option in the Error checks menu on relevant schools, and determine that numbers agree

with hand tallies on release forms. Locate and correct any entry errors on the database. 3. Enter daily position and sightings information from the daily log and school sightings log. 4. Backup the database on the master computer using Consolidated backup diskette. 5. Restore this backup to the slave computer(s). 6. Report details of any tag recoveries to main office by radio. 7. Check hard disks on computers for file problems using Norton Disk Doctor (NDD).

End of cruise

Cruise leader to print out reports relevant to that cruise. These include:

1. Length frequency histograms by species, 2. Releases by tagger, 3. Map of releases, 4. Tally of releases by school, tagger, species and tag type.

Changeover of personnel (including cruise leader)

Cruise leader to prepare, for carrying back to main office, the following:

1. Diskette of consolidated data files of the last group or month of cruises,

2. Diskette of latest backup of data files taken from master.

Staff joining tagging vessel from main office to carry:

1. Diskette of recoveries to date for entry onto master, 2. Updated program diskettes, if changes have been made to database system. Departing cruise leader to:

1. Archive cruises from master computer onto Archive diskettes. This operation is left to the discretion of the cruise leader, and depends on the current size of the database and speed of operation.

2. Carry back to main office top copies of all logs and original tag release forms, along with diskettes of consolidated and backed-up data files.