Skip to content

Main content

GCP Source Transcription One Field Pair Tool

Compare one supplied source/transcription string under an explicit normalization policy.

Loading tool…

Description

Return exactMatch for the original two strings.

Good clinical practice record checks compare supplied versions, language labels, roles, dates, and source links. A local metadata match can reveal consistency but does not establish valid consent, competent authorization, or regulatory compliance.

Return exactMatch for the original two strings.

When to use this tool

Use GCP Source Transcription One Field Pair when you need a literal clinical-trial metadata consistency check.

How to use the tool and how it works

  1. Enter sourceValue, transcribedValue, trimSpaces, caseSensitive. 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 exactMatch, normalizedMatch, sourceNormalized. Inspect exactMatch, normalizedMatch before interpreting the associated values.

Return exactMatch for the original two strings. Optionally remove only leading and trailing ASCII spaces, then optionally lowercase with JavaScript to produce normalizedMatch and sourceNormalized.1

Input fieldMeaning and unitsAccepted input
sourceValueSource ValueRequired. Text; maximum UTF-16 length 8192.
transcribedValueTranscribed ValueRequired. Text; maximum UTF-16 length 8192.
trimSpacesTrim SpacesRequired. Boolean.
caseSensitiveCase SensitiveRequired. Boolean.
Output fieldInterpretationReturned shape
exactMatchExact MatchRequired. Boolean.
normalizedMatchNormalized MatchRequired. Boolean.
sourceNormalizedSource NormalizedRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "sourceValue": " ABC ",
    "transcribedValue": "abc",
    "trimSpaces": true,
    "caseSensitive": false
  },
  "output": {
    "exactMatch": false,
    "normalizedMatch": true,
    "sourceNormalized": "abc"
  }
}

Limitations and assumptions

  • Tabs and other whitespace are not trimmed by trimSpaces, and lowercasing is not locale-specific collation. Text equality does not establish source authenticity, clinical accuracy, or an acceptable correction.
  • 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 complete controlled trial records and applicable professional process. Verify authenticity, protocol scope, consent, competence, and effective versions through the appropriate responsible reviewers.

References

  1. Calculation and input contract: gcp/gcp-source-transcription-one-field-pair — tool.io

Similar or alternative tools

  • Delegation Role Source Gap

    Count role mismatches, zero-length source IDs, and rows with equal roles and a positive-length source ID.

  • GCP Consent Language Document Pair

    Return languageDirect for exact preferred/document language equality, interpretationMatched when interpreterUsed is true and interpreterLanguage exactly matches preference, and versionMatched for translation/required version equality.