Skip to content

Main content

Persistent Identifier Scheme Case Rule Tool

Apply an explicitly supplied Unicode-default lowercase comparison policy to identifier text without assuming scheme-specific case rules.

Loading tool…

Description

Apply a supplied case-insensitive comparison convention to an identifier.

Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.

Apply a supplied case-insensitive comparison convention to an identifier.

When to use this tool

Use Persistent Identifier Scheme Case Rule when you already have identifierText, suppliedCaseInsensitive and need to apply a supplied case-insensitive comparison convention to an identifier.

How to use the tool and how it works

  1. Enter identifierText, suppliedCaseInsensitive. 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 comparisonText. Use the output convention below.

Require identifierText nonempty; return full-string toLowerCase when suppliedCaseInsensitive=true, otherwise preserve the text.1

Input fieldMeaning and unitsAccepted input
identifierTextIdentifier TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedCaseInsensitiveTrue lowercases the entire supplied string with JavaScript toLowerCase; no scheme policy is inferred.Required. Boolean.
Output fieldInterpretationReturned shape
comparisonTextComparison TextRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "identifierText": "ABC:Item17",
    "suppliedCaseInsensitive": true
  },
  "output": {
    "comparisonText": "abc:item17"
  }
}

Limitations and assumptions

  • This does not infer an identifier scheme's actual case rules, perform locale-specific folding, Unicode normalization or verify identity.
  • 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

Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.

References

  1. Calculation and input contract: information-science/persistent-identifier-scheme-case-rule — tool.io

Similar or alternative tools