Finding Aid EAD Tag Completeness Counter

Count required EAD qualified-tag presence from independently namespace-aware parsed actual XML and edition/institution requirements, not regex XML parse or a complete schema/content/hierarchy validation. Duplicate actual tags allowed; source text/empty content and semantics external.

Description

EAD completeness depends on the adopted schema and required expanded element names.

EAD completeness depends on the adopted schema and required expanded element names.^[1]

Namespace-aware parsed evidence is needed before comparing presence with the caller's list. Use this tool to calculate the stated observation or conditional model from supplied measurements.

When to use Finding Aid EAD Tag Completeness Counter

Use this tool to calculate the stated observation or conditional model from supplied measurements. Establish the institution, collection/material context, applicable standards or authority, reference date and measurement units.

How to use Finding Aid EAD Tag Completeness Counter and understand its results

Establish the institution, collection/material context, applicable standards or authority, reference date and measurement units.
Enter callerApplicableEadRequiredQualifiedNames, independentlyParsedPresentEadQualifiedNames, parserEvidenceVerified, using the field meanings and rules below, then run the tool.
Read result.presentCallerRequiredQualifiedNames, result.missingCallerRequiredQualifiedNames, result.requiredTagPresenceFraction. Interpret each field using the units, signs and evidence rules below.
If input validation fails, correct the reported field and run again. Before applying a successful result, check the stated reference scope, units, assumptions and any retained unknown evidence.

Input field	Meaning	Value type	Requirement
callerApplicableEadRequiredQualifiedNames	Caller applicable ead required qualified names	list of string	Required
independentlyParsedPresentEadQualifiedNames	Independently parsed present ead qualified names	list of string	Required
parserEvidenceVerified	Parser evidence verified	boolean	Required

Supply nonempty unique required expanded names and a list of independently parsed present expanded names. Names must match {nonemptyNamespace}localName with ASCII letter/underscore start and subsequent letters, digits, underscores, periods or hyphens. Require parserEvidenceVerified=true; present names may repeat or be empty. Return required names found/missing in caller-required order and foundCount/requiredCount. This compares element-name presence without parsing XML, examining content or validating an EAD schema.

presentRequired=required.filter(name in parsedPresent); missingRequired=required.filter(name not in parsedPresent); presenceFraction=presentRequired.length/required.length

Apply the field units and exact ordering, boundary and evidence rules above.

Output field	Meaning	Value type
result	Structured result containing the calculation or selected reference fields below	object
result.presentCallerRequiredQualifiedNames	Present Caller Required Qualified Names; use the units, sign convention and calculation stated above	list of string
result.missingCallerRequiredQualifiedNames	Missing Caller Required Qualified Names; use the units, sign convention and calculation stated above	list of string
result.requiredTagPresenceFraction	Required Tag Presence Fraction; use the units, sign convention and calculation stated above	number

json

{
  "input": {
    "callerApplicableEadRequiredQualifiedNames": [
      "{urn:isbn:1-931666-22-9}ead",
      "{urn:isbn:1-931666-22-9}archdesc"
    ],
    "independentlyParsedPresentEadQualifiedNames": [
      "{urn:isbn:1-931666-22-9}ead"
    ],
    "parserEvidenceVerified": true
  },
  "output": {
    "result": {
      "presentCallerRequiredQualifiedNames": [
        "{urn:isbn:1-931666-22-9}ead"
      ],
      "missingCallerRequiredQualifiedNames": [
        "{urn:isbn:1-931666-22-9}archdesc"
      ],
      "requiredTagPresenceFraction": 0.5
    }
  }
}

Limitations and assumptions

Namespace-aware parsed evidence is needed before comparing presence with the caller's list. Results depend on the independently established measurement basis and the exact model assumptions above.

Every listed input requires an explicit value. Unexpected fields, incorrect value types, nonfinite numbers and sparse numeric arrays fail validation; tool-specific bounds and alignment rules apply as described above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful calculation that reports a false comparison or retains unknown evidence.

Alternative or Complementary methods

Use Item Level Barcode Check Digit Validator to examine a related aspect: Barcode check digits depend on an institution's declared weighting and modulus scheme.

Use Negative Enclosure Number Assignment Sequencer where its separate inputs and scope apply: Negative numbering uses a collection namespace and an unused numerical range.

References

Finding Aid EAD Tag Completeness Counter — tool.io

Similar or alternative tools

Item Level Barcode Check Digit Validator
Barcode check digits depend on an institution's declared weighting and modulus scheme.
Negative Enclosure Number Assignment Sequencer
Negative numbering uses a collection namespace and an unused numerical range.