Skip to content

Main content

Public Register Series Depth Tool

Calculate public register series depth from explicit caller-supplied inputs.

Loading tool…

Description

Count collectionParts and seriesParts and add one to combinedDepth only when includeCollectionRoot.

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.

Count collectionParts and seriesParts and add one to combinedDepth only when includeCollectionRoot.

When to use this tool

Use Public Register Series Depth when you need a literal archival or public-register record operation.

How to use the tool and how it works

  1. Enter collectionParts, seriesParts, includeCollectionRoot. Keep parallel arrays aligned. 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 collectionDepth, seriesDepth, combinedDepth. Use the output convention below.

Count collectionParts and seriesParts and add one to combinedDepth only when includeCollectionRoot.1

Input fieldMeaning and unitsAccepted input
collectionPartsCollection PartsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
seriesPartsSeries PartsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
includeCollectionRootInclude Collection RootRequired. Boolean.
Output fieldInterpretationReturned shape
collectionDepthCollection DepthRequired. Safe integer.
seriesDepthSeries DepthRequired. Safe integer.
combinedDepthCombined DepthRequired. Safe integer.
json
{
  "input": {
    "collectionParts": [
      "A"
    ],
    "seriesParts": [
      "B",
      "C"
    ],
    "includeCollectionRoot": true
  },
  "output": {
    "collectionDepth": 1,
    "seriesDepth": 2,
    "combinedDepth": 4
  }
}

Limitations and assumptions

  • Parts are supplied list entries rather than parsed catalog paths. The count does not verify archival hierarchy, uniqueness or an official description standard.
  • 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/public-register-series-depth — tool.io

Similar or alternative tools