FISH-USD-CRONT
|[pic] |[pic] |
| | |
| | |
| |European Commission |
| |Directorate-General for Fisheries |
| |
| |
| |
| |
| |
|CATCH REPORTING on the NET |
| |
| |
| |
|USER DOCUMENTATION |
|(FISH-USD-CRONT) |
| |
| |
| |
| |
| |
| |
| |
|Dg Fish Information System Development |
|20/06/2003 |
| |
|Version 0.70 |
| |
|Report Date: 20/06/2003 |
| |
|Project: |FISH |
|Part: |Development – CATCH REPORTING on the NET |
|Title: |USER DOCUMENTATION |
|Date: |20/06/2003 |
|Author: |Samourkasidis/Mills/Diamantopoulos |
|Notes: | |
|Folder: | |
|Distribution: |DG Fisheries, Intrasoft International Sa. |
Purpose of the Document
THIS DOCUMENT DESCRIBES THE USE OF THE CATCH REPORTING ON THE NET DG FISH INFORMATION SYSTEM.
This document is intended to be both an instructional guide (section 2) and a reference manual.
Document History
|VERSION |DATE |COMMENTS |
|0.10 |23-APR-2002 |FIRST DRAFT BY APOSTOLIS SAMOURKASIDIS. |
| | |Submitted to QA for internal review. |
|0.20 |30-Apr-2002 |Submitted to DG FISH for review. |
|0.30 |31-May-2002 |Incorporating DG FISH comments. Re-submitted for review. |
|0.40 |09-Aug-2002 |Incorporating DG FISH comments. Re-submitted for review. |
|0.50 |11-June-2003 |Incorporating DG FISH comments and updates. |
|0.60 |18-June-2003 |Reviewed by Mr. LIAKIS. |
| | |Submitted to QA for internal review. |
|0.70 |20-June-2003 |Incorporating QA comments. |
| | |Submitted to DG FISH for review. |
Distribution List
|COMPANY |NAME |E-MAIL ADDRESS |
|DG FISH |MR. DOM |FRANCOIS.DOM@CEC.EU.INT |
|INTRASOFT |MR. LIAKIS |NIKOS.LIAKIS@INTRASOFT- |
| |MR. PSAHOULIAS |DIONYSSIS.PSAHOULIAS@INTRASOFT- |
Table of Contents
PURPOSE OF THE DOCUMENT 2
Document History 2
Distribution List 2
Table of Contents 3
List of Figures 4
List of Tables 5
1 Introduction 6
1.1 Audience Description 6
1.2 Purpose Statement 6
1.3 Document Usage 6
1.4 Conventions 6
1.4.1 Symbols 6
1.4.2 Other Conventions 7
1.5 Problem Reporting Instructions 7
1.6 Documentation References 7
2 Instructional Guide 8
2.1 Overview 8
2.1.1 Introduction 8
2.1.2 System Purpose 8
2.1.3 System Scope 9
2.1.4 System Overview 10
2.2 Typical Catch-Reporting Concepts 12
2.2.1 Catches 12
2.2.2 Landings 12
2.2.3 Trans-shipments 12
2.2.4 Catch-zone 12
2.2.5 Cumulative Catches/Landings 13
2.2.6 Reporting Periodicity 13
2.2.7 Accumulation Tree/Goals 14
2.2.8 Catch-Reporting Regime (and variations) 14
2.2.9 Landing-Reports 15
2.2.10 Vessel-Reports (not yet implemented) 15
2.2.11 ICCAT- reports (under construction) 15
2.2.12 Data Visibility 15
2.3 Theory of Operation 16
2.3.1 Getting Started 16
2.3.2 The CRONT Home Page 18
2.3.3 The About section 19
2.3.4 The Management of Catch Reporting Data section 20
2.3.5 The Retrieval of Catch Reporting Data section 23
2.3.6 The use of Business Objects 36
2.3.7 Prepared Reports 37
2.3.8 The Management of Catch Report data 39
3 Tutorial 43
3.1.1 The download of all Report data for a particular month 43
3.1.2 Modification/Creation of some Catch Report figures 45
3.1.3 Preparation to Upload the COCR-CATCH-REPORT data 50
3.1.4 Uploading of a Catch Report 52
3.2 The Data Exchange Messages 56
3.2.1 Chart presentation 56
3.2.2 The different Messages 57
List of Figures
FIGURE 2-1: CATCH REPORT ENVIRONMENT 9
Figure 2-2: Login 17
Figure 2-3: CATCH-REPORTING Homepage 18
Figure 2-4:About Catch Reporting 19
Figure 2-5: Management of Catch-Reporting data 21
Figure 2-6: Edit Accumulation Goal 22
Figure 2-7: Retrieval of Catch Reporting Data 23
Figure 2-8: Direct Retrieval of Catch Statistics 25
Figure 2-9: Assisted Retrieval Step by Step 26
Figure 2-10: Assisted Retrieval Continued Step 5 to Step 7 27
Figure 2-11: Catch-Reports 28
Figure 2-12: Year’s Reporting selection screen 29
Figure 2-13: Year’s Reporting, List of the latest reports 29
Figure 2-14: Detail screen of a Report 30
Figure 2-15: List of all Member State’s reports 30
Figure 2-16: Download Landing Report selection screen 31
Figure 2-17: Download Accumulation Goal selection screen 32
Figure 2-18: Download Landing Statistics selection screen 33
Figure 2-19: Statistics screen 34
Figure 2-20: Download A, B reports selection screen 35
Figure 2-21: Prepared Catch Reporting Reports 37
Figure 2-22: Prepared Report 38
Figure 3-1: Download landing report 43
Figure 3-2: Downloaded data 44
Figure 3-3: Report in Notepad 44
Figure 3-4: Save in Notepad 45
Figure 3-5: Import Text File 46
Figure 3-6: Importing Notepad File 46
Figure 3-7: Text Import Wizard – Step 1 of 3 47
Figure 3-8: Text Import Wizard – Step 2 of 3 47
Figure 3-9: Text Import Wizard – Step 3 of 3 48
Figure 3-10: Import data 48
Figure 3-11: Save As in Excel – Text (Tab delimited) 49
Figure 3-12: First Warning Message 49
Figure 3-13: Second Warning Message 49
Figure 3-14: Third Warning Message 50
Figure 3-15: Test COCR Data in Excel 50
Figure 3-16: Opening Excel files in Notepad 51
Figure 3-17: Test File in Notepad 51
Figure 3-18: Replacing tabs with Semicolons 52
Figure 3-19: Link to FIDES2 Home Page 52
Figure 3-20: Re-enter User Name and Password 52
Figure 3-21: FIDES2 Homepage 53
Figure 3-22: Transaction Menu Exploded 53
Figure 3-23: COTQ COCR-LANDING-REPORT 54
Figure 3-24: Uploaded Data 55
List of Tables
TABLE 1-1 DOCUMENTATION REFERENCES 7
Table 2-1 Links with other IS 10
Table 2-2 Responsibilities 11
Table 3-1: COCR_REGIME_PARAMS FIDES message 57
Table 3-2: COCR_REGIME_GOALS FIDES message 59
Table 3-3: COCR_REGIME_REPORTS FIDES message 61
Table 3-4: COCR-AR-LANDING-REPORT FIDES message 62
Table 3-5: CR-RPT-A FIDES message 63
Table 3-6: CR-RPT-B FIDES message 64
Table 3-7: CR-RPT-C FIDES message 65
Table 3-8: CR-RPT-D FIDES message 66
Table 3-9: CR-RPT-E FIDES message 67
Table 3-10: CR-RPT-F FIDES message 69
Table 3-11: COCR-STAT-REGIME FIDES message 71
Introduction
This document describes the way to use the Catch Reporting on the Net (CRONT) Information Systems with specific emphasis on how to manage the data that is to be stored in the Catch Reporting database.
1 Audience Description
Users that normally access the data via a web-browser will not need to read the entire document. They may use the on-line help – About Catch Reporting and Retrieval of Catch Reporting Data, both of which can be found on the CRONT home page (please see the 2.3.1.4 Connect to the FIDES 2/CRONT website section at page 17).
An overall presentation of the major system functions and support information is included in this document from section 2.1.1 to 2.1.4. Users who need to access this information do not need any special technical skills to access and perform actions within the CRONT application.
For other users who are responsible for downloading, uploading, modifying, or inserting Catch Reporting information, a tutorial has been provided. Users that fall into this category need to have some basic knowledge and experience of the FIDES2 application or MS Excel. Otherwise, the tutorial provided will permit both experienced and inexperienced FIDES2 users to familiarise themselves with the preparation of data file.
It must be noted that the manual is intended both for the internal use within DG FISH, and for the external use by personnel of the Member States’ administrations.
2 Purpose Statement
The primary aim of this document is to provide novice users with a reference guide so that they can acquire the necessary skills to be able to manage the CRONT data.
3 Document Usage
The novice CRONT data managers are recommended to read the System Requirements Document (SRD) followed by the tutorial. This will benefit novice users to easily understand the system application.
4 Conventions
Arrows and pointers have been added to some pictures in order for the users to be able to navigate through the CRONT application hyperlink geography, and also to locate the positions of various functions. In other images, the actual test data have been included for the users to compare their input with the one given in the tutorial.
1 Symbols
Some arrows have been added to the screen-copies in order to focus the attention of the reader in certain parts/fields of the screen.
2 Other Conventions
None.
5 Problem Reporting Instructions
In principle, all problems should be reported to the DG Fish Call Dispatch Helpdesk. Users can contact the service by calling +32(2)2953683. Upon connection, the user’s call will be registered and directed to the appropriate person that will be able to provide the required assistance to their problem.
Users can also send e-mails to the FISH Helpdesk (e-mail: fish-helpdesk@cec.eu.int), and, where possible, indicate the problem(s) with a clear description. Under normal circumstances, all users will be contacted within one hour following their telephone call or within one day following their e-mail.
6 Documentation References
This document is based upon the following documents:
|Document |Description |
|CRONT SRD V0.21.doc |CRONT System Requirements Specifications |
|CRONT SDD V1.3.doc |CRONT System Design Document |
| |FIDES2 Format Definitions |
| |FIDES2 DEF Utility – User Manual |
| |The Business Object User Manual |
|IEEE Std 1063-1987 |IEEE Standard for Software User Documentation |
Table 1-1 Documentation References
Instructional Guide
1 Overview
1 Introduction
The Catch Reporting Regime is one of the tools available to the Commission, in particular to the Directorate General of Fisheries – Unit, Licenses and Control (FISH-D/4). It is for the management and limiting of the fishing opportunities in several fishing grounds (stocks), on a national and/or a global level. The limitations applying to the Community fall exclusively within the competence of the Community and arise from obligations set out in Article 8(4) or Regulation (EEC) No 3760/92 of the Council of 20/12/1992. These limitations are set and managed through the use of the TAC-Quota Information System (TQONT).
The Catch Reporting Information System of which the kernel of the system has been built during the 1980-1985 period, distinguished between two major types of catch messages:
• The ones sent by radio/fax by the individual vessels;
• And the ones received from the Member States administrations, the so-called cumulative catch-reports.
Meanwhile, new technologies allow for a more detailed (more voluminous and more frequent) follow-up of catch data and have introduced concepts such as vessel/satellite monitoring. New technologies, coupled with new regulations, also allow the Commission to access data that member States are obliged to collect and store, thereby avoiding the need to have all data transferred and stored locally at DG FISH. Finally, the co-operation with different international organisations on this subject implies the exchange of such data.
2 System Purpose
The new CRONT system offers a framework in order to be able to efficiently carry out the administrative tasks involved with the management of Catches, in comparison with the pre-established TAC and Quota.
The Conservation CATCH-REPORTING Information System (acronym COCR to refer to the complete system, CRONT for the website) has replaced the existing CATCH-REPORTING system as operational from 1981. The new system offers the following benefits:
• Improves and increases the capability of automatic data introduction, with data coming from different administrations;
• It is based on the new COTQ/TQONT system described in the document COTQ SDD V1.0;
• It is able to cope with the different CATCH-REPORTING (sub-regimes), each sub-regime having different parameters where it concerns reporter, report-types, reported stocks and periodicity;
• It is based upon modern web-technology.
3 System Scope
The following schema presents an overview of the CATCH REPORTING environment:
Figure 2-1: Catch Report Environment
The CATCH REPORTING Information System has links with the following DG FISH Information Systems:
|Code Management |This project manages the common codes to all IT applications of the DG FISH, like the Country Codes, |
| |the different Languages, the types of Vessels, of Species, of Fisheries, etc |
| |(It was not shown on the previous figure to avoid complexity) |
|TAC-Quota |This project serves to manage the limitations on the fishing opportunities in several fishing grounds |
| |(stocks) and this on country as well as on global level and its data will be used as basis for the |
| |evaluation of the catch effort. |
Table 2-1 Links with other IS
4 System Overview
The major functions covered by the system are:
1 MANAGEMENT of the REGIMES and CATCH[1]-REPORTS, including:
• Registration of the characteristics of a new reporting regime (scope, frequency, what reports to be included);
• Registration of the accumulation rules (direct or through automatic goal-searching);
• Validation, Registration and Follow-up of the regularly transferred and/or ad-hoc requested catch-report data;
• Accumulation of the data in accordance with the regime rules;
• Sending feedback on accumulated results to the required correspondents (National and International administrations).
Remark: The management of REPORTS can be done independently from the management of REGIMES; at any time new regimes can be added that will use data from reports already introduced in the database.
2 RETRIEVAL of Information, including:
• An explanation about the Catch-Reporting Regime and its working procedures;
• Retrieval of an overview of CATCHES registered at DG FISH, where needed, compared with corresponding TAC and Quota figures for a particular agreement/geographical area, based upon the classification as defined in that TAC and Quota system (stock-groups principle);
• Retrieval and download of data registered at DG FISH: the possibility to retrieve and download CATCH figures based upon selection criteria in a pre-defined format, ready to be downloaded to an office automation software package on PC;
• Predefined Reports: The possibility to retrieve management data on the Catch-Reporting Regime based upon selection criteria (period, country, regulation or agreement, waters). These reports concern especially the catches on stocks, executed by countries, their evolution over years, and compared, if desired, with TAC, EC-Share and quota figures;
• Ad-hoc statistics can always be produced via the download option mentioned above, or via the Business Object software that will be linked to the CATCH-REPORTING and TAC-QUOTA Regime.
3 The responsibilities
The CATCH-Reporting system works with different types of data. The following scheme indicates the data-owners for these types of data. This service is responsible for the introduction of data into the system, and for corrections, if applicable.
|CR Systems |Responsible service |
|Codes (country, species and area codes) |FISH-1 Informatics |
|Regulations |The EURLEX-Reference, OJ-Reference and publication date can be introduced by FISH-D, if |
| |necessary, as part of the introduction of the TAC and Quota data; FISH-1 Informatics will |
| |monitor the process. |
|Accumulation of CATCH-MESSAGES |FISH-D/4 Control and Licenses. |
|Comparison of CATCHES vs. TAC-QUOTA |FISH-D/4 Control and Licenses. |
|Catch Statistics |FISH-D/4 Control and Licenses. |
|Landing Reports |FISH-D/4 Control and Licenses. |
|ICCAT Reports |FISH-D/4 Control and Licenses. |
|Fishing Stops |FISH-A/1 Management of Stocks. |
|Fishing Stops Decisions |FISH-D-4 Control and Licenses. |
Table 2-2 Responsibilities
2 Typical Catch-Reporting Concepts
1 Catches
A quantity of fish in Kg (live weight) caught in a specific catch-zone, by a vessel flying the flag of a country, during a certain period and reported by someone. Discards are normally not declared as catches.
2 Landings
A catch landed in the port of a country.
3 Trans-shipments
A catch transferred from one fishing vessel to another.
4 Catch-zone
Depending upon the instance of who is reporting, the catch-zone can be a basic zone (e.g. simple ICES division or statistical rectangle) or a composed zone as referred to in the TAC/QUOTA Regulation.
As the composed zones are complex in definition and coding (the current system uses an encoding scheme proper to DG FISH), ideally all catch-reports should refer to well-known and internationally defined standard (or basic) zones. FISH-D/4 would prefer that reporting would be done either based on the concept of Statistical Rectangles, or (if the first possibility cannot be met) based on the Fishing Zones as defined by the FAO for Statistical purposes; however, this will require certain regulations and agreements to be adapted.
1 Statistical Rectangle
The concept of the Statistical Rectangle has been described by the Workgroup for the Coordination of Atlantic Fisheries Statistics, also referred to as GTC in the Manuel de Statistiques des Pêches, Rome, 1994. The Codification seems to cover all the seas of the world and is composed of:
• A: 1 digit code specifying the dimension of the quadrangle;
• B: 1 digit code specifying the quadrangle on the earth-globe;
• The latitude (xx xx) and longitude (yyy yy) of the corner of the quadrangle the closest to the point where the equator crosses the Greenwich Meridian;
• Format: A B xx xx yyy yy (SA.B.xxxx.yyyyy).
2 Fishing zones as defined by the FAO for Statistical purposes
The concept of Fishing Zones for Statistical Purpose, has been described by the Workgroup for the Coordination of Atlantic Fisheries Statistics, also referred to as GTC in the Manuel de Statistiques des Pêches, Rome, 1994. At that time 27 main zones were identified:
• 8 major zones covering the 7 continents;
• 19 major zones covering the main seas and their adjacent waters.
Each of these major zones might be subdivided into:
• sub-zones;
• divisions;
• sub-divisions;
• sometimes nk is appended/used to as not known;
• examples: 27.7.9.
5 Cumulative Catches/Landings
The sum of catches/landings made over a period of time; in most cases, according to this terminology, the first day of the period equals the first day of the year.
6 Reporting Periodicity
Most Regulations and Agreements identify a reporting periodicity (e.g. each month) or refer to an event, which requires sending a report (e.g. when entering or leaving a particular zone).
Therefore, the system allows dealing with a reporting period, which can be shortened when necessary (e.g. weekly reports instead of monthly when the summed catch goes above a certain catch-level).
Each catch-report could refer to a period (start and end-date) in which the quantity of fish has been taken. This principle would allow any periodicity (from 1 day to any number of consecutive days). Cumulative catches, as defined above, would then be reported as catches for the period starting first of January until the end of the reporting period; vessel catches would refer to the period in between their last report and the current one.
It has been decided to tend towards a reporting scheme based upon the periodicity - P = D(ay), W(eek), M(onth), Q(uarter), S(emester), Y(ear) - referring with a date (YYYYMMDDP) to the last day of the reported timeframe P.
7 Accumulation Tree/Goals
Catches will be accumulated, following certain rules, in order to have the “total catch” to be compared with a pre-established fishing opportunity (TAC, EC-share, Quota).
This accumulation can be straightforward such that all catches for the same catch-area are simply summed.
However, the reported catch area may differ geographically (and in coding) from the area for which a fishing opportunity has been defined. Two reasons can be identified:
• The reporting area is smaller than (lays within) the latter; e.g. ICES zone IIa is included in ICES zone II;
• The reporting area is a basic zone, but the reporter forgets to mention a condition on that area; e.g. reporting zone ICES zone IIa; the catch to be summed against ICES zone IIa – part of the Community.
In order to deal with both matters, two mechanisms are identified:
• Accumulation Tree: the relation between the areas which will allow a catch made onto a smaller zone to be accumulated onto a bigger one in which the catch zone is included;
• Accumulation Goal: the area levels of accumulation which are of interest to the Catch-Reporting users (in order to check them with the Fishing Opportunities) and which codification differs from the codification used in the TAC-QUOTA Information System.
An important topic to decide upon when accumulating catches concern the risk of accumulating (a part of) a declared catch-quantity twice:
• By using the Accumulation Tree, the user should be careful that the correspondent does not already accumulate the catches and reports on more than one level; if the Accumulation Tree logic is used, reporting should be done on the smallest possible zones’ level only;
• When cumulative catches are reported, accumulation over time is not needed; however, the declaration is considered to be valid for all subsequent time-frames for which no figures have arrived yet;
• For cumulative catches, the starting period should be equal for all accumulation-goals under the regime (in most cases 1 January of the year).
8 Catch-Reporting Regime (and variations)
Regimes are defined by FISH-D/4.
Reports within one regime have a pre-defined structure (which may be different or shared between regimes). Within a regime, regime-variations are possible (e.g. the original Catch-Reporting regime included an A and B report).
The introduction of Catch-Reporting Regimes allows the end-users:
• To compare data from different information sources on equivalent catch areas;
• To be able to restrict the retrieval functions to specific points of interest.
In FIDES2 each regime has its own message types; it could, however, be envisaged in the future to harmonise all message variations into one by adding the regime-indicator into the message.
The word regime is used (and not region) as DG FISH users may decide to create special groups of interest not corresponding to a region (e.g. Highly Migratory Fish or Baltic Sea stocks, etc).
Note: One regime can accept different types of reports (e.g. to compare them), but only one can be the master = used in the calculation of the totals. Stocks can also be mentioned in more than one regime.
9 Landing-Reports
Landing Reports have a pre-defined structure (which may be slightly different or be shared between regimes); variations exist (e.g. the original Catch-Reporting regime included an A and B report, currently C, D, E and F reports have been defined).
Also, Landing Reports concern the declarations of a Member State administration in terms of cumulative catches under its own or another Member States’ flag, landed into one of its ports. The frequency of these declarations is by default on a monthly base; however, the users could increase/decrease the frequency in special cases.
10 Vessel-Reports (not yet implemented)
It concerns the declarations of vessel activity in terms of presence in certain zones (position declarations) and catches (total hold contents and/or catches made from the last declaration). The frequency of these declarations is event based; the reporting zone is based upon the ICES, NAFO or any other subdivision as stipulated in the Regulation and /or agreement.
11 ICCAT- reports (under construction)
In the framework of the co-operation with the International Commission for the Conservation of Atlantic Tunas, all countries involved have been requested to exchange data in the so-called ICCAT format. The data concern:
• Nominal annual catch of tuna and tune-like fish by region (North, South, West or East Atlantic), gear, flag and species, where possible by EEZ and High Seas;
• Catch and Effort statistics by (statistical rectangle) area, gear, flag, species and month;
• Annual size frequencies of samples caught by (statistical rectangle) area (special purpose codes), gear, flag, species and by month;
• Catch-at-size data for bluefin, albacore, yellowfin, bigeye and skipjack tunas and swordfish by gear, sampling area (North, South, West or East Atlantic) and by month or quarters, and for swordfish, by sex and by 5° x 5° rectangles if possible;
• By-catches of sharks by tuna fisheries by quarter.
12 Data Visibility
In some cases, data inserted into the system should not be made immediately visible to all users having access. Data might be classified as data under preparation; to be approved by the responsible service, before both original data and accumulated results become available to other services.
The fact that data needs an approval before being visible is a parameter in the regime-definition. Another (set of) parameter(s) is the one that define the fact that data is to be made available (yes or no) and when (after a certain delay – to allow for evaluation and correction if needed).
3 Theory of Operation
This section describes the normal sequence of operations to be followed, provides examples, and suggests alternatives (where applicable).
1 Getting Started
1 Get your registration and access-permissions
The CRONT system is accessible only to registered users. Two types of registered users exist:
• DG FISH Personnel is by default authorised to access the system. As long as they access the system from inside the Commission’s premises, their normal User-ID and Internet password will be sufficient. Entering through this option gives the possibility to retrieve the public[2] Catch Report data;
• For access from outside the Commission’s premises, users need to be registered under the FIDES2 system. Registration for that system for all users is done via the Registration Authority. The Informatics service that handles this administration can be contacted via the Helpdesk (Tel. 3222953683). Entering through this option gives the permissions, as defined in the FIDES2 System; this option is the one to be used if DG FISH personnel need access rights other than simple retrieval of information.
The following access-permissions exist:
• COCR-CONS: Retrieval of public data (default option applicable for those defined in the categories above);
• COCR-CONS-PREP: Retrieval of all available data, including: data which has not yet officially been published (normally limited to all FISH-D/4 officials);
• COCR-MAN: Management (create, update, delete) Catch Report data (normally limited to certain FISH-D/4 officials);
• COCR-DEV: Development facilities (for FISH Informatics staff).
Remark: DG FISH users have the possibility to access the system through two different channels. Normally, the user-ID is the same in both systems, but the password can be different. If the passwords are the same, that DG FISH user will always access the system as FIDES2 user, with the permissions as defined in the FIDES2 system. If passwords are different, the user has the choice. The small picture in the banner indicates how a user is logged: as FIDES 2 user, [pic] or as DG FISH user. [pic]
2 Check for the correct browser version
The complete system is accessible through a normal Web-browser enforcing 128-bit encryption. Both Internet Explorer (IE 5.5), and Netscape (V5.0 or later) offer that facility. Ensure that the appropriate version has been installed[3]. If users think that they do not have the correct version on their PC, they should ask their local support service (DG FISH users should contact the Helpdesk – tel. 53683; other users must contact their own local Helpdesk).
3 Check for an Internet/Intranet Connection
Users can only access the system if their PC is connected to either the DG FISH Intranet, (the default for all DG FISH users when working on a desktop PC in the DG FISH premises), or World Wide Web. If necessary, users should check their PC connections; if they have access to other WWW-sites they will be OK. If users have any problems with their connection they should ask their local support service. DG FISH users should contact the Helpdesk – tel. 53683; other users must contact their own local Helpdesk.
4 Connect to the FIDES 2/CRONT website
The following addresses (URLs) can be used to access the system:
• [4] (This URL is only for registered FIDES2 users!)
• [5]
• (for internal DG FISH users only)
IMPORTANT: The first address will direct users to the FIDES2 system, giving them access to all FIDES2 facilities for which they are registered. The second address is the direct bookmark to the Catch Report website, and can be used inside the DG FISH building, without being registered as FIDES2 user. Add these addresses to your favourites/bookmarks!
Both FIDES2 websites, accessed with the https URL, will probably issue a security warning indicating that there might be a problem with a not yet accepted certificate from the users side. Users should specify that they want to continue by clicking on the yes button.
When the user decides to activate CATCH-REPORTING application, he/she must enter his /her username and password, as shown below in Figure 2-2.
[pic]
Figure 2-2: Login
2 The CRONT Home Page
Once the user has logged on he/she will be presented with the CATCH-REPORTING home page, as shown below in Figure 2-3. The user will note that on the upper banner, he/she may select the language to operate in. Currently they are either English or French ([pic], [pic])[6].
At the bottom of the upper banner there are 3 “banner-links”: About, Retrieval and Reports. By clicking on them the user can access to these sub-menus sections of the CRONT website.
The Home Page contains the Management of Catch-Reporting data sub-section and the Retrieval of Catch Reporting data sub-section (that can also be access via the Retrieval “banner-link”).
[pic]
Figure 2-3: CATCH-REPORTING Homepage
3 The About section
If the user clicks on the About link, the About Catch Reporting sub menu will be displayed. The user will observe that there are 3 hyperlinks to other sub-menus, which contain various other hyperlinks, as shown below in Figure 2-4.
[pic]
Figure 2-4:About Catch Reporting
4 The Management of Catch Reporting Data section
In the Management of Catch Reporting data, the user can Create or Modify a Regime and its parameters or Modify the Regime’s Accumulation Goals. As shown below in Figure 2-5 these choices are made available from the three hyperlinks within the Management of Catch Reporting data.
Via this section the user can prepare and submit to the FIDES system the messages related to the management of Regimes. Depending on the user selection, the site will display all available records for a regime, and then the user can add, modify or delete the proposed records.
For the Creation of a new Regime, the user has to complete the proposed fields and to provide a non-existing regime code. The only “Operation” permitted on this screen is the “Add” operation. The user can also add to the new regime a certain number of Accumulation Goals, using the table on the bottom of the screen. (Once the Regime is created, the user can also use the Modification of Regime Accumulation Goals in order to add Accumulation Goals).
In order to Modify Regime Parameters, the user can use the “Regime Assistance” button to retrieve an existing regime. By using the assistance, all regime data will be loaded on the screen. Then the user can proceed with the desired modifications, in order to prepare the FIDES message. The permitted “operations” on this screen are the “Modify” and “Delete”.
Once the user is satisfied with the chosen criteria, the user has to click on either the Send or Check button. The Check button will submit the message to the FIDES with the PROBE option, as a testing message. This is useful for the user to test if the proposed message is correct and to consult any optional error messages. The Send button will officially submit the message to the FIDES system, and if there are no errors, the operation will be performed.
Note: All fields marked with a Red asterisk (*) are mandatory, whereas all fields marked with a Blue asterisk require at least one of these fields to be checked, and the rest are then optional.
[pic]
Figure 2-5: Management of Catch-Reporting data
As on each regime one can attach many accumulation goals, in order to facilitate their management, a special screen Modification of Regime Accumulation Goals is implemented. A first screen with some filters is proposed to the user, in order to restrict the proposed list of Accumulation Goals. The user has to provide:
- A valid Regime Code (mandatory),
- The desired year (mandatory),
- A Stock Group code (optional),
- A Species code (optional)
- A Area code (optional)
For all the above fields, there are special “interactive” assistances. The proposed list of records depends on the other choices already made by the user. Thus if the user has enter a year and then clicks on the Species Assistant, only species codes of accumulations on this year are listed. (There is also a limit of a maximum of 10000 records).
Depending on the user section filters, the Edit Accumulation Goal screen is displayed, as shown below in Figure 2-6. At the top of the screen the current selected codes are displayed.
The first table contains some fixed rows, for accumulation goals to be added to the regime. The second table contains all existing goals that fulfil the user’s selection filters. On these goals the user can modify or delete them.
[pic]
Figure 2-6: Edit Accumulation Goal
Note: The Reset button simply resets the open screen to its current default values.
5 The Retrieval of Catch Reporting Data section
Within the Retrieval of Catch Reporting Data, there are two sub-menus, and they are CATCH-STATISTICS and CATCH-REPORTS, as shown below in Figure 2-7. For CATCH-STATISTICS, the user can retrieve the data either by Assisted Retrieval or Direct Retrieval.
[pic]
Figure 2-7: Retrieval of Catch Reporting Data
1 The principles of clicking
The CRONT tries as much as possible to follow normal browser logic to give access to the Catch Report data: underlined items (a user can click on items with an URL behind it) which will provide extra information on the underlined subject; this way of working acts as a menu-driven guided tour to all information. This way of working, and the conventions below will also be applied in other Information Systems at DG FISH.
More precisely, browsing (going from one page of information to the other) can be done:
• In normal pages, by clicking on the appropriate hyperlinks (underlined text - a hand [pic] is shown whenever such a link is passed). These normal links are used to guide the user through the possibilities (acting as a menu) or to give more information on a specific topic (such as detailed data on a specific Report record, the text of the Regulation);
• In selection pages (see hierarchical retrieval or assistance pages further on in this document), by going to the selection box [pic][pic](whenever a selection box is passed, a selection sign will appear [pic]) and clicking on it; this will bring the user to the next selection (in the hierarchical retrieval process) or back to the parameter selection screen (where assistance was requested);
• In screens with different parameters (such as the Direct Retrieval pages), the user has to click on the browse button to get the result of the query; in some cases drop-down lists are used to show the possible parameter values;
• By clicking on special symbols;
• [pic] go back in menu sign: brings the previous page in the retrieval structure (e.g. the list of items from which a user can select);
• [pic] previous sign: gives the same kind of information, but for the item preceding the current one in the list of items to select presented in the previous page;
• [pic] next sign: gives the same kind of information, but for the item following the current one in the list of items to select presented in the previous page;
• [pic] extra information sign: gives alternative information starting from the same selection. For example it allows switching between detailed Report information and Report history. For the same Report-record, it allows switching between public data and data under preparation - for those having this capability;
• [pic]next in query signs are displayed at the top of a table. Under normal conditions, results showed in tabular format are split-up across different pages. The figures displayed at the top of the table show the amount of data retrieved, and give the possibility of browsing other pages of the selected data. There is also an option show all, which allows the user to have their selection on one page (e.g. for printing the complete selection);
• ordering signs: [pic] up and [pic] down are displayed in the header of a table. One column of the resultant table will contain an up or down sign indicating at the same time which data defines the order in which the data are shown, as well as the fact that the ordering is on increased base (up-sign) or decreased base (down-sign). By clicking on the column header the user can change the order (select it and change up or down).
2 Catch Statistics – Direct Retrieval
Experienced users, who already know the codes used in the CRONT system should have a fast way to access the particular data they want. The two options (all reports for one stock or all data for one report) available under the Direct Retrieval option permit the user to specify the codes, and have the result in one click on the browse button.
The user will observe in Figure 2-8 below, that each of the links display the resultant screen as would be seen in normal operations. The assistance buttons (where provided) are made available to help the user select a valid value.
Should the user select Retrieve Accumulated Reports, he/she will be presented with the Catch Reporting Reports. The hyperlink X located under each specific year and for each given country will transport the user to the file he/she wants to view.
[pic]
Figure 2-8: Direct Retrieval of Catch Statistics
3 Catch Statistics – Assisted Retrieval
The Assisted Retrieval option will guide the user through the selection process, and for each step the user will be asked to specify one extra parameter out of a list of possible choices. In Figure 2-9 below, the user will observe that Step 1 begins in the main menu.
To navigate through the application, the user must click on the tick box, located to the left hand side of the chosen parameter. There is an additional option in Step 2, and should the user click the hyperlink of the given record, he/she will be transported to the Regime Details screen.
[pic]
Figure 2-9: Assisted Retrieval Step by Step
From Step 5 at the base of Figure 2-9 above, the user will continue to navigate by clicking on the remaining options, as shown below in Figure 2-10. Once the user has proceeded to Step 6, he/she will have three further options.
Note: If at any time the user has clicked on the All parameter on every occasion between Step 3 and 5 an additional screen will be displayed prior to Step 6. Thus there will be a total of 8 execution procedures instead of the standard maximum of 7.
From Step 6, the user can click on the Display Data in a Graphic button, or he/she may click on the records in the CATCH (T) or COMING FROM fields (Step 7). If the user executes the COMING FROM field he/she will note that they can also click on the Display Data in a Graphic button. However, this function is not available from the CATCH (T) screen.
[pic]
Figure 2-10: Assisted Retrieval Continued Step 5 to Step 7
If the user is in the Catch-Quota By Country (prepared data) screen, the links for the records within the Adapted column are linked to the Catch (T) column. Thus the Warning Level percentage levels within Detailed Quota (Inc. Preliminary Data) Information screen are colour coded as follows:
|Catch Quantity is less than or equal to 80% of the Quota Quantity | | |
| |link colour = |Blue; |
|Catch Quantity is greater than 80%, but less than 100% of the Quota Quantity | | |
| |link colour = |Orange; |
|Catch Quantity is equal to 100% |link colour = |Red. |
4 Catch Reports
For the CATCH-REPORTS sub-menu, the user will observe that all sub-functions are designed so that the criterion for most of the hyperlinks is the same. Even though the number of parameters for each of the hyperlinks is different, Figure 2-11 clearly displays the presentation of all of the sub-menus within CATCH-REPORTS.
[pic]
Figure 2-11: Catch-Reports
1 Year’s Reporting
Via this option the user can access the last report send by each Member State and per period. The user should have the COCR-CONS right (the COCR-CONS-PREP right in case of a DG FISH internal user).
A selection screen will be proposed with all the available choices, as in Figure 2-12 below. The user should choose the Report Type (currently the application supports only Landing Reports) and the desired year.
Then a list of the latest report per country and per report type will be displayed, as in Figure 2-13 below. This list contains:
• The report’s submission date on the FIDES system. (If this date is not available, the report’s reporting date is displayed instead, within parenthesis.
• An indicator on the report’s timeframe type (ex. ‘D’ for daily, ‘M’ for monthly).
• The report’s period.
[pic]
Figure 2-12: Year’s Reporting selection screen
[pic]
Figure 2-13: Year’s Reporting, List of the latest reports
The report’s date is displayed under a special code, regarding the report’s status:
• Green color indicating a ‘submitted’ report by the Member State for approval by a DG FISH user.
• Orange color indicating a ‘submitted’ report with warning errors by the Member State for approval by a DG FISH user.
• Bold black color indicating that the report is accepted by DG FISH but not yet integrated within the statistics.
• Normal black color indicating that the report is accepted and integrated to the statistics database.
The user can click on a date to access the corresponding report. A detailed report screen will be presented, as in Figure 2-14 below. If the user has the COCR-MAN right, and if the report’s status is “submitted” (with or without errors), two more links would be available:
• Accept: By clicking, a accept message is sent to FIDES for the current report,
• Reject: By clicking, a reject message is sent to FIDES for the current report.
Also the user can click on the Member State’s code to access a list with all Member State’s reports, as in Figure 2-15 below.
[pic]
Figure 2-14: Detail screen of a Report
[pic]
Figure 2-15: List of all Member State’s reports
By clicking on a particular month, the detail screen of this report will be presented, as in Figure 2-14 above.
2 Download Landing Report
Via this option the user can retrieve and download an existing report. The user should have the COCR-CONS right (the COCR-CONS-PREP right in case of a DG FISH internal user).
A selection screen will be proposed with all the available choices, as in Figure 2-16.
[pic]
Figure 2-16: Download Landing Report selection screen
By clicking on the Download button, the report will be downloaded to the user’s PC, as an ASCII file.
3 Download Accumulation Goal File
Via this option the user can retrieve and download an existing Accumulation Goal file, in order to consult it, to correct it and to re-submit it again via FIDES. The user should have the COCR-CONS right (the COCR-CONS-PREP right in case of a DG FISH internal user).
A selection screen will be proposed with all the available choices, as in Figure 2-17.
[pic]
Figure 2-17: Download Accumulation Goal selection screen
By clicking on the Retrieval button, the file will be downloaded to the user’s PC, as an Excel file. This Excel file can be later submitted to FIDES, as described on the Tutorial section 3 at page 43.
4 Download Landing Statistics
Via this option the user can retrieve and download statistical data related to the catches of a Member State. The user should have the COCR-CONS right (the COCR-CONS-PREP right in case of a DG FISH internal user).
A selection screen will be proposed with all the available choices, as in Figure 2-18. The user can use the Assistance buttons for help with the codes. The Year, the Landing into Country and the Statistical Period fields are mandatory. The Regime, Species and Area codes are optional.
[pic]
Figure 2-18: Download Landing Statistics selection screen
By clicking on the Browse button, the user can access to the Statistics available for the desired country, as in Figure 2-19 below. The first line displays the filters that were applied, as the Year, the Country code, and the optional Regime, Species and Area codes. Within the table the catches per species and area follows. After the Area column, there are:
• The catches declared by the Country it-self are displayed (from the A Reports);
• The Remaining in board (RB, from the A reports);
• The Trans-boarded quantities (TB, from the A reports);
• The Third-Country landings (TL, from the A reports);
• Per Member State, the quantities declared in behaviour of this country (from the B, C, D etc Reports).
[pic]
Figure 2-19: Statistics screen
The user can download an Excel file with the presented statistics, by clicking on the Download button.
5 Download A, B Reports
Via this option the user can download specific report data. The user should have the COCR-CONS right (the COCR-CONS-PREP right in case of a DG FISH internal user).
A selection screen will be proposed with all the available choices, as in Figure 2-20. The user can use the Assistance buttons for help with the codes. The Year, the Regime and the Catch-Country fields are mandatory.
The user can download an Excel file with the latest report details, by clicking on the Retrieval button.
[pic]
Figure 2-20: Download A, B reports selection screen
6 The use of Business Objects
Business Objects is a tool available under the DG FISH Information System environment that can be used to create or view reports with data taken from the DG FISH databases. Internal DG FISH users can click on the BO-logo [pic] in the footer of the page.
The Business Objects environment is at the moment unavailable to users outside the Commission’s building. However, prepared BO reports refreshed at regular intervals are available to external users via the reports menu, as shown in section 2.3.7.
The Business Objects environment offers various deployment possibilities:
• Users can either be passive viewers (looking at prepared reports – e.g. in PDF-format); active viewers (look at prepared reports, eventually refreshing them to reflect the latest situation, and also requesting the same report with other parameter values); or report developers (making their own reports).
• Viewers do not need much training. Report developers need both, Business Objects training, and training to explain the universe on which they will work. This has to take into account that training aspect, and the price to be paid for the different types of licenses. DG FISH limits the number of Report Developers, but recommends at the same time, two people of the concerned Unit to be trained per major Information Systems in order to satisfy the Unit’s requirements.
• There exists a full client version (the software to be installed on the PC of the user) or web-enabled version (the software accessible via a normal web-browser) – DG FISH promotes the use of the web-enabled version and installs the full client version only in well-motivated cases.
• If a user requires a special report on the Catch Reporting data, he/she should contact the FISH D4 Catch Reporting Project Manager or trained users as mentioned above to discuss his/her requirements. He/she may promptly assist users, or suggest the appropriate training to enable them to create their own reports.
• In the Reports option of the system, users will find prepared reports in PDF format (refreshed regularly and ready to be consulted, downloaded and/or printed). The Other Business Objects facilities are available to registered BO-users by clicking on the BO-logo. Unless users have changed their personal options, they will enter the Business Objects Welcome screen.
• Standard BO reports are available under the Corporate Document Repository. If users are registered as Report Developer they will also find the Create new Document-option amongst the available options. This will provide access to the CATCH-REPORT BO Universe, enabling the user to select the data they want to include in their reports.
Note: Please refer to the Business Objects User manual for more details on how to work in this environment.
7 Prepared Reports
As mentioned above, certain reports are by default refreshed at regular intervals and their output is placed in PDF format, accessible for external users via the Catch Reports section of the website. The main menu of the prepared reports section is presented in Figure 2-21.
[pic]
Figure 2-21: Prepared Catch Reporting Reports
A prepared report is presented in Figure 2-22 below in PDF format. When the user clicks an X from the main menu that corresponds to a country/year combination, he/she gets a prepared report. Acrobat Reader is necessary for viewing PDF files.
[pic]
Figure 2-22: Prepared Report
The prepared reports summarise catches by the following countries/types:
• BEL
• DEU
• DNK
• ESP
• FRA
• GRC
• IRL
• ITA
• NLD
• PRT
• FIN
• SWE
• GBR
• LIST-CTRL-R-G
• LIST-CTRL-R-D
8 The Management of Catch Report data
1 How to prepare the Data
Data should be prepared as a file and submitted to FIDES2 for validation and integration into the database (if the validation was successful).
The user has the possibility to use commonly available tools during the creation of such files. This document will consider only three standard ways of working: the use of MS-EXCEL, or MS-ACCESS in the production of such files; or the use of the FIDES2 Data Entry Facility. Other possibilities can be envisaged (for example, NOTEPAD), as long as the resultant file is compatible with the FIDES2 format and presentation logic. In case of doubt, FISH-1 Informatics can be consulted.
It is recommended to create an archive of the created and submitted files, as shown in section 2.3.8.2 How to archive your data.
1 The use of the FIDES2 Data Entry Facility
The Data Entry Facility (DEF) is a standard tool incorporated into the FIDES2 system, available to all Information Systems for which messages have been defined in FIDES2. The current version (V1.0) allows for messages to be created in accordance with the previously defined syntax. The user does not have to know the exact structure of each message (but needs to know the signification and possible values for each field).
The user has to select the desired message-type; the system will then present a screen, with the appropriate fields that are to be introduced. The records created in this way are stored together as one message in a temporary database, so that they can be used again if necessary. These messages can be downloaded to the local PC in a format and presentation StartTagTerminator-Terminator ready for uploading via FIDES2. Please refer to the FIDES2 Data Entry Facility User-Manual for more information on this tool.
It is a recommendation that the DEF tool should be used for all short messages, (that is messages that do not have too many records). For the Catch Reporting system, the DEF-tool can be of use for changing Regimes, approval or rejecting reports, changing accumulation goals.
2 The use of MS-EXCEL
The standard Office Automation-tool MS-EXCEL can be used equally to create messages.
MS-EXCEL is recommended for larger messages containing repeating data. The use of MS-EXCEL for the preparation of the landing reports is a typical example.
However, in this case, the user is obliged to:
• Respect the format (correct sequence of fields);
• Follow a small procedure, in order to insert the data in the correct format and presentation.
The easiest way to respect the format is to use a previously used MS-EXCEL file as template. This way is recommended for the preparation of the Catch Reporting figures when downloading the data of the previous year. This option exists under the Retrieval menu, in order to adapt the file in accordance with the new requirements. (More information on the different formats can be found in the Catch Reporting System Design Document).
The procedure to be followed is:
a) Save the MS-EXCEL file as tab-delimited text-type (TXT) file (menu - File, option - Save as;
b) Open the resultant file with NOTEPAD, and
c) Replace all tabs with semicolons (menu - extra, option - replace);
d) Add extra semicolons at the end, so that each row has a number of semicolons equal to the number of fields;
e) Save the file after carrying out these changes. The file will now be in a format and presentation (again StartTagTerminator-Terminator), ready for upload via FIDES2.
3 The use of MS-ACCESS
The standard Office Automation tool, MS-ACCESS, can similarly be used to create messages.
MS-ACCESS is recommended for larger messages with data users already managing their personal MS-ACCESS application.
In this case, the user is obliged:
• To respect the format (correct sequence of fields);
• To follow a small procedure, in order to insert the data in the correct format and presentation.
Check the documentation to get acquainted with the correct format specifications. This information can be found in the Catch Reporting System Design Document.
The procedure to be followed is:
a) Create a new query on the data with the selected data compatible with the appropriate format.
b) Introduce an empty column after the last data-filled and ensure that the first column has the following structure: updating-indicator
c) Export the MS-ACCESS query as external file, file-text (*.txt, *.csv, etc) see menu - File, option - Save as/Export. Specify the delimited format, use a semicolon as separator, and set text-qualifier to none.
d) Check the resulting file with NOTEPAD. Save the file after carrying out eventual changes. The file will now be in a format and presentation (again StartTagTerminator-Terminator) ready for upload via FIDES2.
2 How to archive your Data
The FIDES2 system automatically saves archives of files that have been submitted. However, it is recommended that each user maintain an archive of all submitted files, so that eventually, the processing of a complete year can be restarted. After re-initialisation of any year, please contact the Informatics sector, after having corrected some of the files.
It is suggested that the end-user creates a special directory on his PC containing these files. A good idea is that the files are named according to the following convention: e.g. year_seqencenr_subject.txt (e.g. 1999_001_Report.txt; 1999_002_Report_corrections).
3 How to submit the Data
Once a message file is created as described above, and available on the local PC, the message file can be uploaded via the FIDES2 system. Prior to uploading, the user must ensure his/her access rights (in fact, the user must be an authorised DG FISH-D/4 official or be a member of the authorised member State administration for which an upload will be requested).
There are different ways to upload data because FIDES2 supports e-mail, ftp and web-upload facilities; the user is recommended to use the web-upload, which is described below.
• The user goes to the FIDES2 Catch Reporting upload screen, either via the Catch Reporting Home Page (under the Management of Catch Reporting Data menu), or via the FIDES2 Home Page. Select the FIDES2 logo left of the Conservation – Catch Reporting menu item: and a list of available message-types will be received
• The user should select the FIDES2 logo on the left of the message and select what she/he intends to upload. A screen will open, allowing him/her to specify the file, and extra parameters to be used in the upload.
• The user introduces the name, including location (this can be done with the browse option), of the file selected to be uploaded.
• If the file is submitted for the first time: please specify the SYSTEM.PROBE parameter; it is suggested, to enter warning. By doing this, the system will test the file completely, giving the user error- and warning-messages (if any), without any modification to the database. It is also recommended to always use the probe-facility before uploading data; if no probe is given, the message will be accepted and database modifications will be executed if no errors are found. Warnings, however, might be useful to check before submitting the data definitively.
Remark: By executing a test first, users get all errors and warnings at once. If users submit a file to be introduced in the database (not as test), the process will immediately stop at the first error. For example, if the file contains 20 errors, the user will need to submit their file at least 20 times in order to have all errors corrected. Therefore, it is recommended that users should always submit their file in the test mode first!
All other parameters may be left blank, as in most cases the default value is the most appropriate one. Please consult the FIDES2 User Manual for more information on the use of these parameters.
• Click on the submit button to start the upload of the file.
FIDES2 will start processing a user's message. It will usually return the resultant information from the Catch reporting programs, executing behind FIDES2: warnings and errors if any, a summary of the processing (number of declarations, errors, warning, test or transaction succeeded or failed), and a note explaining what to do.
In some cases, users will not receive messages from the Catch Reporting business process, but directly from FIDES2. The most common error messages are given in the annex, together with the action to be taken.
4 The different messages recognised under the COCR Business Process
Database updates (insert, modify, and delete actions) are all issued by sending messages (through FIDES2) to the dedicated COCR Business Process. This Business Process checks users messages for validity, and either issues an error report and does not accept the proposed changes, or produces a processing report with warnings (if any) and accepts the changes.
Member State administrations will be given the necessary option to upload the different reports (CR-RPT-A, CR-RPT-B, CR-RPT-C and others). DG FISH-D/4 users will also have these options available to them, but also extra options allowing them to define new regimes = a collection of stocks for which accumulation is requested, using the existing reports as base for the calculation. The description of all these messages can be found further on in this document.
Under the FIDES2 system, messages need to have a specific structure. For each type of message, a number of fields are defined and have to be submitted in a particular order. Nevertheless, FIDES2 allows different presentations to be used to prepare, and submit these messages. This flexibility permits users to choose its favourite tool, as explained above. Variations in presentations are allowed, where it concerns:
• The use of so-called tags. Pre-defined words between the less than and greater than sign, (for example, = start-tag; = end-tag). Using these tags, with the value of the field between end and start tag, eventually allows the user to specify the field-values, in any desired order. It also allows the user not to specify optional fields;
• The use of fixed record size. Users can specify all fields in the pre-defined order as one long string of characters; spaces need to be inserted, where the field-value does not have the length as previously defined;
• The use of field-separators in variable length records. Users can specify all fields in the pre-defined order, separating the values by a field-separator (for example, semi-colon); again in this case and for most of the time, records will be placed in a text file, that is, one record per line;
• Presence of the FIDES2 header tags. Files can be prepared with or without FIDES2 header-tags, (the appropriate loading procedure has been defined before in this manual).
The flexibility offered by FIDES2 and all Catch-Reporting Messages available to the Member State administrations is further discussed in the FIDES2 – Catch-Reporting Messages manual (name to be verified).
Remark: Both the Data Entry Facility (standard FIDES2 option), and the download option present the data in a format compatible with the requirements. It is recommended to use these tools unless users feel comfortable with the alternative options.
The Reference Part of this manual briefly explains the purpose and major options available in each of the CRONT messages.
Tutorial
The following tutorial is directed towards the management of Catch Reporting, and within this document there are 4 step-by-step exercises. These exercises will also serve as refresher courses as the user begins to use the application on a daily basis.
These exercises are:
• Download of all Report data for the last particular month;
• The preparation of new Catch Reporting figures, based upon the Reports from the last month;
• Upload of the prepared Catch report;
• The modification of one Catch Report.
1 The download of all Report data for a particular month
• Select and click on the desired CATCH-REPORTS to be downloaded.
• When the required menu to be downloaded is displayed, click on download button at the bottom of the screen, as shown below in Figure 3-1.
[pic]
Figure 3-1: Download landing report
This action will invoke a text editor and the data will be displayed as shown in Figure 3-2 below.
[pic]
Figure 3-2: Downloaded data
Users should proceed with the following procedure for downloading data into Notepad:
Step 1
Copy and Paste all the displayed text into Notepad. Notepad can be located from the main PC menu, as shown below in Figure 3-3.
[pic]
Figure 3-3: Report in Notepad
Step 2
Save the data with the following procedure, and as shown in Figure 3-4 below:
a) Select the option Save As;
b) Select drive D;
c) For the option Save as type, choose All files;
d) Enter the File name, and (for this tutorial only) enter the name TestCOCR and Save.
[pic]
Figure 3-4: Save in Notepad
Once the user has saved the data he/she will be in a position to download it. The data can be downloaded in either Excel or Access. For the purposes of this tutorial, the download procedure will be demonstrated in Excel.
2 Modification/Creation of some Catch Report figures
This exercise can only be executed when the user has successfully completed the previous exercise. Users must have a basic knowledge of MS Excel if they have to execute the following exercise on a daily basis.
The user (for this exercise) should open Excel.
• Once Excel is open, click on Data on the toolbar and move the cursor to Get External Data, and finally to Import Text File, as shown below in Figure 3-5.
[pic]
Figure 3-5: Import Text File
• From the Look in drop down command select the directory D;
• In Files of type click on the drop down command and select All Files;
• Click on the file name displayed in the file name directory window;
• Finally, click on Import. This procedure is shown below in Figure 3-6.
[pic]
Figure 3-6: Importing Notepad File
When the above steps have been executed, the Text Import Wizard - Step 1 of 3 will appear on screen, as shown below in Figure 3-7. The user should then:
• Click on the Next > button. Step 1 of 3 is set to default.
[pic]
Figure 3-7: Text Import Wizard – Step 1 of 3
• In Step 2 of 3 (see Figure 3-8), the user must click on the Semicolon tick box in the Delimiters sub-menu, and deselect the Tab tick box. The user should then click on the Next > button so as to proceed to Step 3 of 3.
[pic]
Figure 3-8: Text Import Wizard – Step 2 of 3
• In Step 3 of 3 (see Figure 3-9), click on the Text selection in the Column data format sub-section. Click on the 3rd column within the Data Preview sub-menu, and finally, click on the Finish button.
[pic]
Figure 3-9: Text Import Wizard – Step 3 of 3
In Figure 3-10, the user is provided with the option of where to place the data in the Excel application.
[pic]
Figure 3-10: Import data
The data retrieved from Notepad will now have been converted to the Excel format. The user should save the file to disk with the same name and directory as it was for Notepad. The user must save this file as Text (Tab delimited), as shown below in Figure 3-11.
[pic]
Figure 3-11: Save As in Excel – Text (Tab delimited)
The user will then be prompted by a warning message (Figure 3-12), and he should click on the OK button. A second warning message will be displayed (Figure 3-13) and the user should click on the Yes button. The user may be prompted with a third warning message informing him/her that the file already exists, and whether or not he/she wants to replace it. The user must click on the Yes button (see Figure 3-14 below).
[pic]
Figure 3-12: First Warning Message
[pic]
Figure 3-13: Second Warning Message
[pic]
Figure 3-14: Third Warning Message
Once the file has been saved, the user will be able to make any changes deemed necessary. Each time the user saves the updated information in Excel, they will be prompted by the above warnings for which they would click on the Yes or OK as appropriate.
[pic]
Figure 3-15: Test COCR Data in Excel
3 Preparation to Upload the COCR-CATCH-REPORT data
When users choose to upload the data from ‘Excel’, they should load them using the ‘Notepad’ utility, and proceed as follows:
• Open the file from the directory D;
• Select All Files;
• Click on the desired file name, and for this example the file name is TestCOCR, as shown in Figure 3-16 below.
[pic]
Figure 3-16: Opening Excel files in Notepad
The file will now be displayed, as shown in Figure 3-17 below. However, the user must make certain changes to it, in order to upload it via FIDES2. The first change that the user must initiate is to replace the Tabs with semicolons (;), with the Search and Replace function, as shown in Figure 3-17 below.
[pic]
Figure 3-17: Test File in Notepad
In the Replace pop up screen click on the Replace with window, and insert a semicolon (;), as shown below in Figure 3-18. Position the mouse in any Tab space and drag it one space so that it is highlighted in blue and select the Replace All button. Once all the tabs have been replaced, save the file to disk.
[pic]
Figure 3-18: Replacing tabs with Semicolons
4 Uploading of a Catch Report
The user must now return to the FIDES2 home page by clicking on the FIDES2 link on the bottom banner at the right hand side of the Catch Reporting main menu interface, as shown below in Figure 3-19.
[pic]
Figure 3-19: Link to FIDES2 Home Page
A pop-up window will prompt the user, whereupon he/she should re-enter his/her username and password, as shown below in Figure 3-20.
[pic]
Figure 3-20: Re-enter User Name and Password
Once this has been completed, the user will need to click on the Transaction for the Conservation – Catch Reporting, as shown below in Figure 3-21.
[pic]
Figure 3-21: FIDES2 Homepage
The Transaction menu will appear (Figure 3-22), and the user must click on the desired Transaction. The user will note that there are 4 types of Reports, all of which have common parameters.
[pic]
Figure 3-22: Transaction Menu Exploded
The user must specify the file name that he/she intends to upload; for this example the file name is: D:\DATA\TestCOTQ.txt. Next, the user should go to the bottom field entitled SYSTEM.PROBE, as shown below in Figure 3-23, and enter the word WARNING. Hence, a list of all errors and warnings (if any) will be displayed, and no data/changes will be recorded in the database.
At a 2nd phase, only when the user is sure there are no errors, he/she may proceed with this process without entering WARNING in the SYSTEM.PROBE parameter. Hence, the data will be recorded in the database.
[pic]
Figure 3-23: COTQ COCR-LANDING-REPORT
After the user has entered both the file name and the System.Probe parameter, the next step is to click on the Submit button, and the upload process will begin. The data-file will be treated by FIDES2, and the screen will reflect the results as shown below in Figure 3-24.
[pic]
Figure 3-24: Uploaded Data
2 The Data Exchange Messages
1 Chart presentation
Data exchange messages are represented by tables such as the ones below:
|Rec ID |Field ID (tag name) |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
| |(1) |(2) |(3) | | | | |
(FIDES1-type messages)
Or
|TAG |Type |Length |Mandatory |Value |
| | | |INS |MOD |SUP | |
|(1) |(2) |(3) |(4) |(5) |(6) |(7) |
(For pure FIDES2-type messages)
Where:
1) The tag name;
1) The type of the tag value: A for alphanumerical and N for numerical;
2) The maximum length of the tag value. Values must have this exact length when they are stored in Fixed Record Length files;
3) Indicates if the value is mandatory when inserting a new record. If there is a default value, it is represented in parenthesis (tags with a default value are intrinsically mandatory). The word Key means that the tag value is used to identify the entry to insert. If it is followed by an asterisk *, it means that an empty value is significant;
4) Indicates if the value is mandatory when modifying an entry. There are never default values in this case. The word Key means that the tag value is used to identify the entry to modify. If it is followed by an asterisk *, it means that an empty value is significant;
5) Indicates if the value is mandatory when removing an entry. There are never default values in this case. The word Key means that the tag value is used to identify the entry to remove. If it is followed by an asterisk *, it means that an empty value is significant;
6) Indicates the values that are allowed for this tag. It might be a list of possible values or a general type (represented in italics).
Remark: The definitions below only concern the BODY of the corresponding FIDES2 messages.
2 The different Messages
1 COCR_REGIME: Management of the Regime
Consists of three types of records:
• COCR_REGIME_PARAMS: identifying the regime’s parameters;
• COCR_REGIME_GOALS: adding and removing specific accumulation-goals;
• COCR_REGIME_REPORTS: defining the reports that will be taken into account under that regime.
1 COCR_REGIME_PARAMS: Management of the Regime (parameters)
Purpose:
The Management of the Regimes and their parameters are necessary, in order to be able to direct the accumulation procedures in producing statistics.
Format:
|TAG |Type |Length |Mandatory |Value |
| | | |INS |MOD |SUP | |
|UPD_IND |A |3 |(DAT) |(DAT) | |INS, MOD, SUP, DEL DAT |
|REGIME_CODE |A |8 |Key |Key |Key | |
|YEAR_FROM |N |4 |Yes | | |Valid yearId |
|YEAR_TO |N |4 |Yes | | |Valid yearId or 9999 |
|TIME_FRAMES |A |3 |(NNY) | | |Substring with a sequence of Y/N |
| | | | | | |values corresponding to the DWM |
|PUBL_TIME_FRAMES |A |3 |(NNY) | | |Substring with a sequence of Y/N |
| | | | | | |values corresponding to the DWM |
|MASTER_REP |A |1 |Yes | | |L(LANDREPS), |
| | | | | | |V(VESLREPS), |
| | | | | | |I(ICATREPS), |
| | | | | | |T(TESTREPS), |
| | | | | | |C(LICREPS) |
|PUBL_DELAY |N |3 |(999) | | |In days |
|PUBL_LANDREP |A |1 |(N) | | |N (no), Y (yes) |
|PUBL_VESLREP |A |1 |(N) | | |N (no), Y (yes) |
|PUBL_ICATREP |A |1 |(N) | | |N (no), Y (yes) |
|PUBL_LICREP |A |1 |(N) | | |N (no), Y (yes) |
|STOCK_GROUP_ID |A |6 |No | | |Stock_group_id |
Table 3-1: COCR_REGIME_PARAMS FIDES message
Validation Rules (B = Blocking; W = Warning):
UPD_IND = INS
1) (B) REGIME_CODE: should be present and not yet used;
7) (B) YEAR_FROM: should be present and >=1980;
8) (B) YEAR_TO: should be present and >= YEAR_FROM; it should be a valid year or receive the value 9999 for undefined;
9) (B) TIME_FRAMES: should be present and a be string containing only Y and N characters;
10) (B) PUBL_TIME_FRAMES: should be present and be a string containing only Y and N characters;
11) (B) MASTER_REP; should be present and valid;
12) (B) PUBL_DELAY: defines the publication delay for this regime in number of days to be counted from today’s date. It should be empty between 0 = all data public, and 366 = latest public data are one year old, or 999 = will never be public;
13) (B) PUBL_LANDREP: should be empty, Y or N;
14) (B) PUBL_VESLREP: should be empty, Y or N;
15) (B) PUBL_ICATREP: should be empty, Y or N;
16) (B) PUBL_LICREP: should be empty, Y or N;
17) (B) should be empty or refer to an already existing stock_group_id.
UPD_IND = MOD
1) (B) REGIME_CODE: should be present and already registered;
18) (B) YEAR_FROM: should be >=1980;
19) (B) YEAR_TO: should be >= YEAR_FROM (db value if YEAR_FROM is empty) or equal to 9999 for undefined;
20) (B) TIME_FRAMES: should be a string containing only Y and N characters;
21) (B) PUBL_TIME_FRAMES: should be a string containing only Y and N characters;
22) (B) MASTER_REP; should be valid;
23) (B) PUBL_DELAY: defines the publication delay for this regime in number of days to be counted from today’s date. It should be empty, between 0 = all data public, and 366 = latest public data are one year old, or 999 = will never be public);
24) (B) PUBL_LANDREP: should be Y or N;
25) (B) PUBL_VESLREP: should be Y or N;
26) (B) PUBL_ICATREP: should be Y or N;
27) (B) PUBL_LICREP: should be Y or N;
28) (B) Should refer to an already existing stock_group_id.
Remark: null-value = spaces in a MOD message for non-mandatory fields indicates the unchanged value; as such, a field cannot be forced to be null through a MOD message! Please use a combination of SUP and INS to make such a change.
UPD_IND = SUP or DEL
1) (B) REGIME_CODE: should be present and already registered.
2 COCR_REGIME_GOALS: Management of the accumulation-goals
Purpose:
Management of the accumulation goals and their parameters are also necessary, in order to be able to direct the accumulation procedures in producing statistics.
Format:
|TAG |Type |Length |Mandatory |Value |
| | | |INS |SUP |EXT |MOD |DWI | |
|UPD_IND |A |3 | | | | | |INS, DEL, SUP, EXT, |
| | | | | | | | |DWI, MOD, DAT |
|REGIME_CODE |A |8 |Key |Key |Key |Key |Key |Regime_code |
|YEAR_ID |N |4 |Key |Key |Key |Key |Key | |
|SPECIES_ID |A |3 |Key |Key |Key |Key |Key |Species_id |
|AREA_ID |A |6 |Key |Key |Key |Key |Key |Area_id |
|SUB_AREA_ID |A |3 |Key (*) |Key (*) |Key (*) |Key (*) |Key (*) | |
|CATCH_COUNTRY_ID |A |3 |--- |--- |Key |Key or |Key |Country_id |
| | | | | | |--- | | |
|PUBLIC |A |1 |(N) | |(N) | | |N (no), Y (yes) |
|QUOTA_SPECIES |A |3 |Yes | |No | | |Species_id |
|QUOTA_AREA |A |6 |Yes | |No | | |Area_id |
Table 3-2: COCR_REGIME_GOALS FIDES message
Validation Rules (B = Blocking; W = Warning, N = Notification):
UPD_IND = INS
1) (B) REGIME_CODE: should be present and already registered;
29) (B) YEAR_ID: should be present and within the range specified for the regime; It should also be smaller or equal to the year of today;
30) (B) SPECIES_ID: should be present and a valid species code;
31) (B) AREA_ID: should be present and a valid area code;
32) (B) SUB_AREA_ID: should be empty or a valid country code;
33) (N) CATCH_COUNTRY_ID: is ignored;
34) (B) PUBLIC: should be valid and consistent with the regime publication parameters;
35) (B) The combination (YEAR_ID, QUOTA_SPECIES, QUOTA_AREA) should be present and refer to a stock defined in the TQ.STOCK-PARAMS table;
36) (B) The combination (REGIME_CODE, YEAR_ID, SPECIES_ID, AREA_ID, SUB_AREA_ID) does not exists in ACCUMULATION_GOALS.
UPD_IND = SUP or DEL
1) (B) REGIME_CODE: should be present and already registered;
37) (B) YEAR_ID: should be present and within the range specified for the regime;
38) (B) SPECIES_ID: should be present and a valid species code;
39) (B) AREA_ID: should be present and a valid area code;
40) (B) SUB_AREA_ID: should be empty, or a valid country code;
41) (N) CATCH_COUNTRY_ID: is ignored;
42) (B) The combination (REGIME_CODE, YEAR_ID, SPECIES_ID, AREA_ID, SUB_AREA_ID) exists in ACCUMULATION_GOALS.
UPD_IND = EXT
1) (B) REGIME_CODE: should be present and already registered;
43) (B) YEAR_ID: should be present and within the range specified for the regime;
44) (B) SPECIES_ID: should be present and a valid species code;
45) (B) AREA_ID: should be present and a valid area code;
46) (B) SUB_AREA_ID: should be empty or a valid country code;
47) (B) CATCH_COUNTRY_ID: should be present and a valid country code different from AMS;
48) (B) The COUNTRY_ID should not already be referred to in the ACCUMULATION_GOALS tables for that year (and stock if applicable) = error when trying to create already existing records;
49) (B) PUBLIC: should be valid and consistent with the regime publication parameters;
50) (B) The combination (YEAR_ID, QUOTA_SPECIES, QUOTA_AREA, COUNTRY) should be empty, or refer to a quota defined in the TQ.QUOTAS table.
UPD_IND = DWI
1) (B) REGIME_CODE: should be present and already registered;
51) (B) YEAR_ID: should be present and within the range specified for the regime;
52) (B) SPECIES_ID: should be present and a valid species code;
53) (B) AREA_ID: should be present and a valid area code;
54) (B) SUB_AREA_ID: should be empty or a valid country code;
55) (B) CATCH-COUNTRY_ID: should be present and a valid country code different from AMS;
56) (B) The COUNTRY_ID should already be referred to in the ACCUMULATION_GOALS tables for that year (and stock if applicable), = error when the suppression does not lead to suppressions.
3 COCR_REGIME_REPORTS: Management of the Reports valid for a regime
Purpose:
Management of the regimes and reports.
Format:
|TAG |Type |Length |Mandatory |Value |
| | | |INS |SUP | |
|UPD_IND |A |3 |Yes |Yes |INS, DEL, SUP |
|REGIME_CODE |A |8 |Key |Key |Regime_code |
|REPORT_TYPE |A |32 |Key |Key |Report_type |
Table 3-3: COCR_REGIME_REPORTS FIDES message
Validation Rules (B = Blocking; W = Warning):
1) (B) UPD_IND: should be present and valid;
57) (B) REGIME_CODE: should be present and a valid regime code;
58) (B) REPORT_TYPE: should be present and a valid report-type known to the system.
UPD_IND = INS
1) (B) The combination (REGIME_CODE, REPORT_TYPE) must not exist in REPORT_VS_REGIMES.
UPD_IND = SUP or DEL
1) (B) The combination (REGIME_CODE, REPORT_TYPE) should exist in REGIME_VS_REPORTS.
2 COCR-AR-LANDING-REPORT: Accepting/Rejecting a specific report
Purpose:
To be used by DG FISH-D/4 Officials to accept (or reject) the uploaded reports.
Format:
|TAG |Type |Length |Mandatory |Value |
| | | |ACC |REJ | |
|UPD_IND |A |3 |Yes |Yes | |
|REPORTER_ID |A |3 |Key |Key |Country_id |
|REPORT_TYPE |A |32 |Key |Key |CR-RPT-A |
| | | | | |CR-RPT-B |
| | | | | |CR-RPT-C |
| | | | | |CR-RPT-D |
| | | | | |CR-RPT-E |
| | | | | |CR-RPT-F |
| | | | | |COCR_LANDING_REPORT |
|REPORT_DATE |D |8 |Key |Key |Yyyymmdd |
| | | | | |date of last day of period OR |
|TIME_FRAME |A |1 |Key (M) |Key (M) |D,W,M,Q,S,Y |
|TIME_FRAME_ID |N |3 | | |1-366 or empty |
Table 3-4: COCR-AR-LANDING-REPORT FIDES message
Validation Rules (B = Blocking; W = Warning):
1) (B) UPD_IND: should be present and valid;
59) (B) REPORTER_ID: should be present and a valid 3-alpha ISO country code;
60) (B) REPORT_TYPE: should be present and a valid report-type as defined above;
61) (B) REPORT_DATE: should be present and a valid-date;
62) (B) TIME_FRAME: should be valid;
63) (B) If TIME_FRAME_ID is empty, the TIME_FRAME_ID is calculated from the REPORT_DATE and taking into account the TIME_FRAME; an error message is given. If the date does not correspond to the last date of the calculated time_frame (e.g. 20001230/Monthly declaration would calculate M012), but would give an error message as the 30th December, it is not the last day of the 12th month. If TIME_FRAME_ID is specified, the same calculation is made in order to verify if the date corresponds with that TIME_FRAME_ID. If not, an error message is given;
64) (B) The report (REPORTER_ID, REPORT_TYPE, REPORT_DATE, TIME_FRAME) should exist;
65) (B) A report should exist in the status Submitted, Warning (in the case of a complete message), or a report should have at least one record in status Submitted, Warning (in the case of an incomplete message).
3 CR-RPT-A
The CR-RPT-A message contains cumulative and provisional information concerning catches of the reporting country's vessels for stocks under quota corresponding to the reporting period.
|Transaction name: |CR-RPT-A | | | |
|Input Format: |CR-RPT-A-F1 | | | |
|Rec ID |Field ID (tag name) |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 Code; |FROM FIDES HEADER |L |
| | | | | |reporting MS | | |
|RPM |YEAR_MONTH |DATE |6 |YyyyMM |[01/01/1990, |MANDATORY |R |
| | | | | |01/01/2100] | | |
|DAT |SPECIES_CODE |STRING |3 | |FAO code |MANDATORY |L |
| |AREA_CODE |STRING |6 | |FISH code |MANDATORY |R |
| |PROV_CUMUL |STRING |1 | |P/C |MANDATORY |R |
| |QTY_COUNTRY |REAL |10 | | |0 |R |
| |QTY_THIRDC |REAL |10 | | |0 |R |
| |QTY_TRANSP |REAL |10 | | |0 |R |
| |QTY_OTHER |REAL |10 | | |0 |R |
| |QTY_TOTAL |REAL |10 | | |MANDATORY |R |
Table 3-5: CR-RPT-A FIDES message
Comments on particular fields:
|QTY_* |All quantities are given in metric tonnes with decimal precision. |
| |Last field (QTY_TOTAL) is the sum of the previous 4 fields. |
Validation Rules (B = Blocking; W = Warning):
1) (B) COUNTRY_A3: should be present and should be a valid country code;
66) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB;
67) (B) YEAR_MONTH: should be present and should be a valid year-month;
68) (B) SPECIES_CODE: should be present and should be a valid species code;
69) (B) AREA_CODE: should be present and should be a valid area code;
70) (B) PROV_CUMUL: should be present and equal to C or P;
71) (W) PROV_CUMUL: P value will not be treated any more;
72) (B) QTY_*: should be null or greater or equal to 0;
73) (W) QTY_TOTAL: should be the sum of QTY_COUNTRY, QTY_THIRDC, QTY_TRANSP, QTY_OTHER;
74) (W) If identical reports have been received previously for the same YEAR_MONTH;
75) (W) If stock DG Fish area combination is not defined in the accumulation goals in case of a report type for which the hierarchical accumulation is not applicable;
76) (W) If quantity of previous declaration is greater than the current declaration if it concerns a Cumulative report type;
77) (N) The qty precision is decimal.
4 CR-RPT-B
The CR-RPT-B message contains cumulative and provisional information concerning catches of other Member States' vessels for stocks under quota landed directly in the reporting Member State.
|Transaction name: |CR-RPT-B | | | |
|Input Format: |CR-RPT-B-F1 | | | |
|Rec ID |Field ID (tag name)* |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 code; |FROM FIDES |R |
| | | | | |reporting MS | | |
|RPM |YEAR_MONTH |DATE |7 |YyyyMM |[01/01/1990,01/01/21|MANDATORY |R |
| | | | | |00] | | |
|NOTE |NOTE |STRING |28 | | | |L |
|DAT |SPECIES_CODE |STRING |4 | |FAO code |MANDATORY |R |
| |AREA_CODE |STRING |6 | |FISH Code |MANDATORY |L |
| |PROV_CUMUL |STRING |1 | | |MANDATORY |R |
| |CATCH_COUNTRY_CODE |STRING |3 | | | xxx |R |
| |QTY_TOTAL |REAL |10 | |Metric tonnes |MANDATORY |R |
Table 3-6: CR-RPT-B FIDES message
Validation Rules (B = Blocking; W = Warning):
1) (B) COUNTRY_A3: should be present and should be a valid country code.
78) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB;
79) (B) YEAR_MONTH: should be present and should be a valid year-month;
80) (B) SPECIES_CODE: should be present and should be a valid species code;
81) (B) AREA_CODE: should be present and should be a valid area code;
82) (B) PROV_CUMUL: should be present and equal to C or P;
83) (W) PROV_CUMUL: P value will not be treated any more;
84) (B) CATCH_COUNTRY_ID: should be present and should be a valid country code and must be different to COUNTRY_A3.
85) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB.
86) (B) QTY_TOTAL: should be present, and should be a valid quantity;
87) (W) If identical reports have been received previously for the same YEAR_MONTH;
88) (W) If stock DG Fish area combination is not defined in the accumulation goals in case of a report type for which the hierarchical accumulation is not applicable. If area type is FAO or Statistical Rectangle, first convert area to DG Fish area;
89) (W) If quantity of previous declaration is greater than the current declaration when concerning a Cumulative report type;
90) (N) The quantity precision is decimal.
5 CR-RPT-C
The CR-RPT-C message contains cumulative and provisional information concerning catches of the reporting country's vessels for stocks not under quota corresponding to the reporting period.
|Transaction name: |CR-RPT-C | | | |
|Input Format: |CR-RPT-C-F1 | | | |
|Rec ID |Field ID (tag name) |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 Code; |FROM FIDES HEADER |L |
| | | | | |reporting MS | | |
|RPM |YEAR_MONTH |DATE |6 |YyyyMM |[01/01/1990, |MANDATORY |R |
| | | | | |01/01/2100] | | |
|DAT |SPECIES_CODE |STRING |3 | |FAO code |MANDATORY |L |
| |AREA_CODE |STRING |6 | |FAO code |MANDATORY |R |
| |PROV_CUMUL |STRING |1 | |P/C |MANDATORY |R |
| |QTY_COUNTRY |REAL |10 | | |0 |R |
| |QTY_THIRDC |REAL |10 | | |0 |R |
| |QTY_TRANSP |REAL |10 | | |0 |R |
| |QTY_OTHER |REAL |10 | | |0 |R |
| |QTY_TOTAL |REAL |10 | | |MANDATORY |R |
Table 3-7: CR-RPT-C FIDES message
Comments on particular fields:
|QTY_* |All quantities are given in metric tonnes with decimal precision. Last field|
| |is sum of previous 4. |
Validation Rules (B = Blocking; W = Warning, N = Notification):
1) (B) COUNTRY_A3: should be present and should be a valid country code.
91) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB;
92) (B) YEAR_MONTH: should be present and should be a valid year-month;
93) (B) SPECIES_CODE: should be present and should be a valid species code;
94) (B) AREA_CODE: should be present and should be a valid area code;
95) (B) PROV_CUMUL: should be present and equal to C or P;
96) (W) PROV_CUMUL: P value will not be treated any more;
97) (B) QTY_*: should be null, or greater or equal to 0;
98) (W) QTY_TOTAL: should be the sum of QTY_COUNTRY, QTY_THIRDC, QTY_TRANSP, QTY_OTHER;
99) (W) If identical reports have been received previously for the same YEAR_MONTH;
100) (W) If stock DG Fish area combination is not defined in the accumulation goals in case of a report type for which the hierarchical accumulation is not applicable;
101) (W) If quantity of previous declaration is greater than the current declaration if it concerns a Cumulative report type;
102) (N) The quantity precision is decimal.
6 CR-RPT-D
The CR-RPT-D message contains cumulative and provisional information concerning catches of other Member States' vessels for stocks not under quota landed directly in the reporting Member State.
|Transaction name: |CR-RPT-D | | | |
|Input Format: |CR-RPT-D-F1 | | | |
|Rec ID |Field ID (tag name)* |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 code; |FROM FIDES |R |
| | | | | |reporting MS | | |
|RPM |YEAR_MONTH |DATE |7 |YyyyMM |[01/01/1990,01/0|MANDATORY |R |
| | | | | |1/2100] | | |
|NOTE |NOTE |STRING |28 | | | |L |
|DAT |SPECIES_CODE |STRING |4 | |FAO code |MANDATORY |R |
| |AREA_CODE |STRING |6 | |FAO Code |MANDATORY |L |
| |PROV_CUMUL |STRING |1 | | |MANDATORY |R |
| |CATCH_COUNTRY_CODE |STRING |3 | | | xxx |R |
| |QTY_TOTAL |REAL |10 | |Metric tonnes |MANDATORY |R |
Table 3-8: CR-RPT-D FIDES message
Validation Rules (B = Blocking; W = Warning, N = Notification):
1) (B) COUNTRY_A3: should be present and should be a valid country code.
103) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB;
104) (B) YEAR_MONTH: should be present and should be a valid year-month;
105) (B) SPECIES_CODE: should be present and should be a valid species code;
106) (B) AREA_CODE: should be present and should be a valid area code;
107) (B) PROV_CUMUL: should be present and equal to C or P;
108) (W) PROV_CUMUL: P value will not be treated any more;
109) (B) CATCH_COUNTRY_ID: should be present and should be a valid country code and must be different to COUNTRY_A3.
110) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB.
111) (B) QTY_TOTAL: should be present and should be a valid quantity;
112) (W) If identical reports have been received previously for the same YEAR_MONTH;
113) (W) If stock DG Fish area combination is not defined in the accumulation goals in case of a report type for which the hierarchical accumulation is not applicable. If area type is FAO or Statistical Rectangle, first convert area to DG Fish area;
114) (W) If quantity of previous declaration is greater than the current declaration if it concerns a Cumulative report type;
115) (N) The quantity precision is decimal.
7 CR-RPT-E
The CR-RPT-E message contains cumulative and provisional information. This is a quarterly report of catches that is not subject to TACs and Quotas taken by Community fishing vessels in waters subject to the sovereignty or jurisdiction of third countries and on the high seas and landed and/or transhipped or kept on board, other than catches landed in the territory of another Member State.
|Transaction name: |CR-RPT-E | | | |
|Input Format: |CR-RPT-E | | | |
|Rec ID |Field ID (tag name)* |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|TTL |REPORT_TYPE |STRING |8 | | |CR-RPT-E |L |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 code; | |L |
| | | | | |reporting MS | | |
|RPM |PERIOD |DATE |9 |YYYYMMDDP |[01/01/1990, |The value of |L |
| | | | | |01/01/2100] |position P is, by | |
| | | | | | |default, ‘Q’ | |
|NOTE |NOTE |STRING |32 | |Free format | |L |
|DAT |SPECIES_CODE |STRING |3 | |FAO species code or | |L |
| | | | | |mixed species or | | |
| | | | | |other code referred | | |
| |AREA_CODE |STRING |2+7 | |FAO code for area or| |L |
| | | | | |sub-divisions | | |
| |SUB_AREA_ID |STRING |3 | |ISO-3 code;, *HS, | |L |
| |CATCH_COUNTRY_ID |STRING |3 | |ISO-3 code; | |L |
| |LANDED_INTO_ID |STRING |3 | |ISO-3 code;, *TB, | |L |
| | | | | |*RB | | |
| |QTY_TOTAL |REAL |10 | | | |R |
Table 3-9: CR-RPT-E FIDES message
Validation Rules (B = Blocking; W = Warning, N = Notification):
1) (W) Same reports have been received previously ( display message;
116) (W) This is the first time that a country sends such a report for that periodicity, for that year ( display message;
117) (W) The Stock/Area/Catch country combination is not defined in the accumulation goals (in case of a report type for which the hierarchical accumulation is not applicable) ( display message;
118) (W) Quantity Qty of the previous declaration is less than the current declaration (cumulative report type) ( display message;
119) (B) COUNTRY_A3: should be present and should be a valid country code.
120) Unauthorised Country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB.
121) (B) PERIOD: should be present and a valid period. The date and the periodicity must be valid. The date must be the last of the period;
122) (B) SPECIES_ID: should be present and should be a valid species code;
123) (B) SUB_AREA_ID: should be null or a valid country code;
124) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *RB;
125) (B) AREA_CODE: should be present and should be a valid FAO area code;
126) (B) CATCH_COUNTRY_ID should be present and should be a valid country code.
127) Must be equal to COUNTRY_A3.
128) (B) LANDED_INTO_ID should be present and should be a valid country code.
129) Unauthorised country codes: EEC, AMS, TAC, *HS.
8 CR-RPT-F
The CR-RPT-F message contains cumulative and provisional information. This is a quarterly report of catches that is not subject to TACs and Quotas taken by Community fishing vessels of other Member States in waters subject to the sovereignty or jurisdiction of third countries and on the high seas and landed in the territory of the reporting Member State.
|Transaction name: |CR-RPT-F | | | |
|Input Format: |CR-RPT-F | | | |
|Rec ID |Field ID (tag name)* |Field type |Field |Format |Constraints |Default value |Align |
|(tag name) | | |len. | | | | |
|TTL |REPORT_TYPE |STRING |8 | | |CR-RPT-F |L |
|RMS |COUNTRY_A3 |STRING |3 | |ISO-3 code; reporting | |L |
| | | | | |MS | | |
|RPM |PERIOD |DATE |9 |YYYYMMDDP |[01/01/1990, |The value of position P|L |
| | | | | |01/01/2100] |is, by default, ‘Q’ | |
|NOTE |NOTE |STRING |32 | |Free format | |L |
|DAT |SPECIES_CODE |STRING |3 | |FAO species code or | |L |
| | | | | |mixed species or other | | |
| | | | | |code referred | | |
| |AREA_CODE |STRING |2+7 | |FAO code for area or | |L |
| | | | | |sub-divisions | | |
| |SUB_AREA_ID |STRING |3 | |ISO-3 code | |L |
| |CATCH_COUNTRY_ID |STRING |3 | |ISO-3 code; | |L |
| |LANDED_INTO_ID |STRING |3 | |ISO-3 code; | |L |
| |QTY_TOTAL |REAL |10 | | | |R |
Table 3-10: CR-RPT-F FIDES message
Validation Rules (B = Blocking; W = Warning, N = Notification):
1) (W) Same reports have been received previously ( display message;
130) (W) This is the first time that a country sends such a report for that periodicity, for that year ( display message;
131) (W) The Stock/Area/Catch country combination is not defined in the accumulation goals (in case of a report type for which the hierarchical accumulation is not applicable) ( display message;
132) (W) Quantity Qty of the previous declaration is less than the current declaration (cumulative report type) ( display message;
133) (B) COUNTRY_A3: should be present and a valid country code.
134) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *HS, *RB.
135) (B) PERIOD: should be present and a valid period. The date and the periodicity must be valid. The date must be the last of the period;
136) (B) SPECIES_ID: should be present and a valid species code.
137) (B) SUB_AREA_ID: should be null or a valid country code.
138) Unauthorised country codes: EEC, AMS, TAC, *TC, *TB, *RB.
139) (B) AREA_CODE: should be present and a valid FAO area code;
140) (B) CATCH_COUNTRY_ID should be present and a valid country code.
141) Unauthorised country codes:
142) EEC, AMS, TAC, *TC, *TB, *RB, *HS
143) (B) LANDED_INTO_ID should be present and a valid country code.
144) Must be equal to COUNTRY_A3.
9 COCR-STAT-REGIME
Purpose:
A requested to update, during the day, the statistics for the accumulation-goals of a regime, for a particular year or for all years. This means the simulation of suppression and re-creation of the statistics.
Format:
|TAG |Type |Length |Default |Remark |
|REGIME_CODE |A |8 | |Mandatory |
|YEAR_ID |N |4 | | |
Table 3-11: COCR-STAT-REGIME FIDES message
1) (B) REGIME_CODE must be present and should exist;
145) (B) YEAR_ID: must be empty, or, a valid year in the regime range.
10 COCR-NIGHT-PROCESS
Purpose:
A batch process will be launched (at night) using this request message to calculate the results from data already in the database. In fact, when accumulation goal parameters change, the statistics for all the years that are touched will be deleted and re-calculated. When an accumulation goal is suppressed, all corresponding statistics are also suppressed.
-----------------------
[1] In the first phase, only LANDING-REPORTS has been implemented.
[2] Data “under preparation” are not shown.
[3] For Internet Explorer the user can check for the correct version by checking under the Help/Info menu item; the encoding strength is indicated below the version number.
[4] Pay attention to the s in https; users from inside the Commission’s premises do not need to specify the s
[5] Will be in the near future:
[6] The first version of the CRONT system (February 2002) only provides for the English version)
-----------------------
[pic]
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.