Skip to content

Main content

Multilingual Title Sort Prefix Tool

Remove the longest literal caller-supplied nonfiling prefix without locale collation or language detection.

Loading tool…

Description

Compare title with nonempty supplied prefixes, optionally after lowercasing.

Historical and public-register references combine repositories, series, titles and local identifiers. A syntactic token or hierarchy count helps organize records without authenticating the source or establishing a document's historical or legal meaning.

Compare title with nonempty supplied prefixes, optionally after lowercasing.

When to use this tool

Use Multilingual Title Sort Prefix when you need a literal archival or public-register record operation.

How to use the tool and how it works

  1. Enter title, suppliedPrefixes, 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 matchedPrefix, sortKey. Use the output convention below.

Compare title with nonempty supplied prefixes, optionally after lowercasing. Choose the longest matching original prefix and slice that many characters from the original title.1

Input fieldMeaning and unitsAccepted input
titleTitleRequired. Text; maximum UTF-16 length 8192.
suppliedPrefixesSupplied PrefixesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
caseSensitiveCase SensitiveRequired. Boolean.
Output fieldInterpretationReturned shape
matchedPrefixMatched PrefixRequired. Text; maximum UTF-16 length 8192.
sortKeySort KeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "title": "The Book",
    "suppliedPrefixes": [
      "The ",
      "Le "
    ],
    "caseSensitive": false
  },
  "output": {
    "matchedPrefix": "The ",
    "sortKey": "Book"
  }
}

Limitations and assumptions

  • There is no word-boundary or language-aware article rule, and no extra trimming. Case conversion is JavaScript lowercasing, not locale collation; title identity remains unverified.
  • 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

Consult the source repository's catalog and description conventions for identity and interpretation. Preserve original references and resolve language, hierarchy and identifier rules before treating a token match as an authenticated record.

References

  1. Calculation and input contract: european-studies/multilingual-title-sort-prefix — tool.io

Similar or alternative tools