Database Properties
Database Type: PostgreSQL - 16.4 (Debian 16.4-1.pgdg110+2)
Tables
| Table / View | Children | Parents | Columns | Rows | Type | Comments |
|---|---|---|---|---|---|---|
| decision | 1 | 5 | 13 | -1 | Table | As a CEEB Compliance Coordinator or Officer, I need to be able to capture decision information to ensure that all information necessary in the decision making process can be captured in the complaint. |
| ear_tag_h | 0 | 0 | 6 | -1 | Table | History table for case_file table |
| schedule_sector_xref | 1 | 2 | 8 | -1 | Table | |
| action_type_action_xref | 1 | 2 | 9 | -1 | Table | Contains the relationship between case management actions and logical types. |
| case_location_code | 1 | 0 | 9 | -1 | Table | Contains the list of location types a user can select to indicate that where they take an action on a case. Values are Organization specific. |
| drug_administered | 0 | 4 | 13 | -1 | Table | While an officer is responding to a LEAD they may need to record that a WILDLIFE had a DRUG_ADMINISTERED. This table keeps track of the type and amount of drugs administered, along with what happened to any remaining drug that was not used. |
| flyway_schema_history | 0 | 0 | 10 | -1 | Table | |
| case_code | 1 | 0 | 8 | -1 | Table | Contains the list of case types supported by the system. For example HWCR = “Human Wildlife Conflict” |
| drug_method_code | 1 | 0 | 9 | -1 | Table | Contains the list of drug induction methods types supported by the system. For example DART = “Dart” |
| threat_level_code | 2 | 0 | 9 | -1 | Table | A COS determination that indicates the threat level of the animal to humans. For example 1 = “Category 1” |
| action_h | 0 | 0 | 6 | -1 | Table | History table for action table |
| equipment | 1 | 1 | 11 | -1 | Table | Represents a piece of physical equipment that has been deployed in support of the case. Contains information about where and when the equipment was deployed. |
| age_code | 1 | 0 | 9 | -1 | Table | Used to categorize wildlife into age brackets. For example ADLT = “Adult” |
| inaction_reason_code | 1 | 1 | 10 | -1 | Table | Contains the list of available reasons a user can select to indicate that the reason why they did not take any action on a case. Values are Organization specific. |
| sex_code | 1 | 0 | 9 | -1 | Table | Contains the list of biological sexes supported by the system. For example M = “Male” |
| case_file_h | 0 | 0 | 6 | -1 | Table | History table for case_file table |
| ear_tag | 0 | 2 | 9 | -1 | Table | an EAR_TAG is used to identify a specific WILDLIFE allowing the animal to be tracked over time. |
| configuration_h | 0 | 0 | 6 | -1 | Table | History table for configuration table |
| equipment_code | 1 | 0 | 11 | -1 | Table | Used to track pieces of equipment that could be deployed out in the field. For example BRSNR = “Bear Snare” |
| site_h | 0 | 0 | 6 | -1 | Table | History table for site table |
| agency_code | 3 | 0 | 9 | -1 | Table | Contains a list of all the organizations that have been onboarded onto the Case Management System. This can be used to restrict some content to organization specific values. |
| wildlife_h | 0 | 0 | 6 | -1 | Table | History table for case_file table |
| authorization_permit | 0 | 1 | 8 | -1 | Table | Contains the authroized site id for the Authroization Outcome |
| site | 0 | 1 | 8 | -1 | Table | Contains the unauthorized site id for the Authroization Outcome |
| action_code | 1 | 0 | 8 | -1 | Table | Contains a list of all possible actions that can be performed on a case. |
| non_compliance_decision_matrix_code | 1 | 0 | 9 | -1 | Table | Contains a list of all possible non_compliance_decision_matrix_code codes for a CEEB decision |
| conflict_history_code | 1 | 0 | 9 | -1 | Table | A classification on the frequence that the target wildlife has previously had a history of human conflict. For example L = “Low” |
| configuration | 0 | 0 | 8 | -1 | Table | The configuration table is used to store constants which are expected to change over the lifecycle of the application, or have different values in different environments. By making changes to in the database the behaviour of the application can be altered without requiring a full deployment. |
| action_type_code | 1 | 0 | 8 | -1 | Table | Case management actions are grouped into logical types. For example COMPASSESS = ‘Complaint Assessment’. |
| drug_remaining_outcome_code | 1 | 0 | 9 | -1 | Table | After a drug has been induced to an animal, the fate of the remaining drug in the vial is recorded. This table contains a list of types supported by the system. For example DISC = “Discard” |
| drug_code | 1 | 0 | 9 | -1 | Table | Contains the list of drugs that could be administered to wildlife. For example ATPMZ = “Atipamezole” |
| schedule_code | 1 | 0 | 9 | -1 | Table | Contains a list of all possible schedule_code codes for a CEEB decision |
| decision_h | 0 | 0 | 6 | -1 | Table | |
| hwcr_outcome_code | 1 | 0 | 9 | -1 | Table | Indicates the final outcome for an animal as a result of an HWC. For example DESTRYCOS = “Destroyed by COS” |
| action | 0 | 6 | 14 | -1 | Table | Represents a concrete action recorded by the case management system. All actions have an actor and the date/time they occurred. |
| drug_administered_h | 0 | 0 | 6 | -1 | Table | History table for case_file table |
| sector_code | 1 | 0 | 9 | -1 | Table | Contains a list of all possible sector_code codes for a CEEB decision |
| case_note | 1 | 1 | 8 | -1 | Table | |
| wildlife | 3 | 5 | 13 | -1 | Table | WILDLIFE can be a participant on a CASE_FILE, specifically for CASE_FILE with a CASE_CODE of “HWCR” (Human / Wildlife Conflict) |
| ear_code | 1 | 0 | 9 | -1 | Table | Indicates which ear an identification tag is present on. For example L = “Left” |
| lead_h | 0 | 0 | 6 | -1 | Table | History table for lead table |
| authorization_permit_h | 0 | 0 | 6 | -1 | Table | History table for authorization_permit table |
| case_file | 7 | 6 | 15 | -1 | Table | The central entity of the case management system. |
| discharge_code | 1 | 0 | 9 | -1 | Table | Contains a list of all possible discharge codes for a CEEB decision |
| lead | 0 | 1 | 6 | -1 | Table | A lead is any potential issue that an agency is made aware of. This could be a complaint, referral, etc. A lead needs to be evaluated to determine if it will become a case. |