Slide Menu
Jump to Section...
Search Help Show/Hide Menu
Metadata Rubric
100%
6 / 6
View Report
PIFSC Metadata Library > PIFSC Protected Species Division (PSD) Metadata... > PSD Hawaiian Monk Seal Research Program (HMSRP)... > HMSRP Hawaiian Monk Seal Population Assessment... > HMSRP Hawaiian Monk Seal Population Assessment... > HMSRP Hawaiian Monk Seal Survival Factors >

Table: MS_SFREPS

Entity (ENT)  |  Pacific Islands Fisheries Science Center (PIFSC)
GUID: gov.noaa.nmfs.inport:18302  |  Updated: October 20, 2022  |  Published / External 

Item Identification

Title: Table: MS_SFREPS
Short Name: MS_SFREPS
Status: Completed
Abstract:

A Survival Factor Report is significant as an assessment made after (a) an event or events (e.g., illness or injury) that may affect the survival of an individual seal or (b) death.
Notes:

Loaded by batch 4358, 02-12-2013 15:39

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None death
None entanglement
None hawaiian monk seal
None hmsrp
None injury
None pifsc
None protected species
None psd
None survival

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None hawaiian archipelago
None pacific region

Physical Location

Organization: Pacific Islands Fisheries Science Center
City: Honolulu
State/Province: HI
Country: USA
Location Description:

1601 Kapiolani Blvd

Honolulu, HI

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: MSEAL
Description:

A Survival Factor Report is significant as an assessment made after (a) an event or events (e.g., illness or injury) that may affect the survival of an individual seal or (b) death.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
 Atoll_Year TEXT Atoll and Year for the Survival Factor
100
 GEO_AREA TEXT Geographic are where Survival Factor occurred
100
 SEAL_ID TEXT Seal that had the Survival Factor
100
 SF_NUM NUMBER A sequential number assigned to designate this occurrence as distinct
100
 YEAR NUMBER The current year when the event occurred. [Convert to number, YYYY]
100
 SF_FIRST_DATE DATE The first date on which the Survival factor was observed or presumed to have occurred.
100
 MOBILITY VARCHAR2 Code to indicate degree to which mobility has been affected. LOV
100
 ALERT VARCHAR2 Code to indicate degree to which alertness has been affected. LOV
100
 MOUNT VARCHAR2 Is this a mounting event?
100
 MOUNT_OBS VARCHAR2 Was the mounting observed?
100
 NUMBER_MALES NUMBER Number of males who participated in the mounting.
100
 DIST_OFFSHORE NUMBER How far offshore did it occur?
100
 BEGIN_OBS VARCHAR2 Was the beginning observed?
100
 END_OBS VARCHAR2 Was the end of the mounting observed?
100
 ENTANG VARCHAR2 Is this seal entangled?
100
 ENTANG_OBS VARCHAR2 Was the entanglement observed?
100
 DEBRIS_TYPE VARCHAR2 Identifies the type of debris. LOV
100
 RELEASED VARCHAR2 DId the observer release the seal from the entanglement?
100
 UNENTANG_DATE DATE Date first seen as unentangled after an entanglement event.
100
 LG_SHARK VARCHAR2 Is this a bite of a large shark?
100
 SHARK_OBS VARCHAR2 Was the shark seen?
100
 EMAC VARCHAR2 Is the seal emaciated?
100
 ILL_ABNORMAL VARCHAR2 Is the seal ill or behaving abnormally?
100
 HANDLE_STRESS VARCHAR2 Is the seal reacting to stress caused by observer handling?
100
 OTHER_FACTOR VARCHAR2 Catch-all for otherwise unclassified causes.
100
 UNKNOWN_CAUSE VARCHAR2 Is the cause simply unknown?
100
 NECROPSY VARCHAR2 If the seal died was a necropsy performed? How complete? LOV
100
 INJURED VARCHAR2 Is the seal injured? LOV surv injured
100
 INJURY_DATE DATE Date this seal was observed with injury.
100
 GONE_DATE DATE Date seal first seen dead or date of last sighting of seal if death is uncertain.
100
 INJ_AGE VARCHAR2 Is this a fresh or older injury? LOV surv injage
100
 REOPENED VARCHAR2 Has the injury repoened?
100
 CHRONIC VARCHAR2 Does the seal exhibit a chronic condition?
100
 ABSCESS VARCHAR2 Does the seal have an abscess?
100
 ABSCESS_SEV VARCHAR2 How severe is the abscess? LOV
100
 AMPUTATION VARCHAR2 Has the seal suffered an amputation?
100
 AMPUTATION_SEV VARCHAR2 How severe is the amputation? LOV
100
 SCRATCH_LAC VARCHAR2 Does the seal exhibit a scratch or laceration?
100
 SCRATCH_LAC_SEV VARCHAR2 How severe is the scratch or laceration? LOV
100
 PUNCTURE_GAP VARCHAR2 Does the seal have a puncture or gaping wound?
100
 PUNCTURE_GAP_SEV VARCHAR2 How severe is the wound? LOV
100
 PUNCTURE_GAP_DEPTH VARCHAR2 How deep is the wound? LOV
100
 INFECTED VARCHAR2 Does the seal have an infection?
100
 INFECTED_DATE DATE Date infection was observed.
100
 HEALED VARCHAR2 Has a previous condition or injury healed?
100
 HEALED_DATE DATE Date that healing was noted.
100
 BLUNT_TRAUMA VARCHAR2 Has the seal experienced blunt trauma?
100
 BLUNT_TRAUMA_SEV VARCHAR2 How severe is the blunt trauma ? LOV
100
 SURV_STATUS VARCHAR2 Survival status at the time of this report. LOV. This may trigger an update in chk_seals and/or chk_seal_annuals
100
 NE_DATE DATE Date on which Necropsy was performed.
100
 CARCASS_CONDITION VARCHAR2 Condition of carcass at time of discovery. LOV
100
 CRITICAL_LOCATION VARCHAR2 Is the injury or trauma affecting a critical location on the seal?
100
 CONF_LEVEL NUMBER How much confidence can we have in the accuracy of this data?
100
 CHECKING_LEVEL NUMBER To what level has the checking and/or editing process been successfully completed for this data row?
100
 MEMO_TEXT VARCHAR2 Free-form text entry for notes regarding this survival factor.
100
 CREATED_BY VARCHAR2 Oracle username that created the record
100
 CREATE_DTM DATE System date/time of record creation
100
 LAST_MOD_BY VARCHAR2 Oracle username that last modified the record
100
 LAST_MOD_DTM DATE System date/time of last modification of the record
100
 SF_SEAL_SIZE NUMBER The size observed during the recording of this Survival Factor

Attribute Details

Atoll_Year

CC ID: 846031
Seq. Order: 1
Data Storage Type: TEXT
Required: No
Primary Key: No
Status: Active
Description:

Atoll and Year for the Survival Factor

GEO_AREA

CC ID: 846032
Seq. Order: 2
Data Storage Type: TEXT
Required: No
Primary Key: No
Status: Active
Description:

Geographic are where Survival Factor occurred

SEAL_ID

CC ID: 846033
Seq. Order: 3
Data Storage Type: TEXT
Required: No
Primary Key: No
Status: Active
Description:

Seal that had the Survival Factor

SF_NUM

CC ID: 96339
Seq. Order: 6
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 38
Scale: 0
Status: Active
Description:

A sequential number assigned to designate this occurrence as distinct
General Data Type: NUMBER

YEAR

CC ID: 96340
Seq. Order: 7
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

The current year when the event occurred. [Convert to number, YYYY]
General Data Type: NUMBER

SF_FIRST_DATE

CC ID: 96341
Seq. Order: 8
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

The first date on which the Survival factor was observed or presumed to have occurred.
General Data Type: DATE

MOBILITY

CC ID: 96342
Seq. Order: 9
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Code to indicate degree to which mobility has been affected. LOV
General Data Type: VARCHAR2

ALERT

CC ID: 96343
Seq. Order: 10
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Code to indicate degree to which alertness has been affected. LOV
General Data Type: VARCHAR2

MOUNT

CC ID: 96344
Seq. Order: 11
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is this a mounting event?
General Data Type: VARCHAR2

MOUNT_OBS

CC ID: 96345
Seq. Order: 12
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Was the mounting observed?
General Data Type: VARCHAR2

NUMBER_MALES

CC ID: 96346
Seq. Order: 13
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 38
Scale: 0
Status: Active
Description:

Number of males who participated in the mounting.
General Data Type: NUMBER

DIST_OFFSHORE

CC ID: 96347
Seq. Order: 14
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 3
Scale: 0
Status: Active
Description:

How far offshore did it occur?
General Data Type: NUMBER

BEGIN_OBS

CC ID: 96348
Seq. Order: 15
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Was the beginning observed?
General Data Type: VARCHAR2

END_OBS

CC ID: 96349
Seq. Order: 16
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Was the end of the mounting observed?
General Data Type: VARCHAR2

ENTANG

CC ID: 96350
Seq. Order: 17
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is this seal entangled?
General Data Type: VARCHAR2

ENTANG_OBS

CC ID: 96351
Seq. Order: 18
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Was the entanglement observed?
General Data Type: VARCHAR2

DEBRIS_TYPE

CC ID: 96352
Seq. Order: 19
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Identifies the type of debris. LOV
General Data Type: VARCHAR2

RELEASED

CC ID: 96353
Seq. Order: 20
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

DId the observer release the seal from the entanglement?
General Data Type: VARCHAR2

UNENTANG_DATE

CC ID: 96354
Seq. Order: 21
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date first seen as unentangled after an entanglement event.
General Data Type: DATE

LG_SHARK

CC ID: 96355
Seq. Order: 22
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is this a bite of a large shark?
General Data Type: VARCHAR2

SHARK_OBS

CC ID: 96356
Seq. Order: 23
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Was the shark seen?
General Data Type: VARCHAR2

EMAC

CC ID: 96357
Seq. Order: 24
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is the seal emaciated?
General Data Type: VARCHAR2

ILL_ABNORMAL

CC ID: 96358
Seq. Order: 25
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is the seal ill or behaving abnormally?
General Data Type: VARCHAR2

HANDLE_STRESS

CC ID: 96359
Seq. Order: 26
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is the seal reacting to stress caused by observer handling?
General Data Type: VARCHAR2

OTHER_FACTOR

CC ID: 96360
Seq. Order: 27
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Catch-all for otherwise unclassified causes.
General Data Type: VARCHAR2

UNKNOWN_CAUSE

CC ID: 96361
Seq. Order: 28
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is the cause simply unknown?
General Data Type: VARCHAR2

NECROPSY

CC ID: 96362
Seq. Order: 29
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

If the seal died was a necropsy performed? How complete? LOV
General Data Type: VARCHAR2

INJURED

CC ID: 96363
Seq. Order: 30
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Is the seal injured? LOV surv injured
General Data Type: VARCHAR2

INJURY_DATE

CC ID: 96364
Seq. Order: 31
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date this seal was observed with injury.
General Data Type: DATE

GONE_DATE

CC ID: 96365
Seq. Order: 32
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date seal first seen dead or date of last sighting of seal if death is uncertain.
General Data Type: DATE

INJ_AGE

CC ID: 96366
Seq. Order: 33
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Is this a fresh or older injury? LOV surv injage
General Data Type: VARCHAR2

REOPENED

CC ID: 96367
Seq. Order: 34
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Has the injury repoened?
General Data Type: VARCHAR2

CHRONIC

CC ID: 96368
Seq. Order: 35
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Does the seal exhibit a chronic condition?
General Data Type: VARCHAR2

ABSCESS

CC ID: 96369
Seq. Order: 36
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Does the seal have an abscess?
General Data Type: VARCHAR2

ABSCESS_SEV

CC ID: 96370
Seq. Order: 37
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How severe is the abscess? LOV
General Data Type: VARCHAR2

AMPUTATION

CC ID: 96371
Seq. Order: 38
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Has the seal suffered an amputation?
General Data Type: VARCHAR2

AMPUTATION_SEV

CC ID: 96372
Seq. Order: 39
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How severe is the amputation? LOV
General Data Type: VARCHAR2

SCRATCH_LAC

CC ID: 96373
Seq. Order: 40
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Does the seal exhibit a scratch or laceration?
General Data Type: VARCHAR2

SCRATCH_LAC_SEV

CC ID: 96374
Seq. Order: 41
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How severe is the scratch or laceration? LOV
General Data Type: VARCHAR2

PUNCTURE_GAP

CC ID: 96375
Seq. Order: 42
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Does the seal have a puncture or gaping wound?
General Data Type: VARCHAR2

PUNCTURE_GAP_SEV

CC ID: 96376
Seq. Order: 43
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How severe is the wound? LOV
General Data Type: VARCHAR2

PUNCTURE_GAP_DEPTH

CC ID: 96377
Seq. Order: 44
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How deep is the wound? LOV
General Data Type: VARCHAR2

INFECTED

CC ID: 96378
Seq. Order: 45
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Does the seal have an infection?
General Data Type: VARCHAR2

INFECTED_DATE

CC ID: 96379
Seq. Order: 46
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date infection was observed.
General Data Type: DATE

HEALED

CC ID: 96380
Seq. Order: 47
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Has a previous condition or injury healed?
General Data Type: VARCHAR2

HEALED_DATE

CC ID: 96381
Seq. Order: 48
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date that healing was noted.
General Data Type: DATE

BLUNT_TRAUMA

CC ID: 96382
Seq. Order: 49
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Has the seal experienced blunt trauma?
General Data Type: VARCHAR2

BLUNT_TRAUMA_SEV

CC ID: 96383
Seq. Order: 50
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

How severe is the blunt trauma ? LOV
General Data Type: VARCHAR2

SURV_STATUS

CC ID: 96387
Seq. Order: 54
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Survival status at the time of this report. LOV. This may trigger an update in chk_seals and/or chk_seal_annuals
General Data Type: VARCHAR2

NE_DATE

CC ID: 96388
Seq. Order: 55
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date on which Necropsy was performed.
General Data Type: DATE

CARCASS_CONDITION

CC ID: 96389
Seq. Order: 56
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Condition of carcass at time of discovery. LOV
General Data Type: VARCHAR2

CRITICAL_LOCATION

CC ID: 96390
Seq. Order: 57
Data Storage Type: VARCHAR2
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Is the injury or trauma affecting a critical location on the seal?
General Data Type: VARCHAR2

CONF_LEVEL

CC ID: 96391
Seq. Order: 58
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Status: Active
Description:

How much confidence can we have in the accuracy of this data?
General Data Type: NUMBER

CHECKING_LEVEL

CC ID: 96392
Seq. Order: 59
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 38
Status: Active
Description:

To what level has the checking and/or editing process been successfully completed for this data row?
General Data Type: NUMBER

MEMO_TEXT

CC ID: 96393
Seq. Order: 60
Data Storage Type: VARCHAR2
Max Length: 3000
Required: No
Primary Key: No
Status: Active
Description:

Free-form text entry for notes regarding this survival factor.
General Data Type: VARCHAR2

CREATED_BY

CC ID: 96394
Seq. Order: 61
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Oracle username that created the record
General Data Type: VARCHAR2

CREATE_DTM

CC ID: 96395
Seq. Order: 62
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

System date/time of record creation
General Data Type: DATE

LAST_MOD_BY

CC ID: 96396
Seq. Order: 63
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Oracle username that last modified the record
General Data Type: VARCHAR2

LAST_MOD_DTM

CC ID: 96397
Seq. Order: 64
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

System date/time of last modification of the record
General Data Type: DATE

SF_SEAL_SIZE

CC ID: 96398
Seq. Order: 66
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Status: Active
Description:

The size observed during the recording of this Survival Factor
General Data Type: NUMBER

Support Roles

Data Steward

CC ID: 103291
Date Effective From: 2007-06-13
Date Effective To:
Contact (Person): Johanos, Thea C
Address: 1845 Wasp Blvd.
Honolulu, HI 96818
USA
Email Address: thea.johanos-kam@noaa.gov
Phone: (808)725-5709

Originator

CC ID: 103292
Date Effective From: 2007-06-13
Date Effective To:
Contact (Organization): Pacific Islands Fisheries Science Center (PIFSC)
Address: 1845 Wasp Blvd.
Honolulu, HI 96818
USA
Email Address: pifsc.info@noaa.gov
Phone: 808-725-5360
URL: https://www.pifsc.noaa.gov
Business Hours: 8:00 a.m. - 4:30 p.m.

Point of Contact

CC ID: 103290
Date Effective From: 2007-06-13
Date Effective To:
Contact (Person): Johanos, Thea C
Address: 1845 Wasp Blvd.
Honolulu, HI 96818
USA
Email Address: thea.johanos-kam@noaa.gov
Phone: (808)725-5709

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Time Frame 1

CC ID: 103293
Time Frame Type: Continuing
Start: 1977-12-31

Access Information

Security Class: Restricted
Data Access Policy:

NMFS/PIFSC, Protected Species Division, Hawaiian Monk Seal Research Program Data Access, Sharing, and Dissemination Guidelines
Data Access Procedure:

Requestor will be asked to submit a request to Thea Johanos (thea.johanos-kam@noaa.gov)
Data Access Constraints:

NMFS/PIFSC, Protected Species Division, Hawaiian Monk Seal Research Program Data Access, Sharing, and Dissemination Guidelines
Data Use Constraints:

Use of the data set must be cleared with NMFS/PIFSC, Protected Species Division. These data are PRELIMINARY and have not be completely screened for accuracy. NOAA can not be held liable for use of these data in a manner other than for perusal of preliminary data. The developers of these data are concerned with assuring its proper use. Before data are used to draw specific scientific conclusions, potential users are requested to contact NMFS/PIFSC, Protected Species Division for background on the data. Acknowledgement of the data should be cited. Different versions of the dataset may exist. The user must be sure to use the appropriate data set for the time period of interest. While efforts have been made to ensure that these data are accurate and reliable, NOAA cannot assume liablility for any damages or misrepresentation caused by any inaccuracies in the data or as a result of changes to the data caused by system transfers.

Catalog Details

Catalog Item ID: 18302
GUID: gov.noaa.nmfs.inport:18302
Metadata Record Created By: Vikram Khurana
Metadata Record Created: 2013-02-12 15:39+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-10-20 02:17+0000
Metadata Record Published: 2019-05-30
Owner Org: PIFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2019-05-30
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2020-05-30