Columns
Column | Type | Size | Nulls | Auto | Default | Children | Parents | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
uuid | varchar | 36 | null |
|
|
unique identifier of the FIP from SFP systems |
||||||||||
db_version_year | int4 | 10 | null |
|
|
|||||||||||
current_name | text | 2147483647 | null |
|
|
name of the FIP in SFP systems as of cut off date of each version year (e.g., October 2022 for the 2022 dB version); https://www.fishsource.org/improvement-project; https://fisheryprogress.org/ |
||||||||||
url | text | 2147483647 | √ | null |
|
|
webpage, only available for active FIPs |
|||||||||
acronym | varchar | 40 | √ | null |
|
|
acronym created for data analysis purposes. Since the 2020 version of the database, this is no longer a field that is systematically updated. |
|||||||||
start_date | date | 13 | √ | null |
|
|
Date (in YYYY-MM-DD format) the FIP is formally claimed to be launched (typically when it is publicly announced). This date is affected by multiple political, economic and operational matters. One of the operational challenges is that the FIP is only publicly recognized (for evaluation purposes) when all the evidence is made publicly available. This may result in differences between the date a FIP is publicly listed as active and the date the FIP claimed it started. The date that stage 2 was first achieved is a standardized variable, and a better proxy across FIPs for scientific analysis related to the duration a FIP has been in existence and the delta between stages. |
|||||||||
progress_pattern | varchar | 40 | √ | null |
|
|
Two possible categories; (1) stepwise where stages are achieved in order or (2) opportunistic when stages are achieved out of order (for example a FIP achieves Stage 4 before Stage 3) |
|||||||||
fleet_type | varchar | 40 | √ | null |
|
|
Three possible categories and refers to fleets covered by the FIP (1) industrial (2) artisanal and (3) both; data is available on this variable through Oct 2017, otherwise TBD is entered. The decision tree used to make these decisions is made available in the resources column of this entry. https://docs.google.com/drawings/d/1amJwsYBJw8X55gy6IseP-Pf544rShLW3javXNp3xTUU/edit |
|||||||||
artisanal_component_stock | bool | 1 | √ | null |
|
|
Two choices (1) Y and (2) N which refer to if there is an artisanal component of the fishery that represented >5% of total catch, regardless if that artisanal component is covered by the FIP; data is available on this variable through Oct 2017, otherwise TBD is entered. https://docs.google.com/drawings/d/192tPood_Gv8bAv1s2YYgQmAsQhyD3Zcjhqq7lsIBfuM/edit?usp=sharing |
|||||||||
artisanal_component_notes | text | 2147483647 | √ | null |
|
|
notes supporting categorization of artisanal component (for example % catch attributed to the artisanal fleet) |
|||||||||
first_msc_pa_date | date | 13 | √ | null |
|
|
Date (in YYYY-MM-DD format) of the first MSC pre-assessment. Notes: (1) For basic FIPs, an MSC pre-assessment (MSC PA) is not mandatory. (2) NA means no MSC PA publicly known. This field was systematically revised and updated in the 2023 version. |
|||||||||
scope | varchar | 40 | √ | null |
|
|
Two possible categories; (1) stock which means that FIP outcomes are expected to occur at the stock level and (2) fishery-level which means that FIP outcomes are expected to occur only at the fishery level, not the higher stock level; Note: Data only covers FIPs until June 2016, as this is no longer a required field to report on. For FIPs with no specific information on FIP scope, TBD is entered. |
Indexes
Constraint Name | Type | Sort | Column(s) |
---|---|---|---|
fips_pkey | Primary key | Asc/Asc | uuid + db_version_year |