Permits are any documentation authorizing activity, linked to transactions (Accessions, Loans, and Borrows). Permits may be issued by governmental agencies, landowners, registrations (e.g., CITES), etc.
A permit can authorize any number of transactions, and any number of permits may be required for a transaction.
Permit . Permit_Num VARCHAR2(25) NOT NULL
Permit Number or Permit Identifier is an identifying text string. This is often assigned by the agency issuing the permit. Permit number is a required field; enter any suitable value which will help in locating the permit when such an identifier has not been provided by the issuer.
Permit_Type . Permit_Type VARCHAR(50) null
The kind of activity authorized by the permit. Values are controlled by a look-up table. Permits may have any number of permit_types associated, optionally associated with a permit_regulation.
Permit_Type . Permit_Regulation VARCHAR(50) null
The regulation under which the permit was issued. Values are controlled by a look-up table. Permits may have any number of Permit_Regulations associated.
Permit Roles and Agents
Permits may have any number of agents associated via roles. Roles are controlled by a look-up table.
Permit . Issued_Date DATE(7) null
The day the permit was issued. This is an Oracle DATE datatype, not ISO8601; only day-precision is allowed.
Permit . Exp_Date DATE(7) null
The day on which the permit is no longer valid. This is an Oracle DATE datatype, not ISO8601; only day-precision is allowed. Used to automatically notify the permittees of the approaching expiration.
Permit . Permit_Remarks VARCHAR2(4000) null
These can be anything that extends the definition of the permit or the conditions under which it applies.
Renewals should be entered as a new permit. A shortcut button is provided on the edit forms.