Skip to content

Main content

Botanical Sample Origin Permission

Record explicit sample-origin and permission metadata without determining legal authorization.

Loading tool…

Description

Record explicit sample-origin and permission metadata.

Botanical analytical records connect voucher identities, plant parts, extraction wording, moisture basis and marker units. A dry-basis fraction uses dry mass as its denominator, while a printed drug-extract ratio still needs its stated basis. Source labels and arithmetic do not authenticate a medicinal plant, establish potency or determine safe herbal use.

Record explicit sample-origin and permission metadata.

When to use this tool

Use Botanical Sample Origin Permission when you already have sampleId, originRecordId, permissionPurpose, permissionRecorded and need to record explicit sample-origin and permission metadata.

How to use the tool and how it works

  1. Enter sampleId, originRecordId, permissionPurpose, permissionRecorded. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Enter sampleId, originRecordId, permissionPurpose, permissionRecorded using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup. Boolean permission or verification fields are recorded assertions, not authorizations.1

Input fieldMeaning and unitsAccepted input
sampleIdSample IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
originRecordIdOrigin Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
permissionPurposePermission PurposeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
permissionRecordedPermission RecordedRequired. Boolean.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "sampleId": "S17",
    "originRecordId": "ORG2",
    "permissionPurpose": "analysis",
    "permissionRecorded": true
  },
  "output": {
    "token": "[\"S17\",\"ORG2\",\"analysis\",true]"
  }
}

Limitations and assumptions

  • The result records supplied values without determining legal authorization. Sources and asserted relationships are not independently authenticated.
  • 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

Review the original voucher, analytical method, moisture basis and reference-material documentation. Botanical identity, extraction basis and marker quantity require their own evidence; a recorded ratio or mass-basis conversion does not establish equivalence or medicinal suitability.

References

  1. Calculation and input contract: pharmacognosy/botanical-sample-origin-permission — tool.io

Similar or alternative tools