Description
Check training acknowledgement against a required version.
Biosecurity administration records training assertions, custody, access purposes, inventories and document handling. Local counts, time checks and permission predicates describe supplied metadata; they do not authenticate people or items, enforce access or establish actual protective conditions.
Check training acknowledgement against a required version.
When to use this tool
Use Biosecurity Training Acknowledged Version Pair when checking the stated benign biosecurity record, inventory, support or authorization convention.
How to use the tool and how it works
- Enter requiredVersion, acknowledgedVersion, acknowledged, revoked. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read versionMatches, acknowledgedCurrent. Inspect versionMatches, acknowledgedCurrent before interpreting the associated values.
Check training acknowledgement against a required version. Require nonempty version labels; versionMatches uses equality, acknowledgedCurrent also requires acknowledged and not revoked.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requiredVersion | Required Version | Required. Text; maximum UTF-16 length 8192. |
| acknowledgedVersion | Acknowledged Version | Required. Text; maximum UTF-16 length 8192. |
| acknowledged | Acknowledged | Required. Boolean. |
| revoked | Revoked | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| versionMatches | Version Matches | Required. Boolean. |
| acknowledgedCurrent | Acknowledged Current | Required. Boolean. |
{
"input": {
"requiredVersion": "v3",
"acknowledgedVersion": "v2",
"acknowledged": true,
"revoked": false
},
"output": {
"versionMatches": false,
"acknowledgedCurrent": false
}
}Limitations and assumptions
- Matching labels and assertions do not establish completed training, understanding, competence or actual access permission.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Verify actual records, permissions and conditions through the responsible organization's procedures; use qualified risk assessment and appropriate professional oversight for practical decisions.
References
Similar or alternative tools
- Biosecurity Supplied Permission Intersection
Return requested permissions common to two lists and not denied.
- Biosecurity Document Owner Approval Window
Compare a document owner and approval window.